royk

@mamasaur1 It might be that it tries to read the layout of Orange Pi 5 instead of 5b, on the 5-plus I had to enter: echo "BOARD=orangepi5plus" | sudo tee /etc/orangepi-release So probably for yours it should be: echo "BOARD=orangepi5b" | sudo tee /etc/orangepi-release By the way, it's not a good idea to connect a 2-pins fan directly to a gpio pin, too much current. Search for a pwm fan instead that's compatible for a raspberry pi.

@Dbosco I've no idea what the cause is that you can't build Kodi, but now I see that I also have a dtb overlay enabled. You can install it with: armbian-add-overlay vop.dts Otherwise you can try my build, but it's built without the cec lib: https://drive.google.com/drive/folders/1yYlioTYE4X2ItldgcnkgPobLQk1rT6Wb?usp=sharing vop.dts

@Dbosco (Assuming you set the settings in Kodi correct: settings->player->videos->render method Allow using DRM PRIME Decoder=enable Allow Hardware Acceleation with DRM PRIME=enable Prime Render Method=Direct to Plane) Perhaps something is wrong with your ffmpeg, mpp or rga. Try to follow the steps on: https://github.com/nyanmisaka/ffmpeg-rockchip/wiki/Compilation After that run the cmake command for kodi again before make and install.

@Dbosco Build and install with at least GBM Paste the following in /usr/share/wayland-sessions/kodi-wayland.desktop [Desktop Entry] Name=Kodi Wayland Comment=This session will start Kodi media center Exec=env FFMPEG_RKMPP_DEC_OPT="afbc=on" kodi --windowing=gbm --audio-backend=alsa TryExec=kodi-standalone Type=Application Keywords=audio;video;media;center;tv;movies;series;songs;remote; Icon=kodi Otherwise try to stop the window manager and start it manually to see if it gives an error, from login window press: ctrl+alt+F2 -> sudo systemctl stop gdm3 -> env FFMPEG_RKMPP_DEC_OPT="afbc=on" kodi --windowing=gbm --audio-backend=alsa

@Dbosco Yes that's it

@Dbosco The same here until I compiled Kodi with the patch myself and everything works.

@Antimtr Learn some basic commands first: https://ubuntu.com/tutorials/command-line-for-beginners#5-moving-and-manipulating-files sudo rm /usr/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm

I've found information on how to use your own IR remote controller from this site: https://forum.odroid.com/viewtopic.php?f=215&t=44671 In short: 1. Enable logging from the IR kernel module, enter in a terminal: sudo -i echo 1 > /sys/module/rockchip_pwm_remotectl/parameters/code_print dmesg -w 2. Check if your remote is supported by pressing the keys on your remote. It should give you info like: [ 3485.342354] USERCODE=0xfb04 [ 3485.369309] RMC_GETDATA=fd 3. Download the overlay file below and edit the usercode and the code for each key. So for like with the key above it'll be 0xfd 4. Place the header file "rk-input.h" in the same directory as the overlay file. In my case the location is "/usr/src/linux-headers-6.1.43-vendor-rk35xx/include/dt-bindings/input/rk-input.h" 5. Compile and install with: cpp -nostdinc remote.dts remote-precompiled.dts sudo armbian-add-overlay remote-precompiled.dts remote.dts

@Joel @amazingfate Just tried the 6.1 image (Armbian_24.2.4_Orangepi5-plus_jammy_vendor_6.1.43_kde-neon-amazingfated_desktop.img.xz) and installed to the NVME (with only 1 ext4 partition) with armbian-install. Initially it didn't boot, there are no files in /boot. After copying the files from the boot partition of the SD-card to the /boot folder of the NVME and changing the UUID in armbianEnv.txt to the UUID of the NVME it boots.

@greg396 WiringOP? WiringOP isn't mentioned in this topic as it isn't necessary. AFAIK is the green wire (RPM) only feedback of the actual RPM which will not be used. In case of the OPI5 I'm not sure if there'll be 5v on the PWM wire, if that's the case you might break the OPI5 by connecting it to the GPIO pins (3.3v), otherwise you can try it. In case you have the OPI5 plus you can try to connect it as in:

@rix81 Great tip! Although Wayland can't output HDR yet (it's almost there), Kodi under GBM can output HDR and these days it's pretty common to have a HDR TV, at least where I live unless you mean something different with "true HDR". Eitherway it seems like a good alternative but you might still need to edit the dtb for HDR.

@XXXBold Yes check my previous post:

@bolet75 Yeah HDMI -> DVI didn't work for me either. About the audio, HDMI audio doesn't work yet on the mainline kernel, jack input/output would need to be set correctly in the dtb, last time I checked it didn't work either: https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md

@XXXBold You could try updating mpp: git clone https://github.com/rockchip-linux/mpp.git -b develop cd mpp/build/linux/aarch64 nano make-Makefiles.bash add after '-DHAVE_DRM=ON \' the following lines and save (ctrl-x then y) -DCMAKE_INSTALL_PREFIX:PATH='/usr' \ -DCMAKE_INSTALL_LIBDIR:PATH='lib/aarch64-linux-gnu' \ bash make-Makefiles.bash make -j8 sudo make install