Search the Community

If someone is interested can easy setup OledStats for OrangePi5 and SSD1306 Hardware: Orangepi5 SSD1306 OLED display Software Armbian Jammy KDE Neon 6.1.43 Files attached in ZIP archive device.py PixelOperator.ttf setup.py stats.py How to: 1) add overlay wget https://raw.githubusercontent.com/orangepi-xunlong/linux-orangepi/orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/overlay/rk3588-i2c5-m3.dts sudo armbian-add-overlay rk3588-i2c5-m3.dts reboot 2) connect OLED display to I2C5 M3 Pins SDA + SCL (pins 1(VCC),2(SDA),3(SCL) and 5(GND)) check connection sudo i2cdetect -y 5 must be detected 3c value 3) install needed libs sudo apt-get install i2c-tools python3-smbus python3-pip python3-dev python3-pil 4) download main karabek project git clone https://github.com/karabek/OrangePi-OLED cd OrangePi-OLED rename old setup.py mv setup.py setup_old.py 4) create new setup.py or copy from ZIP archive nano setup.py #!/usr/bin/env python from setuptools import setup setup( name="ssd1306", version="0.1.0", author="Richard Hull", author_email="richard.hull@destructuring-bind.org", description="A small library to drive an OLED device with either SSD1306 or SH1106 chipset", license="MIT", keywords="raspberry pi rpi oled ssd1306 sh1106", url="https://github.com/rm-hull/ssd1306", packages=['oled'], ) 5) Start setup.py sudo python3 setup.py sdist 6) copy generated folders to python3 dist packages sudo cp -r OrangePi-OLED/oled/ /usr/local/lib/python3.10/dist-packages/ sudo cp -r OrangePi-OLED/ssd1306.egg-info/ /usr/local/lib/python3.10/dist-packages/ 7) replace device.py file with file in ZIP archive in dist-packages oled folder cd /usr/local/lib/python3.10/dist-packages/oled mv device.py device_old.py 9) copy stats.py and font file PixelOperator.ttf from ZIP archive start stats.py file sudo python3 stats.py result should be same as on RPI device picture Orangepi5_OLED.zip

Hello! I installed the latest Gnome Noble image from the very top of the Orange Pi 5 page, it has Wayland and generally is working really well - it even is doing higher refresh rate for my monitor and is smooth! HOWEVER the one big thing I noticed right away - my screen never turns off anymore And my Power options are missing such settings? It only gives the option to blank, which still is running my monitor at 100% brightness and a horrible solution Where is the setting to turn my screen off after 5 minutes? NOT blank, but into standby mode Worked on the previous Cinnamon version but that version lacked higher refresh rates and I think was not wayland Thank you!

