royk

Yes, when you out it in device tree mode: https://github.com/edk2-porting/edk2-rk3588?tab=readme-ov-file

This one I made for the Orange Pi 5, perhaps it works also on yours: https://drive.google.com/drive/folders/1r76sUsfG_F8pq0pkzzPgEyzqdRG6fGcz These for RK3399 https://drive.google.com/drive/folders/12VfNmKC30vxNzaNAk2EN5sHDfeCnnzYX For the 5.10.160 kernel there's an already rt patched source from Orange Pi: https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-5.10-rk35xx-rt And when you apply an rt patch in Armbian, you should remove the local version patch. Armbian doesn't support local versions

@Jacob Olness The SD-card has priority, otherwise it would be difficult to recover.

The boot directory is on the nvme, so likely the btrfs file system is not supported by the bootloader. Please put in your title that you've solved it

Maybe it's secure boot that's enabled in the bios why the unsigned module won't load?

@ArmBoy1988 I gave you already the answer if you want full hardware decoding support. Maybe you don't like it, but it's the only way. So a Flatpak won't work unless it's specifically built with rkmpp support. At this moment using the vendor kernel and build Kodi with FFmpeg with rkmpp support it the way to go.

@Gullik To me it sounds like a problem with Mesa. This happens with an x86 box that I have after a kernel update or something with a self compiled Mesa, then in the folder /usr/lib64 the files libGL.so.1, libGLESv2.so.2 and libEGL.so.1 will be relinked to the original files (with a higher version number). In that case relinking them solves the issue. Enter "ls -ltr" in the lib64 folder to see the newest files under

While playing a video press the letter "O" to check if you're using hardware or software decoding. For hardware decoding you need to compile Kodi with FFmpeg that supports rkmmp hardware decoding and with gless. For 10 bit decoding you should run Kodi from GBM. You'll also need to change a setting in Kodi under video, set render method to "Direct to plane". So install FFmpeg as described at: https://github.com/nyanmisaka/ffmpeg-rockchip/wiki/Compilation Build Kodi as described at: https://github.com/xbmc/xbmc/blob/master/docs/README.Linux.md#41-configure-build with as cmake command for example: cmake ../kodi -DCMAKE_INSTALL_PREFIX=/usr/local -DCORE_PLATFORM_NAME="wayland gbm" -DAPP_RENDER_SYSTEM=gles

You could check the UUID with blkid /dev/mmcblk0p1: UUID="b23e98d0-700e-4a09-88b6-95675ee524f5" Then check if this is the same in /boot/armbianEnv.txt and /etc/fstab

@Mr.Tree Yes you can find the compiled one also on the OneDrive. If your application checks /sys/kernel/realtime you'll need a small patch from 6.12 which you can also find on the OneDrive. But it needs the following config: - CRASH_DUMP [=y] && ARCH_SUPPORTS_CRASH_DUMP [=y] && KEXEC_CORE [=y] - PROC_KCORE [=y] && PROC_FS [=y] && MMU [=y]

@BOFFBOY Just boot from SD, enter in terminal: sudo armbian-install Choose 1. Boot from MTD flash - System on .... After that it asks you to also install the bootloader to MTD flash and choose yes

@laurentppol It might be that the links have not been correct in /boot cd boot sudo ln -sf uInitrd-6.1.75-rt23 uInitrd sudo ln -sf vmlinuz-6.1.75-rt23 Image And of course the dtb from the 6.1.75 kernel must be used. Perhaps downgrading the kernel also helps, in case you don't use real-time applications that might be the better option: https://forum.armbian.com/topic/47090-radxa-rock5c-pentahat-and-emmc/#findComment-206251

- Using the panthor driver might help, the 6.1.75 kernel with the panthor overlay enabled. - If Xorg is the trouble maker, try wayland with Sunshine server and moonlight-qt as client. - Disable hw acceleration in de xorg config file, although here it never crashed for months

@Inis Funny that it's likely caused by a "fix" of Radxa themselves for the 5 itx board. But great that you found the problem