Unofficial LE for RK356x RK3328\RK3399 RK3588(s) RK3576

    Quote from Protx

    Armbian have a dts file/patch for their "edge" 6.18 kernel

    From the amount of /delete-node/ and /*commented*/ items in the file I'd guess it either forward-ports a device-tree file that was originally written for the vendor kernel or is a hand-rolled attempt from an inexperienced developer. It probably works(ish) but six months has elapsed since it was created so (as normal for Armbian patches) the author clearly has no intention of trying to submit support for the board upstream, and that's probably because this dts is too much of a hatchet job to be accepted.

    https://github.com/armbian/build/pull/8348 <= The "VPU (Unable to test due to lack of VAAPI support)" comment is amusing :)

    The Armbian PR also confirms the board needs an out-of-tree Ethernet driver to work. For both board and Ethernet support I'll be happy to cherry-pick patches submitted to kernel mailing lists, or items from known kernel contributors (who are trusted to follow-through on upstreaming them) but that's my minimum threshold.

    I have an old NanoPC-T4 that has been running LibreELEC for a long time but now has to be rebuilt.

    I downloaded the most recent build here (LibreELEC-ARMv8.aarch64-13.0-devel-20250618160230-e5590fa-rk3399.img) and flashed it a booted and it works well except for Add-ons. When I try and look at add-ons from the LibreELEC repository I get a "Could not connect to repository." error.

    I assume this is because the build I'm using is an old alpha build and the repository doesn't support older alpha builds. I tried downloading the add-on I need (PVR Tvheadend add-on) directly from Kodi, but that also doesn't work, unsurprisingly I guess, since the only binary available is for the Omega release, the Piers releases are all source code only.

    Is my only way forward here to cross-compile the add-on source for the Piers release of the add-on from: https://github.com/kodi-pvr/pvr.hts ?

    Quote from myrkle

    I assume this is because the build I'm using is an old alpha build and the repository doesn't support older alpha builds.

    As a general rule we keep the current and current -1 repo versions for development images online, but we remove older repos to reclaim disk space. The repo version aligned to that image has probably been deleted.

    You should be able to run touch /storage/.update/.nocompat and manually 'update' to a current LE13 nightly. The compat check needs to be skipped as the image name changes from ARMv8 to RK3399.

    Quote from chewitt

    You should be able to run touch /storage/.update/.nocompat and manually 'update' to a current LE13 nightly. The compat check needs to be skipped as the image name changes from ARMv8 to RK3399.

    Thanks for the response. Tried that and set "Automatic Updates" to manual, but the Update Channel list is empty, as is the Available Versions list. Rebooted, no change. Is that what you meant by "manually 'update'"?

    Quote from myrkle

    Is that what you meant by "manually update"?

    As nightlies can contain breaking changes we don't publish a 'releases.xml' file so neither manual update from the GUI or auto-update are possible. You need to download the update file to /storage/.update and reboot.

    Quote from chewitt

    As nightlies can contain breaking changes we don't publish a 'releases.xml' file so neither manual update from the GUI or auto-update are possible. You need to download the update file to /storage/.update and reboot.

    Ahh, I see. Tried that using the latest nightly for the rk3399. It did update, the add-on repository is available, and I was able to install the PVR add-on I use. Unfortunately, the audio is unpleasant now: crackling more-or-less continually. This wasn't happening with balbes build I updated from. Is it likely to be different for other nightlies, or is this one of the differences with balbes build (using manufacturer's DTB?)?

    AFAIK the images Oleg was building are/were largely the same as official nightlies (other than nightlies now being on newer kernels and other packages). I've not heard of audio issues with current nightlies. Are you using HDMI output or the analogue port?

    I wouldn't expect it to cause issues, but it's always a possibility. Perhaps install the multimedia-tools add-on from the LE repo and then use alsamixer to reduce the output level on the master volume controls. I'm wondering if the signal is just over-driven.

    Well, I installed the multimedia-tools add-on and ran alsamixer, but it shows the message "This sound device does not have any controls.", so no help there (though incomplete support for HDMI on the nanopc-t4 might explain the crackling sound?).

    Is it possible to enable the analog audio jack for the nanopc t4? Searching the forums I see info on the rpi4 audio jack, but no general info.

    Ahh, the lack of controls is due to the alsa conf that we are currently using. Not much I can do about that right now due to lack of time and also alsa being far from something I understand.

    The analogue jack is not currently described in the NanoPi T4 device-tree. It should be possible to add, but this would need some research with schematics and vendor kernel images that I also don't have time for right now.