Hello everyone, I use my Orange Pi 5 board to run Open Media Vault with Wireguard installed. But there is a known issue with Wireguard that, when installing it, you have to manually reinstall the correct kernel into the board again, otherwise it won't be able to boot. However, ever since it has been installed, during apt update / apt ugrade of my board, it keeps recognizing the wrong kernel to be updated and changing the symlinks inside the /boot/ folder, rendering the board unbootable. If I see this happening, I can change the symlinks and it works normally after that. However, sometimes the symlinks changes unnoticed and I cannot boot anymore. I have to take the SD Card to another device, chroot into it, and change the links again. How can I prevent this from happening again and let the updates recognize the correct kernel version? In the image attached, you can see that uInitrd is pointing to uInitrd-6.11.5+bpo-arm64-16k, which is incorrect. I have to manually point it to uInitrd-6.1.99-vendor-rk35xx Sometimes, dtb and Image point to the wrong files as well. I have tried holding back linux-image-arm64-16k from being updated with apt hold, and I have also turned off automatic kernel updates inside armbian-config, but there is still something more to be done. I have just run apt update / apt upgrade, and I think that the part that is breaking my boot is the Processing triggers for initramfs-tools, as can be seen logged below: Setting up linux-u-boot-orangepi5-vendor (25.5.1) ... Armbian 'uboot-orangepi5-vendor' for '2017.09-S3e40-P187d-H0b1f-V023f-Bb703-R448a': 'postinst' starting. Armbian 'uboot-orangepi5-vendor' for '2017.09-S3e40-P187d-H0b1f-V023f-Bb703-R448a': 'postinst' finishing. Setting up systemd-sysv (252.38-1~deb12u1) ... Setting up libicu72:arm64 (72.1-3+deb12u1) ... Setting up linux-dtb-vendor-rk35xx (25.5.1) ... Armbian 'linux-dtb-vendor-rk35xx' for '6.1.115-vendor-rk35xx': 'postinst' starting. Armbian: DTB: symlinking /boot/dtb to /boot/dtb-6.1.115-vendor-rk35xx... 'dtb' -> 'dtb-6.1.115-vendor-rk35xx' Armbian 'linux-dtb-vendor-rk35xx' for '6.1.115-vendor-rk35xx': 'postinst' finishing. Setting up armbian-firmware-full (25.5.1) ... Setting up python3-ruamel.yaml.clib:arm64 (0.2.7-1+b2) ... Setting up libnss-systemd:arm64 (252.38-1~deb12u1) ... Setting up linux-image-vendor-rk35xx (25.5.1) ... Armbian 'linux-image-vendor-rk35xx' for '6.1.115-vendor-rk35xx': 'postinst' starting. update-initramfs: Generating /boot/initrd.img-6.1.115-vendor-rk35xx W: Possible missing firmware /lib/firmware/regulatory.db for built-in driver cfg80211 W: Possible missing firmware /lib/firmware/regulatory.db.p7s for built-in driver cfg80211 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.115-vendor-rk35xx Image Name: uInitrd Created: Sun Jul 20 10:39:28 2025 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 13880399 Bytes = 13555.08 KiB = 13.24 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.115-vendor-rk35xx to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.1.115-vendor-rk35xx' update-initramfs: Armbian: done. Remove unused generated file: /boot/uInitrd-6.1.99-vendor-rk35xx Remove unused generated file: /boot/initrd.img-6.1.99-vendor-rk35xx Armbian: update last-installed kernel symlink to 'Image'... '/boot/Image' -> 'vmlinuz-6.1.115-vendor-rk35xx' Armbian: Debian compat: linux-update-symlinks install 6.1.115-vendor-rk35xx boot/vmlinuz-6.1.115-vendor-rk35xx I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.115-vendor-rk35xx I: /initrd.img is now a symlink to boot/initrd.img-6.1.115-vendor-rk35xx Armbian 'linux-image-vendor-rk35xx' for '6.1.115-vendor-rk35xx': 'postinst' finishing. Setting up linux-headers-vendor-rk35xx (25.5.1) ... Armbian 'linux-headers-vendor-rk35xx' for '6.1.115-vendor-rk35xx': 'postinst' starting. Configuring kernel-headers (6.1.115-vendor-rk35xx) - please wait ... HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/confdata.o HOSTCC scripts/kconfig/expr.o LEX scripts/kconfig/lexer.lex.c YACC scripts/kconfig/parser.tab.[ch] HOSTCC scripts/kconfig/lexer.lex.o HOSTCC scripts/kconfig/menu.o HOSTCC scripts/kconfig/parser.tab.o HOSTCC scripts/kconfig/preprocess.o HOSTCC scripts/kconfig/symbol.o HOSTCC scripts/kconfig/util.o HOSTLD scripts/kconfig/conf # # configuration written to .config # Compiling kernel-headers scripts (6.1.115-vendor-rk35xx) using 8 CPUs - please wait ... SYNC include/config/auto.conf.cmd HOSTCC scripts/dtc/dtc.o HOSTCC scripts/dtc/flattree.o HOSTCC scripts/dtc/fstree.o HOSTCC scripts/dtc/data.o HOSTCC scripts/dtc/livetree.o HOSTCC scripts/dtc/treesource.o HOSTCC scripts/dtc/srcpos.o HOSTCC scripts/dtc/checks.o HOSTCC scripts/dtc/util.o LEX scripts/dtc/dtc-lexer.lex.c YACC scripts/dtc/dtc-parser.tab.[ch] HOSTCC scripts/dtc/libfdt/fdt.o HOSTCC scripts/dtc/libfdt/fdt_ro.o HOSTCC scripts/dtc/libfdt/fdt_wip.o HOSTCC scripts/dtc/libfdt/fdt_sw.o HOSTCC scripts/dtc/libfdt/fdt_rw.o HOSTCC scripts/dtc/libfdt/fdt_strerror.o HOSTCC scripts/dtc/libfdt/fdt_empty_tree.o HOSTCC scripts/dtc/libfdt/fdt_addresses.o HOSTCC scripts/dtc/libfdt/fdt_overlay.o HOSTCC scripts/dtc/fdtoverlay.o HOSTCC scripts/dtc/dtc-lexer.lex.o HOSTCC scripts/dtc/dtc-parser.tab.o HOSTLD scripts/dtc/fdtoverlay HOSTLD scripts/dtc/dtc HOSTCC scripts/resource_tool HOSTCC scripts/kallsyms HOSTCC scripts/sorttable HOSTCC scripts/asn1_compiler HOSTCC scripts/genksyms/genksyms.o YACC scripts/genksyms/parse.tab.[ch] HOSTCC scripts/selinux/genheaders/genheaders HOSTCC scripts/selinux/mdp/mdp LEX scripts/genksyms/lex.lex.c HOSTCC scripts/genksyms/parse.tab.o HOSTCC scripts/genksyms/lex.lex.o HOSTLD scripts/genksyms/genksyms Compiling kernel-headers scripts/mod (6.1.115-vendor-rk35xx) using 8 CPUs - please wait ... CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig CC scripts/mod/devicetable-offsets.s MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/sumversion.o UPD scripts/mod/devicetable-offsets.h HOSTCC scripts/mod/file2alias.o HOSTLD scripts/mod/modpost MODPOST scripts/mod/Module.symvers Done compiling kernel-headers (6.1.115-vendor-rk35xx). Done compiling kernel-headers tools (6.1.115-vendor-rk35xx). Armbian 'linux-headers-vendor-rk35xx' for '6.1.115-vendor-rk35xx': 'postinst' finishing. Setting up armbian-bsp-cli-orangepi5-vendor (25.5.1) ... Armbian 'armbian-bsp-cli-orangepi5-vendor' for '1-PC5315-V4064-H21c6-B1e5d-R756d': 'postinst' starting. Armbian 'armbian-bsp-cli-orangepi5-vendor' for '1-PC5315-V4064-H21c6-B1e5d-R756d': 'postinst' finishing. (...) Processing system modifications ... Processing triggers for initramfs-tools (0.142+deb12u3) ... update-initramfs: Generating /boot/initrd.img-6.11.5+bpo-arm64-16k update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.11.5+bpo-arm64-16k Image Name: uInitrd Created: Sun Jul 20 10:43:32 2025 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 54963626 Bytes = 53675.42 KiB = 52.42 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.11.5+bpo-arm64-16k to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.11.5+bpo-arm64-16k' update-initramfs: Armbian: done. Any help appreciated. Thank you all

