Posts by swever

  • [RK3566] LE for Pine64 Quartz64 Model A

    Ok a workaround I found for the profile creation issue is that I restored a backup from the Kodi app I have installed in my Android TV with the profiles created and now switching between the profiles work. There's probably something wrong in the process of creating a new profile from this version of LE.

    Also when I turn off and then back on my projector, the remote controller no longer works with LE (CEC stops working). I wanted to try to fix it using the getedid script, but the getedid command doesn't seem to exist in this LE. I am trying the latest nightly build. Is there a way I can add or run the script manually? Or is there a possibility to add the getedid command to LE? I just probably need to run the 'getedid create' command to fix this issue.

  • [RK3566] LE for Pine64 Quartz64 Model A

    Hello. Just wanted to share some issues I am having with the latest nightly build for the Quartz64 Model A.

    1. I have the 8 GB of RAM version, but LE is indicating that its only detecting around 4GB of RAM in the System Information. Also in the logs I saw this line, so I don't know if this is on purpose:

    [    0.000000] Memory limited to 3838MB


    2. When creating a new profile, the new profile is able to login successfully, but changing back to the master user makes the OS freeze. After that I rebooted and now I'm only able to login to the new profile, if I try to go to the login screen or try to login to the master user, it freezes again.

    I tried watching the logs for any error message, but there is none. Basically logging in to the master user after creating a new profile is impossible. I investigated a little and saw a similar situation during the LE version 10 era, so I don't know of this can be related? That situation was fixed with this commit.

  • [RK3566] LE for Pine64 Quartz64 Model A

    Quote from chewitt

    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).

  • [RK3566] LE for Pine64 Quartz64 Model A

    OK I have been using the latest nightly build for RK3566 and I've been able to watch videos natively!! I tried playing HDR and SDR videos and all plays smoothly, even 4K. I'm also able to control LE using CEC with my projector's remote control successfully. Thank you!

    I only have some issues at the moment:

    1. When I try to suspend the system, it gets stuck with a loading icon in the middle of the screen and I have to manually reboot. Is this a normal bug of LE or is this related with the nightly releases for the RK chips?

    2. I set LE to not suspend when the projector turns off (because of issue #1) and when I turn my projector off and then on, the CEC no longer works and LE doesn't react to my remote controller.

    3. I installed the Docker add-on and the docker service is not able to start because of an iptables error.

    Error: iptables v1.8.11 (legacy): can't initialize iptables table `nat': Table does not exist...

  • How to add wifi drivers?

    I was having the same issue with my WiFi USB dongle and was able to fix it, so I'll just add it here if it helps someone. I am using LE 13 for RK3566 (I have a Quartz64 Model A)

    chewitt thanks for the instructions on how to see the log. I was able to do it and found this:

    Code
    [   11.871724] rtw88_8821au 3-1:1.0: Direct firmware load for rtw88/rtw8821a_fw.bin failed with error -2
[   11.871760] rtw88_8821au 3-1:1.0: failed to request firmware
[   11.962647] rtw88_8821au 3-1:1.0: failed to load firmware
[   11.962671] rtw88_8821au 3-1:1.0: failed to setup chip efuse info
[   11.962676] rtw88_8821au 3-1:1.0: failed to setup chip information
[   11.962854] rtw88_8821au 3-1:1.0: probe with driver rtw88_8821au failed with error -22
[   11.962982] usbcore: registered new interface driver rtw88_8821au

    As you said, the firmware file rtw88/rtw8821a_fw.bin was missing, so I just downloaded it from here and then I inserted the file in this location: /storage/.config/firmware/rtw88/rtw8821a_fw.bin.

    In my case the firmware folder didn't exist so I had to create it. And after rebooting, voilà! Now my dongle works as expected.