On Tue, 24 Sep 2019 09:31:08 +1000, Adam Carter wrote: > > 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.
I recently updated a firmware and all worked as before, so I think this is implementation-dependent. > # 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. I've just checked a couple of systems that have never used MBR and they say the same. I'd ignore that. -- Neil Bothwick If at first you don't succeed, you'll get a lot of free advice from folks who didn't succeed either.
pgpmYfKbvL8og.pgp
Description: OpenPGP digital signature
