Why not just suspend to disk?
My Asus laptop with 32 GB of RAM is 4 years old, but resumes from the encrypted swap partition in under 5 seconds, which is fast enough for me.
My Asus laptop with 32 GB of RAM is 4 years old, but resumes from the encrypted swap partition in under 5 seconds, which is fast enough for me.
I'm not sure of the status on other distro kernels but allowing it would be a significant bypass of Secure Boot's purpose.
That is worth discussing though, as it's a marked departure from old Macbooks that did support the UEFI method.
Needing a way to securely verify the hibernate image is ALSO a problem, and one of the reasons Asahi haven't focused on suspend-to-disk, but it's not the first-order issue.
In a nutshell:
> Getting hibernate to work would mean a metric truckload of work on the drivers to support restoring firmware state. Not happening any time soon, it's basically forever the bottom of the priority list and we're unlikely to ever run out of other things to work on first.
> Fixing PM with no documentation is a game of trial and error. You do "more things" like macOS and hope that one of them reduces power consumption.
> It definitely isn't obvious what we're missing, and we don't know what the real answer is going to be. If we did, it would already be fixed.
I was able to follow a fairly standard NixOS config with lvm and encrypted swap. I've never had any issues after hibernating a couple times a day for 3 years.
I don't know what the fuck is going on with laptop hardware. That stuff seems to barely work, despite the chips and stuff being off the shelf. Most windows laptops cannot handle sleep correctly either.
Setting the BIOS option to "Linux-compatible sleep mode" fixed this, but it took me FOREVER to figure this out and I'm reasonably certain I first heard about this fix in a comment here.
Not a bit of a problem since.
Having such an obvious name like that is a gift, because otherwise you have to start decoding Intel Marketing names for their features to figure out which are actually anti-features.
The intention was to replace S3 with fine-grained per-device sleep modes that would in aggregate lead to idle power that is almost as good as S3 while allowing for the "wake up and check email" kind of features. But to the surprise of approximately nobody, this complex multi-vendor strategy relying on high-quality drivers for every single peripheral in the machine did not work out as well as planned. The plan also did not in any way require that S3 sleep be eliminated from newer hardware platforms; that was just malicious behavior from the Wintel conspiracy.