A Retroconsole With Lakka


Having grown up with what are now considered "classic" or "retro" game consoles, as an adult that enjoys video games I find myself in particular still facsinated by these older platforms. Maybe it's because I grew up with them, or maybe it's because of an overall preference, but something keeps pulling me back to the classics. Join me as I discuss setting up a "retroconsole" with modern hardware and FOSS!

What's A Retroconsole?

A "retroconsole" may qualify as any hardware that's dedicated (or mostly dedicated) to emulating or running "retro" games and software. These days, game-makers are even producing official retroconsoles that you can simply plug in and play, offering close to the same experience as the older, original incarnations. Some examples are the NES Classic Edition, Super NES Classic Edition, PlayStation Classic, and the Sega Genesis Mini.

The commercial offerings are fine if you're not interested in tinkering, though it's interesting to note that many of them are confirmed to run free software either in the form of the emulators they use or the OS that they run. 1 2

But what if you don't mind a bit of tinkering- or if you specifically crave the process? Don't worry, you aren't alone!


There's a vibrant community around DIY retroconsoles, including several choices for Linux-based operating systems that are preloaded with various emulators and other features. I'll be looking specifically at two of the more popular options: RetroPie and Lakka. But there are other options out there, I just don't have a lot of experience with using them at this time.


About three or four years ago I purchased my first Raspberry Pi; version 3 model B of the hardware to be specific. I can't recall how I came across RetroPie, but it was the first retroconsole OS I tried out.

Overall, RetroPie is an extremely polished experience that is very easy to just jump into and use. By and large, things work the way you expect them to, and it's reasonably simple to figure out most things just by using it and exploring the UI. I still run RetroPie on two Raspberry Pi 3 model Bs, and it's really great.

When I first wrote this some time back in April, there was not yet a build for the Raspberry Pi 4 - however now there is. As of this writing I've yet to try it, though. The reason I didn't jump on it? Well I've been pretty happy with Lakka, so without further ado!


As it turns out, Lakka already had an installer for the Raspberry Pi 4 even back when Retropie did not. Once I realized this I decided to give it a try. Although both could be considered "retroconsole OSes", Lakka and RetroPie are quite different experiences.

The Good

Starting with the things I really like: Lakka is clearly a curated experience. Emulators/cores are baked into the release, and there's no option to manually update things. Some might see this as a bad thing, but from my perspective it allows for a level of stability that can be lost when one starts tinkering around with things.

Lakka itself doesn't have a UI outside of the Retroarch UI; despite the fact that the Retroarch UI itself has a bit of a learning curve, I actually like this setup. Pretty much everything you need to do can be done from here and it works well. Contrast to RetroPie which has a myriad of UIs that are stitched together 3 Lakka may be a welcome breath of uniformity.

The Bad: Part 1

Lakka, like many other powerful pieces of software, has a bit of a learning curve. A novice user that simply turns it on and tries to work things out may very well have a bit of a bad time. This is especially true for folks that can't or don't normally read documentation for things. It didn't take me long to find people complaining on the Lakka forums about how "complicated" it is, but as far as I could tell most if not all complaints could be resolved by reading the documentation.

As a personal anecdote: I was able to find everything I needed to get started in the project documentation. To me, this whole point isn't actually a "bad thing" but I could see it being tough to overcome for others. Aside from making it clear that folks should take some time to read the documentation, I'm not sure what other approach could be taken to remedy this situation. In any case, I wanted to mention this first as it does affect some folks.

The Bad: Part 2

As a hobbyist tinkerer, I prefer to control my systems down to the small details. I want to configure the system and services in very specific ways, and I've got a collection of Ansible roles to do this for me. But with Lakka, the system is distributed as a SquashFS which means that after the system boots, a good portion of what's under / is read-only.

At first, this irritated me. I need to change the SSH configuration, and other things.. what gives? Once I took a step back and realized the overall vision for Lakka is more of a very specific plug-and-play experience, and that the SquashFS pattern certainly has advantages and benefits, I learned to live with it. And today, as I write this piece, I can say I'm okay with it and even perhaps that I love it.

Another point that was sort of a pain was the fact that Lakka is effectively hardcoded to recognize specific ROMs that are known to be good. The result of this was the majority of my existing ROM collection wouldn't be read by Lakka's generated playlists. Even if you have the ROMs recognized by Lakka's database, things like ROM hacks will likely never be listed since they aren "known good" verification hashes. In the end, I've resorted to making my own playlists that contain ROM hacks and the specific games I might play.

The Ugly

I myself don't really have anything bad to say about Lakka. But there are some rather ugly aspects to the user experience. The main thing that I think is kind of ugly is the process for pairing bluetooth devices.

To be clear: this isn't specifically a Lakka problem but rather one with Retroarch and its UI; there's currently no graphical interface for working with bluetooth. Instead, one has to:

  1. Enable SSH
  2. SSH into the machine running Lakka
  3. Run bluetoothctl
  4. Issue several commands to scan for and pair your device
  5. Disable SSH

I used the 8Bitdo Wireless Controller and Wireless Dualshock documentation as a reference for getting all of this working. It's not really ideal, but in the end it does work and in theory one isn't going to be pairing controllers all the time. Still, if SSH and command-line work isn't something you are comfortable with, this can be quite the task.

The Rest

There are a few things I can't file under "good", "bad", or "ugly" because I'm not yet quite sure about them. This includes:


In conclusion: after some time, even in the face of Retropie releasing for the Raspberry Pi 4, I'm really happy with Lakka. I don't see myself moving to Retropie anytime soon, even though I'm sure that's an excellent experience as well.

I don't find myself playing retro games all the time, but when I do I'm very glad to have a slick setup as I've got with Lakka. Big thanks to the Lakka team!

Footnotes And References

1Sony using open source emulator for PlayStation Classic plug-and-play, Ars Technica: Kyle Orland - 11/9/2018

2Nintendo’s $60 NES Classic Runs Linux, OMG! Ubuntu: Joey Sneddon - 7 November 2016

3Don't get me wrong, the execution is great but having several UIs can sometimes be painful in unexpected ways. I also find it nice to have less of Retroarch itself abstracted from me.

This page was last modified on: 2020-07-26