royk

@Kemal You need to activate them by enabling the correct pwm. See /boot/dtb/rockchip/overlay/ Add the one(s) you need to /boot/armbianEnv.txt at overlays= For example: overlay_prefix=rk3588 overlays=pwm1-m1 pwm2-m1 You can find the right pwm numbers in the manual

@Manuel Carvajal With the 6.1 kernel I don't have issues with docker compose: Home Assistant and Frigate

@Manuel Carvajal Sorry I didn't read that you were using the 6.8 kernel. With the mainline kernel not everything works yet. With the Rockchip kernel (5.10.x and 6.1) it will work.

@Manuel Carvajal Perhaps the overlays are interfering, you could try to remove all pwm overlays from ArmbianEnv.txt. How did you connect the fan? If you connected it correctly it should by default go on when it reaches 50 degrees celsius. If you use the overlay from here you could also change the temperature: https://forum.armbian.com/topic/29253-temperature-and-fan-control-on-opi5/?do=findComment&comment=170456

@Manuel Carvajal https://forum.armbian.com/topic/29253-temperature-and-fan-control-on-opi5/?do=findComment&comment=170261

@lanefu Armbian DDR_BLOB='rk35/rk3588_ddr_lp4_2112MHz_lp5_2736MHz_v1.15.bin' BL31_BLOB='rk35/rk3588_bl31_v1.44.elf' Joshua Riek u-boot-rockchip_platforms += orangepi_5 orangepi_5_ddr := rk3588_ddr_lp4_2112MHz_lp5_2736MHz_v1.11.bin orangepi_5_bl31 := rk3588_bl31_v1.38.elf orangepi_5_pkg := orangepi-5 Xunlong Orange Pi if [[ ${BOARDFAMILY} == "rockchip-rk3588" ]]; then local rkbin_url="https://github.com/orangepi-xunlong/rk-rootfs-build/raw/rkbin/rk35" wget -qnc -P ${EXTER}/cache/sources/rkbin-tools/rk35/ ${rkbin_url}/rk3588_ddr_lp4_2112MHz_lp5_2736MHz_v1.15.bin wget -qnc -P ${EXTER}/cache/sources/rkbin-tools/rk35/ ${rkbin_url}/rk3588_bl31_v1.44.elf @Victor Pecherskiy So to rule out that the newer DDR blob is the problem you could try an Orange Pi image.

@z28z34man See Werner's post

@Victor Pecherskiy Then it seems like a software problem, unfortunately I don't have a 32GB to test it with. And what if you copy the dtb from Joshua Riek's image to your Armbian installation? This is a difference I found but not sure if it's possible to be the cause: https://github.com/Joshua-Riek/linux-rockchip/commit/fdf8d484eccb0949664b78b16e0a275e75c52e0d

@Victor Pecherskiy To rule out if it's a hardware or software problem have you tried an "original" image from orange pi?

@VanGeldon You could add the apt sources in my previous post in the 5.10.160 image. With the linux 6.1.43 image I've got Kodi working, but had to change some things, see here You can try if it works with the kernel build from the source of Joshua Riek's repo: https://drive.google.com/drive/folders/17NT-h0FWKA9irXPBUN883xVoPWganMu-?usp=sharing

@VanGeldon Seems like an old image, try one from here: https://imola.armbian.com/dl/orangepi5/archive/ When you choose an image with amazingfated and Wayland like Gnome or KDE you probably only need to install Kodi. By the way when I search the package with apt search, this is the result: libgjs0g/jammy-updates 1.72.2-0ubuntu2 arm64 So or it's corrected or you've got other sources in /etc/apt/sources.list deb http://ports.ubuntu.com/ jammy main restricted universe multiverse # deb-src http://ports.ubuntu.com/ jammy main restricted universe multiverse deb http://ports.ubuntu.com/ jammy-security main restricted universe multiverse # deb-src http://ports.ubuntu.com/ jammy-security main restricted universe multiverse deb http://ports.ubuntu.com/ jammy-updates main restricted universe multiverse # deb-src http://ports.ubuntu.com/ jammy-updates main restricted universe multiverse deb http://ports.ubuntu.com/ jammy-backports main restricted universe multiverse # deb-src http://ports.ubuntu.com/ jammy-backports main restricted universe multiverse

@Markus Braun In armbianEnv.txt remove the line "overlays=ssd-sata" A ftdi adapter doesn't cost the world and it saves you from a lot of hassle.

@Markus Braun It might be a good idea to check the serial console to see what's going wrong, keep in mind that you need a ftdi adapter that can handle a high baudrate. Things you could check: Did you disable the sata overlay? Did you check if all the files are in the /boot folder of the nvme? Checked if the correct UUID is in /boot/armbianENV.txt and /etc/fstab Removed the SD-card at the first boot from NVME?

@Markus Braun To be sure you could make one ext4 partition. "4 Boot from Flash..." is the right one indeed, after that it should ask to install/update the bootloader which you can agree and otherwise you can choose 7 install/update bootloader indeed. And by the way, the reason why it didn't work in the first place was probably because you forgot to edit /etc/fstab

You should use "sudo armbian-install" to install from the sd-card to the nvme. It should copy the boot partition to the /boot folder, so only one partition. After installing to the NVME you should also write the bootloader to the MTD. If it still doesn't work check if the M.2 storage isn't SATA, otherwise you should write the SATA bootloader. To do that you could use the Armbian instructions from: https://www.reddit.com/r/OrangePI/comments/10iq625/guide_how_to_boot_orange_pi_5_from_sata_m2_ssd/