On Sun, 19 Mar 2023 04:28:02 +0100
"Carlos E. R."
On 2023-03-19 02:25, Neil Rickert wrote:
Your UEFI BIOS probably did that.
No.
Then it would happened every day for years. It started to happen today, after an openSUSE update.
Perhaps it did happen every time, but you didn't notice. When that happens, "fallback.efi" is supposed to kick in to fix it. And you might not have noticed that this was going on. May I suggest that you disable secure-boot in your BIOS until you get this working. OpenSUSE 15.2 uses secure-boot signature from the openSUSE CA, while 15.3 and 15.4 use signatures from the SUSE CA. So there could be an incompatibility there. This is supposed to be handled by enrolling a certificate. But that may have failed because you did not have "MokManager.efi" in the directory used for our Boot0003.
Telcontar:~ # l /boot/efi/EFI/main-os/ total 3176 drwxr-xr-x 2 root root 8192 Aug 10 2020 ./ drwxr-xr-x 5 root root 8192 Aug 10 2020 ../ -rwxr-xr-x 1 root root 846240 Mar 18 21:45 MokManager.efi* -rwxr-xr-x 1 root root 56 Mar 18 21:45 boot.csv* -rwxr-xr-x 1 root root 120 Mar 18 21:45 grub.cfg* -rwxr-xr-x 1 root root 1275904 Mar 18 21:45 grub.efi* -rwxr-xr-x 1 root root 143360 Mar 18 21:45 grubx64.efi* -rwxr-xr-x 1 root root 934680 Mar 18 21:45 shim.efi*
Those are likely to be okay.
This are the "UEFI OS" files;
Telcontar:~ # l /boot/efi/EFI/boot/ total 1552 drwxr-xr-x 2 root root 8192 Aug 10 2020 ./ drwxr-xr-x 5 root root 8192 Aug 10 2020 ../ -rwxr-xr-x 1 root root 1208968 Aug 10 2020 bootx64.efi* -rwxr-xr-x 1 root root 358768 Aug 10 2020 fallback.efi* Telcontar:~ #
Those probably come from 15.2 (based on the dates). I am seeing: # ls -l total 1832 -rwxr-xr-x 1 root root 934680 Dec 10 2021 bootx64.efi -rwxr-xr-x 1 root root 86352 Dec 10 2021 fallback.efi -rwxr-xr-x 1 root root 846240 Dec 10 2021 MokManager.efi Those look old. But they are identical with the files from 15.4, as verified using "md5sum". The "bootx64.efi" is identical with the "shim.efi" from 15.4. And you can find "fallback.efi" at "/usr/share/efi/x86_64/fallback.efi". I suggest you manually fix those files. And be consistent. Either they should all come from 15.2 or they should all come from 15.4. Mixing doesn't work. I have a Lenovo system (not my main desktop) which always wants to control the boot order. I can change the boot order with "efibootmgr" but it reverts on the next boot. But the BIOS settings do allow changing the boot order that the BIOS wants. You might have something similar happening. If your 15.4 system happens to have kernel "5.14.21-150400.24.49" and if it uses Intel graphics, then it might not boot. However kernel "5.14.21-150400.24.46" should boot fine.