> > > Looks like the setting gets cleared with every BIOS update. I assume this > > is due to shitty coding by the MB manufacturer and not a limitation of > UEFI. > > An update of the firmware flashes the UEFI EEPROM and as far as I have > experienced no settings are retained.
A backward step from older MBR / BIOS functionality then. I guess that indicates that code and configuration are not separated. > A fresh probe of MoBo devices at first boot re-lists anything bootable. > Do you find that the re-generated list only finds devices, not the .efi files on those devices? (and therefore efibootmgr is still required?) > Desktop/workstation UEFI firmware have more features, which allow tweaking > boot lists. Some also offer a back up/restore facility for settings from > a > file. > > Laptop UEFI boot menus are more sparce, in which case efibootmgr, or with > systemd-boot the bootctl command allow managing UEFI boot entries. I > believe > MSWindows have their own applications to do the same. > Ok thanks for the info. > Regarding the message "GUID partition table header signature is wrong", > this > is probably indicative of an MBR partition table - but I'm not sure. Have > you > installed some OS on an MBR partition schema? > # gdisk -l /dev/nvme0n1 GPT fdisk (gdisk) version 1.0.4 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present <snip> Number Start (sector) End (sector) Size Code Name 1 2048 1955839 954.0 MiB EF00 boot 2 1955840 976771071 464.8 GiB 8300 root Not sure where the 'MBR: protective' came from as the system has been linux only from the start. I guess its either the default or I made an error during the build. AFAIK this is still a valid configuration, so I assume the signature message is not related to that. I guess i could just try re-writing the partition table to see if that clears it.
