On Sunday, August 9, 2020 9:46 AM, DennisG <dwgallien@gmail.com> wrote:
On 8/7/20 7:24 PM, ken wrote:
and what the last update did:
efibootmgr -v
==============
BootCurrent: 0002 Timeout: 0 seconds BootOrder: 0003,3003,0000,0002,0000,2001,2002,2004 Boot0000* openSUSE HD(1,GPT,41ed6387-b441-4000-bc82-0d855e43c971,0x800,0x1e000)/File(\EFI\opensuse\grubx64.efi)RC Boot0001* openSUSE HD(8,GPT,45f7b14b-05f5-433d-b01d-17c097200179,0x1e800,0x64000)/File(\EFI\opensuse\grubx64.efi)RC Boot0002* opensuse-secureboot HD(8,GPT,45f7b14b-05f5-433d-b01d-17c097200179,0x1e800,0x64000)/File(\EFI\opensuse\shim.efi) Boot0003* CentOS Linux HD(1,GPT,41ed6387-b441-4000-bc82-0d855e43c971,0x800,0x1e000)/File(\EFI\centos\shim.efi) Boot2001* EFI USB Device RC Boot2002* EFI DVD/CDROM RC Boot3003* Internal Hard Disk or Solid State Disk RC Note that somehow my previous distro's (CentOS's) entry remained through three opensuse installs and two updates! Note also that CentOS (which is long gone) is the first item in the boot order! Note too that the last specification in the boot order points to a line which doesn't exist! There's other nonsense here, but I'm already belaboring my point.
I no expert in this area, but I suspect the problem is with the CentOS shim installed on the hd1 disk, which is apparently configured as the boot disk. Shim is boot stage1 code used with UEFI and Secure Boot. It contains a certificate signed by the distro that links to the signed grub that gets installed, so the CentOS shim will be incompatible with openSUSE (or any other distro). Either that needs to replaced or Secure Boot must be disabled. I don't think a distro will automatically over-write another distro's signed shim, but the third link below shows how to reinstall the shim so that might over-write the CentOS shim on hd1. YaST Bootloader detects Secure Boot and can install shim and a signed grub accordingly, or it can disable Secure Boot. If this area is unfamiliar, suggest reading up on it before trying anything or you may bork your system.
https://en.opensuse.org/openSUSE:UEFI
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.ref...
https://doc.opensuse.org/documentation/leap/reference/html/book-opensuse-ref...
https://forums.opensuse.org/showthread.php/528400-Repair-a-broken-UEFI-GRUB2...
Finally, you need to be certain that hd1 is your preferred boot disk and matches your bios setup, looks like you have opensuse installed on hd8 with Secure Boot. Or change the boot partition to be whatever hd8 is? At present your machine is trying to boot from hd1 that will never work as it is. When grub is installed it creates its a device.map on the fly which tries (guesses) to map to the boot order defined in bios; you can manually create a device.map to specify this to ensure it will be correctly done. Or in YaST Bootloader you can also define the boot order and it will use that for device.map.
I doubt Secure Boot has anything to do with this. An unfortunate side effect of UEFI allowing multiple bootloaders to be installed is that old bootloaders are left on the ESP even after their OS's are uninstalled. Installing another version of openSUSE will (by default) overwrite the folder for the openSUSE bootlader, but will not (and should not!) touch any other folder. To get rid of this entry, you simply have to remove CentOS' folder, which is probably at something like EFI/centos on the ESP (on openSUSE, the ESP is mounted at /boot/efi.) -- Daniel Stevenson -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org