I mean, it is more than thirty years and has lots of responsibility.. That or lack of melatonin
Linux
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
From what I heard, the sleep mode on the steam deck is just the default linux sleep mode. It works almost flawlessly.
I don't think it's quite true though because I can leave it in sleep mode for days and it just fires back up where it left off with almost no noticeable battery drain. If I put my desktop pc to sleep (bazzite) it acts like a stroke victim. IF it manages to wake up. Usually it just has to be restarted so I don't waste my time and just shut it down now.
Does it? I have a really old sony vaio that last more than a week suspended.
It might be before the time of s2idle sleep ;)
Sleep on Windows 11 is horrendous. It appears to be little more than locking the session and turning off the screen.
On my Linux computer I just close the laptop's lid and it goes to sleep, consuming almost no battery power. I can open it hours later and have basically the same amount of battery left as before.
But some laptop manufacturers have proprietary systems in place for the sleep mode that are not supported in Linux because it would be a gargantuan effort when the laptop manufacturer refuses to coöperate.
This is the answer.
Proprietary firmware. Fuck Intel.
Laptops with AMD chips are not necessarily better in this regard.
From my anecdotal experience with an HP laptop (from work), with an AMD 7840HS, the blame is often also with the system integrator. That one has a bug in the power management system, where if you plug the charger in during sleep, the power state gets locked to some very low power sleep mode, until you either reboot, or plug the charger in while it's not asleep.
HP doesn't want to look at this because they don't support Linux, meanwhile AMD kernel devs claim that this is probably a BMC bug so they can't fix it. Whatever the real culprit is in my case, the BMC can do so much these days that it wouldn't surprise me if a lot of sleep issues are due to bad firmware.
Either way, system integrators like HP refusing to support Linux is in part what allows Intel and AMD to ignore a lot of Linux-specific bugs. SIs have a lot of manpower to help diagnose and fix them, and they have leverage when reporting bugs to CPU manufacturers.
If only going to sleep was simple. There's a bunch of different sleep states. S3 is ram and S4 is hibernate.
Check your supported sleep states. At the command line type cat /sys/power/state
https://www.kernel.org/doc/html/v5.4/admin-guide/pm/sleep-states.html
It also doesn't help that ACPI is a badly-designed mess of a standard. I remember that in the 2010s one of Apple's selling points was that their laptops had sleep and hibernation that worked every time. Heck, MacOS X could even decide intelligently when to do which. This mostly worked because they fully controlled the hardware, firmware, and software. Other laptop manufacturers could just take their best stab at implementing ACPI power states and hope their implementation matched Microsoft's.
Microsoft tried to solve the mess by introducing the S0ix ACPI state (aka "Modern Standby"), which was defined in a way that could actually be implemented without too much guesswork. Unfortunately, this was during the Windows 8 era when Microsoft decided that laptops should be more like smartphones so S0ix is much closer to turning your screen off on a phone than to actual standby.
The system randomly waking up and deciding to do work is an explicitly intended feature because what if you get a Teams message while your laptop is in your bag? Sure, you might say that you'd either have Teams on your phone or wouldn't immediately care but that kind of thinking won't get you anywhere within Microsoft. Also, Windows actually has very little restraint about what it does when it wakes up so it might decide to install a heavy update or an application might decide it's important enough to do work right now. While the laptop is in your bag. Cue you wondering if the laptop turned off because the battery's empty or because it overheated.
And to make things worse Microsoft specified that in order to be allowed to use Modern Standby, the device must not offer S3 (sleep/suspend-to-ram). Some manufacturers still allow you to enable S3 but it's a legacy feature that's even less well supported than before.
The system randomly waking up and deciding to do work
My work macbook did this by default as well, among other dumb things like leaving bluetooth enabled on sleep so my headphones would constantly connect to the laptop when on the train trying to listen to music.
Thankfully the waking up thing is just a setting, but by default, imho, mac os's sleep is also garbage.
Worth noting that this is also an ongoing issue with windows. Only apple has actually solved this, and they do so by owning the whole stack. Each apple product has a specific OS, CPU, and motherboard that were all specifically designed with the end-product user-experience in mind.
But for PCs, the OS, CPU, and motherboard are all designed and built by different companies, each only designed to be generically compatible with the other components. None of them are designed for a specific end-product, so features that require all of the components to play perfectly together for a specific end-user experience (like sleep state) often end up not quite aligning.
None of this helps you, but I think it's worth understanding why the problem exists and why it may just always exist. The best bet is that companies like System76 or Valve solve sleep states for specific linux-based products, and then the rest of us maybe hopefully see some benefit from that.
But IMO this is just a trade-off. It's like a pick 2 situation between Customization, Stability, and Privacy (where a reliabile sleep state is Stability). You can have stability and customization, but you'll probably pay a lot, and the company who sold it will want telemetry data to improve the experience for others. You can have stability and privacy, but the product will be very locked down to a specific use case to ensure a stable experience.
It's not that apple solved it, it's that Microsoft purposely fucked it up.
It's called "modern standby" and if you put your laptop to sleep while it is plugged into power, some windows services and wifi aren't actually put to sleep, and instead will ping windows update servers to download and install some updates while the machine is "asleep".
Even if and when you put the laptop to sleep while plugged into power and then remove power to say out the laptop in your bag. Those services that aren't put to sleep never check to see if you are still on wall power or battery and keep doing what they do draining the battery
Linus tech tips on YouTube did a whole deep dive into it. Some laptops you can disable modern standby through the command prompt but newer hardware doesn't allow for it. The only real workaround is unplug your laptop for a few seconds before putting it to sleep.
As I understand it, apple products support the same update from sleep feature, except it works for all the reasons stated above.
I'm pretty sure all Microsoft needed to do was put in a check to see if it was running on battery or not. And I remember seeing that they finally fixed it months ago.
Modern windows is bogged down by decades old compatibility architecture. Shit programed in the 80s will still run on modern windows for the most part. All because corporations and businesses still run those programs or severs today and refuse to update or replace them. Look at the fucking US aviation industry. Billions of dollars in revenue and still run windows 95 level shit programs.
Microsoft needs to pull an apple and rebuild windows from the ground up without any compatibility layers. Enough is enough.
Components like CPUs and mainboards are absolutely purpose-built for laptops. And precisely this has caused a host of issues from locked-down BIOS/UEFI to broken sleep to incompatibility with real-time audio processing via ASIO, and that's just the ones I have personally experienced.
The real issue here is an outdated x86 architecture that was never designed for efficiency, which is severely struggling to compete with Apple's ARM-based M architecture, but which they can't get rid of for compatibility reasons.
Your system goes to sleep and wakes up? My system goes to sleep and then crashes. We are not the same
Your system and me have a lot in common (⌐■_■)
moth doesn't know what CPU you use, but newer AMD chips don't support S3. AMD removed that because they think modern suspend is better, an opinion that doesn't seem to be shared by the consumers.
No idea if this applies to a lot of laptops, but on my HP with an i5-8350U every Linux distro I've tried seems to come configured using s2idle instead of deep sleep, and battery will drain very quickly even in 'sleep' mode.
If running cat /sys/power/mem_sleep returns "[s2idle] deep" then you can add mem_sleep_default=deep to your kernel args and it will actually go to sleep properly.
On Fedora this was sudo grubby --update-kernel=ALL --args="mem_sleep_default=deep" but it varies by distro.
Why it seems like every distro I've used has this set incorrectly I do not know, it's baffling.
Windows doesn't sleep. Ever. Sleep is now just a nickname for Modern Standby, which is just running in low power mode doing a whole bunch of shit. The amount of times I come back to my laptop and it has gotten stuck at a reboot is just embarrassing. I dual-boot and have Grub, so whenever Windows tries to reboot itself it gets stuck.
People have gotten their laptops damaged because they thought they were sleeping and put them in a bag, when Windows decides to try to update itself while the fans are blocked inside the bad. Bam, heat damage.
i use a kaby lake (7th gen intel i5) laptop, and sleep works well on all linux, freebsd, windows. i'm using s3 sleep, are you on a newer machine that only supports s0ix?
I have the 13th Intel mobile gen and it sucks when it comes to power states
yeah, i think they started getting rid of s3 in favor of s0ix since 11th? 12th? gen. heard it's shitty. :(
It's mostly a mix of newer laptops not supporting suspend to RAM (only suspend to idle), and faulty hardware requiring proprietary hacks to actually go idle.
When I put windows to sleep it just wake up in middle of the night to install whatever update, restart and slowly empty it battery until it die.
I've found on my corpo dell-
Disable wifi
Sleep from start menu
Wait until fan stops spinning
Close lid
I find my laptop suffocating itself in my bag every single time i don't. This way, it only does that 1 in 10 times.
I've only used windows at work in the past 10 years or so but my windows experience with sleep was far far worse.
My laptop would always wake up in my bag on my hour+ commute. The laptop would be scorching hot and the battery dead by the time I got to the office. Every time.
Never experienced that in Linux.
Recently I switched to a Linux computer at work and it's much better in every regard.
My personal desktop (runs arch (btw)), did have some trouble with sleep recently tho...I replaced my 5700G with a 5600X3D and it would refuse to wake from sleep, necessitating a hard shutdown (by PSU switch!)...but I think that was a bios bug. My bios was already very close to latest but I think upgrading that was what ultimately fixed it. Now it works fine.
Every piece of shit windows laptop since they flipped from S3 sleep to "modem standby." garbage. Thing wakes up in the bag at the slightest whiff of wifi. "Oh! Network! Want me to connect so I can install updates, delete all your pinned tabs, break a few apps, and infect notepad with AI slop vulnerabilities? No answer? That must mean you want that - doing it now, boss!"
Dell, Lenovo, and Surface laptops all do the same shit. I fucking hate windows.
Dell support even told me, with a straight face, that if I didn't fully shut down my laptop before putting in my bag that I'd void the warranty.
Always wondered this. My steam deck dies in a day if put to sleep or hibernate.
I once did a deep dive on sleep mode for some problem a friend was having. I'm now convinced it might be the worst thing I've ever seen in modern computing. It's globally horrendous, poorly implemented, and causes random problems in unfathomable places. It's amazing it ever works at all.
I just want the option to put my Linux laptop into S3 ACPI power State. Daim you modern W11 hardware and S0!!!