royk

My advice is to respond to replies you received in duplicate posts from you. That could help others too instead of just receiving.

@Paulo da Silva With the Raspberry Pi you're not really installing it but just write an image to a sd, that does also works right away with the OPI. When you bought an Orange pi you should've known that it's fairly new and it's not the same as a raspberry. Then while Armbian makes these devices much more usable and give great support you're complaining here. If you want to complain go to the manufacturers forum, on this forum you could ask for help You're probably doing something wrong and that's what you could expect when you begin with something new. "without information on the company's website"??? https://orangepinet-5898.kxcdn.com/wp-content/uploads/2023/07/OrangePi_5_Plus_RK3588_user-manual_v1.5.1.pdf Especially look at: http://www.orangepi.org/orangepiwiki/index.php/Orange_Pi_5_Plus#How_to_use_the_debugging_serial_port http://www.orangepi.org/orangepiwiki/index.php/Orange_Pi_5_Plus What's the brand/type of the NVME? and which steps did you take? @vandyman Although I did this at the beginning I've learned that dd (Raspberry Imager) to a nvme/ssd is not recommended and you don't need the official Orange Pi image. With the Orange Pi 5 plus I didn't even had to update the bootloader to make it boot from nvme.

No problem, btw you could enable other PWM pins except the PWM 3 pins. In the DTB you could see that PWM3 controls pin pwm3m1. When you enable the other PWM3 overlays PWM3 might have been pwm3m0, pwm3m2 or pwm3m3 (I believe the last one you've added). So always check which one you need and only activate that.

@nihilowy It does work here with a 2 pins fan with LED and with a 3 pins fan of Noctua, both connected with the black wire to 5v on the fan header and red wire to PWM on the fan header. Did you use the first overlay I had posted? orangepi-5-plus-pwmfan.dts Compiled/installed with sudo armbian-add-overlay orangepi-5-plus-pwmfan.dts ? Checked if the temperature was high enough to trigger the fan? Perhaps you've still enabled all PWM pins? This could conflict with the fan PWM pin, the fan PWM pin is enabled by default. Try to disable all other overlay files in /boot/armbianEnv.txt and see if that helps. (Except sata if you need that one of course) You could rise the temp quickly with: stress --cpu 8 or less if you want to see how it behaves at lower temps. With armbianmonitor -m you could see the temp. (C.St. is always 0/7 and doesn't matter) If you do also want to edit the temp settings you could use this overlay orangepi-5-plus-pwmfan.dts

@alex.i See https://forum.armbian.com/topic/29253-temperature-and-fan-control-on-opi5/?do=findComment&comment=170418

It turns out that the fan connector doesn't give a real PWM signal (tested with pwm signal tester for laser module) and needs PWM values between 0-100. If you really want to use the PWM wire (be sure it's 3.3v and not 5v) and use the above overlay, with the other PWM pins it needs values between 0-255.

The connector is made for a 2 wire fan, so GND of the fan to PWM and the + wire to 5v. Sorry I see I've made a mistake, actually I've connected: FAN Connector Black wire > 5V Red wire > PWM I've also just tested a pwm fan the same way without the yellow wire connected and does work correctly. But this fan needed different values than my other fan, so you'll need to test a few values. Don't try to connect the red wire to another PWM pin than the one at the fan connector! If it goes at full speed immediately at 50 degrees, lower the values of the following line: cooling-levels = <0 65 75 85 95 100>; If the fan only starts from 55 degrees, then raise the first value until it just starts to spin and add 1 or 2 to be more secure it will spin all the time at that level. The following overlay should work with a pwm fan that's compatible with the Raspberry Pi (3.3v). In this case 5v to 5v, gnd to gnd and pwm to pwm14m2 sudo armbian-add-overlay orangepi-5-plus-pwm14m2-fan.dts Don't forget to remove the previous overlay from /boot/armbianEnv.txt After editing the values just run the above armbian-add-overlay command again and reboot. orangepi-5-plus-pwm14m2-fan.dts

