On 09/09/2018 05:32 AM, Tom Horsley wrote:
On Sat, 8 Sep 2018 20:43:46 -0600
Chris Murphy wrote:
Nope. There's no firmware state information saved to disk.
There must be something on disk, because I keep reading web pages that say things like:
You can create a new image file
The bootloader "file" is on the disk, but isn't firmware state information.
and add it to the efi menu with efibootmgr
The EFI menu is firmware state information, but it's not on the disk.
That's held in non-volatile RAM.
Anyway, I think I've figured out my major problem with the USB stick testing I've been doing: The system I've been testing with apparently only claims to support UEFI, both GPT partitions and UEFI installs (even on a msdos partition) fail to work.
Only a traditional msdos partition and BIOS boot actually works.
Many UEFI systems support booting from either UEFI or "legacy" boot
loaders. Yours may have "legacy" prioritized so that it loads first, or
it may be configured to only boot "legacy" mode for external devices.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
