Search the Community

Hi friends, I have one nagging thorn in my side that I just cannot figure out. I need someone who has a 1password account for help with this one. The problem - their desktop app and browser plugin work in tandem -- and it will not synchronize on Armbian for some reason. I've tried everything I can think of - ensuring nothing is downloaded from Flatpak and therefore sandboxed and preventing any connectivity issues. But still not working. If someone can take 5 mins and create a free trial account on 1password, then here are the steps to reproduce: Download the latest arm64 version of 1password Desktop: curl -sSO https://downloads.1password.com/linux/tar/stable/aarch64/1password-latest.tar.gz Extract and move the files: sudo tar -xf 1password-latest.tar.gz sudo mkdir -p /opt/1Password sudo mv 1password-*/* /opt/1Password Run the post-installation script, and launch 1password sudo /opt/1Password/after-install.sh 1password Everything is all good, and working. I log in to my vault, as intended, and the app is fully unlocked. Settings already default to synchronization being enabled, but just for the sake of double checking: So we are all set on the desktop side. Now, for the browsers. I have checked this with both Firefox, and Chromium extensively -- all various kinds of versions, ensuring no Flatpak or anything like that. We install the browser plugin: https://1password.com/downloads/browser-extension And click on your corresponding browser, and enable the extension/plugin. At this point -- and I have done this hundreds of times across all of my other devices and installations -- there SHOULD be nothing to do in the extension as far as entering a username and password goes. It's supposed to detect the local socket and interface with the desktop application, meaning once you are authenticated on the Desktop app, your browser plugin will unlock. The most you'd have to do is click through the 1st-time-launch welcome message and skip the tutorial, but NOT authenticating needed. And sadly, this is where obviously, it doesn't work. We are instead prompted for our username and password and the extension shows a lock symbol which is totally incorrect. We right click the extension in Chrome and pick Settings, to figure out what the heck is going on: And are met, with the dreaded, connection problem and yellow light. Instead of all systems go and the GREEN light, as it is supposed to be: I've pretty much exhausted the amount of testing I can possibly do, I'm just a novice user personally Any help would be greatly appreciated, I'd even make a donation if someone can crack this nut, as it's a pretty glaring (for me) missing feature that I've grown accustomed to across every other device I own, and it does typically work very well, on any other OS.. I run it on Linux Mint, PopOS, Debian, Windows, all kinds of stuff never a problem I am able to report back with any further information requests or diagnostics etc. and already plan to forward this link to 1password support as well Thanks in advance for any help!

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

