Lakka installation and setup — Raspberry Pi or PC, ROMs and controllers not working

Medium4 solutions

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.
Last updated 1 week ago0 users reported this issue2
Sign in to interact

Solutions

solution #975

flash-lakka-and-add-roms-via-network-share (sortOrder=1, isMostHelpful)

Flash the Lakka image to a microSD card, boot the Pi, and transfer ROMs to the Lakka network share from your PC or Mac.

  1. 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.
  2. Flash the image to a microSD card (16 GB minimum) using Balena Etcher or Raspberry Pi Imager.
  3. 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.
  4. 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).
  5. On a PC on the same network, open Windows Explorer and navigate to \\LAKKA\ROMs or use the IP address: \\192.168.x.x\ROMs.
  6. Copy your ROM files into the correct system subfolder. Lakka uses standard RetroArch folder names:
  • NESROMs/Nintendo - Nintendo Entertainment System/
  • SNESROMs/Nintendo - Super Nintendo Entertainment System/
  • GBAROMs/Nintendo - Game Boy Advance/
  • N64ROMs/Nintendo - Nintendo 64/
  • PS1ROMs/Sony - PlayStation/
  • PSPROMs/Sony - PlayStation Portable/
  1. 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

configure-controller-in-lakka-retroarch (sortOrder=2, isMostHelpful=false)

Lakka auto-detects most controllers, but if input is unresponsive you need to trigger the autoconfig or remap manually in RetroArch's input settings.

  1. Connect your controller via USB (or pair Bluetooth: Settings → Bluetooth → Enable, then scan for devices).
  2. Navigate to Settings → Input → Port 1 Controls. If the controller is detected you will see its name listed.
  3. 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.
  4. 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

add-bios-files-for-ps1-dreamcast-saturn (sortOrder=3, isMostHelpful=false)

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.

  • PS1scph5501.bin (USA) or scph5500.bin (Japan) / scph5502.bin (Europe). Dump from your own PlayStation.
  • Dreamcastdc/dc_boot.bin and dc/dc_flash.bin (inside a dc/ subfolder under system/).
  • Saturnsaturn_bios.bin (JP) or sega_101.bin (US).
  • Nintendo DSbios7.bin, bios9.bin, firmware.bin. Without these, melonDS runs in HLE mode (most games still work).
  • GBAgba_bios.bin optional; 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-vs-retropie-when-to-use-which (sortOrder=4, isMostHelpful=false)

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.

Experiencing a different problem?Report a new issue to help the community find solutions.

Comments (0)

No other comments yet. Be the first to share your thoughts.

Sign in to_leave_comment

On This Page