Official LE11 Test Images for Amlogic (Kodi-20)

Runs very smooth on Minix u1 however remote and bluetooth not working.

Thanks

Dug out my old Beelink GT King to test LibreELEC. I did a complete install of the original firmware, then tried to get LE to run from microSD card.

I tried both device trees for the King and King Pro, but it never boots into LE. What am I missing?? I tried the "tooth pick" method and "reboot to LibreELEC" app from Android.

thanks.

Hey everyone, First of all awesome job.

I managed to bring back from the dead my old KII Pro (S905) to use it with an old TV I have. Unfortunately the colour space is wrong (the blue appears violet) and I cannot find a way to change it and my old TV doesn't have any option. Any idea where I can change this?

I had been using a nightly from a couple of months ago on my A95x B7n (s905x) box. I had no issues with the wifi. I

downloaded the latest nightly and did a clean install. The WiFi will connect the first time after a boot. However the data throughput is very very low, and if disconnected it will fail to reconnect. I suspect it may have something to do with this change RTL8812AU: update to githash 20220827. Maybe the newer driver has issues?

Is anyone else seeing similar behavior?

Did a fresh install with Minix U1 and using the corosponding .dtb file and Bluetooth and SPDIF are not working.Theres no red indicator light on the SPDIF port. Any suggestions.

Is this change any chance to fix rewinding on Amlogic S912 with DRM PRIME hardware acceleration enabled?

[le11] ffmpeg: fix version output by SupervisedThinking · Pull Request #6880 · LibreELEC/LibreELEC.tv

This PR picks up the pkg version & writes it to the RELEASE / VERSION file which is picked up by the ffmpeg build before FFmpeg version/source:…

github.com

Seeking works well for H264 but other codecs need further development. LibreComputer are likely to sponsor some development work to improve things, but there's no specific schedule at the moment. Until then, things are what they are.

Quote from Linkinsoldier

Thank you for the answer. Looking forward to try this next month!

Just a follow up note: my box reached its end of life before I wanted to try it

Quote

NanoPi-K2 is the one GXBB device that I don't have so it's untested from a boot perspective (but should work the same as any other GXBB board). Feedback is welcome.

Hello Chewitt,

Finally I found time to do a test on NanoPi-K2. Applying the same u-boot patch as for the Odroid-C2 (eth0 delay) works fine for me.

Hi Chewitt,

I have an Amiko A9 Blue TV BOX currently with Android 9. This box has Amlogic S905X3 (A55 64bit). These test images like 'LibreELEC-AMLGX.arm-11.0-nightly...' are compatible with this harwdare?

Thanks,

Zsolti

Quote from slartibartfazz

Finally I found time to do a test on NanoPi-K2. Applying the same u-boot patch as for the Odroid-C2 (eth0 delay) works fine for me.

Do you mean this? https://source.denx.de/u-boot/custodi…ot.dtsi#L32-L36

Also, are you testing boot from an SD card or the eMMC module?

Quote from ZsoltiD

I have an Amiko A9 Blue TV BOX currently with Android 9. This box has Amlogic S905X3 (A55 64bit). These test images like 'LibreELEC-AMLGX.arm-11.0-nightly...' are compatible with this harwdare

There's no dts for that specific box, but they're all much the same so you can try the following dts:

meson-sm1-h96-max.dts

meson-sm1-x96-air-gbit.dts

meson-sm1-a95xf3-air-gbit.dts

Note that you'll need to disable hardware video decoding (and CPU decode) on an SM1 box; the drivers were written for older GX devices and need major work to make them compatible with newer hardware. Anything @ 1080p should be fine but forget 4K. For that reason CE is still a better option than LE on SM1 devices.

Quote from chewitt

Do you mean this? https://source.denx.de/u-boot/custodi…ot.dtsi#L32-L36

Also, are you testing boot from an SD card or the eMMC module?

Exactly. I booted from SD card.

On the subject of dts..

Reference linux kernel github, meson-g12.dtsi and meson-sm1.dtsi make #include reference to meson-g12-common.dtsi.

There appears to be no meson-g12-common.dtsi, only meson-g12.dtsi.

Quote from intelmorino

There appears to be no meson-g12-common.dtsi, only meson-g12.dtsi.

It's definitely there: https://github.com/torvalds/linux…g12-common.dtsi

Quote from chewitt

It's definitely there: https://github.com/torvalds/linux…g12-common.dtsi

Sorry, you're right of course...Just was not seeing it for some reason.

Quote from slartibartfazz

Exactly. I booted from SD card.

Thanks for confirming. Fix has been merged for future u-boot releases: https://source.denx.de/u-boot/custodi…d6d1937075153b4