@OP5_PLUS It has a 5v driver, the black wire to 5v and red wire to pwm. The result I had with the fan I've got is that the fan didn't spin at 50 and at 55 degrees it was spinning at 100%. I've just looked at it and to me it seems like the cooling-levels should be between 0-100 instead of 0-255. I've made an overlay which you could edit and compile/activate with: sudo armbian-add-overlay orangepi-5-plus-pwmfan.dts With this overlay it works correctly with my fan, so post your results here and perhaps it could be edited in the source. orangepi-5-plus-pwmfan.dts

@bottlelid Yes I do also have that problem from the moment I upgraded to the latest kernel. The video is in front of everything (until you press "X" or stop on the remote control). Another strange thing I found is that when the display is at 59.9hz instead of 60hz I've got no audio over HDMi, this was never a problem before. But again I didn't have time yet to look at what could be the cause of these things.

@mo123 Perhaps using a newer version of MPP, as far as I can see Batocera uses a version from March. That Kodi commit is reverted eventually. Lately I had compiled Kodi with that FFmpeg version and somehow HDR didn't work. I didn't look further into it. With FFmpeg from JeffyCN, latest version of Kodi and MPP, recent Armbian kernel, HDR does work here. AFAIK the rk3588 doesn't support HDR10+ and Dolby Vision. The ones I've tested are regular HDR and HLG.

@Tony3 It depends on the config of your current kernel if the ethernet adapter will work: cat /boot/config* | grep CONFIG_R8125 If that module is not enabled then the easiest thing to do is recompile with your current config and enable the R8125. You could first check if the modules you were missing aren't already in the default config. And you'll need to select the right DTB of course in armbianEnv "rk3588-orangepi-5-plus.dtb". If you don't have that file, download a minimal image and copy to /boot/dtb/rockchip/

@ZZY For ffmpeg check: https://github.com/hbiyik/FFmpeg rkmppenc is what I use with tvheadend to transcode to hevc. https://github.com/rigaya/rkmppenc For gstreamer you'll need to add the repo of amazingfate. Search packages in apt with "apt search ..."

Read OttawaHacker's post of 2 days ago: https://forum.armbian.com/topic/29352-udev-for-i2c-and-gpio/

I don't have a GoPro 11 but just tried 2 4k 120fps samples and they play fine in Kodi (GBM) 1: Stream #0:0[0x1](eng): Video: hevc (Main 10) (hvc1 / 0x31637668), yuv420p10le(pc, bt709), 3840x2160, 163257 kb/s, 119.88 fps, 119.88 tbr, 120k tbn (default) Not exactly the same format though. You could try to update mpp: https://github.com/HermanChen/mpp Default installs in /usr/local/ so add the following lines to "make-Makefiles.bash" (otherwise it still uses the previous installed version) -DCMAKE_INSTALL_LIBDIR:PATH='lib/aarch64-linux-gnu' \ -DCMAKE_INSTALL_PREFIX:PATH='/usr' \ In Wayland I'm only able to play the file decoded with rkmppenc to ffplay, but with high cpu load. ./rkmppenc --avhw -i file.mp4 -o - | ffplay -

@pazzoide Are you sure your fan needs 3.3v? if you want it to be controllable you'll need a pwm fan like this one: https://www.amazon.com/GeeekPi-Raspberry-Controllable-Adjustment-40x40x10mm/dp/B092YXQMX5/ Or a transistor and resistors. The way I did was using a pwm fan (3 pin) and editing the dtb by making a patch with some lines copied from Radxa. Although it does only trigger the fan at a certain temperature, it doesn't regulate the speed as it should, it's missing some lines that were later added. I'll make a new one soon. The pwm fan in this dtb is set at pwm13 and triggers the fan at 60C , pwm13 has to be enabled with the overlay. The thermal policy has to be on step wise, you could check this with: cat /sys/class/thermal/thermal_zone*/policy If it's something else you could set the following line in /etc/rc.local before the last line (exit 0): echo step_wise > /sys/class/thermal/thermal_zone*/policy rk3588s-orangepi-5.dtb orangepi-5-pwm13.dtbo

