this post was submitted on 14 Jul 2025
167 points (94.7% liked)

Linux

11976 readers
209 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
MigratingtoLemmy@lemmy.world
167
Why is sleep so hard for laptops? (lemmy.world)
submitted 3 days ago by squaresinger@lemmy.world to c/linux@lemmy.world
98 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] lambalicious@lemmy.sdf.org 1 points 3 days ago (1 children)

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).

[–] squaresinger@lemmy.world 1 points 3 days ago (1 children)

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.

[–] lambalicious@lemmy.sdf.org 1 points 2 days ago

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=linux parameter? 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.