I’ve been having issues with my PC not waking from sleep, the fan keeps spinning, but the screen stays black, and it won’t respond. I could just keep it on all the time, but it uses a lot of electricity, so I prefer not to.
So far I’ve tried:
- Using Wayland / X11
- Secure boot off/on
- Installing the latest BIOS update
- Waking with keyboard presses, mouse movement, power button
Some more information:
- Sleeps works fine on Windows.
- I’m using an AMD CPU & GPU
- I’m using OpenSUSE Tumbleweed, and I’m fully up-to-date (version 20240919).
- I’m using kernel 6.10.9-1-default (64-bit)
- I have a swap partition with the same size as my memory
Do you have a swap partition? If not try disabling hibernation.
Yes, I do have a swap partition with the same size as my RAM
did you try switching to text mode tty console using Ctrl-Alt-F3 or -F4 or -F1 or so? if that works, maybe switching back helps. if switching back doesn’t help, you can at least investigate the logs/journals with text mode.
Yeah, I’d certainly try to see if it’s a graphical issue or actually locking up.
You can also try toggling num/caps/scroll lock to see if the keyboard LEDs respond. That’s a core kernel function, so if even that isn’t working, it’s really locked up. (Or just really slow to respond.)
It didn’t respond to that anymore after entering sleep mode
I see. You could try and enable Magic SysRq, but honestly I don’t see how that would lead to a permanent fix.
Thanks for the suggestion, I hadn’t heard of it yet and it seems very useful. However, I might as well just shut it down completely in this scenario if I have to reboot anyway.
I’ve been having similar issues for a while on OpenSUSE.
I noticed that if I press the power button it works, but if I try the keyboard, the issue happens
I can’t wake it with the power button either. Do you mean that it freezes after using the keyboard?
Yes, that’s what I meant.
Sorry I can’t help you more
Had that happen yesterday for the first time with a similar (AMD CPU and GPU) setup.
Have you been able to find a fix?
Didn’t happen again so far, so I didn’t investigate further. The qcode display on my mainboard displayed an error code I think.