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

[Robert Moskowitz]

On 01/05/2014 04:04 PM, Chris Murphy wrote:
> On Jan 5, 2014, at 1:33 PM, Robert Moskowitz <rgm at htt-consult.com> wrote:
>> 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?
> Remind me, this is dualboot Windows and Fedora on this computer both on one drive? Or just Fedora?

Just Fedora.  That is all I run on this system.  And the drive is a 
brand new SSD that I have partitioned with EXT4, no LVM.

>
> If it's just Fedora, it ought to still boot even with the failed NVRAM entry because the firmware should find bootx64.efi and use that, which I think is a copy of grubx64.efi.

I will try and boot from the drive.  I never tried that.

> If you must have dual boot, I think you're going to have to abandon grub and look at rEFInd which can boot both Windows and Fedora without grub, and without NVRAM dependency.
>
> Another possibility, is to "disable UEFI" which is a bad way of saying "enable BIOS compatibility". But in that case, Windows must be reinstalled because in BIOS mode it only boots from MBR drives, and in UEFI mode it only boots from GPT drives.
No Windows need apply on this unit.  I have my Corp computer for that.  
I would gladly disable UEFI if that will get me x86_64 installed.  But 
first I will try booting whatever did get installed.