Recently bought a new laptop that comes with an AMD Radeon gpu and installed OpenSuse Tumbleweed on it which I had installed on my previous laptop as well but never had issues with suspending and resuming. However, with the new laptop, I am unable to resume after suspending or closing the lid unless I force it to shut down by holding the power button which is a major inconvenience.
I’m also dual booting alongside Windows and have secure boot enabled and have the Linux and Windows partitions encrypted if that’s what’s causing it which I doubt since this is the same setup I had on my old laptop
Any suggestions or advice would be greatly appreciated.
Edit: I was able to figure out that it does not suspend at all when I close the lid or click the suspend button on Gnome. Only found this out because when going through YaST Services Manager and manually starting systemctl suspend, the laptop suspends just fine and wakes back up. So I’m starting to think it’s more of a systemd issue? Any inputs?
Edit: turns out it was an issue with the official opensuse built kernel not sitting well. Downloaded a community version from the opensuse repository and it works fine. Very odd
deleted by creator
These problems, 9/10 times is solved by using another kernel.
had the same issue on nobara and i always thought it was nvidia problems. for me the only solution was to use another distro :( sometimes ctrl + alt + F2 or F1 got me back to the login screen.
I don’t have any advice, but I just wanted to confirm I have the same issue sometimes with my laptop running fedora.
If you use a recent release of Fedora (last 2-3 years). Try disabling WiFi and/or Bluetooth before suspending. There is an issue with some hardware, especially adapters. It doesn’t happen everytime, and it’s hard to accurately reproduce. Also, the symptoms can vary from black screen to sudo being stuck.
I have/had a similar issue, but for an old nvidia laptop. What happens if you get it to suspend and resume again? Mine would come back the second time.
I can’t even get it to resume again which is the problem lol
Yeah, but for mine, i could close the lid and it would suspend again, and then i could resume. Pressing the power button briefly also worked.
I have a similar issue but for me the black screen comes at random times when I open, close or move my windows or mouse.
I found a temporary fix for it by checking out the archwiki amdgpu page
But it still occurs , especially when I wake up my computer after suspending it.
I had a similar issue on a new out of the box HP Prodesk. Independently of the distro I was running it wouldn’t want to wake up from standby. Turned out to be an (firmware?) issue with the SSD. After replacing it everything worked fine.
I have seen this on HP laptop with WWAN device installed. Disabled device from Bios and problem went away.
Can you check dmesg and/or journald? What model Laptop is it?
Where do I go to check those? Sorry in advance I’ve never been the most knowledgeable about Linux
Edit: here is the exact laptop https://www.bestbuy.com/site/lenovo-yoga-7-16-wuxga-2-in-1-touch-screen-laptop-amd-ryzen-5-7535u-8gb-memory-512gbssd-arctic-grey/6533956.p?skuId=6533956
sudo dmesg | less
and something withjournalctl
(not sure because I don’t use that currently). There should be some other logs you can check in/var/log
too,kern.log
sounds useful (though that might just come from sysklogd).
It’s a wild guess, but try to disable Bluetooth or WiFi before suspending.
It’s doesn’t happen with all hardware, but it is a knowing issue.
I know it’s not super helpful, but I’ll add that this happens to me periodically on my EndeavourOS, Intel based desktop as well. Not even all of the time, just sometimes when it suspends. It seemed to get better when I changed my settings to hybrid sleep, but it just happened again yesterday, so I’m back to square one. Bookmarking to check for possible solutions later.
Are you using the dedicated GPU as your primary GPU or the integrated GPU? I’ve found using the dGPU as the primary can sometimes lead to suspend/resume issues.
I have exactly the same issue (though in my case sometimes there are artifacts instead of just a black screen). I would love a solution but I never found one unfortunately