Linux @lemmy.ml SuperSpruce @lemmy.zip 1 yr. ago

Super weird error, what's happening?

I'm not sure if this is the best community to post in, but I just bought a used computer and slotted in an RX480 as the GPU. I installed KDE Neon 5.27 on it, and it worked flawlessly for 2 days.

Then, even though it was working earlier today, it slept and then would not wake up. So I turned off the power and turned it back on again, and was greeted with this error screen:

The only prior error message I'd gotten from the system was when I tried to install wine for one application, it told me some packages weren't up to date, without a way to fix it. I can enter the BIOS just fine.

What is going on? How do I fix this?

36 comments

None of what's visible helps identifying the error. Try journalctl -xb as suggested it might show more relevant information

Edit: oops should've been joirnalctl instead of journal
- I tried to do that, and it couldn't find the journal package. So I tried to install it, but apt, flatpak, nor snap could find the package to install.
  
  This was probably supposed to say "journalctl -xb"
  
  Read the error again. It's journalctl.
- See. Stuff like that is why i started going non-Systemd.
  
  You're welcome to use whatever init system you want, but Systemd solves a lot of the bullshit problems and limitations that come from init.d init scripts. Systemd also has a lot of its own bullshit and bloat, but it does an excellent job at actually being an init system and service manager if you know how to properly use it.
  
  I doubt other init systems can make the screen bigger so that the vital part of the kernel log is still on screen, but be my guest to prove me wrong 🙄
Shit's broke yo.

Sleep/wake issues with AMD gpu and platform drivers are super, super, super common. Fish back through your kernel journal after a reboot (journalctl -kb -1 should do it) and look for the driver errors immediately after the wake event. If this has been fixed in a later kernel release then update your kernel, if not go report it to either the Ubuntu folks or on the amdgpu gitlab.
Can you remove the GPU and use onboard?

It is mentioning gpu in the errors, so it would be the first thing I would try, to see if the errors change, because I have no idea what's going on here
- The computer is running a Ryzen 9 3900X, which does not have onboard graphics unfortunately.
That monitor just keeps going
Have you tried booting in with a live usb? You might be able to do some sort of recovery from there.

Having said, I’m still very much a Linux noob.
Can you please post the output of journalctl -xb
Before doing anything, if your screen allows it, swap DP to HDMI or HDMI to DP as output, that may fix this to the point of being able to actually boot and further fix the issue.

I've had this before with drivers where suddenly it would fail on either port but would still run on one of the others.
Try updating your DM / your entire system from the emergency mode.
- How do I get into emergency mode?
  
  The Shell where you typed "systemctl reboot" and "exit".
  
  If you are running KDE neon, try "apt update" and "apt upgrade". If It doesn't work do "sudo apt update" and "sudo apt upgrade"
Read the messages on the screen. It's telling you how to check the logs for the error

You've viewed 36 comments.