Werner

https://docs.armbian.com/User-Guide_Board-Support-Rules/ support a whole soc family would be impossible. For example a vendor could do a poor implementation of something which could never work but we "support" it and people complain why it doesn't but there would be literally nothing we could do about.

Hi ssd or nvme? Both needs different handling kernel? edge? vendor? current?

https://askubuntu.com/questions/1371732/what-is-the-purpose-of-cgroup-enable-cpuset-cgroup-enable-memory-cgroup-memory-1 Without further research the answer here mentions that the flags in question may be specific for RaspberryPi, hence won't work on other kernels/boards.

All images are specifically made for the board. Some share the same kernel package since they are from the same soc family (for example, there are a lot of boards using the rk3588/s soc so they can have the same kernel package. Board's components are defined in device tree). Sample board config: https://github.com/armbian/build/blob/main/config/boards/orangepi5pro.csc BOARD_FAMILY is rockchip-r3588 The sources config: https://github.com/armbian/build/blob/main/config/sources/families/rockchip-rk3588.conf Pro, max and ultra are community contributions and for now entirely unsupported since there is also no support from the vendor for us for these whatsoever to make its software better.

Try looking for hints here: https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/rockchip/ They use mali blobs for hw en-/decoding.

I assume should work with vendor. Maybe missing node in device tree. Maybe missing firmware blobs or same as above. Expected since neither SPI nor eMMC are present by default. Direct boot from NVMe isn't support by any Rockchip soc.

But still possible You can also switch manually to a fixed mirror from the list here: https://docs.armbian.com/Mirrors/

Since you are on current you cannot expect a major bump until the next LTS kernel is released. current will receive security fixes only. If you want something more recent you need to switch to edge kernels which follow non-LTS mainline kernel releases.

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

fixed

Either ignore expired cert or wait until we fixed it.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Any up to date Armbian image using vendor kernel should include rknpu kernel driver oob. Mainline npu driver is still pending. You can try to backport it. Check rockchip kernel mailing list.

Hi We all started at some point. But overall prepare for some frustration We don't support this device. Support was added via community effort. May work, maybe not. We don't know nor do we track status of such configurations. Regarding OPi5+. It is using - in terms of ARM socs - a fairly recent SoC, the Rockchip RK3588. Mainline support is far from feature-complete. Will take a few additional years to complete. If you need an almost feature-complete kernel, you have to use vendor branch which is based on Rockchip BSP. current (Linux 6.12.y LTS at this time) has basic support for rk3588 and is good enough for general server application, though for your usecase might not be enough. This branch will receive fixes only but no new features. edge may be sufficient. When using some graphics related I suggest to use an image with mesa-vpu extension included. Also there a two ways to make use of it: - We backported the open source Panthor driver into vendor. Can be enabled via device tree overlay (check code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-config) - Using proprietary mali blobs is also possible. I think Jellyfin has a tutorial how to setup those: https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/rockchip/

Between days and month. Depending on time, issues, regressions,... Refrain from asking for ETA. Putting pressure on developers who give you something for free is abusive.

Check journalctl/syslog for clues.

If nvme is correctly recognized code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-install should do.

https://debug.armbian.de for obtaining low level logs to debug further.

I'd probably try to code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } dd the Armbian image directly onto sda and boot.

rk bsp branch has been bumped to .115 (or rkr5.1 as they call it) a few weeks or month ago, so fairly recent.

This kernel does not come from radxa but from Rockchip themselves as BSP. However we put lots of work on top of that:https://github.com/armbian/linux-rockchip This will basically be a thing until mainline catches up. Though there will be a few years to go in that matter.

I'd probably start with comparion the device trees of both images and check for altered/removed nodes related to audio.

Check assets at community releases as csc hw is ususally not on mirrors but on GH: https://github.com/armbian/community/releases

Seems working nicely: https://paste.armbian.com/eniduhodih