Good evening, I have got Orange pi 5 board. MAC address of this board network interface `end1` changes every time I reboot the system. I tried adding entry in /boot/armbianEnv.txt, I tried specifying hwaddress in /etc/network/interfaces. Neither of those two options worked.

A few days ago I had an issue with a successfully running Armbian installation running from the NVME of my Orange Pi 5 that suddenly developed an issue with nothing being shown on my TV. So after seemingly not being to identify the problem, I started again, wrote the image to an SD card and then moved the installation to the NVME drive using armbian-config utility. So now that I have a set-up that works again, I want to instigate a more belt and braces approach and create an image of the NVME installation using GZIP to compress the image file and decided to use the DD option from terminal. Having tried well over a hundred different combinations of commands, I am unable to get things to work. I either get errors of Not a directory, No such file or directory or Is a directory The output of lsblk is NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk1 179:0 0 59.5G 0 disk └─mmcblk1p1 179:1 0 59.5G 0 part zram0 252:0 0 3.9G 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk nvme0n1 259:0 0 238.5G 0 disk └─nvme0n1p1 259:1 0 238.5G 0 part /var/log.hdd So in order to create the copy of the NVME installation, that is only taking up 13gb of the 238Gb total, to the root of a 64Gb SD card, completely empty and formatted to EXT4 via gparted, using the information above, can anybody see where I am going wrong. A few typical examples of command structures that I have tried are: sudo dd if=/dev/nvme0n1 of=/dev/mmcblk1/armbian.gz conv=sync bs=64K | gzip --stdout > bs=4M status=progress dd if=/dev/nvme0n1 conv=sync bs=64K | gzip --stdout > of=/dev/mmcblk1/armbian.gz dd if=/dev/nvme0n1p1 conv=sync bs=64K | gzip --stdout > of=/dev/mmcblk1p1/armbian.gz bs=4M status=progress This is the general template that I initially followed from a website dd if=/dev/SOURCE conv=sync bs=64K | gzip --stdout > /path/to/file.gz I've researched the use of the DD command until I am cross eyed.