Hey everyone, for the past couple of days I've been looking into the Mesa-VPU script made by AmazingFate that's used to patch Mesa/VPU onto a custom build of Armbian. https://github.com/armbian/build/blob/main/extensions/mesa-vpu.sh I already have an install of Armbian (Debian XFCE 6.12.28-current-rockchip64 ) on my Rock5b and was looking into applying as much as I can without re-building an image or starting from scratch. From my understanding, You'd need the vendor rk3588 kernel if you want the best possible compatibility with things like the VPU for multimedia acceleration (Someone please correct me if this is not the case lol) What follows is what I was able to piece together after troubleshooting, reading the Mesa changelog & trying to apply as many packages as I can from AmazingFate's kernel extension script. I've also included some tweaks for XFCE to hopefully provide a smooth graphical experience. Although my Rock5b is used as a headless server and doesnt have anything plugged into the HDMI port, I can say that the following changes have made a huge difference in graphical performance of VNC. Please keep in mind that i'm not a developer for Armbian. I just wanted to share this as a guide i've put together to hopefully help someone else who's tried the same (Please let me know your thoughts or if there was anything i've missed. Like I said, this is what has worked for me) (Obviously the correct fix is to rebuild Armbian with Mesa-VPU. What follows was done as an experiment) #################### GUIDE BELOW. THIS IS NOT A SHELL SCRIPT! PLEASE READ AND DO NOT COPY/PASTE ENTIRETY INTO TERMINAL!############################# #### -- 01 Setup AmazingFate Panfork-Mesa repo for mali-g610-firmware 01 -- #### ## 1A: import gpg key and use it to sign repo ## wget -qO - https://download.opensuse.org/repositories/home:/amazingfate:/panfork-mesa/Debian_12/Release.key | sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/panfork-mesa.gpg ## 1B: Add Repo to apt sources & update ## echo "deb https://download.opensuse.org/repositories/home:/amazingfate:/panfork-mesa/Debian_12/ /" | sudo tee /etc/apt/sources.list.d/panfork-mesa.list sudo apt update ## 1C: Install firmware ## sudo apt install mali-g610-firmware libmali-g610-x11 ## 1D: **RECOMMENDED** : Remove panfork-mesa repo ## sudo rm -rf /etc/apt/sources.list.d/panfork-mesa.list sudo rm -rf /etc/apt/trusted.gpg.d/panfork-mesa.gpg #### -- 02 Enable Debian Experimental Repo for recent Mesa Packages 02 -- #### sudo nano /etc/apt/sources.list ## 2A: Add the following to the bottom of the document... ## deb http://deb.debian.org/debian unstable main contrib non-free deb http://deb.debian.org/debian experimental main ## 2B: Update and install Mesa Packages ## sudo apt update sudo apt install -t experimental mesa-vulkan-drivers mesa-utils libgl1-mesa-dri libglx-mesa0 mesa-vdpau-drivers mesa-va-drivers mesa-opencl-icd mesa-libgallium ## 2C: **RECOMMENDED** : Re-open apt sources and remove Experimental/Unstable repos... ## sudo nano /etc/apt/sources.list #Remove the following and update apt...# deb http://deb.debian.org/debian unstable main contrib non-free deb http://deb.debian.org/debian experimental main sudo apt update #### -- 03 Add rockchip-multimedia Ubuntu Repo to Apt 03 -- #### echo "deb [arch=arm64] https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu jammy main" | sudo tee /etc/apt/sources.list.d/rockchip-multimedia.list ## 3A: Download Key and add convert to gpg ## curl -o rockchip-multimedia.asc "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x8065BE1FC67AABDE" gpg --dearmor rockchip-multimedia.asc sudo mv rockchip-multimedia.asc.gpg /etc/apt/keyrings/rockchip-multimedia.gpg ## 3B: Add PPA Repo and update ## echo "deb [arch=arm64 signed-by=/etc/apt/keyrings/rockchip-multimedia.gpg] https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu jammy main" | sudo tee /etc/apt/sources.list.d/rockchip-multimedia.list sudo apt update ## 3C: Install packages ## sudo apt install libv4l-rkmpp chromium gstreamer1.0-rockchip1 rockchip-multimedia-config ## 3D: **OPTIONAL** : Disable rockchip-multimedia PPA repo ## sudo mv /etc/apt/sources.list.d/rockchip-multimedia.list /etc/apt/sources.list.d/rockchip-multimedia.list.disabled sudo apt update #### -- 04 Optimize XFCE/Xorg and Reboot 04 -- #### ## 4A: Open default xorg config ## sudo nano /etc/X11/xorg.conf.d/01-armbian-defaults.conf #Add the following... # Section "Device" Identifier "Mali-G610" Driver "modesetting" Option "DRI" "3" # Required for Mali GPUs Option "GALLIUM_DRIVER" "panfrost" Option "PageFlip" "on" # Reduces tearing Option "TearFree" "true" # Xfce-specific anti-tearing EndSection ## 4B: Add XFCE Specific tweaks ## sudo nano /etc/X11/xorg.conf.d/20-xfce-tweaks.conf #Add the following... # Section "Extensions" Option "COMPOSITE" "Enable" EndSection Section "ServerFlags" Option "AutoAddGPU" "off" # Prevents duplicate GPU detection EndSection ## 4C: Reboot ## sudo reboot now

I tried installing the OS using SD card and EMMC, but both failed. Orange Pi OS (Arch) on the official website ran normally. However, I installed focal_desktop_xfce or jammy_desktop_gnome from Ubuntu Image, but they all failed. After inserting the image into the SD card, the symptom is a black screen and no booting. Does it only support SSD? Because it is entered through a translator, there may be unnatural sentences. If you reply about that, I will get back to you.

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.

