Comment 3 for bug 1876733

Had some time to try to reinstall Grub and Boot files today with the assistance of Boot Repair as a guide, but following the Grub directions in Ubuntu on the terminal (not Boot Repair).

When using Boot Repair Advanced Menu (After program launch and probe for setup) I noticed on my system that the program is interpreting my Bios (Insyde EFI) as a valid UEFI BIOS when it is not. The dmicode utility shows its name as "EFI" but the system as a standard (Old School) MBR and BIOS. In the BIOS Menu, there is no mention of Secure Boot, TPM, UEFI vs. Legacy, etc.

Using Grub in MBR/BIOS mode, and turning off Secure Boot and EFI settings in Grub using Boot Repair as a guide (but following the directions in Ubuntu/Grub ONLY) I directed the Grub to install itself back on sda, and to include all relative locations (sda1-vfat-boot, sda5-extended-ext4-ubuntu20.04LTS)where grub may be needed to boot.

After reload, grub determined, based on BIOS/MBR settings that the sda1-vfat partition did not need a copy of Grub (even though the directions in Ubuntu said to be safe and select all partitions that may boot Grub) and placed all the boot data into sda5 where Ubuntu lives on the hard drive. I verified the sda1 partition in sudo file manager level. No files were loaded on the vfat (sda1) at all, but I am sure that Grub knows it is there now.

So to be clear, I had to direct Grub to NOT USE UEFI/Secure Boot. It sees the name of the BIOS as Insyde EFI and thinks it is UEFI. Wrong Answer. Everything is OK now. I guess I could load Windows 10 but my hardware is not really ready for Win10 2004, so I am not really thrilled with the new OS upgrade from MS. (So we are clear, I do not like TPM, Secure Boot is eh, OK, but can be difficult to manage, and if chip-independent device, you can easily brick your device chip by playing around with it, even the OEM has to be careful, so God help us users. No tools to manage=don't mess with it!