State of S3 – Your Laptop is no Laptop anymore – a personal Rant
blog.jeujeus.de
blog.jeujeus.de
Regardless of a valid use case for "modern standby", there is DEFINITELY a use case for "old suspend to RAM" and "old hybrid suspend to RAM", which have de facto been blown away by the change.
I have no problem with adding a new sleep state that makes sense for other users. Go ahead and add S22 for that exotic sleep state manufacturing robots use between shifts. S344 for bluetooth devices waiting for reconnection. Whatever, I don't care. But don't replace an existing PRIMARY UI PATTERN with them.
To be fair this is not on microsoft for inventing S0, or even pushing for it for windows devices. It's on device manufacturers like Dell and Lenovo for dropping S3 from UEFI in favor of it.
It's like they don't even use their products
Oh who am I kidding, if they used they would notice all the bloatware on it and the shoddy build quality, etc
Once upon a time, there were fifty times as many Windows laptops as Linux (by which I mean debian, mint, etc) and Linux was ignorable. Now the factor is closer to ten, and I find it difficult to believe that device manufacturers simply ignore that. If they don't support S3, there likely is a better reason than the dominance of Windows.
I don't like using Windows, and I would like them to be a smaller player. But if I search for "desktop" operating systems share world wide I get numbers that are way way different.
some show that Windows is around 70%.
Anyway, if you as CTO tell the CEO that testing with Linux will get you access to x% of the market, the CEO answer will obviously depend on x. As Windows loses market share to tablets and macs, x increases, and it becomes less plausible to suggest that vendors are simply ignoring Linux because it's small.
We are talking about laptops. Not tablets.
Windows has been losing market share to Macbook-s at about one percent each year, so good luck reaching your 20% in your lifetime.
I'd argue that the deficiencies in Windows as a laptop OS has led to some people choosing iPads and the like when they would've chosen a Windows laptop.
Obviously, a tablet and a laptop have divergent usecases, but there's some overlap. And for those consumers that exist in the overlap, I think many (maybe most?) would rather choose an iPad.
Microsoft kind of saw the writing on the walls with this and that's how we got the whole Windows 8 fiasco.
Consumers consider them somewhat interchangeable ("I bought a Surface to replace my old laptop"), so they IMO can't be excluded. And if you don't exclude them, then the share of windows laptops is now so low that adding linux support is a noticeable increase in the sales potential of that hardware.
Device manufacturers are quite cynical IMO. Would you personally take on extra testing burden to increase the sales potential for a new model by 0.25%? 0.5%? 1%? 2%? 4%? 8%? I postulate that the device manufacturers wouldn't bother for the numbers at the low end, but if they don't do it now, then they have a better reason than "windows doesn't require it" (quoting from GP).
If you just look at "desktop/laptop" Windows still reigns supreme.
Now the question is could be: should you include those for this discussion or not?
Yes because lots of people use them. No because the conversation was about laptops.
regardless, I now understand your point
Perhaps in the US, though I doubt it. Chromebooks are not even sold in a lot of places. Apple products are much more expensive (relatively and absolutely) in the rest of the world.
Pretend that you know someone at your bank who can answer the question "what devices do people use for your online banking?" You don't need to really ask, you already know the answer: For a while it was overwhelmingly Windows on PCs/laptops, now Windows has been pushed to a minority position by smartphones, tablets and macbooks.
You might say that those don't count, but I think that for a device manufacturer they do count. I have private and work smartphones and laptops, mine are made by three different manufacturers, all three make both phones, tablets and laptops. AFAICT that's typical. There are exceptions (such as Dell) but overall, the markets overlap so much that most manufacturers need to regard it as one market with different nïches.
Within the market of personal computers (not the fictional market of personal computers combined with other devices that aren't personal computers), Windows has very dominant market share.
I agree, but there is a venn diagram here. Many use cases are covered by both products. As time goes on, the venn diagram gets closer to a circle. An iPhone of 2008 was a niche device, but nowadays you can complete 99% of tasks completely on an iPhone (yes I made up 99%, just pretend it's some number higher than it once was).
I think, for most adults, their primary personal computer is a smartphone. Many, not sure of the numbers here, don't own a laptop or desktop at all. They may have one for work, though.
To my mind, my ultralight private laptop is more similar to a many tablets and two-in-ones than to the 16" Macbook Pro that I was issued from my employer. Saying that the two laptops are in the same market and the tablets/two-in-ones aren't in that same market… just doesn't make sense to me.
Note that even CPU manufacturers no longer provide firmware development support for making S3 work on recent series of CPUs. (Apparently some get an exception, as I’ve heard of some laptops from large brands that are sold with Linux and do have S3 support in the firmware.)
Even if I create 200% swap file, I get `Call to Hibernate failed: Not enough suitable swap space for hibernation available on compatible block devices and file systems` on fedora 40.
It tries to go into hibernate but immediately wakes up.
There are others in Fedora forum who have had successful hibernate with Zram & swapfile.
I didn't find anyone else with my laptop Asus ROG Strix Scar 16 (2023) with successful Hibernate either on our Linux discord.
But in a nutshell, unplug your laptop before you close the lid. Windows does not suspend to modern standby when that happens. I always had an overcooked and dead laptop at the other end of my commute, which went away when I started unplugging first. Now my windows machine can go literal days in sleep mode without really impacting remaining battery that much.
- monitoring if power is unpluged
- monitoring if battery level sings below threshold
- monitor CPU temperature
and take appropriate actions, like transitioning to "classical" S3 or better hybrid S3
it's totally a misterious for me how that doesn't work well even 10 years later
I mean bugs which idk. unexpectedly drain a bit more battery etc. are to be expected but I would expect the UEFI to be like "uh that's too much CPU heat lets stop here", "uh that's draining the batter too fast let's stop", "uh only 40% batter better not even try anything". And sure you want hello to work even with <40% battery but that's if its enabled, which often it isn't.
This might be an urban myth so read with a pinch of salt, but there was a line of Dells at some point that warned to not close the lid without a proper shutdown, because it'll literally cook the LCD and cause permanent damage. Dell decided this was the right course of action for this problem.
I remember there used to be utilities that could save and restore icon positions, but perhaps that was only for good versions of Windows.
Yes I know ACPI was ratified in 1996 but it didn't ACTUALLY exist until 1998 and I would argue it wasn't actually implemented until early 2000 for enterprise users and 2001 for consumers.
Every single criticism, every single one, levied at modern standby was also made against pre-modern standby ACPI.
In addition to that, tech luminaries too numerous to count ranted for years and years and years that ACPI was a secret evil plot by the NSA to I don't know, kidnap your dog or something. That's not an exaggeration. That actually happened 20+ years ago.
> Modern PCs are horrible. ACPI is a complete design disaster in every way. But we're kind of stuck with it. If any Intel people are listening to this and you had anything to do with ACPI, shoot yourself now, before you reproduce.
Linus Torvalds, 2003. https://www.linuxjournal.com/article/7279 He's talking here about pre-modern standby ACPI, the standard everyone loves and misses today and writes long articles eulogizing.
I'm going to chalk this up to people hating change for the sake of hating change.
edit: I'm actually gonna chalk this up to hating for the sake of hating. I know, you know, and I know that you know that if old-skool BIOS was the standard, Hacker News would be flooded with 10,000 word Medium articles about how the evil tech companies are conspiring to keep our systems insecure so the NSA can kidnap our dogs and if pre-Modern Standby was the standard there'd be stories hating on that too.
It's like how haxxors reminisce about the days when the CPU bus was exposed on a port or card-edge connector out the back of a machine and everything was "so free and open" but when a modern interface with 1/10,000,000,000th the number of vulnerabilities is introduced those same people hate on it.
You might be new to Microsoft (and Google). /s
I think somedody told them that you cannnot sale the same GUI for more money so they keep "inovating".
I've personally always solved this problem by enabling "Hibernate" (not sure if that's a Windows-specific term) which writes the entire RAM contents to a file and then shuts down completely. The downside is that it takes a few seconds to boot (impressively few seconds on a modern machine, actually), but still, the laptop doesn't come on instantly. But I like knowing that there's no chance the laptop somehow turns on and overheats/drains in the backpack, because it's completely off.
This doesn't take away from the author's rant at all, the idea that a sleep mode would need to support notifications or updates (!) is absurd. A good sleep mode would need to only support "minimum power usage" and "fast wake-up" and nothing else. But with MS's usual mix of excellence and absurd stupidity, that appears to not exist, and "hibernate" is to me an acceptable compromise. My understanding is that Macbooks have gotten this right for decades already, pretty nuts that PCs lag behind so much.
This also alleviates the problem of sync'ing between multople laptops, as I use both a MacBook Air (lighter + better mobility: wake-up, WiFi, handling media) and a Lenovo X1 (Linux environment for software development and research).
Side-rant: It's nuts how hard it is to find a good laptop that has 64G RAM, let alone "more than 64G" as you cite. I finally thought I found one in a Thinkpad X1 2-in-1, but then it just had terrible build quality, broken speakers (low rumbling sound, unfixable even after a repair and a replacement), badly working components (eg fingerprint reader) etc. I ended up returning it. The HP is a full 1000 euros cheaper (!), and it's better in every way (incl processor speed) except the smaller RAM. Oh how the mighty have fallen.
Like this one? Found it in ~30s
https://www.apple.com/shop/buy-mac/macbook-pro/16-inch-space...
> terrible build quality, broken speakers [...], badly working components [...]
There was a dark time in Apple's lineup (2015-2020) when they ran hot, the keyboard was widely considered terrible, battery time was unimpressive, and the lack of ports forced everyone to carry half a dozen dongles everywhere... These times are gone.
> The HP is a full 1000 euros cheaper
Oh true, Macbooks do seem expensive, until you consider actual value. If "an actual computer" is the primary tool of your trade, I'm 100% convinced it's good ROI to invest in your own comfort/productivity/peace of mind.
If I need a mouse and do a controlled shutdown/boot I might as well use a desktop.
In contrast, my M-chip MBP never gets hot and the battery is reminiscent of my iPad. I used to stress about my power cord and making sure I had it with me, I still always carry one because I like being prepared but I don’t have to use it hardly ever away from home.
Windows worked for a while, then didn't, then it worked again.
I actually destroyed a Windows laptop with a faulty lid suspend. Closed the lid, put it in a laptop bag and drove 3 hours. Got there and it was 100% dead, cooked itself alive pretty much by overheating in the bag.
Linux sometimes works, sometimes it doesn't. Depends on hardware and software versions. It might work at first, then you update the OS and it breaks again.
PS. A related video from LTT: https://www.youtube.com/watch?v=OHKKcd3sx2c
I've battled this for a long time. The prospect of having my laptop be and stay charged is exciting.
Bravo, what an excellent design.
What’s double weird is that, if I close it without hibernating it, not only does it not lock the laptop but it seems to prevent the “lock after x minutes inactivity” setting kicking in. Which seems like a huge security problem.
https://wiki.archlinux.org/title/Power_management/Suspend_an...
That is just peak level stupidity. I sometimes boot into Windows, and every time Windows Update runs, the fans are on high, my system is taken hostage ("Do not turn off your computer - updates ready 100%" - showing for 15 minutes), and there is nothing I can do about it.
Compared to this, an `apt upgrade` is basically an instant action (only kernel updates take a bit longer). Too bad Ubuntu is trying to break that with snap, but it is still a minor inconvenience.
The major H1/H2 releases take a bit longer, up to 15 minutes. But not stuck at 100%.
Yeah right, implying everyone should get specified hardware to have a decent user experience definitely seem to be making sense.
The same cannot be said about Windows.
At the moment, the user cannot choose, but is forced to be always "on".
When it is working, S3 sleep covers my needs perfectly. And it is not about email updates. I don't want my laptop to do anything while in sleep. It's that simple.
Sure, S0 on Windows makes your laptop turn on in your bag for impossible-to-disable updates, causing it to overheat or the battery to run down. And no laptops on the market will S0 on Linux without running down the battery in less than 24 hours.
Why should hardware vendors mollycoddle users who make the foolish decision to use either Windows or Linux?
[1] - https://www.dell.com/community/en/conversations/xps/faq-mode...
EDIT: Added source cited in the article
I do. I had a few poor experiences with laptops accidentally turning on while in the bag between 1995 and 2010.
After the last time, in 2010, when the thing started beeping due to overheating, I started the habit of shutting down/hibernating completely instead of just closing the lid and popping it into the bag.
What an awful laptop.
Don't conclude from your own carelessness to others. Even just one person shutting down their laptop will instantly disprove your claim, that "nobody does XYZ". So you will basically almost always be wrong with such a statement/claim.
In the past where a computer would be connected to the corporate network all the time you could usually get Wake-on-LAN to work so you could boot computers at night to apply updates and ensure that users weren't waiting around forever. With laptops and people working remotely you need a new way to ensure that the bulk of the updates happen when they won't interfere with users trying to work - this is the solution.
Microsoft may well tout additional potential benefits, but that's more about selling it to consumers so they don't complain about changes as much.
And, of course, some manufacturers do a better job than others at implementing this. --I haven't had a problem with any of my Lenovo laptops or even the Surface laptop. Dell, on the other hand, doesn't seem to implement it well at all.
I believe iOS is capable of flushing most cleartext data on suspend until the passcode is reentered, so suspend should be as good as shutdown; I don’t know if macOS can do it. On desktop Linux it’s theoretically possible with systemd-homed, but in practice that needs desktop-environment support that’s as far as I know does not exist, so shutting down is more secure. I can’t remember anything about Android either way except for some features for disabling the USB port in some alternative firmware.
On Windows with a typical TPM-only setup, powering off is probably just as bad as suspending, because just powering the machine back on is enough for it to helpfully unlock everything. If you do need to enter a BitLocker passphrase at boot, then you’re in the same situation as typical desktop Linux, so powering off is more secure.
"enterprise customers" have proper security policies and tooling to enforce them in place.
My employer has a "small" utility that periodically checks for version of installed software and will warn me if I don't install the necessary updates. If I don't install updates for more then x days I'm cut off every network access to the corporate network, and I must first install the updates and then ask my manager to let me back in the corporate network (again, there's automated tooling for that).
So this push for "always on" bullshit is not what enterprises asked for.
Microsoft wants mac/ios/android-like experience, but just can't deliver such thing due to hardware fragmentation.
I never understood why microsoft doesn't go full apple and only allows certain top-tier features on surface laptops or other hardware they own from top to bottom.
If you're serious about software you can't underrate the role of hardware: Apple has clearly got this incredibly right, and it's a fundamental part of their value proposition.
I guess Microsoft should go full-apple and allow microsoft windows ONLY on microsoft hardware?
But you don't want that to happen when your laptop is in your backpack.
It is bonkers that Microsoft and manufacturers both would remove the ability for the users to decide it is not a good idea to have an OS running. It effectively forces anyone to shutdown completely their laptops.
And any issues related to applying updates after downloading them has nothing to do with this issue.
> That is just peak level stupidity.
It also violates the core idea of sleep mode: Keep the current state of my computer intact until I continue working. If a windows update forces a reboot, then that computer state will be lost.
basically you don't block any bandwidth while a user is using the computer and instead when they are not
also you download slower (less bandwidth) in the background because you have much more time available to download it (like e.g. the whole night)
this feature is also only about downloads, that windows tends to force apply updates once they are downloaded is a different unrelated issue altogether
so theoretically especially for laptops which are only used idk. 1-2h max a day for people with not so fast internet this could be grate
could because it isn't, due to implementation details
e.g. you would only want to run this if you are: plugged in (power), the internet is reliable (at least as reliable as "normally" for any given network) etc.
but AFIK it doesn't really detect changes in power status, doesn't detect bad natwork conditions (which can lead to increased power use), and probably doesn't use "intentional slow" download either
you also can't opt out
so yeah it seems shit with how it's implemented -- but the idea by itself isn't bad
From the article,
> Traditional Sleep requires all system hardware and software components to work together. The operating system must support Sleep, as well as the hardware (e.g. CPU) and the BIOS/UEFI. According to the UEFI to Hardware Interface Standard (ACPI), this usual form of sleep is referred to as S3. S3 is a Sleep State in which all system components, except for the RAM and CPU Cache, are powered off.
ACL = Access Control List / Association for Computational Linguistics
AAA = Authentication Authorization, Accounting / American Automobile Association / Triple-A Battery Size
...
S3 = AWS Simple Storage Service / ACPI Sleep States: S3 is one of them, they range from S0 - S5) / Suspend-to-Idle (S0ix) "Windows 10" mode selected in system firmware, "s2idle" selected in /sys/power/mem_sleep, and Suspend-to-RAM (S3)I cannot imagine what the benefit of receiving notifications and other information like this on a Windows system would be. As far as I know, very, very few apps are programmed for the native "App" development flow (or even to use the notifications api) as opposed to "desktop" apps, and the number only gets smaller as you go into long tail enterprise apps. Perhaps this was designed for Outlook, but I think the use case is dubious.
Of course, there are millions of laptops in the wild, many of which are undoubtedly used by the people who work on Windows. Every time I find the laptop closed and running its fans, or find a computer in a bag that is slightly warm near the CPU (expected behaviour of working Modern Standby), I wonder whether it's just my computer or if it's every single one of them out there. Do people just accept that their computer has to be either shut down or will have an unknown amount of remaining power? It seems like there would have been a huge push to get this fixed if it was really broken, but I rarely hear users talking about it.
Of course I do wonder whether with the advent of the new Qualcomm ARM CPUs, whether they have finally managed to get Modern Standby to be a good clone of what Android devices do...
Why is this important, or even something to consider? The only thing that's important with Windows and features in it is whether something delivers value to Microsoft.
Oh, sweet summer child. I sometimes use Windows on my work machine, complete with the "new" Teams and "new" Outlook. For some reason, these need a while to update when I wake my machine from sleep, even though it usually sleeps connected to power, with a network cord plugged in and in range of Wi-Fi. Teams, in particular, will say it's offline for a few minutes, even though I can browse the web as soon as the box actually becomes interactive.
The computer actually does something while asleep, judging by how hot it gets. But, as you say, it's really not clear what. It will do this even though Defender is deactivated (we have some other handbrake at work which doesn't do a full system scan on its own) and the system is fully up-to-date.
Why do you think it was created to deliver value to the customer?
It is merely a reason for Microsoft to spy^Hextract value from a customer even when the PC is sleeping. Like humans, laptop spend a third of their life in sleep mode and it would be nice to monetise that time, multiplied by a couple billion users.
I think it is clear that the goal of the Windows division is to milk every user for all their worth. By the time they are done, laptops will be an obsolete product and Microsoft doesn't really want to support Windows 20 more years.
Modern standby is making my laptop unpredictable, and that is very inconvenient for me
How is this the case? Suspend to/from RAM on Linux wakes up in less than a second in my experience. Which makes sense, because everything is still in RAM and systemd doesn't need to do a bunch of work to get everything back online. Maybe Windows has a weird implementation of S3?
My shiny new work laptop without S3 wakes up in the same time, and then says "Battery critically low, shutting down."
This is not a convenience, it's insubordination. I told it to sleep, and it didn't.
But you know what's really insane? When the new work laptop is just sitting there with the screen locked and I walk up and hit a key, it takes longer to just display the password box than the 10 year old Thinkpad takes to wake up from S3 and display the password box. (Ok, it's an unfair comparison, Windows vs Linux, but still...)
And S3 is basically «instant».
So I don't see much point in S2Idle/S0ix.
I guess the value is for enterprise users because the ecosystem is so bad.
When I return from sleep on my laptop, my VPN is disconnected and can't reconnect itself automatically as I need to go through the auth + 2FA phase. I am also logged of all Azure AD authenticated web apps and Microsoft web apps like Teams and Outlook are so bad they don't automatically sign in back when you have signed on on other Azure AD resources.
I haven't started my corporate laptop on the original windows 10 for years so I can't compare but I imagine a "modern standby" would have some keepalive on the VPN connections and apps like teams so they don't sign you out?
But in the end this is kind of useless on those Dell laptops because it drains the battery so fast and they have such a low battery life that you just want to shut them down if they are not connected to their docking statino. I guess it serves the people who are on-prem and close the lid to go from one meeting room to another.
But when I was working on-prem I would just configure it to just lock the laptop and would use the sleep shortcut to put the laptop to a normal sleep. Apparently most people were too dumb to figure that out and would walk between their desk and the meeting room awkwardly with the lid up, I can't believe they have managers roles or are even allowed to work in the IT industry ¯\_(ツ)_/¯
Whoever fixes this first will make a lot of money.
Edit: SteamDeck is also very good at this and that's why I'm sticking to it for handheld gaming.
edit: maybe not the specific S3 sleep problem but a general inability to sleep correctly
On my personal laptops the cause could be all the accumulated junk I installed. Apple's refusal to support legacy software may help out since it seems the old software doesn't want to run on new hardware.
I've never had any issues with entering my password/doing TouchID to unlock the laptop as soon as I've opened the lid.
This isn’t something to be proud of. It means that you’re not applying the regularly-released security updates.
macOS is spectacularly good at restoring state on reboot. It’s like it never happened.
Update your software.
Numerous minor updates have screwed up things for me, particularly with some applications I rely on. I will usually lag 2-3 patches behind and wait for other people to suffer first and confirm what I use is stable. I am still on Sonoma / 14.5 at the moment.
Incidentally I actually have a Mac Pro here which is running Monterey which hasn't been patched for about 9 months. The universe has not and will not be imploding any time soon.
Everyone forgets the "availability" bit of security.
I don't disagree, but also...
I find it a bit surprising that this is still a thing. Why is there ever a time when I _must_ reboot? Is it just that mainstream kernels were designed at a time when people had lower expectations around this sort of thing, and now it's too hard to evolve their designs toward something that would allow for zero-downtime patching in ~all cases?
Other examples that make me wonder if it's mostly because people haven't demanded better:
- Enormous updates for all kinds of things (gigabytes for a bug fix release) because differential updates aren't pervasive. - Windows updates where a huge amount of work is done during the "rebooting" phase (why can't most of this be done before reboot?) - Absolutely atrocious power management on pretty much anything that's not a MacBook, and even not perfect on those.
I never thought we'd have flying cars by now, but if you asked me a decade ago to predict the future of operating systems... it wouldn't be this.
Note that security updates are independent of the OS updates (or should be). There is no real excuse of forcing a user upgrade an OS version.
Otherwise under personal use/control macbooks are great, though, in not forcing you do updates of annoy you to death about them.
I've my own ritual for preparing myself for the "I am done" phase. Doing the last commits, writing down a few sentences on what should I do when I go back to work and closing the lid.
The solution happened to be unplug and replug for the first issue, and force reboot for the second. I've enough people having issues with external displays that I don't think it's an isolated problem.
For comparison a Surface Pro failing to go to sleep or getting hot in the bag hasn't happened to me in 2 years of owning these machines. It might surely happen, but it's far from a regular occurrence I think.
I got woken up in the night a couple of times because of my macbook doing that.
This have never happened with any other laptop I've had.
Here's the thing: this self-serving behaviour from Microsoft will eventually kill someone, or quite possibly a large number of people. It's just a matter of time until a high-powered laptop does this in someone's luggage on a plane, catches fire, and then there will be congressional investigations like we had with the Boeing 737 MCAS system.
In both cases near-monopoly companies are gambling with peoples' lives to meet some internal KPI that in the grand scheme of things just doesn't matter... but it does to some manager's bonus, so you see... people are going to have to die.
„old” and „legacy” hardware 8-10 years ago was fighting with the tasks and you could still put laptop on your legs. Funny enough yesterday I went into this sleep stuff, because my 5yo Dell battery drained while being „shut down” after 1.5 weeks and while charging I tried to run 2 tabs in browser to look for fix and my legs burned - so I had to put it diagonally on the table to cool down.
We have order of magnitude faster hardware capable of doing order of magnitude less things.
I almost always shut down my laptop. This serves me two purposes:
1) It saves power
2) I always start with a fresh session, keeping distractions at a minimum and having habits to "finish" the current task I am working at. (I do the same with browsers for example. Here I even less frequently save my session).
There are a few exceptions where I know I'll just take a quick break and resume work shortly, but they are rare. No, you don't have to have everything always available within milliseconds. No, I don't need notifications always on (so I guess I agree with the author here). But maybe just different tastes, different habits.
I don't know if this is true, but I talked about a broader topic along those lines with my therapist recently and she was like: 'We invent all these smart things to save time and have more for ourselves, but in reality people have less time, because then they just want to put more tasks into the same timespan'. I have absolutely no idea if there is any truth to that, but it feels true on my empirical observations. Embrace slowness!
Shutting down and booting are intensive operations, it's likely that for short enough periods of time, sleep is actually more power-efficient if it works well.
I don't have numbers though and with SDDs and fast boot times, maybe booting is way less power hungry than before in the end.
Can't argue with 2) of course.
Unless this is about setting up some kind of custom work environment on top of the boot ?
> It is possible to require a PIN to be entered in addition to the TPM state being correct. Simply add the option --tpm2-with-pin=yes to the command above and enter the PIN when prompted.
[1] https://wiki.archlinux.org/title/Systemd-cryptenroll#Trusted...
But regarding the work laptop, Sometimes it's nice to have stuff ready when you're oncall. I have my applications/windows pre-prepared so that I don't have to go trough a thousands hoops in the middle of the night to resolved that priority 1 incident.
I understand your point, but I also can see what's the fuzz about. If the fuzz is legit is not for me to say.
Windows has been broken since XP and linux desktop has been usable for decades now.
I refuse to buy more computers preloaded with windows or built with ANY consideration of what incompetent Microsoft want.
Why do we accept being spat upon and treated like basement bums when we put our money on the table???
Tell me you aren't in the target market without telling me you aren't in the target market.
Microsoft will never, ever, ever be able to make everyone happy. I do not agree with the direction they are going either, because I (as a long-time developer on Windows) am not in their target market.
This is the target market. It's not power users, it's not computing professionals, it's not me, it's likely not you. It's my mom. It's your mom. It's people that don't really know what their computer is doing.
Windows is no more sold to your mom or mine than it is to either of us. It's sold to people who aren't even users.
And that's why when you buy a computer with pre-installed Windows on it, you can now ask the store to remove Windows and give you back that money.
People put their money on the table when they purchase MacBooks.
Articles like these make me afraid that the damn thing will break eventually and I'll have to spend exorbitants amounts of money on something like a Framework to get a usable Linux experience.
Not to mention that having a fake-off state like S0ix is a golden ticket for covert surveillance (like our phones don't do enough for the gestapo). I don't think anybody cares about Cortana, even less so on a suspended laptop. The notifications and update angle is really suspicious as well.
The community.frame.work forum has reports from people running newer boards so you don't have to guess before buying.
Steve Jobs had an insight that a computer was just another household appliance
But it was built by engineers who came from the homebrew world
This is a great example of how our appliance has gotten worse, even though it’s on hardware that is 1000x the throughput, and we’ve lost the ability to configure it too
Moved to Apple Silicon in 2021 after my Dell Precision cooked itself (and my lunch!) to death in my bag on a train. No issues since.
The core issue is that the firmware in most laptops is just ancient garbage and nobody seems to really care about it. Apple has full ownership over their own firmware so it's less of an issue for them (though it still has issues). But most chip manufacturers servicing the wintel laptop market treat software as an afterthought. They aren't very good at it and they just put in the minimum effort that they can get away with. So, it's all proprietary, poorly designed, decades old, etc. If it breaks they bang on it until it sort of works again (windows only).
Laptop makers then make things worse by just buying a lot of cheap components. Synaptic seems popular for touch pads, for example. My Samsung has one. It's not good. I've actually never come across anything made by them that wasn't garbage.
With Linux slowly creeping up in market share on desktops, it's something that could start changing. Most Linux users are very selective in what they buy and there are certain brands that are just so hopeless that people actively avoid them. Lenovo bought a good reputation from IBM when they acquired their laptop division. That's ages ago but they sort of nurtured that and it's probably helped a lot. It's not rocket science to just make sure things work on Linux.
My work laptop is a macbook. The hardware is just miles ahead of the competition. It's just not even close. Everything else is a major downgrade. I bought that Samsung to replace a mac because I was waiting for the M1 to come out when my old laptop died. I worked on that thing for half a year. Going back to a mac was just such major upgrade in every way possible. You forget how great they are. Software wise I'm actually fine with Linux. Everything I use is open source or available for Linux. I don't use any of the Apple software (the i* stuff). I'm there for the hardware only. If Linux support catches up, I might switch actually.
I remember getting a BIOS update on my Dell a few years ago that permanently turned the fan on too.
And they can wait to switch to S3 (and shut down the fans) once the temperature got low enough, a bit like how with S3+swap, the computer won't enter suspend until the RAM has been copied to swap.
But Windows tends to wake it up randomly and do God knows what, since the PC will actually be hot to the touch.
Bonus points for attempting to install updates, then reboot, only to end up stuck waiting for the BitLocker PIN.
I wonder how limited the preboot BitLocker screen environment really is. Could there could be some flag set by the UEFI that says "I'm a laptop and the lid is closed without power connected, shut down after a timeout".
The first is my desktop, without a TPM, which will ask for a BitLocker password. In this case, if I'm not fast enough, it will shut down the computer.
The second is my work laptop, which I usually expect to reboot or otherwise am around when it ends up there, in which case I'll usually type in the PIN quickly enough. However, I expect it to have a similar behavior as the first case, although I haven't tried.
But the reason I know this happens, is that I once left this PC attached to my 32" screen next to my bed, and it woke me up at night. I just went and forcibly shut off the thing.
The command in question is ```bcdedit /set {bootmgr} bootshutdowndisabled 1```.
https://www.tenforums.com/antivirus-firewalls-system-securit...
For the best part of a decade the first thing I do on any mobile device I touch is disable wake calls in the power plan settings. Learned it the hard way after the T420 woke me up multiple times per night with loud beeps...
Technically true, but not enough for you to notice.
Modern SSDs have drive write lifetimes in the high hundreds of TB of writes.
If you had 128GB of memory in your laptop, writing that down to disk isn't going to consume much of that write lifetime.
Samsung warranties their 990 Pro SSD at 600TBW for 1TB, 1200TBW on 2TB, and 2400TBW on 4TB.
So, lets assume you've got a laptop with 32GB RAM and a 1TB SSD. If you hibernate it 3x per day. After 10 years you'll have used 350TB of your writes.
(32GB * 3) * 365.25d * 10y = 350.64TB
I think your SSD will handle it just fine. :)
I think this is less and less true as time goes on. I have a laptop from 5 ish years ago I still use and it's actually pretty fast.
And, even so, it's not like the ONLY wear on your SSD is the hibernation. So this 5 year figure, I'm not sure it's right. I think, maybe if you're someone who stresses your hard drives a lot (maybe you work with photography or videography?) hibernation might make an impactful difference.
For those with heavy I/O workloads, they likely have higher-grade or larger SSDs with a higher TBW rating.
Additionally, TBW isn’t a hard limit and can often be exceeded, with some drives lasting beyond 200%.
For most users, TBW won’t be an issue, and other components are more likely to fail before the drive wears out.
Their aim with S0ix is relatable and can somewhat be compared to Apples move to force USB-C on everyone - which is great and a necessity to be done by a market leader.
So, wait for the EU to mandate companies use the same standard? Even then, there were rumors that Apple was going to cripple non-Apple brand chargers.They tried, but the EU shut that down real quick and forced them to use the actual standard.
EU: Ahem.
Apple: We're gonna only offer USB-C for great interoperability with competitors' systems, aren't we generous and great? Also this was our idea this whole time, stop asking questions!
Updates? Well here is an RTC to wake-up. Voice control? Well here is an always on audio dsp. Remote wake-up? Well here is a WiFi frame filter to trigger IRQ.
I think it isn't tractable on most laptops because of all the hardware that has been onloaded to software, and the hardware isn't capable of those hardware filtering, and partly OS and drivers are probably to blame too. An embesded OS takes under 1s to wakeup, so even managing TCP KeepAlives wih resume/suspend is realistic on those devices. Not so much when wakeup takes 10s.
There’s something breathtakingly arrogant about that
"Breathtakingly arrogant" is pretty much exactly what I would think of if someone asked me to describe Microsoft in 2 words.
Microsoft decides for you how you would like to use your computer. If you don't agree, use Linux. Or Mac, but Apple is really no better than Microsoft with regard to arrogance.
Maybe I could look past this sleep nonsense if their super cool new sleep actually worked. But it just doesn't, instead it cooks your laptop 10% of the time and it you open it up and it's dead.
The fact that they are pushing S3 as "Linux Sleep" or "Legacy Sleep" and S0ix as "modern sleep" is absolutely not innocent from a marketing perspective.
We ought to reverse Uno this non-sense. Perhaps the Linux Foundation and all the distro development teams out there should start calling S3 _True_Sleep_™ in all their official communication.
S0ix/s2idle Nap
S3 SleepIs sleep really fixed and finally can be used on Windows? Do you tweak power settings or configs for that in any way?
In particular, sleep worked for me on T series Thinkpads: T420, T450, T490, my current T14.
So also acquiring a new laptop is now a pain in the ass... good to know.
The previous Macbook Air 11 also was great for sleep/wake. The Windows 7 Thinkpad before that was ok but took like 30 seconds to restart from sleep and would crash sometimes.
The current one. Fold it shut, stick it in my backpack. No noticeable powering-up or overheating issues, but if it's more than a few hours, the thing has a drained battery and is fully shut down. Luckily Windows "fast startup" mitigates the pain - it doesn't take very long for it to unsuspend-from-disk and reach a usable state again, with apps still open etc. No idea what Linux would do here. I actually have Linux on my previous work laptop (Elitebook 840 G6) and "proper" suspend works just fine on it.
Tbh all my Apple laptops, including the piece of shit one with the emoji keyboard, have had no problem sleeping.
Ofc that's on mac os, not sure what they offer if you install linux or windows.
More than once I went on a train ride to the office, having clicked "Suspend" in the main menu and watching the screen go black before placing the laptop in my bag, just to find out the battery was completely drained and the 2019 MBP so hot that it not just required cooling down before it would power up again but also hot enough to fry an egg - an IR thermometer showed 70 °C!
If anyone knows or writes an application that could place a red warning icon in the menu bar warning me that "suspending" will not actually work, I'll be glad to exchange it for a crate of beer.
mac os is nice enough to allow applications to prevent sleep. Check "pmset -g assertions" to point out the culprit.
A couple years ago it was Chrome for me. It kept an assertion saying "WebRTC has active peer connections" on all the time. This has only lead me to have a pathological hatred for WebRTC and I turn it off in all my browsers now.
As for the dGPU, i've never had one but I do have a feeling that spells trouble, especially with these electron apps and their Helper (GPU) processes. I'm old fashioned enough to do most of my work on desktops that are plugged in and only buy lightweight laptops (13-14 inch mbpros wit no discrete GPU).
But since it's sporadic, I sometimes forget to look into Activity Monitor if I'm in a rush, and for fucks sake this is not a problem that should exist in the first place.
I mean, yes, I've had more issues back when I still used Windows, but my Apple gear costs thousands of dollars, I expect better quality.
I expect that if the system knows that my intent will not be successful (because some application locks suspend) that the option is either not available/greyed out or that I at least get a goddamn prompt "XYZ is locking suspend. <Abort attempt/Force suspend>".
As for Electron, yes, Teams is cursed in that regard (as it is in locking the dGPU), but for me it's usually Parallels, closely followed by IntelliJ that randomly messes up suspend. Neither of them are Electron.
Tbh I don't understand why an OS would allow applications to prevent sleep either, but you mentioned MS Teams and I mentioned Google :)
I don't think IntelliJ ever prevented sleep for me, but I mostly used the Android Studio flavor. I've caught it using up all my ram though if i left it on for weeks.
As for Parallels, I've never tried to close a laptop with a running VM on it. I don't know why, but I always suspend the VMs manually (from the Parallels menu for example) if i use them.
Meanwhile MS have been trying to do the same since 2012 and there are still numerous issues.
I'm just glad my Lenovo Legion still uses S3.
My suggestion to anyone dealing with annoying power management is to get a MacBook Pro (you can get tons of ram, we are ordering 96gb models for our engineers) and run your preferred OS in a full screen VM if you don’t like MacOS. I did this for years because I don’t trust Linux to manage battery or reliably pair with Bluetooth devices (especially Bluetooth audio), but I much preferred Linux window management and access to Docker.
Parallels runs Windows quite well, and either that, Virtualbox, or the various apps that are thin layers over the system Hypervisor.framework all do the trick.
(Though I still wouldn't recommend that, as it's still supporting Apple by giving them money & mindshare.)
It's somewhat surprising that this is still the case, 20 years later.
I’d like to do this, as I find a laptop that cannot last in sleep for at least a week ill-suited for my needs. Where do I go to figure out if my next laptop supports proper sleep?
Or do people do not care because they do not use laptops on the go anymore?
'Luckily' hibernate only takes about 4x as long as sleep while still being just quick enough not to be too annoying.
I agree with the author that it totally defies the purpose of a laptop. Another terrible move by Microsoft
It is why I will fork out 2-3x for a Macbook, because apart from the screens being amazing, when I close the lid, I know it does exactly what 99.99999% of the population expects it to do, and I can safely put it in my bag.
Nope, it does not, but Apple is miles ahead of MS in this implementation, so it works almost as intended (not really sleeping while not preheating your lunch in your backpack).
In lenovo x1 they call it "Linux sleep" in bios settings.
It used to be that you could count on a sleeping Mac to stay asleep until you explicitly woke it up by opening the lid, pressing a key on the keyboard, or pressing the trackpad (or separate trackpad buttons — yes, those used to exist). Perhaps more importantly, you could count on the sleep function to have barely any effect on the Mac battery.
I don’t recall when, but at some point over the aforementioned three decades, Apple started changing the terms of this sleep contract.
It seems Apple decided that some functions should still be available when the Mac is “sleeping”, with no way to restore the previous behavior. As a result, random wake-ups are the new normal, replete with unexpected battery drainage.
I have seen modern MacBooks go to “sleep” with an 80% charge at night, only to be rendered dead with a 0% battery level by morning. Does something this extreme happen often? No. But it never happened before. And moderate battery loss while sleeping? That happens very often on today’s MacBooks.
Your mileage may very. And Apple probably continues to implement better computer sleep behavior than competing vendors. But I would argue that people who think MacBook sleep behavior is excellent… have never experienced how it behaved in the past. That behavior was superb.
But sadly, I imagine most people have never experienced that excellence.
I don’t quite understand this line. Are they talking about Lightning or MagSafe with the parenthetical? MagSafe specifically is something users were begging them to bring back and they did it without removing USB-C charging (best of both worlds).
On paper modernizing S3 made even sense since getting all the system components to work nicely with S3 is not an easy task. What wasn't thought off is that handling the same task in modern standby generally isn't easier.
Thus, a faulty implementation of a device or driver is not to blame on the standby mode. FWIW, Modern Standby works fine on my Thinkpad X1 Titanium Yoga with Windows 11. The only device that drains more battery than necessary if not disabled is the Qualcomm WWAN modem. That stops once you disable it, like in the "good old days". So for me, it's nothing negative, but actually adds convenience because with Modern Standby, my device goes to sleep and resumes much faster than the devices ever did with S3.
With some machines, the modern sleep where it stays connected to the network can sometimes cause connection issues that aren't as obvious to the end user.
In a lot of cases we disable fast boot, and disable modern sleep and the problem goes away - but having the ability to select which parts should be enabled and disabled, like how you get the option with PS5's rest mode, would be very useful - especially if controllable by GPO / Intune.
Hibernate = S4
https://wiki.archlinux.org/title/Power_management/Suspend_an...
Do you get all your workspace back exactly like it was before, after a shutdown and turn on again ?
starlite mkv 0yo Intel(R) N200, has deep.
framework0 2yo Intel 12th gen, has deep.
framework1 1yo AMD Ryzen 5, lacking deep!
That explains it—I haven't really taken the last one out of the house yet.So what can we do about this? Can we start a class action lawsuit for breaking the PC? Probably too late to return the AMD.
Finally I recommend calling S0ix/s2idle nap, and leave s3 as sleep.
Sounds like a nightmare!
Now I have an M2 Apple and it’s like a day and night difference. Close the lid works exactly how it should work. I maybe did shutdown the Mac onces.
I’m curious how well Asahi linux works with standby on a Apple Silicon Mac.
This seems to have been fixed for a while now (say a year or so), but when the Intel machine was new, Windows would sometimes not wake up from sleep, or if did, the screen would be garbled.
The AMD still has an issue where Windows will "unexpectedly shutdown" (according to the event log) during modern standby. This happens every single time I leave it on standby during the night. This is an almost four-year-old machine by now, not some brand-spanking-new thing, which works otherwise perfectly, especially on Linux.
I think most people intend their laptop to retain it’s charge when they close the lid and standby used to do this, but on windows machines, it really doesn’t anymore.
It should really write all the ram to hd after a short period of time in your backpack instead of quickly depleting the battery.
In the default config on my machine, it actually starts to hibernate if it's asleep and unplugged for a while. Don't know what the delay is.
I’ve not tried it long but from my short experience, it works well.
Btw, Asahi is actually really easy to install if you are curious. Everything is done/installed from macOS including shrinking your macOS partition. And uninstalling it is as simple as removing the partition from Disk Manager and growing back your macOS partition.
All you need is some disk space and, one command line to copy paste and about 20 minutes.
And it works really well overall. It have everything to be a daily driver (including graphics acceleration) except external display support and TouchID. But both of those issues are being worked on.
But overall, I was pretty impressed by Fedora Asahi. I was expecting a clunky experience with hacks and bugs everywhere but I'm now actually expecting to use it as my daily driver as soon as possible.
Like, there are those things (USB-C, external display, Touch ID) that doesn't work at all but everything else works wonderfully. Even the audio is as good as on macOS (thanks to the specially built audio driver) which iirc, have never been the case on Intel macs (yes, audio works on intel but the sound is better on macOS because Apple have a special driver that is able to shortly and safely overdrive the speakers to get better sound - and asahi replicated this driver).
1) Every component has to be in the right "state of mind" in order for Si0x sleep to work properly. Do you have shitty NVMe that has buggy PCI powersaving? Too bad, battery will drain 10%/hour. Your yubikey keeps USB bus by constantly sending interrupts? Ha, enjoy your new backpack heater and watch out for fires...
2) It is extremely hard to debug these issues. I've figure out the yubikey and few things, but some of them are esoterical! ifconfig eth0 down = some part of Intel AMT stops sleeping and is now fully on all the time. Why? Because fck you, that's why. If you want to get some debug info, you can get some very cryptic state-flags for (some) components and you really have to guess what these really are - there is no documentation unfortunately.
3) UEFI is a mess - one would say that you want critical component, such as BIOS/boot chain to be as simple as possible and not* to be extensible in nature - because if some malicious code manages to get in the UEFI modules, you are simply hosed. But the other problem is that UEFI provides quite a lot of interfaces through ACPI and ACPI tables are buggy as hell. I had to patch DELL's DSDT tables in order to get back "deep" sleep - unfortunately it stopped working some time ago as they must have changed something somewehere and the computer would not wake up anymore... It is impossible to debug (or rather it is a royal pain to debug).
Bizarrely, Microsoft also wants to hide this option from you too. But it still exists and modern SSDs are extremely fast.
while true; do pm-suspend; sleep 12; done
I just ctrl-c it when i need to use it and then restart it when i am done. Dirty but it works..
For example, on mobile phones it used to be the case that the application processor wasn't actually the main processor of the phone, it was actually the baseband, and relatedly, this meant that the application processor could be shutdown and woken up when the phone received a text message or phone call. Similarly, modern arm processors have a big/little configuration where you can switch to the efficiency cores when the system is asleep.
While I'm aware that at some point intel started offering efficiency cores, the vast majority of devices that run windows, AFAIK, don't have any way of being awake in sleep mode other that just leaving the CPU running with the screen off.
Maybe s0ix will make more sense as big.LITTLE and other secondary CPU schemes become common, but today seems like it's just upsetting existing users for no apparent gain
This is bad UX, loses productivity (users waiting for the machines to fire up), and appears to be a relic - ancient machines needed it and then it was perhaps never questions.
2. For desktop PCs, it's not a problem if wake-up time is a bit slow, but laptops should be up instantly (<4s).
It wasn’t Apple move. They were forced with possibility to loose whole EU market if they don’t.
Annoyingly when I enable S3 on my P1 Gen 5 Windows 11 give me a whole bunch of warnings in the security center.
Seems like S3 itself is incompatible with some modern firmware protections.
But frankly, I don't care whether it's S0 or S3. I just want it to sleep, and I don't want the OS to NOT offer me the options to say 'don't do stuff in sleep mode'
More reliable even if it does take just a little longer.
This post reminds me of the people who complained about the transition from APM to ACPI. Despite much wailing and gnashing of teeth about "Why can't my laptop just support nice simple APM? Why do I bother with ACPI?", ACPI won, and we're all better off for it.
More parts are kept on, for the sake of updates and notifications. Notifications that you will get on your phone anyway (and that the laptop won't be able to get if it's not connected to a wifi anyway), and updates that will likely cause too much excess heat to be safe to perform inside of a bag.
If you see the benefits more clearly, perhaps you could elaborate on what they are?