Re: [Bug 1006304] BootLoaderError: failed to set new efi boot target

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 01/03/2014 02:27 PM, Adam Williamson wrote:
On Fri, 2014-01-03 at 14:23 -0500, Robert Moskowitz wrote:

(disclaimer: never trust the monkey, I know a bit more about UEFI than
the average monkey but not everything.)
So why is the install failing?
We don't know yet, but Chris is on the right track looking into it.

When we had the big problem with nvram exhaustion a couple of releases
back, it became apparent that some firmwares are very bad at freeing
nvram space. Just deleting an entry via efibootmgr does not in itself
physically empty that area of the nvram; the firmware has to do 'garbage
collection' before that happens, and some firmwares seem to be very
reluctant to do it. it seems like sometimes there has to be a certain
threshold of garbage to be collected before it happens, or it won't
happen until you reboot five times, or other silly things like that.
it's one of those things that's difficult to debug from afar, though :/
Just did a test and it failed.  :(

I updated the firmware. Rebooted twice. Did NOT go into Bios setup. Booted the f20 x86_64 netinstal CD and it failed at the same point. I copied all the logs and will upload them to bug 1047993.

I rebooted with the f20 x86_64 LiveDVD, the efibootmgr -v showed no changes to the boot list; LAN is still removed. Did the steps that Chris requested and I doubt you will see anything in the dmesg reports which I will upload to 1047993.

Is there anyway to install x86_64 without efi? I seem to recall some Bios settings about legacy efi?


--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test





[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux