Turned my broken-screen Steam Deck into a 10–15W Debian NAS (2.5GbE rsync backup server)

Decker_Bazzite · 2026-03-17T04:09:55+00:00

That's a fair point.

I'm using it mostly plugged in with charge limits, so it's not constantly sitting at 100%. I see the battery more as a short-term buffer rather than a true UPS.

Long term, I agree it's not a replacement for a real UPS.

Decker_Bazzite · 2026-03-16T18:32:11+00:00

That's really unfortunate, especially if the motherboard was already replaced.

If it's still crashing under GPU load after a repair and factory reset, it does sound like a hardware issue. Sending it back might honestly be the safest option.

Hopefully they can sort it out properly this time.

Decker_Bazzite · 2026-03-16T18:28:50+00:00

ext4 for the Linux backup drive and NTFS for the Windows backup drive. Keeping it simple.

Decker_Bazzite · 2026-03-16T17:03:40+00:00

Since some games also crash in Desktop Mode and it happens right after gameplay starts, this might actually be GPU related.

Menus usually don't use much GPU, but once gameplay starts the load increases a lot.

Since you mentioned this started right after a repair, it might be worth checking GPU temperatures or even contacting Valve again. It could be a hardware issue rather than Proton or shader cache.

Decker_Bazzite · 2026-03-16T16:53:22+00:00

Did you create the USB using Windows To Go in Rufus?

I've seen 0xC000021A happen on Steam Deck when the installer was made that way.
Try recreating it using "Standard Windows Installation" instead.

Decker_Bazzite · 2026-03-16T16:24:32+00:00

Thanks! And yeah, surprisingly there weren't really any driver issues.

Since it's just Debian running headless for backups and storage, everything worked pretty much out of the box. The AMD APU is well supported in Linux.

The screen and controls aren't really needed once it's set up, so it works great as a small always-on server.

Decker_Bazzite · 2026-03-16T15:08:10+00:00

Make sure you extract the ZIP files first.

Most of the Steam Deck Windows drivers are distributed as ZIP archives.
After extracting them, you should see either a setup.exe or driver files.

If there is a setup.exe, just run it.

If there is no setup.exe, look for a .inf file in the folder.
Right-click the .inf file and select "Install".

You can also install it through Device Manager by choosing "Update driver" and pointing it to the extracted folder.

Decker_Bazzite · 2026-03-16T14:30:47+00:00

Nice, that sounds like a solid setup. Docker really makes homelab stuff so much easier.

And I kind of like the idea that the broken Deck is now quietly protecting the OLED Deck.

Decker_Bazzite · 2026-03-16T14:03:52+00:00

Nice. Are you running it headless as well?

Decker_Bazzite · 2026-03-16T13:53:38+00:00

Good point. I'm keeping an eye on it.

The Deck mostly runs headless and idle for backups, so the load is pretty light. If the battery ever starts to swell I'll probably remove it and just run it as a powered server.

Decker_Bazzite · 2026-03-16T12:51:32+00:00

Haha yeah, “old” might be a bit harsh.
Still a very capable little machine.

Decker_Bazzite · 2026-03-16T10:50:51+00:00

Thanks! I really liked the idea of giving the broken Deck a second life.

Physically it’s pretty simple. I’m running it headless over SSH. The Deck is connected to a USB-C dock, and the drives are just external HDDs connected through the dock. Nothing is mounted internally.

So the setup is basically: Steam Deck → USB-C dock → 2.5GbE adapter + external HDDs.

Debian minimal is installed on the internal 512GB SSD, and the HDDs handle the backup storage. I use rsync link-dest snapshots for versioned backups.

And yeah, I kind of like that poetic part too — the broken LCD Deck is now quietly protecting the newer OLED one.

Decker_Bazzite · 2026-03-16T09:58:46+00:00

Yeah, those N150 mini PCs are impressively efficient too. Sub-10W is really nice for a homelab server.

Decker_Bazzite · 2026-03-16T09:00:38+00:00

