On 9/2/24 8:27 PM, Carlos E. R. wrote:
There is a wiki page with things to do for diagnosis, but I don't remember which one; maybe tomorrow I can find it in one of my bugzillas. It is is 3 AM here, so perhaps you can find it. Anyway, I know little about TW, I don't like living at the edge.
Wiki page is 2020 for suspend to RAM and really has nothing useful. The other page is pm-utils which doesn't exist anymore in TW. The Arch wiki had good info: https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate Here is the bottom line from testing (with systemd defaults): Tumbleweed Sleep: # echo s2idle > /sys/power/mem_sleep # cat /sys/power/mem_sleep [s2idle] deep # systemctl suspend (s2idle reached but system fan not stopped, power remains on) # echo deep > /sys/power/mem_sleep # cat /sys/power/mem_sleep s2idle [deep] # systemctl suspend (deep is s3 suspend, and suspend works) The odd part is just days ago when I closed the lid -- all hell broke loose trying to come out of sleep resulting in a hard-reset and praying the SSD wasn't corrupted. Tonight, invoking s2idel or s3 suspend from the command line both worked as advertised. The only surprise is s2idle does NOT result in the system being powered off with the little power-button like blinking to indicate you are in sleep mode. In s2idle the RAM and disk are frozen effectively stopping CPU processing, but otherwise the system looks like it is ON. Suspend [deep] in /sys/power/mem_sleep is your normal s3 suspend mode and it does power down the system and the power-button blinks normally. In either case, wireless networking is reestablished as soon as the laptop is brought out of sleep -- very nice. I don't know why the lid closing caused suspend to fail to resume -- but after adding the resume= line (which has nothing to do with suspend to RAM), it all seems to work fine. Dunno. -- David C. Rankin, J.D.,P.E.