LE13 Testing for RK3288, RK3328, RK3399, RK3566, RK3568, RK3576, RK3588

    Quote from chewitt

    I've been running tests on an RK3576 Rock-4D board. The kernel codebase is still maturing in places but I think this will be a nice sweet-spot for LE use. The boards are less-featured than RK3588, which makes the boards cheaper, but the peripherals that have been omitted are all things that LE has no use for, while the media capabilites are essentially the same.

    I have my eye on the NanoPi R76S because it could possibly free up an R6C which you so kindly added exp. support for :saint:

    Looking at it its very small (2.3"x2.3"), so as a router its great, but I wonder if it has any LE potential compared to the Rock-4D.

    edit:

    I could not find a case for the Rock-4D, does it fit a PI-case by any chance?

    Edited once, last by Elicity (September 3, 2025 at 10:23 AM).

    Just information.

    ASUS tinker board S R2.0 (RK3228) is working good.
    image: LibreELEC-RK3288.arm-12.90.1-tinker.img.gz
    HDMI display(FullHD)/audio OK, KODI is shown, H264/H265 video is played.
    I use the following sample video.
    https://kodi.wiki/view/Samples - 4K (UltraHD) & HDR Formats -
    7. HDR 10-bit HEVC 59.94fps (MP4, Camp by Sony)

    Note.
    I will test with ROC-RK3328-CC when it arrived on middle Sep.

    Edited once, last by Yasai-san: microSD boot - Maskrom mode (September 3, 2025 at 1:12 PM).

    Hi, guys!

    Does Anybody have Banana pi m7 (armsom sige7)? I have. I've tried to use an image LibreELEC-RK3588.aarch64-12.90.1-armsom-sige7.img.gz

    But it doesn't want to boot.

    The most interesting the image LibreELEC-RK3588.aarch64-12.90.1-rock-5c.img.gz does. But during loading there is an error about mount disk uuid=5899aaae-1fbd-4452-8807-236cf98c8c98.

    Quote from sinbadxiii

    The most interesting the image LibreELEC-RK3588.aarch64-12.90.1-rock-5c.img.gz does. But during loading there is an error about mount disk uuid=5899aaae-1fbd-4452-8807-236cf98c8c98.

    The DTB is different between those 2 boards. Most likely storage isn't (or not 100%) recognized and therefore fails to boot. My 2cts.

    You could try to franken-boot it. I did something like that here.

    Quote from chewitt

    No idea, I have no RPi cases kicking around at the moment (other than RPi5 cases which definitely aren't the same).

    I looked but couldn't find a good case to match the board which could be a reason why it has such a competitive price. Its the R76S for me, once I have convinced myself to part with my money that is :D

    Quote from chewitt

    EGL rendering is always a workaround not a solution, as it's not as efficient as DRMPRIME rendering.

    Agreed, I read up on Patch v2 that enables x264/x265 decoding and there are still some small issues. WIP /shrug

    Edited once, last by Elicity: Merged a post created by Elicity into this post. (September 4, 2025 at 6:56 AM).

    Quote from chewitt

    I've been running tests on an RK3576 Rock-4D board. The kernel codebase is still maturing in places but I think this will be a nice sweet-spot for LE use. The boards are less-featured than RK3588, which makes the boards cheaper, but the peripherals that have been omitted are all things that LE has no use for, while the media capabilites are essentially the same.

    RK3576 actually has a better (or at least newer) multimedia capabilities (VOP3 for RK3576 vs VOP2 for RK3588). Not sure if the all the code to make use of it are upstreamed already though.

    Quote from treedav

    Can anyone provide some instructions on how to get the wifi chip on an orange pi 5b going?

    Run "journalctl | paste" after boot and share the URL generated so we can see which device-tree is being used, and assuming it's one where WiFi/BT are described, what chipset is being used and what firmware might be needed.

    Quote from chewitt

    Run "journalctl | paste" after boot and share the URL generated so we can see which device-tree is being used, and assuming it's one where WiFi/BT are described, what chipset is being used and what firmware might be needed.


    Latest orange pi 5b device tree had no wifi/BT description. (linux v6.17-rc4)
    https://github.com/torvalds/linux…orangepi-5b.dts (add)
    https://github.com/torvalds/linux…orangepi-5.dtsi (add)

    By Orange Pi 5B User Manual, it has AP6275P device.
    > WIFI+BT Onboard WI-FI6+BT 5.0 module (AP6275P), supports BLE

    Armbian has patch file for orange pi 5b wifi. I can't find about BT patch.

    build/patch/kernel/archive/rockchip64-6.16/rk3588-1072-arm64-dts-rockchip-add-AP6275P-wifi-to-Orange-Pi-5B.patch at main · armbian/build
    Armbian Linux build framework generates custom Debian or Ubuntu image for x86, aarch64, riscv64 & armhf - armbian/build
    github.com


    Sorry I have no orange pi 5b. (I have orange pi 5 and orange pi 5 Max)

    treedav I've picked the Armbian patch that Yasai-san flagged, and pushed an updated image to my test share. On reboot the card should now be detected, but firmware will be missing. Check the system log for errors and filenames.

    See https://wiki.libreelec.tv/how-to/add-firmware for instructions on manually adding firmware. This repo has firmware files with a blind guess at the needed filenames: https://github.com/chewitt/brcmfm…re/tree/ap6275p

    https://forum.armbian.com/topic/36744-or…dComment-214649 suggests this might not be enough, but best to try. If it does work I can send the patch upstream and add the firmware to our collection. Please share the journal log, e.g. journalctl | paste and share the URL.

    Quote from chewitt

    treedav I've picked the Armbian patch that Yasai-san flagged, and pushed an updated image to my test share. On reboot the card should now be detected, but firmware will be missing. Check the system log for errors and filenames.

    See https://wiki.libreelec.tv/how-to/add-firmware for instructions on manually adding firmware. This repo has firmware files with a blind guess at the needed filenames: https://github.com/chewitt/brcmfm…re/tree/ap6275p

    https://forum.armbian.com/topic/36744-or…dComment-214649 suggests this might not be enough, but best to try. If it does work I can send the patch upstream and add the firmware to our collection. Please share the journal log, e.g. journalctl | paste and share the URL.

    firmware/ap6275p at master · orangepi-xunlong/firmware
    Orange Pi specific firmware. Contribute to orangepi-xunlong/firmware development by creating an account on GitHub.
    github.com

    the orangepi-xunlong github - firmware repo has ap6275p firmware files.
    These may be able to use.

    Note.
    This device seems pcie device not sdio.

    I did some testing on the PINE64 Quartz64 Model B (rk3566) with my standard set of test files:

    1. Device Tree 101 - 1080p x264
    2. Big Buck Bunny (BBB) - 1080p x264
    3. BBB - 1080p x265 10-bit (re-encoding of 2)
    4. BBB - 2160p x264
    5. Bo Burnham - Can't Handle This - 1080p x264
    6. Bo Burnham - Kill yourself - 1280x640 x264 10-bit
    7. Bo Burnham - White W0man's Instagram - 1080p x264 *
    8. Elementary S01E01 - 1280x720 x265 10-bit

    *) Mangled the title a bit as it contained a disallowed word ...

    Test results:

    1. Played, but starting took a while (possibly due to debug logging and its size (>1GB)?; without debugging it seemed to just play fine)

    2. Played fine

    3. Failed to start

    4. Audio played, but picture 'refreshed' once per 30 secs or once per minute?

    5. Played fine

    6. Audio played, but no picture. The wait screen (kind of) flickered

    7. Played fine

    8. Failed to start, just wait screen. No screen flickering though


    I uploaded a compressed debug log (both FFmpeg and 'Video' components enabled) to the location chewitt knows. It's 8.2MB compressed, but uncompressed it's 256MB

    Quote from diederik

    I did some testing on the PINE64 Quartz64 Model B (rk3566)

    I also noticed that Bluetooth didn't seem to work. Which was kind of a relieve as it also doesn't work on my 'normal' (Debian) system.

    The controller is there and it gives the impression that it (can) work ... but I've not been able to actually make a connection with anything.

    Quote from chewitt

    Feedback on issues related to distro packaging and specific boards (boot issues, missing hardware etc.) is useful.

    Using the latest build from 03-september, wifi on a Radxa Zero 3w appears to not be recognized. A usb ethernet adapter does work.

    https://paste.libreelec.tv/intent-monarch.log

    Tried to paste the kodi.old.log into pastebin but it was too large. I assume that log was from the previous boot, which did not include the wired ethernet adapter. (If that matters?)

    Quote from grackle

    wifi on a Radxa Zero 3w appears to not be recognized

    The initial dev samples of the Zero3W had a Broadcom WiFi5 chip. The release versions were 'upgraded' to WiFi6 with an AIC8800 chip that has no drivers in the upstream kernel, which is probably why the WiFi/BT nodes required to use a driver that doesn't exist have not been added to the device-tree file.

    Radxa have an AIC8800 driver in their repo: https://github.com/radxa-pkg/aic8800 but LE has no interest to add downstream vendor drivers to codebase unless there is a visible/known plan to upstream them (so we can drop them once upstream).

    chewitt I saw that Armbian is starting support for the R76S. So I'm gathering info/files on the device before it gets here. Hopefully by the end of next week. I figured I could maybe franken-boot an RK3576 image. Which one do you recommend:

    1. LibreELEC-RK3576.aarch64-12.90.1-roc-pc.img.gz
    2. LibreELEC-RK3576.aarch64-12.90.1-rock-4d.img.gz
    3. LibreELEC-RK3576.aarch64-12.90.1.tar