Most very recent laptops no longer support S3 sleep which used to be the default for a long time. On my old laptop it allowed me to just close the lid in the evening and open it again in the morning, and it would only loose a negligible amount of charge during that time.
My new laptop (Dell Inspiron 14 Plus, Alder Lake) uses s2idle by default on Linux (Fedora in my case), which depletes the battery very quickly. I tend to shut down my computer every evening now, but even when I just put my laptop in my bag for 2 hours it will have lost 10-15% when I get it out. It’s not terrible and I have gotten used to using my laptop like that but there’s got to be a better way right?
I know hibernation / suspend-to-disk is an option in theory, but I use secure boot (and also disk encryption), and that makes it a lot more complicated, involving compiling your own patched kernel, so no thanks.
The way sleep on modern laptops is supposed to work is apparently called S0iX but it is not used by default and I don’t know if or how I could make use of it on my laptop, and a guide that is linked everywhere on 01.org now just redirects to some generic intel site.
If you have a recent laptop without S3 sleep support, how are you dealing with this? Do you just live with the poor battery life, or is there some secret to getting more power saving sleep on modern machines?
Edit for mare clarification:
- The laptop does enter s2idle correctly, it just doesn’t get down to a very low power state at all and consumes ~5% an hour
cat /sys/power/mem_sleep
only returns[s2idle]
, no deep sleep is supported.echo deep | sudo tee /sys/power/mem_sleep
doesn’t work (tee: /sys/power/mem_sleep: Invalid argument
)- There’s no option in the BIOS to enable other sleep modes
- I’ve even tried patching the ACPI table myself to enable S3 sleep and it didn’t work. I have no idea if I did it correctly although according to dmesg it did seem to load my patch
Thank you all for your input but it looks like on this Dell laptop I’m stuck with horrible s2idle sleep :/
Hibernate on lid shut, and I hate it
It’s just infuriating when I close the lid, immediately remember that I needed to quickly look at whatever else on screen, and open it back up to a boot screen that takes 15-20 seconds to go away. First world problems maybe but my Android tablet can be locked without overheating in my bag and without losing all of its battery overnight, in addition to opening instantly.
My new Asus laptop didnt support S3 sleep.
Turns out it does indeed support it but the BIOS claims it isnt.
I found a patch for Linux ACPI that would make it enable S3 anyway and lived happily ever after
I have this same issue on my 11th Gen Intel Framework and I never found a solution after a lot of research. I’m upgrading from Intel to an AMD board so I hope it will make a difference.
My Steam Deck (AMD) gets amazing sleep performance and barely loses any charge so I hope I can match that with my new AMD board when I get it
@Rando @Sh1nyM3t4l4ss AMD generally has worse firmware than Intel.
Your laptop should support S3 sleep though. It might be labeled in the BIOS as “Linux” sleep.
If you use a modern kernel s0ix (called s2idle in Linux) will work fine as well.
[edit] I’m sorry I though you had a Thinkpad, wrote the comment on Mastodon app on phone and couldn’t see the message I was replying to haha.
I have a Framework Laptop 13 (i5-1240P) and run Fedora Workstation. It uses s2idle (another name for s0ix, afaik) by default and the battery depletion is OK imo.
If it’s low on battery and I can’t charge it instantly though, I tend to make the next sleep state use ACPI sleep state S3 by running echo deep | sudo tee /sys/power/mem_sleep
. You can check if that’s available on your platform (and the current mode) by running cat /sys/power/mem_sleep
afaik.
You arent supposed to shut down your laptop when you dont use it for more than 10 minutes?
That’s actually exactly what I do with my old Macbook Pro - its the only laptop I have, but I think there must be an issue with the battery since if I let it suspend for a bit, when I come back to it I have to hard reset it in order for it to come back on…
I normally run Fedora 38 on it, but I still keep macOS on it for firmware updates (well, that was the original intent, I don’t think Apple will be updating mine for much longer if they still even are), but it occurs there too.