I read how most laptop vendors nowadays force S0ix (Modern Standby). You can no longer pick S3.
On Linux the names for these policies in the kernel are:
-
deep, aka the S3 sleep or suspend to ram
-
s2idle, aka the new Modern Standby or S0ix or suspend to idle.
I am thinking of getting the new Framework laptop, but after talking with their CS, they mention that all Framework will run on S0ix and will not support S3 sleep.
There was a video of LTT bashing S0ix/Modern Standby years ago and he was correct. I had a Thinkpad and it defaulted to S0ix: resume and suspend were very unpredictable. Luckily that laptop also supports S3 so i can just switch to it.
Is resume / suspend getting better on Linux with this forced S0ix? Or i better hold on to an old laptop with S3 lol?
BTW, those with Framework, is resume/suspend reliable? Almost Mac like?
Fair point. Even my asus zenbook 2025 around 20% of times when I close my lid, it goes to hibernation and asus Software notifies that due to system not going to sleep within time, it was forced to go into hibernate. In Linux, forcing might work for s3 but u need to test out wirh everything. Else it’ll be stuck in between. Do you have a system currently which is comparable to framework specs? Yes I know they have much better out of the box suppoet for Linux but in this way you can test out you main Hardware for support. Try a live boot on a system and then check.
Even if u force s3 with kernel ur hardware on uefi level will not handle it properly and change that it will not go deep sleep or stay somewhere in middle of getting sleep with big chance u will get just black screen and u will have to reboot in the end. I am sorry s3 really dead
So i have not used a laptop with linux for quite some time. Only desktop and servers for the most part.
Recently however, I setup a dell XPS17 with opensuse Tumbleweed. This works great but I did run in to the issue initially that when using LUKS full disk encryption in combination with secure boot it disables the ability for hybernation. Something the due with kernel lockdown.
The solution was to not use secure boot and that allows the laptop to hybernate even with LUKS.
Something to keep in mind when setting up a laptop.
I’m also interested in this. In my old xps 13 the s0 was very buggy. Would be a shame if you can’t switch to s3 at all. I thought it was a limitation of the x86 architecture actually?
I had a similar experience with the XPS 13, which is odd because Dell explicitly supported Linux on this laptop. It was a good device and ran well for at least a decade.
If you have to ask you won’t be able to get it working.
This is so backwards. You know how people learn to do things? It is to ask things…


