You are not logged in.
The out but is as follows:
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0004,0000,2001
Boot0000* EFI HDD Device (M4-CT128M4SSD3) ACPI(a0341d0,0)PCI(1f,2)03120a00000000000000HD(1,800,100000,2a87baae-320c-43f0-81c1-09db46487eb4)RC
Boot0001* EFI Network 0 for IPv4 (28-D2-44-07-2C-E4) ACPI(a0341d0,0)PCI(1c,0)PCI(0,0)MAC(28d244072ce4,0)IPv4(0.0.0.0:0<->0.0.0.0:0,0, 0RC
Boot0002* EFI Network 0 for IPv6 (28-D2-44-07-2C-E4) ACPI(a0341d0,0)PCI(1c,0)PCI(0,0)MAC(28d244072ce4,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000RC
Boot0004* Linux Boot Manager HD(1,800,100000,2a87baae-320c-43f0-81c1-09db46487eb4)File(\EFI\gummiboot\gummibootx64.efi)
Boot2001* EFI USB Device RCMost of the entries are either self explanatory or of no concern, but regarding entries 0000 and 0004, I'm pretty confused.
They both seem to launch GummiBoot, yet they're seem pretty different. I'm especially concerned with the ACPI part.
I suspect that 0000 was added automatically by GummiBoot and I then added 0004 manually using efibootmgr, because I didn't think the first entry had been added.
There is no observable difference, but I'd like to be sure.
Thanks and best regards.
Last edited by zacariaz (2013-08-23 22:30:43)
I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.
Offline
Your Boot0000 was probably added by your firmware, and it probably launches EFI/BOOT/bootx64.efi. That filename doesn't appear in the efibootmgr output, but it's the fallback boot loader filename for x86-64 systems -- that is, it's the boot loader that's launched if nothing else works. Some EFIs create an explicit entry for this boot loader that appears in efibootmgr's output.
Your Boot0000 and Boot0004 entries presumably both launch gummiboot because gummiboot is probably installed twice, once as EFI/gummiboot/gummibootx64.efi and once as EFI/BOOT/bootx64.efi. IIRC, the Arch gummiboot package sets the boot loader up this way. (This sort of thing is common because many problems can result in the NVRAM entries being wiped or ignored, leading to the system being unbootable if EFI/BOOT/bootx64.efi doesn't exist. Thus, putting something there helps keep the computer bootable in the event of such problems.)
Offline
Well, as long as it doesn't make a difference which entry is being used, I'm perfectly happy with that explanation.
Thank you very much.
I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.
Offline