royk

@Inis If that's the case you also won't be able to see the emmc memory and pentaHat at the same time after booting from SD From what I can see is that SPI flash and emmc share the same pins, so the bootloader should be written to the emmc

Probably the bootloader, when you boot from SD it uses the bootloader from the SD and when you boot from emmc it loads the bootloader from spi flash or emmc. So update the bootloader and see if it helps

Which kernel? The 5.10 kernel has known issues with USB audio, the 6.1 vendor kernel should work correctly. Further a realtime kernel might help and set pulseaudio at rt priority.

@laurentppol Perhaps you've tried the 6.1.75 legacy kernel which doesn't work with nvme on the Orange Pi 5 like Igor mentioned? Here I have a RT patched kernel with that commit reverted which works with nvme, https://drive.google.com/drive/folders/1r76sUsfG_F8pq0pkzzPgEyzqdRG6fGcz?usp=drive_link The current image should be with a kernel from before that commit but I cannot confirm that.

@Pine Li No I didn't, perhaps it's without thermal limit and it overheats? I had it running continuously for months without issues. Isolating core 5 and 7 and the realtime task on core 7 gave the best result with LinuxCNC. With the 6.1.75 kernel only isolating core 7 is sufficient. I think that the 6.1.75 kernel is better either way. For USB audio the 5.10 kernel gives a lot of (known) problems too. In case you had problems with booting from nvme with the 6.1.75 kernel, Igor pointed to a (revert) commit that created that problem, removing that solves it.

It might be that the OPI5 plus doesn't provide enough power to the m.2 slot for that nvme drive and it still is an power issue like Werner told. The same as with the Raspberry Pi 5 has with many nvme drives. Perhaps it helps to lower the pcie speed, although I haven't tried that.

Not sure if it's documented somewhere, there are some posts about it, but it's in general with these arm boards, mainline support is behind and some will never get (full) mainline support. At least for the rk3588 Collabora is working on it and they got already far. There are also images with the 6.1.75 vendor kernel by the way: https://mirror.vinehost.net/armbian/dl/orangepi5-plus/archive/

@SeanTheITGuy You're not using the vendor kernel, so it's to be expected that not everything works. https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md

@Pine Li You can find the config in the deb file in the boot folder.

@going https://github.com/orangepi-xunlong/u-boot-orangepi/tree/v2017.09-rk3588

@Joel I had the same issue after testing another bootloader, this bootloader from Orange Pi self solved the issue: https://drive.google.com/file/d/1J7fn88rrWoUupGCVTqEs-izYPMA4eTnd/view?usp=drive_link To install: sudo flash_erase /dev/mtd0 0 0 sudo dd if=rkspi_loader.img of=/dev/mtdblock0 bs=4K

@Benjamin Sonntag Have you tried to enter sudo alsa force-reload after connecting the source?

@Mr.Tree Depending on the kernel version. For 5.10.160 there is a rt patched source on the GitHub of Orange Pi, for 6.1.75 you could patch the source of the GitHub of Armbian but the rejected needs to be done manual or 6.11 you could patch as usual but misses some features on the rk3588. From 6.12 rt is mainline so only the right configuration will be necessary. Some of I've compiled you can find here with config, the 6.1.75 is with the rt patched source https://drive.google.com/drive/folders/1JglCIPKvyFwviAEmfyAsL1SmroZcjOvr?usp=drive_link So adding the drivers for your board should be sufficient. The only thing I found out was when I was making a Deb package, somehow the kernel image was compressed and gave an missing arm64 magic error. Simply decompressing solves it. For which board?

Your logs are not visible without logging in at the forum of banana-pi

If the image doesn't include it already you could compile/install ffmpeg from: https://github.com/nyanmisaka/ffmpeg-rockchip From an Orange Pi 5: ffmpeg -hide_banner -encoders | grep rkmpp V..... h264_rkmpp Rockchip MPP (Media Process Platform) H264 encoder (codec h264) V..... hevc_rkmpp Rockchip MPP (Media Process Platform) HEVC encoder (codec hevc) V..... mjpeg_rkmpp Rockchip MPP (Media Process Platform) MJPEG encoder (codec mjpeg) ffmpeg -hide_banner -decoders | grep rkmpp V..... av1_rkmpp Rockchip MPP (Media Process Platform) AV1 decoder (codec av1) V..... h263_rkmpp Rockchip MPP (Media Process Platform) H263 decoder (codec h263) V..... h264_rkmpp Rockchip MPP (Media Process Platform) H264 decoder (codec h264) V..... hevc_rkmpp Rockchip MPP (Media Process Platform) HEVC decoder (codec hevc) V..... mpeg1_rkmpp Rockchip MPP (Media Process Platform) MPEG1VIDEO decoder (codec mpeg1video) V..... mpeg2_rkmpp Rockchip MPP (Media Process Platform) MPEG2VIDEO decoder (codec mpeg2video) V..... mpeg4_rkmpp Rockchip MPP (Media Process Platform) MPEG4 decoder (codec mpeg4) V..... vp8_rkmpp Rockchip MPP (Media Process Platform) VP8 decoder (codec vp8) V..... vp9_rkmpp Rockchip MPP (Media Process Platform) VP9 decoder (codec vp9) ffmpeg -hide_banner -hwaccels | grep rkmpp rkmpp

@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