martivo

Seems this issue has been fixed, I am able to use the new kernel now with video playback. I did not do anything different...just update/upgrade.

Should this also work with the 5.10.160-legacy-rk35xx kernel?

It does boot up and graphical user interface works, but I now get segmentation fault with any video playback with ffplay or mpv (using ppa:liujianfeng1994 repo). So anyone switching kernels should be aware that there might be video playback issues.

Here is my ansible for running a small LCD over I2C https://github.com/martivo/armbian-orange-pi-5-ansible/tree/main/roles/oledinfo

curl https://raw.githubusercontent.com/orangepi-xunlong/linux-orangepi/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/overlay/rk3588-i2c5-m3.dts -O rk3588-i2c5-m3.dts armbian-add-overlay rk3588-i2c5-m3.dts reboot So this is how you can make the fix permanently. If you use different Kernel or arch then it might be a bit different location in the github repo. # uname -a Linux opi 5.10.160-rockchip-rk3588 #1 SMP Fri May 26 08:01:48 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

@Efe ÇetinThank You for pointing me to the right direction! What was simple was to restore the boot/dtb/rockchip/overlay/rockchip-rk3588-opi5-i2c5-m3.dtbo file from backup and reboot....now it works again. Having to rumble through a 3.8Gb git repo to get some dts files from it just to get I2C working is really ugly solution in my personal oppinion. I am a bit puzzled about this - it is a basic functionality of Orange Pi 5 SBC and I understand Armbian tries to support these SBCs. Also Armbian provides SBC specific images. Is there a reason these dts files can't be at least packaged into Armbian OPI5 image that are related to OPI5? So it would be easy to call the "armbian-add-overlay" command at least? Is it some licencing issue? I did manage to find it in this folder in the git repo after some digging https://github.com/orangepi-xunlong/linux-orangepi/tree/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/overlay rk3588-i2c5-m3.dts - no idea if it's even the file I need. I assume during next update the overlay will break again since I just restored the file...I guess I will give it a shot once it breaks again in the hopes to fix it permanently.

After updating my Orange Pi 5 I no longer can use the "opi5-i2c5-m3" overlay in /boot/armbianEnv.txt to activate and use i2c. Seems the file (or any ohter "opi5-i2c*") is gone from /boot/dtb folder. #uname -a Linux 5.10.110-rockchip-rk3588 #1 SMP Sun Apr 2 14:30:48 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux Is there a new or different procedure to activate i2c? Do I need to install a separate package for it? Or build the entire OS? Anyone else having the same issue? It does detect some i2c devices(0,10,2,6,7,9), but they don't seem to be related to the GPIO headers, prevoiusly I could also use (1,3,5). # ls -l /dev/i2c- i2c-0 i2c-10 i2c-2 i2c-6 i2c-7 i2c-9 I would like to use physical pins 3 and 5 - these were until now working fine.

@VidorThis post might be helpful.

I am having the same occasional freeze issue(mouse won't move, all windows frozen in place, movie audio plays but picture won't move), but I found out that unplugging the HDMI and plugging it back in seems to recover desktop withour rebooting. I have only tried this a few times so far since I only realized it recently. Can someone confirm that it solves the freeze issue for them too?

@WarHawk_AVG The onboard nvme drive KingSpec M.2 2242 NVMe 512GB (theoretical max speed 600 MB/s in specs) Here the PCI 2.0 lane of the OPi 5 is defenetly not helping and its a cheap e-bay drive... root@:~# dd if=/dev/nvme0n1 bs=1M count=10000 of=/dev/null 10485760000 bytes (10 GB, 9.8 GiB) copied, 50.3259 s, 208 MB/s The Samsung 850 EVO SSD over USB in the enclosure (theoretical max speed 540 MB/s in specs): root@:~# dd if=/dev/sda bs=1M count=10000 of=/dev/null 10485760000 bytes (10 GB, 9.8 GiB) copied, 27.1413 s, 386 MB/s The Software Raid in on the 6TB WD Red HDD (max theoretical should be 2x speed of WD Red) root@:~# dd if=/dev/md0 bs=1M count=10000 seek=100000 of=/dev/null 10485760000 bytes (10 GB, 9.8 GiB) copied, 53.1439 s, 197 MB/s Single WD Red HDD (theoretical max by spec 180 MB/s) root@:~# dd if=/dev/sdd bs=1M count=10000 of=/dev/null 10485760000 bytes (10 GB, 9.8 GiB) copied, 57.9577 s, 181 MB/s So in case of the Spinning hard drives the harddrive itself will be the bottleneck. In case of SSD the enclosure is the limiting factor. I am happy with it, more than Ill need for my purposes.

My HDMI 1.4 LG TV works just fine at 4k 60Hz on HDMI port.

Here is a video of my Orange Pi 5 setup. Hopefully someone finds it helpful!

@Marvin RöschI am not sure if it is relevant here, but I was also unable to get surround sound to work in pulseaudio - I resorted to using a52(DolbyDigital) alsa plugin(dcaenc is also an option). It created pulse audio sinks that will send compressed audio over HDMI or DP resulting in Surround sound working. Ansible role that I used on the OPi5 to get Surround sound to work: https://github.com/martivo/armbian-orange-pi-5-ansible/tree/main/roles/hdmi-audio-dts-a52 https://github.com/alsa-project/alsa-plugins (a52, branch v1.2.6, https://github.com/alsa-project/alsa-plugins/blob/master/doc/a52.txt) <-currently using due to my TV lacking DCA support https://github.com/darealshinji/dcaenc <-i know it works but not using atm.

I would guess too that you need to erase SPI. For me this video was very helpful It also covers how to erase SPI flash and initialize it again. Or you can read the orange pi 5 manual https://drive.google.com/drive/folders/1Bre2q0bGgXQuQlYaYDMvwstpvtHLmcgX it covered also the MaskROM recovery steps in case you cant boot from any media anymore.

The current quick fix/workaround is to clone and build from fork of mpp. It has this commit in addition https://github.com/martivo/mpp/commit/38afa760be814dbbf32019b6c588be8304c1e486. Or keep the old version of mpp1. git clone --branch force-dma32-fix https://github.com/martivo/mpp.git cd mpp/build/linux/aarch64 ./make-Makefiles.bash make -j4 cp mpp/librockchip_mpp.so.0 /usr/lib/aarch64-linux-gnu/librockchip_mpp.so.0 This fix is undone when librockchip-mpp1 package is updated, you might want to mask it. (sudo apt-mark hold librockchip-mpp1)