My first post here - I'm new to SBCs and stoked I got my home webserver up and running on a Orange Pi 5 which boots from an NVMe (pats-self-on-back : -) It runs great, pages are up, and it's all SO COOL, but it fails to do a restart... I can do a shutdown -h now, count to three and power it back up and all is well, but if I do a shutdown -r now it will go down, start back up, all the way to the login prompt but then barfs a long Oops message. God please... don't make me start over !

Hello, I had to encode lately some video files and I discovered that video encoding hardware acceleration seems to be broken. gart@orangepi5:~$ uname -a Linux orangepi5 6.1.115-vendor-rk35xx #1 SMP Tue Jun 3 13:10:51 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux gart@orangepi5:~$ sudo dmesg | grep mpp_rkvenc [ 12.705174] mpp_rkvenc2 rkvenc-ccu: probing start [ 12.705179] mpp_rkvenc2 rkvenc-ccu: probing finish [ 13.267729] mpp_rkvenc2 fdbd0000.rkvenc-core: Adding to iommu group 10 [ 13.267963] mpp_rkvenc2 fdbd0000.rkvenc-core: probing start [ 13.268179] mpp_rkvenc2 fdbd0000.rkvenc-core: Looking up venc-supply from device tree [ 13.268187] mpp_rkvenc2 fdbd0000.rkvenc-core: Looking up venc-supply property in node /rkvenc-core@fdbd0000 failed [ 13.268207] mpp_rkvenc2 fdbd0000.rkvenc-core: rockchip_init_read_margin: no regulator (venc) found: -19 [ 13.268214] mpp_rkvenc2 fdbd0000.rkvenc-core: bin=0 [ 13.268293] mpp_rkvenc2 fdbd0000.rkvenc-core: Failed to get leakage [ 13.268342] mpp_rkvenc2 fdbd0000.rkvenc-core: Looking up venc-supply from device tree [ 13.268350] mpp_rkvenc2 fdbd0000.rkvenc-core: Looking up venc-supply property in node /rkvenc-core@fdbd0000 failed [ 13.268367] mpp_rkvenc2 fdbd0000.rkvenc-core: error -ENODEV: _opp_set_regulators: no regulator (venc) found [ 13.268395] mpp_rkvenc2 fdbd0000.rkvenc-core: failed to set opp config [ 13.268401] mpp_rkvenc2 fdbd0000.rkvenc-core: failed to init opp info [ 13.268406] mpp_rkvenc2 fdbd0000.rkvenc-core: failed to init_opp_table [ 13.268453] mpp_rkvenc2 fdbd0000.rkvenc-core: attach ccu as core 0 [ 13.268489] mpp_rkvenc2 fdbd0000.rkvenc-core: probing finish [ 13.268700] mpp_rkvenc2 fdbe0000.rkvenc-core: Adding to iommu group 11 [ 13.268940] mpp_rkvenc2 fdbe0000.rkvenc-core: probing start [ 13.269126] mpp_rkvenc2 fdbe0000.rkvenc-core: Looking up venc-supply from device tree [ 13.269135] mpp_rkvenc2 fdbe0000.rkvenc-core: Looking up venc-supply property in node /rkvenc-core@fdbe0000 failed [ 13.269152] mpp_rkvenc2 fdbe0000.rkvenc-core: rockchip_init_read_margin: no regulator (venc) found: -19 [ 13.269159] mpp_rkvenc2 fdbe0000.rkvenc-core: bin=0 [ 13.269199] mpp_rkvenc2 fdbe0000.rkvenc-core: Failed to get leakage [ 13.269231] mpp_rkvenc2 fdbe0000.rkvenc-core: Looking up venc-supply from device tree [ 13.269238] mpp_rkvenc2 fdbe0000.rkvenc-core: Looking up venc-supply property in node /rkvenc-core@fdbe0000 failed [ 13.269253] mpp_rkvenc2 fdbe0000.rkvenc-core: error -ENODEV: _opp_set_regulators: no regulator (venc) found [ 13.269272] mpp_rkvenc2 fdbe0000.rkvenc-core: failed to set opp config [ 13.269278] mpp_rkvenc2 fdbe0000.rkvenc-core: failed to init opp info [ 13.269283] mpp_rkvenc2 fdbe0000.rkvenc-core: failed to init_opp_table [ 13.269345] mpp_rkvenc2 fdbe0000.rkvenc-core: attach ccu as core 1 [ 13.269379] mpp_rkvenc2 fdbe0000.rkvenc-core: probing finish When I try to encode my files are fucked up and I have this in log : gart@orangepi5:~$ sudo cat /var/log/syslog 025-07-04T19:38:45.309928+02:00 orangepi5 mpp[3513]: mpp_serivce: mpp_service_ioc_attach_fd failed ret -1 errno 22 Invalid argument 2025-07-04T19:38:45.311485+02:00 orangepi5 kernel: rk_vcodec: mpp_process_request:1434: can not import fd 127 2025-07-04T19:38:45.311503+02:00 orangepi5 kernel: rk_vcodec: mpp_collect_msgs:1622: session 1 process cmd 401 ret -22 2025-07-04T19:38:45.311504+02:00 orangepi5 kernel: rk_vcodec: mpp_dev_ioctl:1732: collect msgs failed -22 2025-07-04T19:38:45.311505+02:00 orangepi5 kernel: rk_vcodec: mpp_task_attach_fd:1841: can't import dma-buf 271 2025-07-04T19:38:45.311506+02:00 orangepi5 kernel: rk_vcodec: mpp_translate_reg_address:1897: reg[ 0]: 0x0000010f fd 271 failed 2025-07-04T19:38:45.311507+02:00 orangepi5 kernel: rk_vcodec: mpp_task_dump_mem_region:2084: --- dump task 0 mem region --- 2025-07-04T19:38:45.311508+02:00 orangepi5 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: no memory region mapped 2025-07-04T19:38:45.311509+02:00 orangepi5 kernel: rk_vcodec: mpp_process_task_default:589: alloc_task failed. 2025-07-04T19:38:45.311510+02:00 orangepi5 kernel: rk_vcodec: mpp_process_request:1434: can not import fd 128 2025-07-04T19:38:45.311511+02:00 orangepi5 kernel: rk_vcodec: mpp_collect_msgs:1622: session 1 process cmd 401 ret -22 2025-07-04T19:38:45.311512+02:00 orangepi5 kernel: rk_vcodec: mpp_dev_ioctl:1732: collect msgs failed -22 2025-07-04T19:38:45.311513+02:00 orangepi5 kernel: rk_vcodec: mpp_task_attach_fd:1841: can't import dma-buf 273 2025-07-04T19:38:45.311515+02:00 orangepi5 kernel: rk_vcodec: mpp_translate_reg_address:1897: reg[ 0]: 0x00000111 fd 273 failed 2025-07-04T19:38:45.311516+02:00 orangepi5 kernel: rk_vcodec: mpp_task_dump_mem_region:2084: --- dump task 0 mem region --- 2025-07-04T19:38:45.311517+02:00 orangepi5 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: no memory region mapped 2025-07-04T19:38:45.311518+02:00 orangepi5 kernel: rk_vcodec: mpp_process_task_default:589: alloc_task failed. 2025-07-04T19:38:45.311520+02:00 orangepi5 kernel: rkvenc2_wait_result:2340: session 0000000017eca1cc pending list is empty! 2025-07-04T19:38:45.311520+02:00 orangepi5 kernel: rk_vcodec: mpp_msgs_wait:1693: session 1 wait result ret -5 2025-07-04T19:38:45.311521+02:00 orangepi5 kernel: rkvenc2_wait_result:2340: session 0000000017eca1cc pending list is empty! 2025-07-04T19:38:45.311523+02:00 orangepi5 kernel: rk_vcodec: mpp_msgs_wait:1693: session 1 wait result ret -5 2025-07-04T19:38:45.351471+02:00 orangepi5 kernel: rk_vcodec: mpp_process_request:1434: can not import fd 133 2025-07-04T19:38:45.351492+02:00 orangepi5 kernel: rk_vcodec: mpp_collect_msgs:1622: session 1 process cmd 401 ret -22 2025-07-04T19:38:45.351494+02:00 orangepi5 kernel: rk_vcodec: mpp_dev_ioctl:1732: collect msgs failed -22 2025-07-04T19:38:45.351495+02:00 orangepi5 kernel: rk_vcodec: mpp_task_attach_fd:1841: can't import dma-buf 274 2025-07-04T19:38:45.351495+02:00 orangepi5 kernel: rk_vcodec: mpp_translate_reg_address:1897: reg[ 0]: 0x00000112 fd 274 failed 2025-07-04T19:38:45.351497+02:00 orangepi5 kernel: rk_vcodec: mpp_task_dump_mem_region:2084: --- dump task 0 mem region --- 2025-07-04T19:38:45.351498+02:00 orangepi5 kernel: mpp_rkvenc2 fdbd0000.rkvenc-core: no memory region mapped 2025-07-04T19:38:45.351499+02:00 orangepi5 kernel: rk_vcodec: mpp_process_task_default:589: alloc_task failed. 2025-07-04T19:38:45.351500+02:00 orangepi5 kernel: rkvenc2_wait_result:2340: session 0000000017eca1cc pending list is empty! 2025-07-04T19:38:45.351501+02:00 orangepi5 kernel: rk_vcodec: mpp_msgs_wait:1693: session 1 wait result ret -5 2025-07-04T19:38:45.351502+02:00 orangepi5 kernel: rk_vcodec: mpp_process_request:1434: can not import fd 130 2025-07-04T19:38:45.351503+02:00 orangepi5 kernel: rk_vcodec: mpp_collect_msgs:1622: session 1 process cmd 401 ret -22 2025-07-04T19:38:45.351504+02:00 orangepi5 kernel: rk_vcodec: mpp_dev_ioctl:1732: collect msgs failed -22 2025-07-04T19:38:45.354822+02:00 orangepi5 kernel: rk_vcodec: mpp_task_attach_fd:1841: can't import dma-buf 270 2025-07-04T19:38:45.354845+02:00 orangepi5 kernel: rk_vcodec: mpp_translate_reg_address:1897: reg[ 0]: 0x0000010e fd 270 failed does anybody else has this behaviour ? I'm sure to have use rkmpp encoding with ffmpeg before (a long time ago) probably before kernel 6.1, and that was working. In my opinion, it's an issue with vendor kernel. Let me know. Regard

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

