Comment by ohazi
18 days ago
RIP S3 sleep... Took years to get it to work reliably under Linux, then we had a good decade+ run of it "just working" like this, now back to trying to weed out all the wacky platform quirks and weird hardware/firmware behavior that make the S0ix states be just barely unusable.
Maybe in another five years...
Can you explain a bit more? What happened?
Linux used to be able to do S3 sleep well, and now it can't because... new platforms removed S3 for S0ix? Or S3 became even more complicated with mroe platform quirks and weird hardware?
The problem is platforms moved away from S3 sleep. I've heard people claim it was mostly so managed Windows laptops could force updates with the lid shut and the laptop suspended.
Now I have to worry about my laptop randomly overheating itself in my backpack and even catching fire.
I've heard people claim it was mostly so managed Windows laptops could force updates with the lid shut and the laptop suspended.
That, but probably also to compete with Mac's Power Nap feature (2012) that updates Mail, Messages, and other applications during sleep (so that when you open up the laptop messaging apps are immediately up to date):
https://www.engadget.com/2012-06-11-apple-introduces-power-n...
Apple managed to do it without setting your laptop on fire. Meanwhile Dell recommends you to switch off a laptop when you put it in your backpack:
https://www.dell.com/support/kbdoc/en-us/000124304/notebook-....
3 replies →
My Macbook Pro lasts about two days on battery while doing work (in clamshell mode, with the screen off). My Thinkpad drains its battery in less time than that in sleep. The removal of S3 is a travesty.
I believe it came about during the "Windows must run on tablets" era. They needed a way for WiFi to stay on during sleep so things like notifications would continue to work. It also enabled media players to continue playing audio in sleep mode, similar to iOS and Android.
6 replies →
weirds me out since acpi etc. is uaed to control power qnd such states why would devices even need to do such things to support some OS.. the OS should be able to manage states, its the controller and hw should listen... in this case, windows could simply not put the devices to sleep?
i know it didnt end up with this logic but it melts my brain as to why... is it cheaper to implement the hw without support for deep sleep?
most specifications have it included (pcie, nvme, ahci etc. etc.) so you'd expect most devices working via pc platform would implement these things :(
cant wait to push my OS onto real hardware and burn my fucking house down