Some testing today from f20 live x86_64 DVD
On 12/31/2013 08:00 PM, Chris Murphy wrote:
On Dec 31, 2013, at 5:34 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:
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.
Confirmed. Sorta.
The program.log info is buried in the anaconta-tb, so looking at that I see you have a bunch of NVRAM entries you probably don't need:
17:08:21,590 INFO program: BootOrder: 0005,0006,0007,0008,0009
17:08:21,590 INFO program: Boot0000 Setup
17:08:21,591 INFO program: Boot0001 Boot Menu
17:08:21,591 INFO program: Boot0002 Diagnostic Splash Screen
17:08:21,592 INFO program: Boot0003 Rescue and Recovery
17:08:21,593 INFO program: Boot0004 Startup Interrupt Menu
17:08:21,594 INFO program: Boot0005* USB CD
17:08:21,595 INFO program: Boot0006* USB FDD
17:08:21,596 INFO program: Boot0007* ATA HDD0
17:08:21,596 INFO program: Boot0008* USB HDD
17:08:21,597 INFO program: Boot0009* PCI LAN
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
I tried deleting #9. A couple times. Turns out boot on LAN was #1
priority, and KVM support was disabled (caught that in the boot
messages). So I changed boot to USB CD as #1, then I was able to delete
#9 and remove it from the boot order with:
efibootmgr -o 0005,0006,0007,0008
Thing is, I can't tell you want you can get rid of. If you efibootmgr -v it will give their verbose listings and in theory you can replace them based on that information, should they need to be replaced. Better would be a firmware setup option to reset NVRAM but that seems rare outside of Apple hardware.
Pick one that seems unlikely to be used ever again for deletion, after you issue and save the results from efibootmgr -v, and then use the form:
efibootmgr -b 000x -B
Where x is the entry you want to remove. That will delete that entry. Open question how many of these you need to delete to release enough space in NVRAM, one or two? And another question on how long it takes for the firmware to go garbage collection and actually make space available in NVRAM for a new entry.
Next, try:
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. 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
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.
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
