Closed armadillu closed 1 year ago
There is no big community reporting about Lakka performance on their RG351MP, so your post made me curious.
How exactly did you get Lakka to boot on RG351MP?
Did you change dtb file with the other one from different os to make it boot? Do you have volume buttons working? What about N64 emulation? Can you get it running?
In my case, I had to get dtb from AmberElec and modify extlinux.conf to make my device to boot into Lakka.
@blindm0use worked out of the box with the release, just copy image into an sdcard and it works. All buttons work, including volume, out of the box. The device vibrates at boot. Amberelec works too, without the boot vibration. I tried the dtb swap too (use the one from amberelec in lakka), but as you report, with this dtb the volume buttons didnt work.
That seems unusual, because my RG351MP would not boot with the dtb of Lakka that comes with the image...I get kernel panic instead
@blindm0use there may slightly different hardware versions?
Sadly, I am not aware of that, but Kernel Panic can be a result of different hardware revision
Used this dtb and got volume buttons working, but the volume is not balanced with the gain. At max the sound starts cracking
To add to this different HW versions discussions, here's a pic of the board inside my rg351mp. It has "RG351MP_v1.3 2021-03-30" printed on it.
Theme issue take it to ozone developers
As there's no rg351mp support for the newer versions of lakka, we may as well close this now...
Support is coming with mainline kernel and mesa to OGA family but not everything will be supported as there are a lot of devices and a lot less developers with them
Oh that's great to hear! I will check again on the new version (when is testable) and report back
I can't get the
ozone
GUI to look decent using lakka. I am using an rg351mp with the latest release, and I also tested the last nightly build (3.x). Ozone looks squeezed (as if the screen was 16:9, but its 4:3) and way too small. The rg351mp has a 640x480 display.I tried ssh'ng in and starting with
retroarch --verbose
to see some logs, and I see retroarch is creating a 640x480 gl context. It almost seems like ozone is rendering into a 16:9 fbo and blitting it to the 4:3 screen somehow, it also seems to render too slowly (I get 37fps in ozone). But the logs say otherwise:Note that RGUI and XMB render normally. Trying to increase the Scale Factor only allows me to go up to 1.42, but the text is still too small. Going beyond 1.42 doesnt increase the text size.
I tested EmuElec and ozone renders as you would expect, and renders at 60fps.
dmesg
shows that screen can run at 640x480@60 and 640x480@149, I am unsure which one is chosenI tried forcing a video mode in the kernel boot arguments with
video=DSI-1:640x480@60
but I get the same look in ozone.