Hi,
I’m trying to install OpenSuse Tumbleweed on my computer next to windows 11. After installation is complete, I can choose opensuse in the boot uefi. Grub starts, I can choose windows and opensuse, everything works fine in grub. But if I start opensuse tumbleweed, nothing happens. I see text the “Loading kernel 6.8.2…” in a small black window, after that window is blink and just black screen showing with _ in a left up corner. After few minutes reboot.
The only way to start the system is to choose safety mode in grub.
What have I tried:
Installing with KDE Plasma, secure boot enabled/disabled, update nvram enabled/disabled
Installing with Generic Desktop, secure boot disabled, update nvram disabled
I found this thread and installed ucode-intel in safety-mode, but nothing changed.
Every try I turn on/off secure boot if it was needed.
How can I fix the problem and boot into opensuse tumbleweed in normal mode?
Could you try adding the nomodeset kernel command line flag from grub menu and see if it boots? Press e to edit the menu entry and add to the end of the linux ... vmlinuz ... line.
If not, try recovery mode and view the priority 3 errors from the previous failed boot:
What does this mean? Did it automatically reboot, or did you wait a while, then force a reboot? How few minutes? Did you try longer than a few, maybe 8-10? Did you try Alt-F4 after waiting a few minutes but before rebooting? What CPU and GPU(s) do you have? Do you use more than one display? If yes, did you try with only one connected?
So, I reinstalled the entire system, choose KDE, secure boot disabled, nvram enabled and tried to start the system with nomodeset flag, but nothing has changed.
journalctl -p3 -b 1 showed me this in recovery mode:
Apr 05 22:51:34 localhost kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0xb2 (or later)
Apr 05 22:51:34 localhost kernel: RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible!
Apr 05 22:51:36 localhost kernel: nouveau 0000:01:00.0: bus: MMIO write of 80000108 FAULT at 10eb14 [ PRIVRING ]
Apr 05 19:52:03 localhost.localdomain jackdbus[2127]: default: failed to stat "/home/dedligma/.config/jack/conf.xml", error is 2 (No such file or directory)
Apr 05 19:52:03 localhost.localdomain jackdbus[2127]: default: open() failed to open conf filename.
Apr 05 20:03:36 192.168.1.3 kscreenlocker_greet[3063]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory
Apr 05 20:03:36 192.168.1.3 kscreenlocker_greet[3063]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so
Apr 05 20:03:36 192.168.1.3 kscreenlocker_greet[3063]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/security/pam_pkcs11.so: cannot open shared object file: No such file or directory
Apr 05 20:03:36 192.168.1.3 kscreenlocker_greet[3063]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so
To fix TSC_DEADLINE... I installed ucode-intel
To fix PAM errors I have installed fprintd-pam and pam_pkcs11
However, nothing has changed. After rebooting and attempting to boot the system several times, the output of journalctl -p3 -b 1 remained the same.
I read about RETBleed error, and from what I understood, it’s a hardware problem, so that’s confusing to me. But, I don’t think that my machine is not suitable
It means that my computer restarts after 1-2 minutes. It’s happening automatically, I’m not touching anything. After I choose opensuse in grub menu, the pc shows me _ and the computer doesn’t react to anything and after around 1 minute and 30 seconds, it restarts automatically.
I have 2 displays and I tried boot with only one, but that gives no effect.
The i5-6400 provides an iGPU. To which outputs are your display cables connected? Motherboard ports? GeForce port(s)? Both? In BIOS setup, what is/are your setting(s) for graphics?
This shows the first bootup before you applied any fixes/changes.
The current boot is 0, the previous one -1, the latter is what you want from recovery mode.
But still, it’s concerning that a fresh installation is missing key shared libraries. Perhaps the installation itself did not complete correctly.
Thanks to your advice, I read several logs of the latest boots and found a couple of new errors. I found some information in this thread and read about troubles with ventoy, which I used to install. So, in recovery mode I remove the parameters rdinit=/vtoy/vtoy of ventoy and that fixed everything! I can’t even imagined, that the problem was with ventoy…
Kinda funny … I thought the Solution goes to the person who provided the info for the fix, but maybe it goes to the OP who reported the issue and couldn’t solve it
But you understand that the TO found the solution himself by reading other threads? And you also understand that you can’t tag a post in another thread (which is not yours) as solution? And you also understand that the TO is free to mark whichever post he wants as solution, also that one that really contains the solution and explanation for the root cause?
I still don’t understand very well how everything works on this forum, and if you tell me what and how is right, then I will try to do it that way.
I just thought that the solution goes to the post with the instructions on how to resolve the problem, and I tried to make a post with these instructions