Greetings everyone. I hope to receive some assistance here. Our company is a small Linux cloud gaming provider that uses the Cinnamon edition of Linux Mint for our cloud gaming services https://maximumsettings.com/ . We are searching for an affordable local streaming device that we can recommend to our clients, capable of decoding H.265 at 4K - 80Mbps. The Orange Pi 5 is a perfect fit for this role, and the Armbian Cinnamon desktop is well-suited since our clients already use Linux Mint Cinnamon edition on the cloud Gaming PC. However, there is currently no support for our open-source streaming client, Moonlight, which we use as the default option for our clients. This is where we hope to receive your help. We are willing to offer a $1000 Canadian Bountysource donation to Armbian if someone can create a binary version of the Moonlight streaming client https://moonlight-stream.org that can be easily installed by a novice Linux user on the Orange Pi 5 with the Armbian Cinnamon desktop edition OS. Ideally, without the requirement of using the terminal. I should mention that the Moonlight client would require full hardware decoding support for both H.264 and H.265.

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!

Hello, I installed lm-sensors on my Opi5 and I'm able to check temperatures, however I don't know how to make the little fan spin when the temperature rise. I know the temperature is not going to rise till critical levels, but I live in very hot country and I just don't want my device to become too hot. And do you know how to make the fan start at certain temperature rise? Also I'm not sure which pins I should connect the fan to.. One pin should be the 3.3V to get the power, what about the other one? I'm running Armbian 23.02.2 with kernel 5.10.110-rockchip-rk3588 Thanks in advance

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.

Hi, I recently got my hands on a used unit of those, quite faster than my old SBC! Only issue I currently have is that I can't seem to get audio output on the 3.5mm jack. (Well the other issue is unrelated .. ) Anyone have an idea on what I should be hunting? I did the obvious cable, etc.. checks. There's always the possibility that it's damaged, hell if I know. Armbian 25.2.1 6.1 kernel KDE Neon (Why use a beta version btw? just wondering) Thanks! DW.

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.