I simply stopped even trying to use sleep mode because I had some issues and many people responded to my inquiries telling me that it’s always been spotty in Linux. I have one laptop that goes into sleep mode perfectly fine when I close the lid, and wakes perfectly when I open it. That’s an Asus x202e with Pop!OS. Then I have an older HP Elitebook with Elementary OS that goes into sleep mode when I close the lid, but in order to resume, I have to open the lid and then press the power button to wake. And finally my new ASUS zenbook with Kubuntu would go into sleep and never be able to wake no matter what, and required a hardware forced shutdown. So that’s my main system and I simply disabled sleep. When I close the lid it just shuts off the display. It’s actually not bad because I can leave something running and close it, and it continues the tasks.

These days the computers use such less power than they used to, so it’s not really the biggest necessity to use sleep mode.

New kernel may introduce regressions. See this similar issue on kernel 6.10.3, or try another version of kernel on startup if it's possible.

Step 1: give up

Do you have steam running in the background? Or do you have gamemoded enabled?

I've had some suspend adventures too, but my experience is just on Intel laptops.

About a month ago, Debian Trixie had a regression that made my laptop wake up right after a suspend attempt. Afaict, it was not directly a kernel change, something in userland changed and triggered problems. This pm_async thing fixed it. Frankly, I don't know why "async" power management is a thing anybody would want. Taking a whole extra millisecond to suspend in a more reliable way seems like a no-brainer.

echo 1 > /sys/power/pm_debug_messages # why would you ever want to not syslog it??

echo 0 > /sys/power/pm_async

Cat /sys/power/pm_wakeup_irq may tell you something about whomst is responsible for sleep failure. Anyways, suspend is the worst thing to diagnose good luck.

Hello, I'm far from an expert but I had a similar issue on my desktop, running mint and an Nvidia GPU. After looking at a lot of places for an answer one that did work for me was below

Ust/bin/Nvidia_sleep.sh. (off the top of my head it is something like this, can confirm later if you can't find it.)

At the top put in "exit 0"

See if it works for you. But it seems when I get an update it does at times get overwritten.

Perhaps not useful, but my linux machine doesn't sleep unless I disconnect my ploopy trackball first, exhibiting the same symptoms.

I’d start with looking at what the logs say when the computer fails to sleep.

https://linuxhandbook.com/journalctl-command/