For a few weeks I've been using the latest official release from May 26, 2025, running just fine from my NVME drive. But then I turned it on and at the screen where you get the Amrbian grey/red logo in the middle of the screen and the spinning circle, it went no further. The spinning circle would either stop rotating or disappear after a minute or so. I can SSH into the device. But when I use remote desktop from a Windows PC, the full and functioning desktop is there. It's just not on my TV screen any more. I've done the usual HDMI cable testing and powering off the TV completely, but no change. The fact that the desktop is accessible remotely does indicate that it must be loading in some fashion. Took a log here: https://paste.next.armbian.com/qococumoga

Hello all, I am running an Orange Pi 5 board with Armbian on a SD Card and I realized that my /var/log path is constantly full, with it being at /dev/zram1 It gets full at 50Mb with the file /var/log/samba/cores/smbd/core taking up all the space I have not managed to read this file, so I can't tell what kinds of errors are showing up. My OpenMediaVault and samba setup are running perfectly fine, and even though I delete this core file, it shows up again during reboot. I have tried to set enable core files = no in smb.conf With no sucess. The file continues to show up during reboot. Any ideas how to solve this? Best regards

Been trying to enable multiple overlays on kernel 6.12 (orange pi 5) but I am not able to get any pwm device in /sys/class/pwm/ The i2c also seems to be missing. Is going back to 6.1 the safest option? Thanks

See for more details but without using the overlay-user folder - I was not able to get the pwm to work on a fresh download.

Hi, I'm using orange pi 5, and I noticed that I'm using 100Mb/s instead 1000Mb/s, i changed the cables that are working in another pc to a 1000Mb/s but still works to 100Mb/s, I changed to another kernel like 6.12.32-current-rockchip64 with no luck, any idea how to solve it? root@opi5 /home/pi# ethtool end0 Settings for end0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Full 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Full 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 100Mb/s Duplex: Full Auto-negotiation: on master-slave cfg: preferred slave master-slave status: slave Port: Twisted Pair PHYAD: 1 Transceiver: external MDI-X: Unknown Supports Wake-on: ug Wake-on: d Current message level: 0x0000003f (63) drv probe link timer ifdown ifup Link detected: yes

This guide is specifically for the official orange pi 5 PCIe WiFi 6.0 Module that can be found here although it has been in and out of stock https://a.co/d/bhjoolW It uses the ap6275p chip. The guide will be split into 2 sections depending on what OS you want to use Orange Pi OS 1. install the wifi module into the m.2 slot and boot sd card with either the latest orange pi os ubuntu or debian http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-pi-5.html 2. edit the boot file to enable wifi by adding overlays=wifi-ap6275p to the end. Note if you already have overlays=<anything> line such as ssd-sata, delete it so it only says overlays=wifi-ap6275p sudo nano /boot/orangepiEnv.txt overlays=wifi-ap6275p Save and reboot 3. now you can search for you wifi and connect nmtui-connect Armbian OS Preface, for Armbian OS this is currently only working with the nightly build which can be found here https://github.com/armbian/build/releases/ I repeat, this will not work with the stable build of Armbian here https://www.armbian.com/orangepi-5/ as it is missing drivers but you can upgrade your stable build to nightly build 1. You first need to obtain the .dtbo file from the latest orangepi5.img, I would download the smallest img which is debian_bullseye_server http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-pi-5.html 2. use 7zip to first extract the Orangepi5*.img then open that .img file in 7zip further which will show 2 files named 0.bootfs.img and 1.rootfs.img 3. Go into the folder /0.bootfs.img/dtb/rockchip/overlay/ and at the end grab the file rk3588-wifi-ap6275p.dtbo 4. rename the file to rockchip-rk3588-wifi-ap6275p.dtbo and copy it to the /boot/dtb/rockchip/overlay/ directory on your orange pi sudo cp /path/to/rk3588-wifi-ap6275p.dtbo /boot/dtb/rockchip/overlay/rockchip-rk3588-wifi-ap6275p.dtbo 5. edit the boot file to enable wifi by adding overlays=wifi-ap6275p to the end. Note if you already have overlays=<anything> line such as ssd-sata, delete it so it only says overlays=wifi-ap6275p sudo nano /boot/armbianEnv.txt overlays=wifi-ap6275p Save and reboot 6. now you can search for you wifi and connect nmtui-connect

