JohnU

So I tried running Armbian Minimal/IoT version with kernel 6.1 and the fan is operating normally (tested it with the stress command). I didn't realize i was working with two different kernel versions. Sometimes you just need another set of eyes to look at a problem. Thanks for the help, cheers!

desktop: $ uname -a Linux opi5p-cl1 6.1.115-vendor-rk35xx #1 SMP Fri Nov 21 14:02:48 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux minimal/iot: $ uname -a Linux orangepi5-plus 6.12.58-current-rockchip64 #3 SMP PREEMPT Thu Nov 13 20:34:41 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux Good call, I'm going to download the other Minimal/IoT image that uses kernel 6.1 and give it a try. Will let you know what happens.

I have several Orange Pi 5 Plus SBCs, and I have found that the fan works correctly if I install the Ubuntu desktop (Noble/XFCE) version of Armbian. But if I install the Minimal/IOT version of Ubuntu (Noble) the fan stays on constantly. I have not had any success trying to build my own orangepi-5-plus-pwmfan.dtbo (overlay), and I also tried copying the /boot/dtb/rockchip/rk3588-orangepi-5-plus.dtb file from the desktop version over top of the minimal version and rebooting, but my orangepi-5-plus would not even boot. it would be really nice if one of the maintainers could take a look at this and see if the minimal version is missing some component. I did see the following error in the journalctl -xe output after booting the minimal version: Jan 12 15:07:56 orangepi5-plus kernel: fan53555-regulator 0-0042: FAN53555 Option[10] Rev[1] Detected! Jan 12 15:07:56 orangepi5-plus kernel: rockchip-thermal fec00000.tsadc: Missing rockchip,grf property Jan 12 15:07:56 orangepi5-plus kernel: fan53555-regulator 0-0043: FAN53555 Option[10] Rev[1] Detected! Thank you, John

I had the same problem with /var/log filling up. It was causing Jellyfin playback to fail. I tried disabling armbian-zram-config service in the config file, but then the /var/log got mounted to an armbian-ramlog device that is the same 50M size. So I ended up changing the armbian-ramlog size to 500M in it's config file and re-enabling the armbian-zram-config service in it's config file. Now it's once again mounted to /dev/zram1, but it's now 500M.