When I A bug or an system display related issue I found in Arch Linux running with SDDM.
It wakes up.
Black screen.
I'm running Arch Linux with SDDM. NVIDIA GPU. Consumer card.
Here's the thing about NVIDIA on Linux: their power management on consumer-level hardware is broken by design. When the display sleeps and wakes, the driver conflicts. The screen doesn't recover. You're left staring at nothing, wondering if you broke something or if something was always broken.
It's a known issue. Documented in forums. Mentioned in bug trackers. NVIDIA just hasn't cared enough to properly fix it for us.
Linus Torvalds, 2012 (Still accurate)
A Year on Arch (Without Going Down the Rice Hole)
I've been on Arch for a year now.
I didn't rice it. Not obsessively, anyway. I knew the trap — you spend three months building a desktop that's perfectly yours: every keybinding, every color, every font chosen by your own hands, understood by exactly one person on Earth. Beautiful to you. Useless to your deadline.
That wasn't wise for me. Not yet.
But I still learned more from this OS than any hand-holding distro ever taught me. Arch doesn't protect you from yourself. It hands you a blank canvas, a wiki, and your own stubbornness — then steps back.
You learn because you have to. And somehow that sticks.
Today's Rabbit Hole
I was installing Omarchy on a CachyOS base — Hyprland setup, fresh install, ready to go. Used what was labeled a "safe" test script from GitHub.
It wasn't perfect.
I started troubleshooting. Logs, terminal output, forum threads from 2019 that are somehow still the most relevant thing on the internet. Feeding output to my AI, clicking through configs, muttering to myself.
And then — the pieces connected.
That display bug I'd been living with for months? I finally traced it. NVIDIA drivers conflicting on wake from sleep. Consumer power management. A problem that's been sitting in plain sight, documented and unfixed, waiting for me to finally look it in the eye.
The Hours You Spend Confused Are the Investment
Nobody tells you this when you install Arch.
The blank screens, the journalctl rabbit holes, the 3am forum threads — that's not wasted time. That's tuition. You're paying for a mental model of your own system. One that no YouTube tutorial can hand you.
I questioned those moments. Hard. Staring at nothing, wondering why I was doing this to myself, wondering what normal people do with their evenings.
But today I can say: I know what was wrong. I understand my system.
And the fix?
# In /etc/systemd/logind.conf
HandleLidSwitch=ignore
One line. Toggle the lid behavior off. The display stops sleeping. The conflict never triggers.
That's it. That's the ending. Months of blank screens, solved by one config line I could've written on day one — if I'd known enough to write it.
Still With You, Linus
NVIDIA makes powerful hardware. They also make Linux users' lives unnecessarily difficult — and have for decades. The open-source community has worked around them, patched around them, and occasionally yelled at them in legendary fashion.
I'm still here. Still on Arch. Still learning things the hard way, which turns out to be the only way that actually sticks.
The system I'm running today — I understand it. Not perfectly. Not completely. But more than I did yesterday, and infinitely more than if I'd stayed somewhere comfortable.
What I Actually Learned (TL;DR for the skimmers)
- NVIDIA + Linux + display sleep = known conflict, poorly maintained
-
HandleLidSwitch=ignorein/etc/systemd/logind.confsidesteps the wake issue - A year on Arch without ricing was the right call for me — depth over aesthetics
- The painful hours are the curriculum. There's no shortcut that gives you the same understanding
- Omarchy on CachyOS/Hyprland is worth exploring — just go in with eyes open
Running Arch. Still here. Send help (or just more coffee).
If you've hit the same NVIDIA sleep bug — drop your fix in the comments. There are a hundred ways to solve this and I've probably only found one of them.
Top comments (0)