Already tried a virtual display? https://help.realvnc.com/hc/en-us/articles/360004324217-Beginner-s-guide-to-Virtual-Mode#what-is-virtual-mode--0-0

@hammsandwich21 Did you apply the ffmpeg commits and reverted the Kodi commit?

Try to format the disk so you've got 1 ext4 partition and install with armbian-install. Choose no when it asks if you want to install/update the bootloader to MTD. Check if you've got the overlay sata in /boot/dtb/rockchip/overlay In case the filename is orangepi-5-sata.dtbo then in armbianEnv.txt you should have the following lines: overlay_prefix=orangepi-5 overlays=sata

@hammsandwich21 For FFmpeg there are only 16 commits: https://github.com/FFmpeg/FFmpeg/compare/master...JeffyCN:FFmpeg:master For Kodi I reverted this commit to keep HDR working: https://github.com/xbmc/xbmc/pull/23116/commits/e278e3a4b990d5de7afe9642b6b39c7eeff999bb But I'm not sure if that's still necessary.

@Alejandro Pinar Ruiz Where do you see 10-15% I see 1.4% I guess the 12% system load is only a snapshot.

@hammsandwich21 This one should build fine, I had Kodi build from the master repository of 4-11-23, had to edit one or a few things (not sure). In a few minutes I will add that link in this post. FFmpeg 6 https://mega.nz/file/K5oESSoa#bbuzHfFCqqNYdbl8b2aZ32SAb3S89pTU3ZBQRYjJZbE How I build it: configuration: --prefix=/usr --extra-version=0ubuntu0.22.04.1+rkmpp20300327 --toolchain=hardened --libdir=/usr/lib/aarch64-linux-gnu --incdir=/usr/include/aarch64-linux-gnu --arch=arm64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-opencl --enable-opengl --enable-sdl2 --enable-librsvg --enable-libdc1394 --enable-libdrm --enable-chromaprint --enable-frei0r --enable-libx264 --enable-libdrm --enable-rkmpp --enable-version3 --disable-libopenh264 --disable-vdpau --enable-shared --enable-version3 --disable-doc --enable-libaribb24 --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libtesseract --enable-libvo_amrwbenc --enable-libsmbclient Kodi 21a: https://mega.nz/file/q4gFULjT#AgD0S-H0UCkoQKMAj0nV0W6ULWYNuBpSH3m9TJra87s Not sure which options I chose but you could find them in the cmakecache CMakeCache.txt

@hammsandwich21 Wait a minute I could upload the source of ffmpeg 6 I use

@hammsandwich21 I would try without "-DWITH_FFMPEG=/usr/bin/ffmpeg -DENABLE_OPENGL=ON" HDR movies do only play on GBM (with the right settings in Kodi) so you might want to enable that one too. Although with the Mali blob driver I was able to play HDR on Wayland as SDR. ffmpeg: --enable-omx ???

@Minh I've seen a GitHub of someone who added hw encoding to ffmpeg but can't find it atm. Perhaps this will help you: https://github.com/rigaya/rkmppenc Not sure if this one works for rk3588: https://github.com/jjm2473/ffmpeg-rk

@CryBaby Seems to be true for this specific chip indeed. Explanation: https://techblog.willshouse.com/2015/01/07/how-to-tell-if-pl-2303hx-pl-2303-is-3-3v-or-5v/ That something works doesn't always mean that it's good, I've seen people connecting 5v to 3.3v pins, (probably something between 4 and 4.5v) and didn't have problems for a few months and eventually it broke. But you're right about the PL-2303HX.