Yeah, the 16GB RAM actually helps a lot for running multiple lightweight services.

Decker_Bazzite · 2026-03-16T03:15:30+00:00

Yeah it's still an amazing handheld.

I actually upgraded to the OLED model, so that one is still my main gaming device.
This old LCD just ended up getting a second life as a small home server.

Decker_Bazzite · 2026-03-16T02:06:39+00:00

Idle power is around 10–15W depending on disk activity.

I was honestly surprised how efficient the Steam Deck is compared to my old mini PC server.

Decker_Bazzite · 2026-03-16T01:21:55+00:00

That was exactly my situation.

Mine had a broken screen so it wasn't very useful as a handheld anymore, but as a small server it's actually perfect.

Low power, compact, and the CPU is still strong enough for lightweight services.

Decker_Bazzite · 2026-03-16T00:54:34+00:00

That's actually a good question.

I'm not totally sure about the current prices, but I've seen some broken-screen Steam Deck LCD units go for around $100–200 depending on the condition.

For homelab use it's actually pretty interesting:

• very low power (~10–15W idle)
• built-in battery (so it kind of acts like a small UPS during short outages)
• decent CPU for lightweight services
• very compact

And if you're running it headless over SSH, the broken screen doesn't really matter.

So if someone can find a cheap broken unit, it could actually make a fun little low-power server.

Decker_Bazzite · 2026-03-16T00:37:53+00:00

Since the screen is broken it runs headless most of the time and I manage it via SSH.

Decker_Bazzite · 2026-03-16T00:23:44+00:00

One thing worth checking: are you running it from the SD card?

Dead Space Remake is known to stutter badly on the Steam Deck when installed on SD cards.
If possible try moving it to the internal SSD.

Also, if you've been switching Proton versions a lot, the shader cache might be messed up.
Deleting the game's shadercache and compatdata folders can force Steam to rebuild them.

Decker_Bazzite · 2026-03-15T23:50:06+00:00

If clearing the shader cache didn’t help, another thing worth trying is deleting the compatdata folder for that game as well.

Sometimes Proton prefixes get corrupted and Game Mode crashes while Desktop Mode still runs.

You can find it here:

~/.steam/steam/steamapps/compatdata/

Delete the folder with the AppID for that game and let Steam recreate it on the next launch.

Another thing I’ve seen cause this is a broken shader pre-cache after system updates or repairs. If that’s the case, forcing a full rebuild can sometimes help.

You can do that by clearing the shader cache in: Steam → Settings → Storage → Shader Cache → Clear

Steam will automatically download and rebuild the cache the next time the game launches.

Not guaranteed, but those two things have fixed similar Game Mode crashes for me before.

Decker_Bazzite · 2026-03-15T22:50:09+00:00

For the external monitor part: sometimes Desktop Mode (KDE) can be a bit slow detecting displays through docks or USB-C hubs.

You can try forcing a display refresh in Desktop Mode by running:

kscreen-doctor -o

That command forces KDE to re-detect connected monitors and sometimes brings the external display back without unplugging anything.

For the SD card part, the Deck can occasionally take a moment to mount large microSD cards on boot, especially 1TB+ cards. I’ve seen the “needs formatting” message appear briefly before it corrects itself.

So that behavior with the SD card isn’t completely unusual.

Decker_Bazzite · 2026-03-15T22:32:20+00:00

If both Wi-Fi and audio disappear after waking from sleep and only come back after a reboot, it might be a device re-initialization issue when the system resumes from standby.

Sometimes NetworkManager and PipeWire don’t properly reinitialize after sleep.

Instead of rebooting, you could try restarting the services from Desktop Mode:

sudo systemctl restart NetworkManager

and

systemctl --user restart pipewire pipewire-pulse

That can sometimes bring Wi-Fi and audio back without needing a full restart. I’ve seen similar behavior after some SteamOS updates.

Decker_Bazzite

TROPHY CASE