I just installed Leap 15.3 on one of my compters and afterwards it can’t boot. It is just stuck at a black screen with the Dell logo. I can boot if I use the USB key I installed from and just select the boot from disk option. So I think something is not working right with UEFI or something. I don’t know a whole lot about UEFI as this is the first computer I’ve used it on. Lol.
I tried reinstalling several times. Tried with and without Secure Boot. But it just won’t boot like it should.
A little history on this computer. It originally had Leap 15.1. Then it had Ubuntu 20.04. I decided to switch back over to Leap now that 15.3 is out and that is when I ran into the problem.
As for the install, Only thing I change is that I set disk encryption and lvm and I do that through the guided setup. So it’s a default install.
Now I’m stuck and don’t know what else to do. Any ideas how I can get it to boot or even just figure out what is wrong?
This looks right to me. It says the “opensuse-secureboot” is the first one. I do have secure boot enabled this time so that should be right. Although, one thing that is odd here is that when I look at the boot order in the BIOS setup it doesn’t show the SanDisk stuff.
I decided I would just delete everything in there. I did that using “efibootmgr -B -b ####”. Then I went into Yast Boot Loader and clicked save. I checked and it then only had the opensuse-secureboot option in there after doing that. But it still just gets stuck at the Dell screen with no messages. I can consistently boot from the USB though so that’s good. Lol.
After all that I’m right back where I was but now it looks like this. What else should I check?
I secure boot enabled as that’s what it’s trying to use? Boot from USB and boot the system and in YaST bootloader uncheck the secure boot box, check that’s it’s added the ‘opensuse’ efi entry in the efibootmgr output and it’s set to default.
and try booting without the USB to see if that now works.
I’ll explain what this is doing.
The file “bootx64.efi” on the USB is really “shim.efi”, but renamed to make the USB bootable. You are successfully booting with that when you boot using the USB. But your installed system probably has a slightly newer “shim.efi” and perhaps that isn’t working.
By doing that copy, you are testing whether you can boot with the original “shim.efi” from the install media.
Note that if this works, it is only a temporary fix. It will break again in the future. The point is to test whether this is the problem. I seem to recall that there is a bug report where some BIOS don’t like the newest “shim.efi”.
Hi, I’m having the same problem. Just loaded (upgrade) Leap 15.3 from DVD iso.
Upgrade goes fine then it wants to reboot and when doing so from hard disk(SSD)
it posts ok then black screen.
It appears that 15.2 is still there too:
Start boot loader from read only snapshot
*openSuse Leap 15.3 (5.3.18-150300.59.43,2022-01-28T02:17.post,afterupdate
*openSuse Leap 15.2 (…etc…,pre,beforeupdate
open Suse… older etc.
When selectin 15.3 it starts booting but then returns a black screen
When selecting 15.2 it actually boots up Ok , although I have not tried running anything
except firefox (which in the Help drop down shows it to be for Leap 15.2 )
As root I tried # efibootmgr -v
EFI variables are not supported on this system.
uname -a produces
[FONT=monospace]Linux x1-6-f4-6d-04-0f-40-b1 5.3.18-lp152.106-default #1 SMP Mon Nov 22 08:38:17 UTC 2021
(52078fe) x86_64 x86_64 x86_64 GNU/Linux
Everything seems to be the same as prior to the update so I guess I am
running a snapshot of the old system?
A quick check in /boot/grub2/
shows that i386-pc folder contains files written around the time of update.
If you have any suggestion for what to try, or would like me to show more info
please let me know.
There are multiple other threads here about this. It happens to everyone using an older AMD/ATI GPU. The 59.43 kernel has a bad radeon kernel module. You need the next kernel, or an older kernel, or the radeon module from the previous kernel. Instructions for this can be found here.
Please don’t hijack an old thread with a new problem, even if it sounds like the same thing. Much changes in a year. Black screens have had many and varied causes.