Article there: http://www.lakka.tv/articles/2017/10/11/lakka-21-rc5-released-with-improved-dolphin-support-and-experimental-asus-tinkerboard-support/
4 Likes
@Kivutar Do you have instructions for generating an XU4 emmc image (or even better, do you have one available) ? I tried your instructions here without success.
Also, if I understand you correctly, the issue with emmc is the sd2emmc adapter provided by HardKernel. However, if that’s the case, I would have expected that booting to ubuntu on the XU4 via SD, and then imaging the emmc from there would have worked. Am I missing something?
Regardless, thanks for all your hard work. I’m excited to try RC5 tonight!
Cheers,
–John
Hmm now I’m not able to mount my CIFS shares anymore:
mount: mounting //192.168.1.125/MEDIA/roms on /storage/roms/nas/ failed: Operation not supported
This was fine in RC4. Even manually via cli it’s not possible. Any ideas?
I’m stuck on the flower screen either when after I install Lakka or run from live USB. My gpu is NVidia gtx 1070.
@Sniper21777 : you are using Pascal gpu family so we will have to wait that we use at least kernel 4.12 for generic platform.
@hermanchunky : on which platform ?
Orangepipc does not appear to boot [blackscreen] lakka 
tested with armbian, retrorangepi and then to see if I was installing lakka correctly, I installed it on my rasp pi 3 with no problems.
do you know when you guys will import kernel 4.12 into lakka?
Thank you for your tests! Please report bugs on the issue tracker: https://github.com/libretro/Lakka-LibreELEC/issues
Some comments (not sure if they are proper bugs):
- The update failed on my RPi 3, first time it has ever happened. I had to re-flash.
- The database updates made a mess of my GB/GBC playlists, they merged into one and GB games now have rather unfriendly tags (such as (W) (V1.0) [!]). This is not Lakka’s fault but in my opinion just looks bad, and also breaks thumbnails.
For now I went back to RC4, which has worked great.
Regards, Marco
Lakka 2.1 RC5 update failed in S805 with RC4 .
First time running Lakka on my S805 M201D, i did my setup with version 2.0 without any problem, updated to version 2.1 RC4 by means of manual update, placing the img.gz file into .update folder, turned on the box and updated with no problem, but when i try to do the same procedure with 2.1 RC5, it ends with a fail message telling me that the release is not compatible with my hardware.
I rechecked the page, to see if i miss downloaded the file, but notice that the RC5 file size is bigger than the ones i used before. I’m going to try a clean install on a spare SD card and see if it works.
I can confirm that I am seeing the same issue with the Gameboy and Gameboy Color roms. They were merged together and for some reason GBC roms are using the GoodSets naming convention rather than the No-Intro naming convention. So not only are they merged but it’s all mixed up with some showing “(USA)” and some showing “(U)[!]”.
To all the users who got an upgrade issue: please create a single shared bug report on github.
I tested an upgrade from 2.0 to 2.1-rc5 on RPi and it worked fine.
So we need to discuss and test this together in a separate thread on github to find the cause of this and fix it.
I created a bug report for the Gameboy issue.
GoodTools GoodGB was broght in, and it unfortunately doesn’t split GB from GBC. Let’s talk over at https://github.com/libretro/libretro-database/issues/537 about a fix.
Yup, Lakka 2.1 RC5, on S805 cant be updated from 2.0 or 2.1 RC4, it needs to be setup from zero.
What version of FB Alpha is used in the RC5
You can see the commit id there https://github.com/libretro/Lakka-LibreELEC/blob/Lakka-V2.1-dev/packages/libretro/fbalpha/package.mk#L22
And the version here https://github.com/libretro/fbalpha/blob/907d3c6ee2e938ec7fe9b1e65b8a416c60a57cae/src/burner/libretro/libretro.cpp#L9
I is v0.2.97.42
I just wanted to point out that it might be useful to check out the LibreELEC release notes:
LibreELEC (Krypton) 8.2.0 RELEASE
I had issues accessing the Lakka SMB shares from Android and Kubuntu (but not Windows 7) and found out that it’s for security reasons.
I got around this by adding the following line to /storage/.config/samba.conf under [global]:
min protocol = CORE
This is against what’s recommended but might be useful for some, since I saw posts in various places regarding shares not working in 2.1-RC5.
The share works just fine. I just navigate from windows computers to \\ipaddressoflakkabox and it works just fine.
Yes, as it should. This only might be a problem for people using other OSes (and Windows XP and below, I believe).