On Sun, Aug 30, 2015 at 7:21 AM, Paul Cartwright <pbcartwright@xxxxxxxxx> wrote:
> On 08/30/2015 08:28 AM, Tom H wrote:
>> Doesn't the firmware boot screen correspond to the output of "efibootmgr"?
> it looks that way..
> so, tell me what the difference is between Fedora, 0005, and UEFI OS:
>
> Boot0005* Fedora
> HD(8,GPT,ac2fc695-5de9-47d0-a19b-01e236404130,0x5ae5d800,0x2f800)/File(\EFI\FEDORA\shim.efi)
> Boot0009* UEFI OS
> HD(8,GPT,ac2fc695-5de9-47d0-a19b-01e236404130,0x5ae5d800,0x2f800)/File(\EFI\BOOT\BOOTX64.EFI)
>
> what is the difference between FEDORA/shim.efi and FEDORA/BOOTX64.EFI ...
\EFI\BOOT\BOOTX64.EFI is a fallback bootloader in case NVRAM gets
corrupted or wiped. In a Fedora only installation it's the same thing
as shim.efi, which also has code to create a new NVRAM entry for
itself and set the BootOrder. With a Windows installation already
present, I don't know if BOOTX64.EFI is the Windows bootloader, and I
don't know if Fedora overwrites it. You can use sha1sum on each
OSLoader to find out what matches up with BOOTX64.EFI.
>
> efibootmgr -v
> BootCurrent: 0005
> Timeout: 0 seconds
> BootOrder: 0005,0009,000C,0004,0003,0002,0010,0000,0001
> Boot0000* P0: WDC WD10EZEX-75M2NA0 BBS(17,,0x0)
> Boot0001* P4: TSSTcorp DVD+/-RW SH-216DB BBS(19,,0x0)
> Boot0002* Fedora
> HD(8,GPT,ac2fc695-5de9-47d0-a19b-01e236404130,0x5ae5d800,0x2f800)/File(\EFI\fedora\shim.efi)
> Boot0003* Windows Boot Manager
> HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...9................
> Boot0004* ubuntu
> HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\ubuntu\shimx64.efi)
> Boot0005* Fedora
> HD(8,GPT,ac2fc695-5de9-47d0-a19b-01e236404130,0x5ae5d800,0x2f800)/File(\EFI\FEDORA\shim.efi)
> Boot0009* UEFI OS
> HD(8,GPT,ac2fc695-5de9-47d0-a19b-01e236404130,0x5ae5d800,0x2f800)/File(\EFI\BOOT\BOOTX64.EFI)
> Boot000C* UEFI OS
> HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\BOOT\BOOTX64.EFI)
> Boot0010* ubuntu
> HD(1,GPT,4cc2fdac-58ea-400c-8ef9-11e13499addf,0x800,0xfa000)/File(\EFI\Ubuntu\grubx64.efi)
You have superfluous boot entries. That's why your F12 firmware boot
manager lists extras. Boot0002 and Boot0005 look identical, if so,
delete one of them with e.g. 'efibootmgr -B -b 0005'
--
Chris Murphy
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
