On Tue, 2013-12-31 at 20:23 -0500, Robert Moskowitz wrote:
On 12/31/2013 08:00 PM, Chris Murphy wrote:
> On Dec 31, 2013, at 5:34 PM, Chris Murphy <lists(a)colorremedies.com> 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
Oh, lots more information. I will try all of this tomorrow. I really
need to get busy in the honeydo patch now... ;)
So, this is basically just a boot menu. If it were me I'd probably drop
entry #9, unless you have any intention to do a UEFI native boot via LAN
later.
With efibootmgr you can list out the actual contents of each entry and
save it somewhere, so you could re-create any entry you delete later.
And as long as you make sure you can still get into the firmware
interface, a factory reset of the firmware should restore the default
efi boot manager list, I *think*.
(disclaimer: never trust the monkey, I know a bit more about UEFI than
the average monkey but not everything.)
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net