On 08/30/2015 10:18 AM, Paul Cartwright wrote:
On 08/30/2015 12:17 PM, Gordon Messmer wrote:
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)
0005 & 0009 are both fedora.. same UUID, hd(8..
Both of those entries identify a boot loader located on the same
partition. Everything before "/File" is part of the device path.
how do you boot different files shim vs bootx64..
I'm not sure how to make that more clear than it is. You have a FAT32
filesystem which contains many files. One of them is
\EFI\Fedora\shim.efi, which verifies and loads grubx64.efi. The other
file is \EFI\BOOT\BOOTx64.EFI.
When you select a boot option from the UEFI menu, or as a result of
searching the list for a valid boot loader, the firmware will load the
file into memory and begin execution of whatever code is in that file.
--
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
