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

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

 



On Jan 1, 2014, at 12:11 PM, Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote:
> 
> I got the same with efibootmgr -v:
> 
> BootCurrent: 0005
> Timeout: 0 seconds
> BootOrder: 0005,0006,0007,0008,0009
> Boot0000  Setup
> Boot0001  Boot Menu
> Boot0002  Diagnostic Splash Screen
> Boot0003  Rescue and Recovery
> Boot0004  Startup Interrupt Menu
> Boot0005* USB CD 030a2400d23878bc820f604d8316c068ee79d25b86701296aa5a7848b66cd49dd3ba6a55
> Boot0006* USB FDD 030a2400d23878bc820f604d8316c068ee79d25b6ff015a28830b543a8b8641009461e49
> Boot0007* ATA HDD0 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f600
> Boot0008* USB HDD 030a2400d23878bc820f604d8316c068ee79d25b33e821aaaf33bc4789bd419f88c50803
> Boot0009* PCI LAN 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803

Seems like a lot of entries aren't actually pointing to anything.

>> 
>> efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \\EFI\\fedora\\shim.efi
>> 
>> And see if you get an error; and you can also reissue efibootmgr -v to see if that entry is now in NVRAM to confirm.
> 
> No errors and no change to NVRAM.

Any new messages in dmesg at the time you issued the efibootmgr command?


>  Rebooted and tried again.  Same thing.  Ran out of time for right now to try  an install even though I cannot add to the boot list with this command.  I may try later tonight.  Or let me know what to try next.
> 
> Oh,  Here is my system info:
> 
> 
> Lenovo x120e
> UEIF Bios ver        8FET32WW (1.16) (date 2011-11-03)
> Embedde Ctlr Ver    8FHT21WW (1.09)
> Mach Type            0611AH9

Check their site for firmware updates, maybe even check the change log to see if it fixes anything significant or related before bothering with doing it.


> 
> 
> 
>> If there's no error, and if the entry is present in NVRAM, remove it with efibootmgr -b xxxx -B. Then try to install Fedora 20 again and hopefully this time it takes.
>> 
> 
> Now what?  Other than try install again as is.

That's not going to change anything. If the efibootmgr -c -w L etc command doesn't produce any errors and also doesn't write anything to NVRAM I'm not sure what's next which is why I think it still needs a kernel bug report.

Chris Murphy
-- 
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