And it’s crap across the OSes. On Linux laptops don’t wake up from sleep, on Windows they keep waking up when nobody asks for it.
In our home office room there’s three laptops. My private one running Fedora, my work PC that sadly runs Windows and my wife’s laptop also running Windows.
My work laptop and my wife’s laptop keep waking up wasting electricity, and my private laptop needs a hard reset to wake it up every second time.
That feature should be stupid simple, yet it doesn’t work across the board.
Rant over.
wakes up when nobody asks for it.
Wrong. You might not have asked for it, but it is not your computer, it’s Windows’ computer. Microsoft decides when it wakes up.
Fair.
And it’s crap across the OSes.
Never had these problems with MacBooks. It’s probably one advantage of the OS and hardware being made by the same company.
Agreed. For all the downsides people point out with Mac’s, they handle this and battery life quite well. My daily driver is a Mac, and everything I connect to runs some flavor of Linux. Then there’s the Windows 11 thing my work foists upon me.
That’s fair, never had one, so I can’t judge that.
Macs aren’t immune to S0 sleep options. The Apple silicon CPUs are just so efficient that when it fails to fall to sleep it doesn’t matter. Intel ones it sucks balls when it fails.
Even my Intel MacBook Pro slept like a champ. They aren’t 100% immune but 99.95% I didn’t have an issue compared to my work windows laptop which was like 25% sleep worked and woke up correctly.
Hell, why is sleep so hard for most humans?
Stop judging, at least I made it to bed. It’s not my fault sleep can’t find me.
Sleep is easy, you just prioritized that 30 minute YouTube video
First thing I do on any OS, but especially linux, is turn off every sleep-related option permanently. I don’t care anymore. I won’t fight with it.
In 35 years of experience I’ve never got it to work correctly on any OS except IOS. I’ve only met ONE tech who claimed it worked for them, and that was in the 2000’s. He couldn’t demonstrate how exactly.
I do the same thing, turn that shit off because it does not work.
Yeah I don’t bother with sleep either, I just turn all my stuff off when I’m done with it. With the advent of SSDs and M.2 drives, it takes about 10 seconds for my desktop to boot from fully powered off. I can wait that long lol
my guess is because the CPU power levels are fucking trashed because of all the patches they have to run at runtime. before Intel went all “wild west” with their security practices to improve performance, sleep worked just fine for me.
keep in mind, this was before uefi too, so it might also have a hand in the problems.
My laptop refuses to stay asleep if fstab disks were disconnected prior to sleeping. It works perfectly fine for me now that I figured that out.
Just one more weird behavior with fstab and kde or Linux or arch? I don’t know who to blame.
deleted by creator
on Windows they keep waking up when nobody asks for it
Good to hear.
I have an old Dell XPS 13 sleep works great on for Linux probably can sleep a week or two and still have charge left when I open the lid. I have a newer framework and it’s dead in 2 days while “sleeping.”
S0 standby is the problem. It’s a flawed idea from the start. The theory is it’s more “secure” or something. But like… Who cares about stealing shit from memory going from sleep to wake.
Now my laptop drops 20% charge in 5-10 minutes and goes into hibernation. It draws more power than if it’s on.
I think the laptop really does matter, and it’s because chipsets are not all equal in how well their sleep modes are supported in the OS.
I’ve been buying XPS13s for over a decade; I’ve had four (three personal, and one requisitioned for me by my job), and sleep and suspend have worked almost flawlessly on them under Linux. In the office, most everyone else would move between meetings or to their desks with the lids almost closed, to prevent sleep and the problems it caused, but I’d just fearlessly close my lid; it was ironic to me that running Linux on the XPS I had more reliable sleep behavior than the Windows people on their laptops.
For OP: low power, initialization, and restoring state has to be implemented by each chip, and there are a lot of shitty, poorly implemented chips. Then the OS also has to store and restore state for each chipset, and even if the chip implements it well, the OS has to do a good job restoring power in the correct order and restoring the state for each chip. If anything goes wrong in either the chip or driver implementation, you get a broken state.
This is aggravated by the fact that Linux is a monolithic kernel, and if any device drivers get borked it usually borks the whole kernel. This wouldn’t be as bad a problem if Linux were a microkernel architecture and drivers could just be killed and restarted.
Newer Dells have removed the s3 deep sleep. I believe the cutoff is between Intel 11th gen and 12th gen in (at least) Latitudes. I have a i7 12th gen that sucks at sleep, but an i5 8th gen that sleeps well.
I researched this in (checking notes) 2009 or so… things may have slightly changed since (and my memory is fading away)
At the time there was a standard for sleeping. Microsoft was part of the standard… and then they decided to implement in a different way (classic Microsoft, of course).
Hardware producers then adjusted to windows because… well… we were dozens of us using Linux on laptops.
This created issues in Linux because there were some purist developers that wanted to follow the standards, others that were more pragmatic and wanted to implement the windows way. In the end nothing worked.
Fast forward to today, windows waking up constantly I guess it’s broken as expected because it wants to allow background processes to do stuff. Linux not waking up sounds still the issue from 2009: there are multiple levels of sleep and the deepest was the most problematic. If I have to guess your laptop wakes up just fine if the battery is full and you left closed for few minutes… while it doesn’t when the battery is low-ish and/or you left sleeping for a longer period
It’s waking up because another device on the network (probably router) is pinging it
Disable “Wake on Magic Packet” and the Windows sleep issue goes away
This kind of stuff must happen at hardware level… wake on lan is in hardware.
Ethernet cards keep in getting packets (arp at very least) even if they are not directed for them. If the OS needs to check all packages it would be always on
That said… wake on lan is also a waste of energy if you don’t need (why powering the Ethernet cards?)
The setting I am suggesting gets disabled keeps the card powered during sleep so Wake on LAN can work on a hardware level.
The OS isn’t checking the packets. The NIC gets a packet and wakes up the OS.
I am not defending it, just explaining how to stop it from happening. A lot of people who know what Wake On LAN is don’t know about Wake On Magic Packet
In my case its because Sony messed up the bios in more ways than one and refuses to correct the problems. They work around it with their own drivers witin Windows and leave it like that, but it also breaks Linux functionality as a result.
weirdly i have the windows problem on linux with my laptop: never have I had it not wake from sleep, but sometimes it starts overheating while on sleep and drains the battery super quick
many times ive put my laptop on sleep in my pouch, taken it out and hear the fans blasting, the laptop is burning hot and the battery lost 40% in 20 minutes
Are you talking about sleep, hibernate, or monitor off?
Sleep and hibernate don’t work for me.
Hibernate just acts like a power loss. After shutting down the state is just lost and the laptop starts up with a fresh boot.
With Modern Sleep, kernels 6.11+ go to sleep fine, but don’t manage to wake back up. The keyboard lights up for half a minute, the fan goes on, the screen stays dark and after half a minute the laptop goes back to sleep. Kernel 6.10 sometimes works, sometimes behaves like 6.11+. I’d say it works 80% of the time.
I disabled Modern Sleep in BIOS and tried to enable S3, S2 and S2+S3 in BIOS instead. I set the corresponding sleep states in Linux as well, and no matter which one of the non-modern-sleep options I try, and no matter if I’m using kernel 6.10 or 6.15, it never manages to wake up (same symptoms as above).
Yes
My laptop uses 0.07w sleeping, draining about 1.8% of the battery per hour. I would say that’s acceptable with 32GB RAM s2idle
Framework 16 on NixOS