As a followup: we have some help from @c0rnelius who digged out a solution to that kthread=high load issue (see latest commit / patches in my branch on https://github.com/sven-ola/armbian-build/tree/orangepi-rv2). Maybe this helps for the R2S too?

Just a feedback. Device: Orange Pi 5 Plus OS Image: Armbian_26.2.0-trunk.370_Orangepi5-plus_noble_current_6.18.8_gnome_desktop.img.xz media-player: mpv-.37.0-1ubuntu4 Following the gudide on the first page and added "profile=fast" (in order to have smooth 4K/60 playback) in /etc/mpv/mpv.conf. mpv-.37.0-1ubuntu4 playback 8bit 4K/60 h264 and h265 (hevc) video with vpu hardware accceleration. 10bit h265 or any vp9 and av1 video NO vpu hardware acceleration as far as I can tell. 10bit 4k/60 hevc video -- No vpu hw acceleration 4K/60 hevc -- with vpu hw acceleration. Error messages. Full HD av1 -- No vpu hw acceleration Full HD vp9 -- No vpu hw acceleration Edit: Chromium_v144 can play 8bit 4K/60 h264, h265 and av1 videos with vpu hw acceleration. No vpu hw acceleration with vp9 videos. If not mistaken the current kernel-6.18.8-current-rockchip64 or 6.19-rc8-edge-rockchip64 do not support vpu hw acceleration with vp9 codec.

@Kevin suIf the build error was due to a base files installation error, rerun the build with the same options. It should complete the image compilation. I haven't found a proper fix yet, but rerunning the build should resolve it. I'll update the server image soon.

Hello - if someone get this type of TV Box from ebay (10€ ) - and dont have an GoogleAccount or do not want use the ADB way. The switch is located in one corner but not soldered. Use a small cable to put GND from end of arrow where the pointing of arrow in picture - to do the reset - (during restart just hold some seconds and device did start from SD-Card -) This device also features a RX/TX -Console and Jtag Interface - you find it if you take closer look.

Hi @maxsub we see a high load (== 2.00 on idle) on RV2 and probably other SpacemiT devices. Both on 6.6.99 and 6.18.8 kernels. Caused by an active kthread() that is needed for the communication to the rCPU. Note: rCPU means the extra realtime RISCV-CPU that is powered by the realtime OS we load on boot with CONFIG_EXTRA_FIRMWARE="esos.elf". On the RV2 the high load display has no temperature side effects, but maybe this is not true for R2S. We have a photo of the R2S on the PullRQ (see https://github.com/armbian/build/pull/9299#issuecomment-3811665824 ) so the large cooling cap obviously is necessary? Can you retry with a 6.18.8 kernel with disabled kthread on the R2S? Just rename the last 3 patches in build/patch/kernel/archive/spacemit-6.18 from {016,017,018}*.patch to *.disabled and rebuild. TIA // Sven-Ola