My Tumbleweed was working perfectly and was my favorite distro, with KDE Plasma.
However, things got weird since I started to use a custom script to sustpend, poweroff and reboot my system. Why did I use a custom script? I just wanted to make sure I unmounted cleanly my rclone remote (a ProtonDrive), and stopped any background sync with it. In addition to that, I started using sudo systemctl at the end because (I don’t know why, maybe I did a bad configuration job) ProtonVPN required sudo authentication to be turned off… I know it’s a very bad idea now, but at the time it seemed just like a temporary fix or shortcut.
So then suspending started to disfunction: my PC locked and froze instead of suspending.
Then one day, I had to reboot in front of a black screen telling me that the locking function was broken (or something like this, I wasn’t smart enough to take a screenshot…).
And finally… I can’t boot anything from Tumbleweed’s Grub anymore. Kernel Panics everywhere!
So now I’m stuck with my backup (gaming oriented) Fedora dual-boot, which is very painful (Gnome seems like Windows XP when you come from KDE Plasma…).
I have no idea how to debug this. I can successfully chroot my Tumbleweed from Fedora, at least we have that…
Tomorrow my computer will probably in repair (the fan’s going crazy, as if I needed any more problems), so please forgive me if I don’t answer at once to your next command. I’m not abandoning this thread, my PC will just temporarily be somewhere I can’t use it.
Thanks for the fast answer, I hope this will help.
Btw, I’m quite surprised of the output of efibootmgr, it’s the first time I see that on my PC, both hard disks have been relying on EFI so far, so I really dont understand why we get that…
Ah and just so you have the full picture, here is lsblk -f run from Fedora:
Simple question but complicated answer… I get to see logs of the ongoing boot process only under certain conditions, that unfortunately I haven’t perfectly identified so far… Most of the time I select a boot option, then the screen turns black and that’s it. At times I don’t even know if my computer has shut down or not, that’s to say how non-verbose and non-responsive it gets…
I’ll try to see what I can get from the last snapshot when I get my computer back.
To all friendly souls that want to help me on this topic, my computer is in repair for a few days (fan problem), so I won’t be able to investigate for some time.
But please don’t un-follow this topic, I’ll revive it ASAP!
From the “Kernel panic” message, from the beginning I have been inclined to think that the reason for the problem is a hardware failure, most probably temperature, which in a laptop can affect everything, such as memory, which will fail randomly or continuously depending on the constancy of the problem that causes the temperature of all components to rise. Therefore, it is possible that when you get your computer back, you will no longer have the problem.
There are ISOs with test benches that will run stress algorithms to find out if something is wrong with the equipment under certain circumstances.
Windows, in fact, is more sensitive to problems with RAM modules. I know this because I had a dual-boot computer that Windows was unable to use without blue screens, but Linux did. A stress test showed that a RAM module failed.
It would be absolutely amazing if back from repair my openSUSE problem was fixed along with the noisy fan problem! I’ll keep you updated. It is indeed true that both problems occured and worsened simultaneously…
A Windows notebook would crash whenever accessing a folder. Cleaned the fan, applied new thermal paste, replaced the HDD by a SSD and installed Xubuntu. The user is happy since six years now. She maintains the website of the local sports club.
Had a similar event happen not long ago.
I booted into the dedicated BIOS and ran the System Diagnostics selection (Advanced, detailed) - no issues showed up. Oddly enough, after shutting it off for 30 minutes, then booting back, all seems to be fine. Computers can be unpredictable, like people