Hello. Is it possible to enable OV13855 camera on OPi5 with the latest armbian image? If yes, how do it? Thanks!

G’day guys, just grabbed a version of Armbian again to play around with on an orange Pi 5 I have had for a while. I have installed the latest stable (25.5.1 Noble Gnome). Everything went smoothly, and I have a 512GB ssd on the board, so I went through the install process using armbian-install. I managed to get the OS installed on the SSD, but when I went to install the bootloader, I got some error messages saying that the SPI image was not chosen. I followed the process for erasing the MTD, but still I got error messages relating to no spi image. I tried to boot from the ssd and just got a black screen. I downloaded Joshua Riek’s Ubuntu 24.04 distro and booted it from the sd card and ran his command “sudo u-boot-install-mtd”. It installed to the MTD and then I shut down and removed the sd card and booted up. Armbian has now booted from the SSD with no issues. I couldn’t find anything on the forum so I thought I would post this to assist anyone else who has this issue. If the guys at Armbian have any thoughts on why this may have happened please let me know.

Has anyone seen this? The claims there is a Vulkan driver now: https://github.com/Bleach665/Mali610Vulkan Can't confirm.

Hey there! I've just bought a used Orange Pi 5, according to the owner he never managed too boot up the first time, because he said it was bricked, for the price he offered for the device and accessories I thought I'd give it a go.. and yeah, I tried to install on different microSD cards, Armbian, OrangePi Os, Android 12 for Orange Pi, many tries but none of them booted or did anything after waiting even 15min. If I set the device into maskrom mode it enters the mode but it gives error to anything I try. I read on a post that using this firmware fixed someones board: https://dl.radxa.com/rock5/sw/images/loader/rock-5b/release/ I tried and I get the following: Download Boot Start, Download Boot Success, Wait for Maskrom Start and Success and then on Test Device Start, I get Test Device Fail , Note: Comunication issues, Certainly please check usb, Completed... If I go to the advanced function tab, Test Device fails, Get ChipInfo fails, ReadFlashInfo Fails too Flash ID... all of them,... IDK if I'm missing something or this one is really dead and there is nothing I can do. If someone has any idea of what could I try to do to get it working it would be nice! Thank you!

Has anyone activated the ov13855 camera on Orange Pi 5 (kernel 6.1.x)? If so, can you share your experience?

I have an Orange Pi 5 running Armbian Noble and I need a distribution that supports USB OTG in peripheral mode and supports dcw3_generic kernel module. I've tried to compile one with support, but I keep getting: modprobe: FATAL: Module dwc3_generic not found in directory /lib/modules/6.1.115-vendor-rk35xx I triple checked .config and the appropriate flags are set to Y. I am trying to get the Pi to act as a mouse attached to another machine's USB port. Any help is greatly appreciated.

Hello! I'm trying to look around in the Armbian build/config scripts to see how I can enable a mainline v6.15-rc3 kernel to be built. I did try to make a build/userpatches/lib.config file with the contents, KERNELBRANCH="tag:v6.15-rc3" But that's not working. Would anyone be able to tell me the file I need to edit for an OrangePi 5? Update: I actually seem to have it try by editing config/sources/families/rockchip-rk3588.conf changing the version tag. But I get a bunch of red errors complaining about SHA1. hmm...an 'rc3' is probably not to be found in a tree with 'stable' in it. Cheers! Fred

