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

[Robert Moskowitz]

On 12/31/2013 07:34 PM, Chris Murphy wrote:
> On Dec 31, 2013, at 5:27 PM, Robert Moskowitz <rgm at htt-consult.com> wrote:
>
>> On 12/31/2013 07:18 PM, Chris Murphy wrote:
>>> On Dec 31, 2013, at 4:39 PM, Robert Moskowitz <rgm at htt-consult.com> wrote:
>>>
>>>> On 12/31/2013 05:00 PM, bugzilla at redhat.com wrote:
>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1006304
>>>>> In additional info, include computer model and firmware revision. And then
>>>>> attach your program.log, anaconda-tb, and syslog.
>>>> How can I find out my firmware revision without rebooting into bios setup?  Seems there is a command somewhere that shows this…
>>> No, this is something that I'd expect only the firmware will show you somewhere in its setup menu.
>>>
>>>>> Also include as attachments the current results of:
>>>>> efibootmgr -v > efibootmgr.txt
>>>>> ls /sys/firmware/efi/efivars/ > efivars.txt
>>>> I am currently running f20 i386  on this system (my Lenovo x120e). My f17 x86_64 drive got hosed and won't boot.  So how am I suppose to get these outputs?
>>> Boot any x86_64 Fedora media in EFI mode (not CSM-BIOS mode - this is a setting in your firmware, sometimes irritatingly called "disable UEFI" when the CSM is being used). If it's not a livecd, like netinst or dvd, you can ctrl-alt-f2 to get to a shell, and issue those commands. And hardwire ethernet typically works from all media out of the box without configuration so you can either fpaste them (save the URLs!) or you can scp them to another computer or stick them on a USB stick.
>> I am downloading the f20 x86_64 live iso right now; and it looks like a liveDVD, not liveCD by its size.  I will run all of this tomorrow (My new years Holiday was some 3 months ago :) ).
> Based on a google search it sounds like this Lenovo model may be getting tagged as a model with a problem if NVRAM is more than 50% full, and so efibootmgr refuses to write to it anymore. I still don't know why we don't get more information from dmesg when there's a fail though.
>
> Since you only have Fedora to boot, the simplest fix might be to delete all of the NVRAM entries, and hope that in a reboot or two, it does sufficient garbage collection that you can then try another installation.

I was going to ask you how to clean this up, but did a bit more google 
searching, and perhaps my search foo was strong enough:

http://forums.fedoraforum.org/showthread.php?t=295390

Right up about this bug.

So I still have to learn a bit about nvram and what to delete not to 
brick my system.  Perhaps that also ties into the USB and audio problems 
I am having...

I have built a USB drive as recommended at: 
https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface#bcfg

Once I take a look, perhaps your comment about 'all of the NVRAM 
entries' will make sense.