Depends on which suspend tho. iirc there’s one system that’s forcefully being discontinued by big corpo, while the replacement is still very buggy everywhere.
It’s called S0ix/Modern Standby/s2idle. It was designed to replace S3, but not only is it shit on Winshit and kekOS, it’s also very unreliable on Linux in my experience. The true issue it that manufacturers started to discontinue S3 (so shallow/standby and deep/s2ram) in favor of s2idle. You can check which actions are theoretically possible in the kernel docs, and check which are supported on your system (and enabled) by cat-ing /sys/power/mem_sleep. That’s what systemctl suspend chooses. My PC and Server still have deep, but my Laptop already only has s2idle.
Suspend on Linux just works as well. The PC will sleep until the user wakes it up.
Depends on which suspend tho. iirc there’s one system that’s forcefully being discontinued by big corpo, while the replacement is still very buggy everywhere.
Hmm, do you remember which one was it? Personally I never had problems with
systemctl suspendorloginctl suspend.Found it. AW article
It’s called S0ix/Modern Standby/s2idle. It was designed to replace S3, but not only is it shit on Winshit and kekOS, it’s also very unreliable on Linux in my experience. The true issue it that manufacturers started to discontinue S3 (so shallow/standby and deep/s2ram) in favor of s2idle. You can check which actions are theoretically possible in the kernel docs, and check which are supported on your system (and enabled) by cat-ing /sys/power/mem_sleep. That’s what systemctl suspend chooses. My PC and Server still have deep, but my Laptop already only has s2idle.
Thanks for the Arch Wiki article, really informative! It seems I have both s2idle and deep.