Your TV Just Got Rooted. Build a Retro Console You Actually Own Instead.
A hands-on guide to building your own retro console: Debian, RetroArch cores, and EmulationStation Desktop Edition on a cheap N100 mini PC, with hardware comparisons, config layouts, and install commands.
Your TV Just Got Rooted. Build a Retro Console You Actually Own Instead.
The Samsung TV root shell post that blew up on HN this week is a perfect little horror story for anyone who buys hardware. 831 points, and the thread underneath is the usual mix of "well, obviously" and "wait, my TV?" The short version: the thing hanging on your wall is a general-purpose Linux computer with a vendor-controlled boot chain, a pile of unauthenticated services, and a business model that depends on you never looking inside it. Someone looked inside it. Someone always does.
I've been thinking about that thread while rebuilding the emulation box under my TV for the fourth time. And the contrast is stark. A locked-down appliance is a computer you rent from a company that would prefer you didn't read the EULA too closely. A retro console you build yourself is a computer that does one thing, boots in eight seconds, has no telemetry, and will still work when the vendor's update server goes dark. Dan Luu's piece about being more ambitious with the software we build landed the same week, which felt like a coincidence worth noticing. Emulation is one of the most ambitious pieces of software on my shelf — we're running GameCube titles written for a 2001 PowerPC chip on a CPU the size of a postage stamp, at 60fps, with a CRT filter on top. That's the ambition. A TV that phones home is the opposite.
So here's the build. Debian, RetroArch for the cores, EmulationStation Desktop Edition (ES-DE) for the frontend, one controller, no cloud.
Why this is easier than it was three years ago
Three things changed, and they all point the same direction.
First, x86 mini PCs got stupidly cheap. An N100 box with 8GB of RAM and an NVMe slot runs about $130 new. That's roughly Raspberry Pi 5 territory once you add a case, PSU, and storage — except it has an actual x86 GPU stack, which means every libretro core builds and runs, including the software renderers that ARM builds sometimes skip, and including PCSX2 and Dolphin at 1x-2x internal resolution.
Second, ES-DE matured into something I'd actually put in front of a guest. It handles gamelists, scraping, per-system emulator selection, and it no longer needs a config file hand-edited from a forum post. It's free for personal use on desktop; the Android build is a paid thing, which is fine and honestly a good signal.
Third, Valve made "Linux handheld with a real GPU" a mainstream product. If you already own a Steam Deck, you own a better retro console than anything you can buy pre-made. Dock it, pair a controller, and skip half this article.
The flip side: the pre-built distros (Batocera, RetroPie, Lakka) are still great, and I'm not going to pretend a hand-rolled Debian install beats them on convenience. But if this box is going to live on the same network as everything else I run, I want it to be a machine I administer, not an appliance I flash. That's the same reasoning behind the Proxmox and lean-lab principles I wrote about here — own the OS, or the OS owns you.
Pick your hardware
| Box | Real cost | Ceiling | OS you'll actually run | Honest verdict |
|---|---|---|---|---|
| Raspberry Pi 5 (8GB) | ~$110 all-in | PS1, N64 mostly, PSP okay, Saturn shaky | RetroPie or plain Debian | Fine if you have the accessories. Weakest GPU per dollar. |
| N100 mini PC | $130–170 | PS2, GameCube, Wii at 1x–2x | Debian + RetroArch/ES-DE | Best value. This is what I'd buy today. |
| Used SFF office PC (i5-8500) | $60–100 | Same as above, sometimes better | Batocera or Debian | Cheapest raw performance. Noisy, 15W idle, ugly on a shelf. |
| Steam Deck (docked) | You own it | Adds PS3, Wii U, some Switch | SteamOS + Flatpak | Best handheld, mediocre as a permanent TV box. |
| Old Android TV box / Fire Stick | $30–60 | PS1, N64 with luck | Android + RetroArch | You're back to renting someone else's OS. See: the Samsung thread. |
I've owned three of these. The Pi 3 build I did in 2019 was a weekend of fighting dispmanx and I'd do it again exactly never. The N100 replaced it and idles at 6W.
Pick your software stack
| Stack | Base | Config lives in | Scraping / metadata | Upgrade story | Best for |
|---|---|---|---|---|---|
| RetroArch alone | Any distro | retroarch.cfg, per-core overrides |
None | flatpak update |
Tinkerers, single-system setups |
| RetroArch + ES-DE | Any distro | ~/ROMs + ~/.emulationstation |
Excellent, built-in scraper | Flatpak + swap the AppImage | A box that also does other things |
| Batocera | Its own image | /userdata, config via web UI |
Excellent | Reflash or upgrade script | Set-and-forget appliance |
| RetroPie | Raspberry Pi OS | ~/RetroPie |
Good | apt + setup script |
Pi owners, huge forum archive |
| Lakka | LibreELEC | RetroArch's own menus | None | OTA | Minimalists who hate metadata |
The middle row is the one I run. RetroArch alone is a headache the moment you want two systems, and Batocera is a headache the moment you want to run a Jellyfin server on the same box.
The actual install
Debian 13 minimal, non-free firmware enabled, one user with sudo. No desktop environment — I want X to exist only to host a fullscreen frontend.
sudo apt update
sudo apt install -y \
retroarch \
libretro-snes9x libretro-nestopia libretro-genesisplusgx \
libretro-mgba libretro-beetle-psx libretro-mupen64plus-next \
libretro-pcsx2 libretro-dolphin \
xserver-xorg xinit openbox xinput joystick \
mesa-vulkan-drivers vulkan-tools \
bluetooth bluez
Debian's retroarch package is a few minor versions behind the Flatpak, and the Flatpak ships the full slang shader collection plus a pile of cores. If you don't care about distro purity:
flatpak install -y flathub org.libretro.RetroArch
Then ES-DE. Grab the AppImage from the releases page, drop it in ~/ES-DE/, and create a portable.txt next to it — that makes ES-DE keep its config inside that folder instead of littering ~/.emulationstation.
mkdir -p ~/ES-DE ~/ROMs/bios
cd ~/ES-DE
# unzip the release archive here
chmod +x ES-DE_AppImage
touch portable.txt
./ES-DE_AppImage
ES-DE expects ROMs at ~/ROMs/<system>/, with one directory per system name from its es_systems.xml. It creates the whole tree for you on first run. BIOS files go in ~/ROMs/bios — PS1, Sega CD, and Dreamcast all need them, and ES-DE will tell you which ones are missing.
Smoke-test a core before you trust the frontend. ES-DE hides a lot, and it's much easier to debug a core from a shell than from a controller-driven menu:
CORE=$(find /usr/lib -name 'snes9x_libretro.so' | head -1)
echo "$CORE"
retroarch -L "$CORE" ~/ROMs/snes/Super\ Mario\ World.sfc
If that opens a window and plays, the plumbing works. If it exits with "failed to load core," your core path is wrong — which is also the most common ES-DE failure, and it's always the path, not the game.
Booting straight into the frontend
A console that drops you at a login prompt is not a console. Autologin the user on tty1, and have .bash_profile start X only on that tty. Then ~/.xinitrc does two things: kills the screensaver and execs ES-DE.
# ~/.xinitrc
#!/bin/sh
xset s off -dpms
xset s noblank
exec /home/retro/ES-DE/ES-DE_AppImage
# ~/.bash_profile
if [ -z "$DISPLAY" ] && [ "$(tty)" = "/dev/tty1" ]; then
exec startx
fi
Pair an 8BitDo in XInput mode once and it stays paired:
bluetoothctl
> scan on
> pair XX:XX:XX:XX:XX:XX
> trust XX:XX:XX:XX:XX:XX
> connect XX:XX:XX:XX:XX:XX
trust matters. Without it, the controller re-pairs every boot and ES-DE starts with no input device — which looks exactly like a frozen frontend.
The tuning that actually matters
Ninety percent of "emulation feels wrong" complaints are three settings, and none of them are about raw performance.
Latency. RetroArch's runahead is the single biggest quality-of-life improvement for 2D systems. One frame of runahead hides roughly 16ms of input lag and costs almost nothing on an N100.
# in retroarch.cfg
run_ahead_enabled = "true"
run_ahead_frames = "1"
video_vsync = "true"
video_hard_sync = "false"
Do not stack runahead with video_hard_sync on Intel integrated graphics. I spent an evening convinced my TV had broken game mode. It hadn't.
Shaders. The Flatpak build ships crt-guest-advanced-ntsc and friends. A good CRT shader on a 4K panel does more for how a SNES game looks than any upscaler setting. Point video_shader at the .slangp file and enable it — then resist the urge to tweak it for two hours.
Core choice. For SNES I run snes9x, not bsnes. Accuracy is lovely until it's dropping frames. That's the same lesson as the 10-year-old CNN that outscored frontier LLMs at skin cancer diagnosis — the specialized thing that's been tuned for one job usually beats the general thing that's impressive on paper. mupen64plus-next over the older mupen64plus. beetle-psx unless you have a GPU and want the hardware renderer.
ROMs, storage, and not being a jerk
Store ROMs on your NAS and mount them, not on the boot NVMe. They're read-mostly, they're large, and they don't belong in your backups of /home.
# /etc/fstab
nas:/export/roms /home/retro/ROMs nfs ro,soft,timeo=50,_netdev 0 0
A read-only NFS mount is a nice safety property: nothing on the console can corrupt the library, and every device in the house sees the same saves-adjacent structure. If you already run a file server, this is the same pattern as the self-hosting and automation setup I described here — one source of truth, thin clients everywhere else.
Then scrape once with ES-DE's built-in scraper (you'll need a free ScreenScraper account) or from the shell with Skyscraper:
skyscraper -p snes -s screenscraper -i ~/ROMs/snes
One opinion, stated plainly: dump your own cartridges and discs, or play homebrew and public-domain ROMs. I'm not going to write a tutorial that assumes you're downloading a 40GB torrent of someone else's PS2 library. The homebrew scene for NES, SNES, and Game Boy is genuinely good right now, and it's the honest way to test a build.
Do this next
Buy the N100 box. Install Debian minimal. Run the apt line above, drop the ES-DE AppImage in ~/ES-DE, and smoke-test one core from the command line before you touch a controller. If retroarch -L plays a game, you're ninety percent done, and the rest is autostart config and a shader.
The whole build takes an evening. The hardware costs less than the TV that got rooted. And in five years, when the vendor has moved on and the update servers are gone, the box under your TV will still boot, still play, and still belong to you.
If you want the same discipline applied to the rest of the rack, the CI/CD pipeline post covers how I keep this config in git — because the fifth rebuild of this console is going to be an ansible-playbook run, not another weekend.
Recommended tools & services
Disclosure: some links below are affiliate links. If you buy through them I may earn a commission at no extra cost to you. I only list tools I actually run.
| Tool | Why it is here | |
|---|---|---|
| Amazon - SSDs & NVMe | Boot drives and storage for your homelab | Visit |
| Amazon - Mini PCs | Low-power always-on nodes (ProDesk, EliteDesk, N100 boxes) | Visit |
| Amazon - PC Components | CPUs, RAM and cases for a build | Visit |
| Amazon - GPUs | Consumer GPUs for local inference (16GB VRAM is the sweet spot) | Visit |
| Amazon - RAM & Memory | More RAM is the cheapest upgrade for VMs and containers | Visit |
| Amazon - Raspberry Pi & SBCs | Pi 5, Zero and clones for Pi-hole, DNS and thin clients | Visit |