Hi everyone,
I have been using opensuse for a long time, and I consider it very solid in terms of updates, but unfortunately today after having done the kernel security update and other updates, unfortunately grub doesn’t work, it gives me an error and won’t let me log in, so I rolled back in the last snapshot.
Unfortunately I’m not very good with the terminal, but if there’s anyone who can tell me what to do I’d be very grateful.
I use opensuse 15.5
I ran efibootmgr -v and it returned me this
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,2001,3002,0000,0001,2002,2004
Boot0000* openSUSE HD(1,GPT,0bb932bd-c2fe-4651-88cf-91f2ca728a92,0x800,0x82000)/File(\EFI\opensuse\grubx64.efi)RC
Boot0001* Windows Boot Manager HD(1,GPT,0bb932bd-c2fe-4651-88cf-91f2ca728a92,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS…x…B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}…
Boot0002* opensuse-secureboot HD(1,GPT,0bb932bd-c2fe-4651-88cf-91f2ca728a92,0x800,0x82000)/File(\EFI\opensuse\shim.efi)
Boot2001* EFI USB Device RC
Boot3002* Internal Hard Disk or Solid State Disk RC
Kinda lack of more info.
Try go to your bios and look for the opensuse EFI and use it to boot.
I had a weired almost like this on my SSD connected to the USB port
I was able to boot it from bios and use the opensuse EFI.
When you able to boot, you can run the yast2 bootloader to fix the loader.
Yap, go to the bios and look for opensuse EFI boot there’s EFI or grub2 try each one which one will take you to boot. Don’t forget to run the yast2-bootloader to update your grub it will take care also of doing the mkinitrd.
You are using kernel 6.6.6, which is not a standard kernel for Leap 15.5.
I’m guessing that you installed from the “Kernel:/stable:/Backport/standard/” repo. In this case, you should have seen a blue screen on boot. That was asking whether you wanted to enroll the signing key used for that kernel. If you don’t do that, you will get that “bad shim signature” message.
You should be able to boot to a previous kernel. Use the “Advanced options” entry in the grub menu, and then select an older kernel. That should get you into your system.
Once in, you can try again to enroll that key. The key itself should be in “/etc/uefi/certs”. You can probably tell which key it is based on having a recent date for the file.
Thank you very much nrickert I followed your advice
Blockquote
You should be able to boot to a previous kernel. Use the “Advanced options” entry in the grub menu, and then select an older kernel. That should get you into your system.
Once in, you can try again to enroll that key. The key itself should be in “/etc/uefi/certs”. You can probably tell which key it is based on having a recent date for the file.
For a while, I was doing that here (also with Leap 15.5). But if you do that, then if a blue MokManager screen shows up on the next boot, you will need to enroll that key. Use the root password when asked for a password with the enroll. If you fail to enroll the key, you are likely to see that “invalid signature” message on boot.
You might not get the blue screen, if the needed key is already enrolled.
