Sirmalinton

I have tested them and they don't work that much 😞 The kernel is too old, Linux kernel 6.12 lacks many existing mainline patches in 6.14, but even with 6.15 (current development) the board lacks support for the wireless chip or the NPU. For sure one day the board will work with mainline kernel, but it's not now, currently Vendor 6.1 kernel works the best for the board.

Have tested the Orange Pi 5 Ultra and the Armbian Linux v6.1 vendor IOT image for the 5 "Max" model, using the same Max' `rk3588-orangepi-5-max.dtb` FDT file works better than with the rk3588-orangepi-5-ultra.dtb (extracted from the old official Orange Pi image), as surprisingly, dmesg shows less errors with the Max DTB. Tested: ✅ eMMC works. HDMI ports: ✅ Port 1 out works fine. ❓ Haven't tested the port 2 input. Would guess it doesn't work as the Max has bot ports as output. For the AP6611s (SYN43711): ✅ WiFi: works. ✅ Bluetooth: works with some extras, rfkill and bluez: sudo apt install rfkill bluez sudo bluetoothctl status scan on ✅ The NPU works great. Using rkllama: https://github.com/NotPunchnox/rkllama cat /sys/kernel/debug/rknpu/version RKNPU driver: v0.9.8 Based on this, it seems to that anyone looking for an Arbian image for the Orange Pi 5 Ultra can use the Max's Linux 6.1 vendor version, which is the most useful image. For mainline open source versions, it appears like Linux kernel >6.15 or >6.18 will be required.

Moved to:

@serverlesslove, your mount options for the device might not be ideal. If the device is used as a multimedia server, then you can avoid, for example, updating file access times on each read, reducing disk writes and improving performance, using the `noatime` option. Also increase the file system journal commit interval to 120 seconds (instead of the default 5 seconds) using `commit=120`. Check your current `mount` options for the device and try these: ``` defaults,noatime,commit=120,errors=remount-ro ```

Hey, how did you do this? I would like to do the same. Did you replace the 'Max' dtb file content or placed the new file and referenced it from elsewhere (like /boot/armbianEnv.txt)?