With the vendor kernel, my logs are getting flooded with drm error messages Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062 Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062 Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062 Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062 Apr 13 17:04:05 kitchen-opi kernel: [drm:rockchip_vop2_mod_supported] *ERROR* Cluster0-win0 unsupported format modifier 0x800000000000062 this seems an old issue (Kernel messages flooding logs · Issue #86 · Joshua-Riek/ubuntu-rockchip) - it doesn't seem complicated to fix, I am familiar with the build system but I cannot figure out how I can create a patch for the kernel source. Which repo should I patch? Can I just put my patch into build/patch/kernel/rk35xx-vendor-6.1? Thanks

I recently added a monitor to my server as there were issues and I wanted to see logs directly on the OPi5. The monitor is part of the Motorola HD Dock. I'm using it for it's keyboard and monitor. In any case, the following messages appear in DMESG and keeps repeating ever second or two: [522074.762209] vop2_isr: 107217 callbacks suppressed [522074.762239] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0 [522074.762321] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0 [522074.762359] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0 [522074.762400] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0 [522074.762441] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0 [522074.762483] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0 [522074.762525] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0 [522074.762566] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0 [522074.762608] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0 [522074.762650] rockchip-vop2 fdd90000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp0 I left the dock attached. Went back later to check and it's still doing it. Is there any way to stop this or filter it out? Thanks.

So a clean install of "Armbian 25.2.1 Noble Gnome" with the vendor kernel (6.1.99) fails to boot when installed on an nvme SSDwith the armbian-install script, when btrfs is chosen as the partition type. I am not sure if the files are copied over correctly, since the ~6GB image on the SD card is copied as 2.9GB on the btrfs partition, but there are no errors occuring as far as I can see. The bootloader is up-to-date, and I can access the btrfs drive when booted from the SD card, so the kernel supports btrfs I guess? However, I think there are some things going "wrong", since the armbianEnv.txt file on the nvme SSD has ext4 instead of btrfs as the rootfs? This is basically my first install of armbian so I don't know that much about the installation procedure, but I just followed the official guide (which is also somehow out of date afaik, the images seem wrong...) (Additionally, apt update + upgrade don't work right now, erroring out with "Mirror sync in progress", so I don't know if this failure is happening because of out of date packages...)

I installed U-Boot in the Orange Pi 5's SPI memory, connected via UART via the CH340G adapter (the power switch is lost). The speed is 1500,000 baud, 8n1. Connected TX-RX, RX-TX, GND-GND. After starting the board, I see the logs, but I can't enter anything at all. When I change the power supply, the input works, but it enters incomprehensible characters instead of the usual ones. When installing the EDK2-RK3588, there was no such problem on the same power supply and adapter. How can I fix the UART input?

Hi all, this is my first post here on the forum. I'm getting ready to wrap up for the night, but I recently purchased an Orange Pi 5 (non-B) to do some tinkering with. I downloaded the Bookworm XFCE variant as I am somewhat familiar with XFCE already. Anyway, upon initial testing, I thought my power supply wasn't good enough for the board. I wasn't getting any HDMI output. When I removed the micro-SD card and tried to boot it that way, an orange pi splash screen would show on the attached display, so I think the port actually works (?) I have a spare USB to TTL Serial adapter so I was able to verify the board was successfully booting into Armbian, but xrandr didn't show any connections. I tried a USB-C to HDMI cable that I had handy, and that actually worked. I then stumbled across a forum thread on a similar issue with someone's Orange Pi 5B, and a comment said they fixed it by enabling the HDMI port in armbian-config. I tried that and it still didn't work. I also noticed a few debug messages that would come over the UART interface, something with an error -22. I'll try to replicate it tomorrow and add a comment with the exact error. I don't have it handy, but googling the text didn't really help. Anyway, like I mentioned earlier, I'm wrapping it up for the night so I'll try any suggestions tomorrow after my college classes. Any insights are appreciated.

All images have build dates 1 month back. Several images seem to be based on "vendor kernel". What is happening? G

Hi I want to work with g_audio drivers on the usb type c otg port. When I build the image with current kernel, by applying the following overlay (I only change dr_mode to peripheral) i am able to convert the usb port in peripheral mode and successfully load the g_audio drivers and audio interfaces also come up. /dts-v1/; /plugin/; / { compatible = "rockchip,rk3588s"; fragment@0 { target = <&usb_host0_xhci>; // This matches the label in the device tree __overlay__ { dr_mode = "peripheral"; }; }; }; But when i want to do similar with the vendor kernel, which has different device tree, changing dr_mode doesn't work. /dts-v1/; /plugin/; / { compatible = "rockchip,rk3588s"; fragment@0 { target = <&usbdrd3_0>; // Target the usbdrd3_0 node __overlay__ { usb@fc000000 { dr_mode = "peripheral"; // Change dr_mode to peripheral }; }; }; }; The device trees for usb type c port for both kernels are as below - //***This node is of current kernel*** usb@fc000000 { power-domains = <0x21 0x1f>; snps,dis-u1-entry-quirk; snps,dis_enblslpm_quirk; phy-names = "usb2-phy\0usb3-phy"; clock-names = "ref_clk\0suspend_clk\0bus_clk"; snps,dis-u2-freeclk-exists-quirk; usb-role-switch; phy_type = "utmi_wide"; resets = <0x1f 0x152>; interrupts = <0x00 0xdc 0x04 0x00>; clocks = <0x1f 0x194 0x1f 0x193 0x1f 0x192>; snps,dis-u2-entry-quirk; compatible = "rockchip,rk3588-dwc3\0snps,dwc3"; snps,dis-del-phy-power-chg-quirk; status = "okay"; phys = <0x23 0x24 0x04>; reg = <0x00 0xfc000000 0x00 0x400000>; phandle = <0x116>; dr_mode = "peripheral"; snps,dis-tx-ipgap-linecheck-quirk; port { endpoint { remote-endpoint = <0x25>; phandle = <0xeb>; }; }; }; ------------ dmesg output [ 15.417624] i2c 6-0022: deferred probe pending: typec_fusb302: cannot register tcpm port [ 600.475296] g_audio gadget.0: Linux USB Audio Gadget, version: Feb 2, 2012 [ 600.475317] g_audio gadget.0: g_audio ready Vendor Kernel //***This node is of vendor kernel usbdrd3_0 { #address-cells = <0x02>; clock-names = "ref\0suspend\0bus"; clocks = <0x02 0x1a3 0x02 0x1a2 0x02 0x1a1>; #size-cells = <0x02>; compatible = "rockchip,rk3588-dwc3\0rockchip,rk3399-dwc3"; ranges; status = "okay"; phandle = <0x22b>; usb@fc000000 { power-domains = <0x06 0x1f>; snps,dis-u1-entry-quirk; snps,dis_enblslpm_quirk; phy-names = "usb2-phy\0usb3-phy"; snps,dis-u2-freeclk-exists-quirk; usb-role-switch; phy_type = "utmi_wide"; quirk-skip-phy-init; resets = <0x02 0x2a4>; interrupts = <0x00 0xdc 0x04>; snps,dis-u2-entry-quirk; compatible = "snps,dwc3"; snps,parkmode-disable-hs-quirk; snps,dis-del-phy-power-chg-quirk; status = "okay"; snps,parkmode-disable-ss-quirk; phys = <0x74 0x75>; reg = <0x00 0xfc000000 0x00 0x400000>; phandle = <0x22c>; dr_mode = "otg"; reset-names = "usb3-otg"; snps,dis-tx-ipgap-linecheck-quirk; port { #address-cells = <0x01>; #size-cells = <0x00>; endpoint@0 { remote-endpoint = <0x76>; reg = <0x00>; phandle = <0x183>; }; }; }; }; //dmesg output [ 41.238153] [GTP-ERR][__do_register_ext_module:79] Module [goodix-fwu] timeout [ 243.574594] g_audio gadget.0: Hardware params: access 3, format 2, channels 2, rate 48000 [ 243.574756] g_audio gadget.0: Linux USB Audio Gadget, version: Feb 2, 2012 [ 243.574773] g_audio gadget.0: g_audio ready [ 243.578558] typec_fusb302 6-0022: Looking up vbus-supply from device tree [ 243.581576] dwc3 fcd00000.usb: device reset Can some one help me what kind of overlay should i make to convert the port to peripheral mode.