Hi,
this project looks awesome.
(When) will Raspberry Pi 4 be supported?
5schatten has merged several pull requests I created to fix building for a RPi4 but a few build errors remain. Furthermore, nothing has been tested regarding performance. I haven't actively worked on the RPi4 build errors for a while as I recently moved which has taken up most of my free time.
Assistance is welcome.
Have a look at my latest changes in dev-rr branch and see if you can build and run Qt now. My changes were primary ment for lima & panfrost but should fix your mesa related problems too. At least I was able to compile AMLGX with lima/panfrost & all of my packages including Qt but neither SDL2 nor Qt can properly pick up the KMS/DRI device... well I guess the driver needs some fixing then. But the RPi4 driver should be in way better shape.
Cool. Hopefully, I can check it out soon.
Regarding Pi4:
I still can't get Qt to build so I can't get Skyscraper or Pegasus to build.
However, if I disable those two in OEM then the build completes. This time Kodi seems to function properly and retroarch works. I haven't tested emulationstation or any emulation cores since I didn't load any roms yet. I'll try that out soon.
Display MoreI now have Pegasus and Skyscraper left to work through compile errors (due to qt/gstreamer gl errors).
Aside from those, I was able to build a full RPi4 image. Pull requests have been sent for everything that I have been able to fix so far.
I tried to boot it just now and the initial boot was ok (resizing the partition) but after rebooting the libreelec-rr logo remained on screen. Though I could hear kodi navigation sounds when I hit up, down, left, right, and enter keys.
Progress...but definitely not usable on a RPi4 yet.
Built again with all the latest changes. It now boots but the screen gets scrambled shortly after booting, making it unusable. I am guessing this is largely due to the state of RPi4 support in LibreELEC which in turn is largely based on RPi4 in Linux 5+ kernels. At least for now, I can take my time getting the full build to compile for RPi4.
I cannot get VLC to compile for the RasPi4. No matter what I try I get "cannot find -lGL" errors.
It's clearly an opengl related error due to the pi switching to Mesa with the 4.
Since I'm still learning the build system, do you have some thoughts or guidance to provide?
I now have Pegasus and Skyscraper left to work through compile errors (due to qt/gstreamer gl errors).
Aside from those, I was able to build a full RPi4 image. Pull requests have been sent for everything that I have been able to fix so far.
I tried to boot it just now and the initial boot was ok (resizing the partition) but after rebooting the libreelec-rr logo remained on screen. Though I could hear kodi navigation sounds when I hit up, down, left, right, and enter keys.
Progress...but definitely not usable on a RPi4 yet.
I cannot get VLC to compile for the RasPi4. No matter what I try I get "cannot find -lGL" errors.
It's clearly an opengl related error due to the pi switching to Mesa with the 4.
Since I'm still learning the build system, do you have some thoughts or guidance to provide?
Btw. can you test my PR if it works for you? Makefile: added devices for Amlogic & Rockchip platforms by 5schatten · Pull Request #74 · libretro/mupen64plus-libretro-nx · GitHub
I tested this PR but it threw an error with your patches. When I reviewed your patches, it looks like it was the same as the PR. So, I tried building with your latest commits and using your patch. This failed. Then I tried to build with this PR and deleting your patches. This failed.
I did however find a branch that m4xw was working on for Pi4 support.
Using this commit, deleting your patches (the second patch caused an error with the commit), and adding these lines to package.mk, it built successfully:
I have no RPi4 so I can't really build & test images for one. Also the support is actually right WIP since it uses a VideoCore VI with mesa3d. It will take some time until libretro cores have been updated & stop using old vendor blob stuff.
I attempted to build an image for a Pi 4 last night and surprisingly only about 7-10 packages did not build. I have not tested to see if anything runs yet as I want to get everything building before I even test it.
For a first attempt and no changes being made, it seems quite promising. I will work with you on a Pi 4 image if you have time/interest in building it.
Edit: just noticed MagicSeb posted a pi4 build with retroarch.
I've uploaded testbuilds for Generic & RPi to Index of /testing/
Both are based on latest master with a huge load of updated packages packages: mega bump by MilhouseVH · Pull Request #3537 · LibreELEC/LibreELEC.tv · GitHub & many libretro cores & standalone emulators have been bumped too so feel free to test and report if something is broken. Both should boot fine btw. so don't worry about that.
Which branch are you currently basing on? libreelec-9.2?
FBAlpha is dead, FBneo will be the active branch, all the people working on alpha have moved on after what Barry did
Related to Capcom arcade stick?
Well that's Amlogic Kernel hack "magic".
"Magic." The reason why I would like to move away from my amlogic box but haven't found the right balance of performance, price, and support yet.
Edit: I fixed the issue. I'm not totally sure how, but I think it maybe when I reset the ALSA configuration (from your rr-config add-on) to default and then rebooted. I'm leaving the original up in quote just in case it needs to be reviewed further.
QuoteDisplay MoreEverything has been working great...until...yesterday.
I am using a generic s905x tv android box. I originally had a clean install of your build from a few months back (most recently running 20190315). After updating to 20190326 a couple days ago, audio stopped working with some (all?) videos with MP3/AAC stereo only audio streams. The surround sound (5.1) files still play without any issue. MP3/AAC audio only files seem to play just fine though.
I have tried to reset audio settings to defaults in Settings > System > Audio
and reset video settings to defaults in Settings > Player > Videos
and set ALSA in your configuration add-on and then reset again to default (with reboots in between)
I downgraded back to 20190315 and then upgraded to 20190326 once again, testing in both versions. All with the same results.
Any help would be greatly appreciated.
My logfile can be found here: http://ix.io/1euu
I did notice the below line while Kodi is opening a video files.
- fixed duplicated bluetooth devices in LibreELEC-settings
This has been an annoyance since Krypton and maybe even Jarvis. Thank you!
Well I think that's something everyone should decide for yourself. A path like /storage/roms/*system*/savefiles would be okay if you prefer a somewhat clean directory. I've stored my roms in a central place and play games from different systems so for my usecase it makes sense to store the savefiles in this central point too.
Cool, I'll just do this for my own setup and not submit a pull request.
5schatten Would you be interested in having a dedicated folder for savefiles and savestates (at least for retroarch for now)? This helps to keep rom folders less cluttered.
This is easy to do via the retroarch config file. In fact, Lakka does this.
savefile_directory = /storage/savefiles/
savestate_directory = /storage/savestates/
Here are the folders I used but open for other ideas (I think I followed escalade or niabi's build)
savefile directory = /storage/.config/retroarch/savefiles/
savestate directory = /storage/.config/retroarch/savestates/
If you like the idea, I can submit a pull request for it.
I guess so if someone gets me a S905/S912 device to test my builds ¯\_(ツ)_/¯
Vanilla LE9.0 should build fine for several Amlogic devices as listed here https://github.com/libreelec/libreelec.tv/tree/master/projects/amlogic/devices
but as I said I do not own S9xx devices so even if I could build it I couldn't test and debug it.
I decided to try to compile your project for S905. With a small bit of effort...most packages built. A few will need some changes but I suspect it will not be difficult, especially since I have done a lot of this work on my own build previously. If I get everything built, would you be interested in a PR? If so, I have some questions for you about how you would prefer to handle some things, would you like to handle via DM or via the forum?
Note: I did not try to burn the image to an sd card yet so I can not yet verify that it's working but I will test before submitting a PR if you are interested.
Well I had a look into your fork and I would really recommend a clean start. AFAIK you mostly copied escalades packages but those use the LE8.2 build system which has been changed in LE9.0 also you have some... well call it interesting way to sort the packages.
Interesting? Lol. Thanks for having a look. It's important to know that the Leia branch is what I am currently working on.
QuoteAbout moonlight I guess you have just cloned my repo and copy'n pasted my files? Well won't work. You have to check the dependencies for each package and make sure these packages were build as they should be build. For example moonlight needs opus shared libs but you haven't changed the upstream LE9.0 opus package so it still builds as static lib.
Exactly what I did. I didn't think about other packages you may have changed having an impact. Great call out. Thank you.
QuoteIf you really want to create your own fork then first dig through mine or escalades commits and try to understand what we added and changed to make it work, otherwise you'll run into a lot of problems and building the projects will fail. I did this myself, forked escalades repo and updated / changed it according to my needs until I had enough knowledge about the underlaying system so I could "hard fork" it and rebase it on my own agains LE9.0 upstream code.
This is basically what I'm doing. I only commented on the S905 since I had some basic stuff working on it already. Otherwise, I was just trying to understand how to get moonlight working. And you've given me some great direction, so again, thank you.
Basically my fork could work too for S905 but first some project specific args have to be passed to several packages. For example Retroarch has specific build args for generic & RPi and IMHO S905 will then need some specific stuff too. Same goes for emulation cores, most of them have specific make flags according to the project. If an emulator needs optimizations for S905 this has to be passed too.
I believe I implemented a few changes for s905 but didn't spend much time optimizing. It all seems to work at reasonable speeds so I haven't spent anymore time on it.
