Title: Problem with Linux System After Update (Arch-based) and After Installing Solus

Hello,

I am a new user of Solus. This is my first post on the forum, I am Polish, and I don’t write in English. Chat GPT is helping me with translations. I greet you all warmly and I hope to stay with you here for a long time. Please be understanding in case of any misunderstandings, and treat my threads as informational.

I’ve been having an issue with my Linux system since mid-December, after I performed an update. At the time, my system was based on Arch. After the update, I tried to roll back some critical packages, including the kernel, Mesa, etc., but I was unable to stabilize the system. Unfortunately, I forgot to create snapshots, and that would have solved the problem.

After a while, I reinstalled the system, but unfortunately, without success. I had some time, so I had the option of either going back to Manjaro or installing Solus, which suited me in some aspects. I chose to install Solus. It’s a great system, and I like many of the solutions it offers. Unfortunately, the system is still unstable.

What’s happening? The system crashes at random moments, everything freezes, and the only way to recover is by using SysRQ. This happens while watching videos on YouTube, and interestingly, it crashes faster when I use Brave. I encounter this problem less frequently on Firefox.

It seems like a problem that occurs in many distributions. For now, I’ll wait it out, hoping that the problem will be resolved and that with one of the upcoming updates, everything will be fine.

I also have a question for you: Is there a way to roll back updates in Solus? I tried not updating after the installation from the disk, but the installation of MC pulled in a whole bunch of packages (around 200), and the system broke. Is there a way to roll back already installed packages in Solus to make it work? Or is this problem only happening to me?

I’m using open-source drivers for AMD.

Best regards!

There are some issue with AMD systems on linux, I fight with freez since i buy my Ryzen laptop 5 years ago.
Probably your issue is due to mesa, so it is present on every linux OS you will try
You can see this
https://discuss.getsol.us/d/11235-random-freezes-after-last-update-possibly-amdgpu
On arch I have freez only using Hypnotix that is a TV streaming on pc, in Solus I have freez even browsing with firefox. For my old hardware abandoned by the produser is a mix of things as no BIOS update, microcode that AMD does't procude for older cpu and some issue with mesa too.
If your hw is recent so probably is only a mesa issue and you have to wait untill mesa solve it, if they solve it...

I found the "GLOBAL-C STATE CONTROL" option in my BIOS and disabled it. Now I'm checking if this will solve the issue on my hardware. I also have a better understanding of what causes these freezes.

Thank you for the links and your response. I’ll be following those discussions.

Warm regards!

ps. It didn't help. The system still freezes.

in your case is the MESA issue, so reactive C-STATE on your BIOS (so you can benefit some energy efficient setting) and if you are using Wayland (I don't know what DE are using on Solus but if is KDE probably you are using wayland) then when you insert your password there is a Wayland/X11 choice, try use X11 instead. in X11 you loose gesture in FF ,so swipe using touchpad or mouse to go back is lost, but probably freez are not vanished but less frequent. Untill a mesa update solve issue on AMD GPU there is not a solution.

UPDATE: in last update there is a Mesa update too, cersion 24.3.3
https://docs.mesa3d.org/relnotes/24.3.3.html#bug-fixes
Looking at the changelog seem nothing good for AMDGPU but you can try if this update solve your issue.

I enabled C-STATE in the BIOS when I realized it didn't help. On Solus, I use the Budgie desktop environment. I haven't eliminated the freezes, but I've learned to live with it. I don't use the Brave browser, and I watch YouTube videos in 480p resolution. It seems to work reasonably well, I think. Maybe the Mesa update to version 24.3.3 fixed something. We'll see how it goes.

Thanks, best regards!