royk

@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/

@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

@XXXBold Perhaps because you're using a kernel from February while the FFmpeg you're using needs recent made fixes. Try a newer kernel/image. https://fi.mirror.armbian.de/archive/orangepi5/archive/Armbian_23.8.1_Orangepi5_jammy_legacy_5.10.160_xfce_desktop.img.xz

I had the same issue with an old Samsung TV/monitor and use a HDMI->VGA adapter as workaround.

@vale Yeah, I found out it was because I was sitting on the remote. But seriously In case you've got the OPi5 plus it is possible that the IR receiver receives a signal from another remote, I remember that mine did with a remote, I thought the one of LG. Perhaps it's better to disable the remote in the DTB by default, for now you could try to put a piece of tape over it or disable it if it's a module.

@Seb042 In the manual on page 215/216 you can see a better picture, the colored one you'll only see the functions and pin names and beneath that picture you'll see more details with gpio numbers. The prefix you need to use depends on the filename like I explained in my previous message. ls -l /boot/dtb/rockchip/overlay/*spi* The overlay files I've got there begins with rk3588 so that's what you need to use as prefix. If you also need another overlay that begins with orangepi-5-plus then use that as prefix and rename the spi overlay you'd like to use from rk3588-.... to orangepi-5-plus-.... Or to prevent it from getting overwritten after a update, even better to download the dts from: https://github.com/armbian/linux-rockchip/tree/rk-5.10-rkr6/arch/arm64/boot/dts/rockchip/overlay and install it as useroverlay: sudo armbian-add-overlay your-download-spi-overlay.dts Can you post your armbianEnv.txt ?

@Seb042 Yes and it's m0 by the way. So assuming you've got the overlay with filename "rk3588-spi4-m0-cs1-spidev.dtbo" you should have the following in armbianEnv.txt: overlay_prefix=rk3588 overlays=spi4-m0-cs1-spidev