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

  • 1. I'll have to ask the upstream kernel maintainers if suspend/resume are supported and expected to work. I won't guarantee it.

    2. In theory the kernel should handle the display device going away and coming back. Kodi only checks things at startup though so might not handle things properly even if things lower in the stack do. In either case the workaround will be (or should be) to run the 'getedid' script so the kernel (and thus Kodi) always sees the display device (via it's EDID data) as connected.

    3. If you are using official nightlies please try the latest image in my testing share and see if that fixes the issue? - I've added some kernel options to make iptables work but can't remember if that change has made it into official nightlies. I'm also unsure if I added all the options for Docker though.

  • 1. I'll have to ask the upstream kernel maintainers if suspend/resume are supported and expected to work. I won't guarantee it.

    2. In theory the kernel should handle the display device going away and coming back. Kodi only checks things at startup though so might not handle things properly even if things lower in the stack do. In either case the workaround will be (or should be) to run the 'getedid' script so the kernel (and thus Kodi) always sees the display device (via it's EDID data) as connected.

    3. If you are using official nightlies please try the latest image in my testing share and see if that fixes the issue? - I've added some kernel options to make iptables work but can't remember if that change has made it into official nightlies. I'm also unsure if I added all the options for Docker though.


    Thank you for your response!! I'll try the getedid script and hopefully it works.

    For #3, I tried the latest image in your testing share for the Quartz Model A that was uploaded on Oct 19. The docker service is still failing :( Seems to not be able to create the nat chain in iptables, at least is a different error haha

    Code
    Oct 29 22:37:37 LibreELEC dockerd[1521]: time="2025-10-29T22:37:37.316172917Z" level=info msg="Loading containers: start."
    Oct 29 22:37:37 LibreELEC dockerd[1521]: time="2025-10-29T22:37:37.548707191Z" level=info msg="stopping event stream following graceful shutdown" error="<nil>" module=libcontainerd namespace=moby
    Oct 29 22:37:37 LibreELEC dockerd[1521]: time="2025-10-29T22:37:37.551579816Z" level=info msg="stopping h3althch3ck following graceful shutdown" module=libcontainerd
    Oct 29 22:37:37 LibreELEC dockerd[1521]: time="2025-10-29T22:37:37.551939733Z" level=info msg="stopping event stream following graceful shutdown" error="context canceled" module=libcontainerd namespace=plugins.moby
    Oct 29 22:37:38 LibreELEC dockerd[1521]: failed to start daemon: Error initializing network controller: error obtaining controller instance: failed to register "bridge" driver: failed to create NAT chain DOCKER: iptables failed: iptables --wait -t nat -N DOCKER: iptables v1.8.11
    Oct 29 22:37:38 LibreELEC dockerd[1521]: Perhaps iptables or your kernel needs to be upgraded.
    Oct 29 22:37:38 LibreELEC dockerd[1521]:  (exit status 3)
    Oct 29 22:37:38 LibreELEC systemd[1]: service.system.docker.service: Main process exited, code=exited, status=1/FAILURE
    Oct 29 22:37:38 LibreELEC systemd[1]: service.system.docker.service: Failed with result 'exit-code'.
    Oct 29 22:37:38 LibreELEC systemd[1]: Failed to start service.system.docker.service.

    I'm just trying to use LE to also stream music from my turntable (which has a USB cable) by HTTP, but the ffmpeg add-on comes with ALSA disabled and docker is not working. I'll continue to investigate any other way to do this with LE (if it's even possible).

  • There are changes to iptables/nftables in recent kernels and I probably need to spend more time on the issue; which won't happen that quickly as I'm travelling for most of the next week.

  • There are changes to iptables/nftables in recent kernels and I probably need to spend more time on the issue; which won't happen that quickly as I'm travelling for most of the next week.

    Ok I understand, thank you for taking a look into it!

  • I finally had some time to test the LE 13 nightly on one of my RK3588 device and I think it is a really good client now even playing more difficult streams than some other devices. Would it be possible to build ffmpeg with libx264 and libx2645 support or are they still too slow?

    Martin