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.
this post was submitted on 14 Jul 2025
165 points (94.6% liked)
Linux
12216 readers
51 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:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
founded 2 years ago
MODERATORS
On the Windows one, consider hibernating it. Its a longer wake up time, but it doesn't wake up randomly.
load more comments
(1 replies)
With OpenSUSE Leap sleep always worked for me, (even hibernate works) but if you had it as external monitor only then sometimes the screen power off would not come back on, and the laptop screen was told to stay off. I found myself using KDEconnect on my phone to try to cycle monitor power on/off command and sometimes it figured it out
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=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.
Its mostly the blue light and the lack of melatonin. Seriously though I have not had an issue with it in linux and not really that much with windows but half the time I shut my machine down.
Instructions unclear, now my laptop is covered in sticky stuff.
Sleep on my minisfourm v3 is awesome with Linux. It correctly detects the keyboard cover, auto rotates based on the accelerometer and can be unlocked using the fingerprint sensor.
Roughly 1M anecdotes in the comments already
@squaresinger@lemmy.world It's probably because my kernel version is very old (5.14.11-arch1-1, haven't updated since 2019, even though it's Arch, a rolling-release distro) and my Acer laptop is old as well (Intel Core 7th gen), but I rarely have problems regarding laptop sleep. After I wake the laptop up, the video (including every VT#) may get frozen and I have to remotely SSH and request a reboot (and when this happens, sometimes the reboot gets stuck as well, so I have to do a hard power-off). But it's very rare, as stated, and I daily put my laptop to sleep without issues, sometimes the system uptime stretches to weeks (currently, my system was booted almost four days ago).
It does work fine too on my 2010 EEE PC running Antix running on a 5.10.x kernel. Seems to be more an issue with newer devices, since every single laptop I own that's newer than maybe 2013 has these issues.
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