Lakka installation and setup — Raspberry Pi or PC, ROMs and controllers not working
You have flashed Lakka to a Raspberry Pi or PC but ROMs are not appearing, the controller shows no input, or you cannot access the network share to transfer files.
Lakka is a lightweight Linux distribution that boots directly into RetroArch — no desktop environment, no EmulationStation, just the emulator frontend itself. It is leaner than RetroPie and excellent for low-spec hardware or users who want a clean RetroArch experience without the extra layer.
Three issues appear in nearly every first-time Lakka setup:
- ROMs not found — Lakka only scans the
/storage/roms/directory. ROMs placed elsewhere, or files transferred before the Pi fully booted, are not detected. - Network share not accessible — the Samba share (
\\LAKKA\ROMs) requires the Pi to be on the same network and fully booted; a missing hostname in DNS can prevent the share from resolving by name. - Controller not responding — Lakka auto-detects most USB and Bluetooth controllers, but an initial autoconfig step in RetroArch may need to be triggered once.
Solutions
solution #975
Flash the Lakka image to a microSD card, boot the Pi, and transfer ROMs to the Lakka network share from your PC or Mac.
- Download the Lakka image for your hardware from lakka.tv/get. Choose the correct variant: Raspberry Pi 4, Pi 3, Pi 5, or Generic x86_64 for PCs.
- Flash the image to a microSD card (16 GB minimum) using Balena Etcher or Raspberry Pi Imager.
- Insert the card and power on the Pi. Lakka will boot directly into the RetroArch XMB interface — this takes about 30–60 seconds on first boot as it expands the filesystem.
- Connect the Pi to your network via Ethernet (recommended) or configure Wi-Fi: go to Settings → Wi-Fi → Enable and enter your network credentials using the on-screen keyboard (or a USB keyboard).
- On a PC on the same network, open Windows Explorer and navigate to
\\LAKKA\ROMsor use the IP address:\\192.168.x.x\ROMs. - Copy your ROM files into the correct system subfolder. Lakka uses standard RetroArch folder names:
- NES →
ROMs/Nintendo - Nintendo Entertainment System/ - SNES →
ROMs/Nintendo - Super Nintendo Entertainment System/ - GBA →
ROMs/Nintendo - Game Boy Advance/ - N64 →
ROMs/Nintendo - Nintendo 64/ - PS1 →
ROMs/Sony - PlayStation/ - PSP →
ROMs/Sony - PlayStation Portable/
- After transferring, go to Add Content → Scan Directory in RetroArch, navigate to
/storage/roms/, and run the scan. Your games will appear in the playlists.
Mac users: Finder → Go → Connect to Server → smb://LAKKA. If the name does not resolve, use the Pi's IP address directly.
solution #976
Lakka auto-detects most controllers, but if input is unresponsive you need to trigger the autoconfig or remap manually in RetroArch's input settings.
- Connect your controller via USB (or pair Bluetooth: Settings → Bluetooth → Enable, then scan for devices).
- Navigate to Settings → Input → Port 1 Controls. If the controller is detected you will see its name listed.
- If no autoconfig is applied, go to Settings → Input → Load Autoconfig Profile and select your controller from the list. Lakka ships with autoconfig profiles for hundreds of controllers including Xbox, DualShock 3/4/5, 8BitDo, and Switch Pro.
- If your controller is not listed, select Bind All and map each button manually.
8BitDo controllers: set the mode switch to X (XInput) before pairing. In D mode, buttons may be missing from the autoconfig profile.
USB-connected PS4/PS5 controller: works immediately in Lakka without DS4Windows — Lakka uses the kernel HID driver directly.
solution #977
PS1, Sega Saturn, Dreamcast, and Nintendo DS require BIOS firmware that Lakka does not include. Without the correct BIOS file, games will not launch.
All BIOS files go in /storage/system/, accessible via the Lakka network share at \\LAKKA\System.
- PS1 —
scph5501.bin(USA) orscph5500.bin(Japan) /scph5502.bin(Europe). Dump from your own PlayStation. - Dreamcast —
dc/dc_boot.binanddc/dc_flash.bin(inside adc/subfolder undersystem/). - Saturn —
saturn_bios.bin(JP) orsega_101.bin(US). - Nintendo DS —
bios7.bin,bios9.bin,firmware.bin. Without these, melonDS runs in HLE mode (most games still work). - GBA —
gba_bios.binoptional; most games work without it.
After placing BIOS files, retry launching the game. RetroArch will automatically detect them at launch; no manual path configuration is required in Lakka.
solution #978
Lakka and RetroPie both run on Raspberry Pi, but they suit different needs. Here is when to choose each.
- Choose Lakka when: you want the absolute leanest setup (less RAM overhead, faster boot, no extra OS layer), you are comfortable with the RetroArch interface, or you are installing on low-RAM hardware (Pi Zero 2 W, Pi 2, Pi 3). Lakka uses ~60–80 MB RAM at idle vs ~150–200 MB for RetroPie.
- Choose RetroPie when: you prefer EmulationStation's game-art/scraping experience, you want a more beginner-friendly setup wizard, or you need to install systems that require standalone emulators rather than RetroArch cores (e.g. PCSX2 on Pi 5).
- Performance on Pi 4: both are similar — they run the same RetroArch cores and the same underlying emulators. Lakka's advantage is lower overhead for edge-case systems (Saturn, N64 on Pi 3).
- SSH access in Lakka:
ssh root@LAKKA(default password:root). Change immediately after first boot: Settings → Services → Enable SSH → SSH Password.
Still not working? Lakka logs are at /tmp/retroarch.log — SSH into the Pi and read the log to identify core loading or BIOS errors. The Lakka documentation and community forum are at lakka.tv.
Comments (0)
Sign in to_leave_comment