Werner

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

elaborate

BOARD=uefi-x86

Could you file this as bug here: https://github.com/armbian/configng

May work once rockchip64 has been bumped to 6.15 https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md

Use BRANCH=edge. This should give you 6.14

Install code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } qemu-user-static package and retry

If the desired image combination is not available DIY. That's the build framework made for https://github.com/armbian/build/

Not sure if it is possible to use a local kernel source directory. At least I don't know how to do that. Easiest is probably just to create a repo and define url and branch in board your custom board config.

openssh-server should be installed by default on all images/configurations.

Same answer as above. Without serial logs impossible to debug. It leaves to mention that this board is not officially supported but configuration has been provided by a community effort. Board status is unknown to the core Armbian team.

moved

Rufus was never tested nor recommended. https://docs.armbian.com/User-Guide_Getting-Started/#deploy-the-image