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.
Considering the security implications of suspend and how much enabling zram has improved my workflow for hibernate, I can’t really say I miss suspend any much. It was fast (near-instant in good days) but it’s always been a bet whether you can restore state or have to clean boot.
Also at least in my experience there were always a number of things that just borked suspend if you left them unattended. Back when I was still maining Debian Stable on 2022, having a remote mounted via SSHFS or having Redshift active always would lead to a near-eternal freeze before suspending, or worst case scenario a suspend-into-crash (ie.: suspends right, but panics during resume).
I wouldn’t mind if at least hibernation worked. But it always loses the state on hibernate and acts as if there was just a power loss. It boots up with a fresh state instead of the stored one.
It’s quite a bit old and maybe superseded by something more modern in 2025 already, but have you tried setting up your boot with the
acpi_osi=linuxparameter? It should enable some corrections and capabilities from the BIOS that are not available if the system “lies” to the BIOS by telling it it’s Windows (“for compatibility, they said”). Dunno, maybe it juuuust happens to include the fix you need.