Search the Community

I want to install jellyfin on my OrangePi 5 Plus and need OpenCL to enable HDR-SDR mapping. I tried to follow the instruction on Jellyfin's official website: Rockchip VPU | Jellyfin However, I'm stucked on the step of installing OpenCL. I also tried this: Install OpenCL on Debian and Ubuntu and Armbian for Orange Pi 5 RK3588 But no luck either. Both instruction led to broken hardware acceleration in chrome and failing to start kernal in Jellyfin. Logs from ffmpeg: sudo /usr/lib/jellyfin-ffmpeg/ffmpeg -v debug -init_hw_device rkmpp=rk -init_hw_device opencl=ocl@rk Applying option init_hw_device (initialise hardware device) with argument opencl=ocl@rk. arm_release_ver: g13p0-01eac0, rk_so_ver: 10 Failed creating base context during opening of kernel driver. Kernel module may not have been loaded [AVHWDeviceContext @ 0xaaab055f5460] 1 OpenCL platforms found. [AVHWDeviceContext @ 0xaaab055f5460] 1 OpenCL devices found on platform "ARM Platform". arm_release_ver: g13p0-01eac0, rk_so_ver: 10 Failed creating base context during opening of kernel driver. Kernel module may not have been loaded [AVHWDeviceContext @ 0xaaab055f5460] 0.0: ARM Platform / Unknown Device Segmentation fault Logs from Jellyfin: Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Logs from clinfo: arm_release_ver: g13p0-01eac0, rk_so_ver: 10 Failed creating base context during opening of kernel driver. Kernel module may not have been loaded I want to know how to correctly enable OpenCL on OrangePi 5 Plus, thank you!

EDIT: I tried using ext4 rather than btrfs and.. somehow that solved it? I don't understand how the SSD file system would change how the bootloader is flashed because if properly flashed, the SD card shouldn't work at all, unless something has changed. Hey all, I wanted to move to the newest version of armbian (25.2.1) and for whatever reason neither `apt update && apt upgrade` nor `armbian-upgrade` (as a sanity check) worked so I wiped the SPI flash using `mtdtools` as prescribed in the forum post linked on the support page. 1) Booted from SD, installed Armbian and the bootloader. 2) Shut down, removed SD and turned on. Machine hung and never booted from NVMe. 3) Thought somehow I did something wrong or there was an error and used MaskROM mode and `rkdeveloptool` to revert it to boot from SD. 4) Repeated step 2 5) Still won't boot from NVMe but boots from SD (should have tried this first) 6) Tried reinstalling the bootloader to SPI flash, get this message: Processing blocks: 394/394 (100%) diff blocks: 0 Done Which reads like the flash is identical to what would is contained in the installer itself so it isn't overwritten. Wiped again and tried to install bootloader again. Still won't boot from NVMe but boots from SD card normally. Also, forgot to include this in my steps: I formatted the NVMe 3 times total and installed/reinstalled Armbian from the `armbian-install` script as a sanity check. Have had no issues in the past with any of this (I think I was on 24.11 most recently) so my first thought was a bug in the installer but am not seeing anyone else having this issue so figured I would ask here just to be sure. My questions are: 1) Has anyone else tried to use the installer on 25.2? I can't imagine there were any (much less breaking) changes but I am perplexed at this point. 2) Is the bootloader file available separately so I can flash it from `rkdeveloptools` Worst case I can image 24.11 on to the SD and try to install the bootloader that way but again, id be surprised if there were major changes. Thanks in advance!

My setup includes orange pi 5 plus, Samsung NVME SSD M2 4 TB with Armbain os. 256 GB eMMC and Intel BE 200 Wi-Fi. There are no drivers for the intel BE 200 Wi-Fi or any instructions to make it work.

I followed this manual I tried to boot , led was green and red , Display did not work. But Orange pi official images ca n boot my machine. How can I solve this problem?

I have installed Armbian 25.02 via an official Armbian image for Armbian 25.02 (Debian 12) Vendor Kernel 6.1.xx, is it possible (and sane) to upgrade to Armbian 25.05 (Debian 12) Vendor Kernel 6.1.xx? If so besides downloading the new image and installing fresh what are one's options?

I would love to use Armbian Build to construct a Debian 12 Bookworm images with KDE Plasma as the windows manager. I note that KDE Plasma isn't an option in the armbian builder. I have no problem building with XFCE or Cinnamon.

I'm new to boards with linux and this is my very first attempt to install linux systems on board so there might be something that I cannot be aware of. I tried to install armbian v6.12 on the SD card but after I finish configureing the setup, the wifi doesn't work. Unfortunately I have no wires to connet to the board so now it is unable for me to connect the board to the internet. The problem is exactly the same as the post Wifi module AX210 - Orange Pi 5 Plus - Armbian Community Forums. I can see the network controller through `lspci -v`: And the dmesg shows that iwlwifi cannot find suitable version to use: And I indeed have the firmware I need under /usr/lib/firmware: (the one ended with 59) Unfortunately I have no wires to connet to the board so now I cannot use apt to update and upgrade the system and the firmware in it and cannot use Armbianmonitor.

I am running an unmodified Server version of Armbian Linux v6.12 (Ubuntu 24.04) on an Orange Pi 5 Plus. I need to play sounds using the headphone jack on my SBC. Unfortunately the ES8388 sound chip is not recognized, the aplay -l output is as follows: **** List of PLAYBACK Hardware Devices **** card 0: Analog [Analog], device 0: fe470000.i2s-es8328-hifi-analog es8328-hifi-analog-0 [fe470000.i2s-es8328-hifi-analog es8328-hifi-analog-0] Subdevices: 1/1 Subdevice #0: subdevice #0 The correct output on desktop systems should like this (and it was like this on Desktop Armbian). What should I do to enable the ES8388 sound chip while staying on a server OS? Change something in the boot environment maybe? Install drivers?

Is there a list of Armbian Kernels that include EMMC support? I've tried the vendor kernel build 6.1.99, the LTS 6.12.21, and Bleeding Edge 6.14.0 to find they all lack the mmcblk0 under /dev/ , and lack overlays for it under /boot/dtb/rockchip/overlays/. I have wiped SPI and SPNOR without success.

Hi @ all, long time reader, but never managed to register. Now it is time... as I'm not able to solve this myself, kindly asking for help. I'm stuck, my Orangepi 5 plus stops boot at this: Loading, please wait... Starting systemd-udevd version 252.36-1~deb12u1 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... (initramfs) What happened before? Last year I bought the Orangepi 5 plus (8GB) and went ahead, testing everything out - having incredible fun with this little box. But with a way to old/slow sd card which finally failed two or three months ago. I went ahead and wrote the Armbian based Cinnamon (Kernel 6.1 incl. MESA/VPU) to a new SD Card. Everything was working flawless, but still ... SD Card. Therefore I bought a 1TB nvme, installed it and used armbian-install to install the bootloader on MTD Flash. Afterwards I got everything working from nvme. Amazing results, it just worked after armbian-install was finished. I shut down the system, removed SD card and used the nvme install from now on for weeks on a daily basis. Several apt-get dist-upgrades no problem at all. The last one done Sunday, if I remember correctly. Until today. I had some spare time and decided to apt-get update and apt-get dist-upgrade again. The commands finished without any error and new updates were done. But now -I wanted to reboot the device- reboot stalled. I see a black screen with above mentioned white text. So, something must have gone wrong I think. The Orangepi boots fine when I insert the SD Card again, also the nvme is there and can be mounted. Seemingly all data is still there. But how to proceed? I'm at a loss. Can anything be done on my side to solve this? Or is a reinstall to be done? The apt history logfile on the nvme (/var/logs/apt/history.log) contains both upgrades I mentioned and reads: Start-Date: 2025-04-01 16:15:10 Commandline: apt-get dist-upgrade Requested-By: edited (1000) Upgrade: armbian-config:arm64 (25.5.0-trunk.286.0324.065110, 25.5.0-trunk.325.0401.114753), tzdata:arm64 (2025a-0+deb12u1, 2025b-0+deb12u1), firefox-nightly:arm64 (138.0a1~20250324091950, 139.0a1~20250401094015), ghostscript-x:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7), libgs10-common:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7), libgs10:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7), ghostscript:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7), linux-headers-vendor-rk35xx:arm64 (25.2.3, 25.2.3), libgs-common:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7) End-Date: 2025-04-01 16:15:46 Start-Date: 2025-04-02 09:42:43 Commandline: apt-get dist-upgrade Requested-By: edited (1000) Upgrade: linux-image-vendor-rk35xx:arm64 (25.2.3, 25.2.3), firefox-nightly:arm64 (139.0a1~20250401094015, 139.0a1~20250401212749), linux-headers-vendor-rk35xx:arm64 (25.2.3, 25.2.3), armbian-bsp-cli-orangepi5-plus-vendor:arm64 (25.2.2, 25.2.3) End-Date: 2025-04-02 09:44:34 term.log in this directory shows nothing unusual, too. As far as my limited knowledge reaches ofc: Log started: 2025-04-01 16:15:10 (Reading database ... 218528 files and directories currently installed.) Preparing to unpack .../0-tzdata_2025b-0+deb12u1_all.deb ... Unpacking tzdata (2025b-0+deb12u1) over (2025a-0+deb12u1) ... Preparing to unpack .../1-armbian-config_25.5.0-trunk.325.0401.114753_all.deb ... Unpacking armbian-config (25.5.0-trunk.325.0401.114753) over (25.5.0-trunk.286.0324.065110) ... Preparing to unpack .../2-firefox-nightly_139.0a1~20250401094015_arm64.deb ... Unpacking firefox-nightly (139.0a1~20250401094015) over (138.0a1~20250324091950) ... Preparing to unpack .../3-ghostscript-x_10.0.0~dfsg-11+deb12u7_arm64.deb ... Unpacking ghostscript-x:arm64 (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ... Preparing to unpack .../4-ghostscript_10.0.0~dfsg-11+deb12u7_arm64.deb ... Unpacking ghostscript (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ... Preparing to unpack .../5-libgs10_10.0.0~dfsg-11+deb12u7_arm64.deb ... Unpacking libgs10:arm64 (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ... Preparing to unpack .../6-libgs10-common_10.0.0~dfsg-11+deb12u7_all.deb ... Unpacking libgs10-common (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ... Preparing to unpack .../7-libgs-common_10.0.0~dfsg-11+deb12u7_all.deb ... Unpacking libgs-common (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ... Preparing to unpack .../8-linux-headers-vendor-rk35xx_25.2.3_arm64.deb ... Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' starting. Cleaning directory /usr/src/linux-headers-6.1.99-vendor-rk35xx ... Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' finishing. Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' starting. Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' finishing. Unpacking linux-headers-vendor-rk35xx (25.2.3) over (25.2.3) ... Setting up libgs-common (10.0.0~dfsg-11+deb12u7) ... Setting up linux-headers-vendor-rk35xx (25.2.3) ... Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' starting. Configuring kernel-headers (6.1.99-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.99-vendor-rk35xx) using 8 CPUs - please wait ... SYNC include/config/auto.conf.cmd HOSTCC scripts/dtc/flattree.o HOSTCC scripts/dtc/dtc.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/kallsyms HOSTCC scripts/sorttable HOSTCC scripts/resource_tool HOSTCC scripts/asn1_compiler HOSTCC scripts/genksyms/genksyms.o YACC scripts/genksyms/parse.tab.[ch] HOSTCC scripts/selinux/mdp/mdp HOSTCC scripts/selinux/genheaders/genheaders 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.99-vendor-rk35xx) using 8 CPUs - please wait ... CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig CC scripts/mod/devicetable-offsets.s UPD scripts/mod/devicetable-offsets.h MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/file2alias.o HOSTCC scripts/mod/sumversion.o HOSTLD scripts/mod/modpost MODPOST scripts/mod/Module.symvers Done compiling kernel-headers (6.1.99-vendor-rk35xx). Done compiling kernel-headers tools (6.1.99-vendor-rk35xx). Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' finishing. Setting up tzdata (2025b-0+deb12u1) ... Current default time zone: 'Europe/Berlin' Local time is now: Tue Apr 1 16:15:44 CEST 2025. Universal Time is now: Tue Apr 1 14:15:44 UTC 2025. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up armbian-config (25.5.0-trunk.325.0401.114753) ... Setting up firefox-nightly (139.0a1~20250401094015) ... Setting up libgs10-common (10.0.0~dfsg-11+deb12u7) ... Setting up libgs10:arm64 (10.0.0~dfsg-11+deb12u7) ... Setting up ghostscript (10.0.0~dfsg-11+deb12u7) ... Setting up ghostscript-x:arm64 (10.0.0~dfsg-11+deb12u7) ... Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for desktop-file-utils (0.26-1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for libc-bin (2.36-9+deb12u10) ... Processing triggers for man-db (2.11.2-2) ... Log ended: 2025-04-01 16:15:46 Log started: 2025-04-02 09:42:43 (Reading database ... 218527 files and directories currently installed.) Preparing to unpack .../armbian-bsp-cli-orangepi5-plus-vendor_25.2.3_arm64.deb ... Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PCe1b9-V4064-H2670-B1e5d-R756d': 'preinst' starting. Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PCe1b9-V4064-H2670-B1e5d-R756d': 'preinst' finishing. Unpacking armbian-bsp-cli-orangepi5-plus-vendor (25.2.3) over (25.2.2) ... Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PC7d0b-Vcff1-H2670-B6e44-R89c9': 'postrm' starting. Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PC7d0b-Vcff1-H2670-B6e44-R89c9': 'postrm' finishing. Preparing to unpack .../firefox-nightly_139.0a1~20250401212749_arm64.deb ... Unpacking firefox-nightly (139.0a1~20250401212749) over (139.0a1~20250401094015) ... Preparing to unpack .../linux-headers-vendor-rk35xx_25.2.3_arm64.deb ... Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' starting. Cleaning directory /usr/src/linux-headers-6.1.99-vendor-rk35xx ... Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' finishing. Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' starting. Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' finishing. Unpacking linux-headers-vendor-rk35xx (25.2.3) over (25.2.3) ... Preparing to unpack .../linux-image-vendor-rk35xx_25.2.3_arm64.deb ... Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' starting. Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' finishing. Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' starting. Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' finishing. Unpacking linux-image-vendor-rk35xx (25.2.3) over (25.2.3) ... Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postrm' starting. Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postrm' finishing. Setting up linux-image-vendor-rk35xx (25.2.3) ... Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' starting. dkms: running auto installation service for kernel 6.1.99-vendor-rk35xx. dkms: autoinstall for kernel: 6.1.99-vendor-rk35xx. update-initramfs: Generating /boot/initrd.img-6.1.99-vendor-rk35xx update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.99-vendor-rk35xx Image Name: uInitrd Created: Wed Apr 2 09:43:11 2025 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17096044 Bytes = 16695.36 KiB = 16.30 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.99-vendor-rk35xx to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.1.99-vendor-rk35xx' update-initramfs: Armbian: done. Armbian: update last-installed kernel symlink to 'Image'... '/boot/Image' -> 'vmlinuz-6.1.99-vendor-rk35xx' Armbian: Debian compat: linux-update-symlinks install 6.1.99-vendor-rk35xx boot/vmlinuz-6.1.99-vendor-rk35xx Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' finishing. Setting up linux-headers-vendor-rk35xx (25.2.3) ... Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' starting. Configuring kernel-headers (6.1.99-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.99-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/srcpos.o HOSTCC scripts/dtc/treesource.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/kallsyms HOSTCC scripts/resource_tool 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.99-vendor-rk35xx) using 8 CPUs - please wait ... CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig CC scripts/mod/devicetable-offsets.s UPD scripts/mod/devicetable-offsets.h MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/sumversion.o HOSTCC scripts/mod/file2alias.o HOSTLD scripts/mod/modpost MODPOST scripts/mod/Module.symvers Done compiling kernel-headers (6.1.99-vendor-rk35xx). Done compiling kernel-headers tools (6.1.99-vendor-rk35xx). Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' finishing. Setting up armbian-bsp-cli-orangepi5-plus-vendor (25.2.3) ... Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PCe1b9-V4064-H2670-B1e5d-R756d': 'postinst' starting. Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PCe1b9-V4064-H2670-B1e5d-R756d': 'postinst' finishing. Setting up firefox-nightly (139.0a1~20250401212749) ... Processing triggers for initramfs-tools (0.142+deb12u1) ... update-initramfs: Generating /boot/initrd.img-6.12.12+bpo-arm64-16k W: Possible missing firmware /lib/firmware/rtl_nic/rtl8126a-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8126a-2.fw for module r8169 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.12.12+bpo-arm64-16k Image Name: uInitrd Created: Wed Apr 2 09:44:31 2025 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 57076607 Bytes = 55738.87 KiB = 54.43 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.12.12+bpo-arm64-16k to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.12.12+bpo-arm64-16k' update-initramfs: Armbian: done. Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for man-db (2.11.2-2) ... Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for desktop-file-utils (0.26-1) ... Log ended: 2025-04-02 09:44:34 Any tips how to resolve this and boot from the nvme again? I know initramfs exists and I can wrap my mind arround it what it does, but in the last years never had to solve anything regarding it. I do not know where to look or start debugging

Hello, this is my first time setting up orange pi + Armbian Linux. I'm a linux newbie. I've been trying to install various version of the Debian 12 Desktop images working. I can always get into it via SSH but never get a display out via HDMI except fro Ubuntu 24.04 Noble Gnome Images Success Armbian_25.2.1_Orangepi5-plus_noble_vendor_6.1.99_gnome_desktop Images Failed Armbian_25.2.1_Orangepi5-plus_bookworm_current_6.12.13_cinnamon-backported-mesa_desktop Armbian_25.2.1_Orangepi5-plus_bookworm_current_6.12.13_xfce_desktop After SSH and setting up roo/user accounts I always get to the message Now starting desktop environment... But it doesn't do anything afterwards. I've done initial troubleshooting verifying that HDMI cables work using different monitors Trying different power supplies trying different microSDs Is there something else I can check on the Debian bookworm variants to see what the issue is? Thanks for taking a look.

Where has enabling things like I2C moved to ? I do not see it any more in armbian-config (at least on the Orange Pi 5 plus image) Thanks

I have Linux 6.1.99-vendor-rk35xx #1 SMP Wed Mar 19 11:16:36 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux on my Orange Pi 5 Plus. Trying to setup VM with CPU host-passthrough but can only use cortex-a76 custom with TCG. If I try to use virt type KVM and host-passthrough on virt-manager I get: Error starting domain: internal error: process exited while connecting to monitor: 2025-03-26T08:55:56.040008Z qemu-system-aarch64: Failed to put registers after init: Invalid argument Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn ret = fn(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/virt-manager/virtManager/object/domain.py", line 1402, in startup self._backend.create() File "/usr/lib/python3/dist-packages/libvirt.py", line 1379, in create raise libvirtError('virDomainCreate() failed') libvirt.libvirtError: internal error: process exited while connecting to monitor: 2025-03-26T08:55:56.040008Z qemu-system-aarch64: Failed to put registers after init: Invalid argument

The images Debian Bookworm "Minimal/IOT images with Armbian Linux v6.12" generate what I understand is bad partition information. Once flashed to the SD card, the partition won't be recognised by Linux hinted by the message "couldn't find valid filesystem superblock", therefore they can't be mounted. The desktop image is fine though and the partitions generated after flashing into the SD card are recognised by the "disks" application. I've also tried with the Ubuntu-rockchip image which also generates correct/mountable partition information. I've tested this for the minimal images for OrangePi Max as well as OrangePi 5 Plus. The images were flashed with both "Raspberry Pi Imager" and "imageusb", since for some reason the recommended "USBImager" won't list my usb devices on Windows

Since at least one week I find the system every morning with solid red led, waiting for a command in uboot. When looking at the journal messages, the last messages are always: Feb 10 23:45:01 etnas2 CRON[5176]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Feb 10 23:45:01 etnas2 CRON[5177]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) Feb 10 23:45:01 etnas2 CRON[5176]: pam_unix(cron:session): session closed for user root Feb 11 00:00:01 etnas2 CRON[5213]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Feb 11 00:00:01 etnas2 CRON[5212]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Feb 11 00:00:01 etnas2 CRON[5215]: (root) CMD (/usr/lib/armbian/armbian-apt-updates) Feb 11 00:00:01 etnas2 CRON[5214]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) Feb 11 00:00:01 etnas2 CRON[5212]: pam_unix(cron:session): session closed for user root Feb 11 00:00:03 etnas2 CRON[5213]: pam_unix(cron:session): session closed for user root Feb 11 00:00:49 etnas2 systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service... Feb 11 00:00:49 etnas2 systemd[1]: Starting logrotate.service - Rotate log files... Feb 11 00:00:49 etnas2 systemd[1]: dpkg-db-backup.service: Deactivated successfully. Feb 11 00:00:49 etnas2 systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service. Feb 11 00:00:49 etnas2 armbian-ramlog[5278]: Tue Feb 11 12:00:49 AM CET 2025: Syncing logs to storage Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: sending incremental file list Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: ./ Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: Xorg.0.log Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: Xorg.0.log.old Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: armbian-hardware-monitor.log Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: auth.log Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: boot.log Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: btmp Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: cron.log Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: kern.log Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: lastlog Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: syslog Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: user.log Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: wtmp Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: cups/access_log Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/ Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/lightdm.log Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/lightdm.log.old Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/seat0-greeter.log Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/seat0-greeter.log.old Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/x-0.log Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/x-0.log.old Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: samba/log.nmbd Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: samba/log.smbd Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: sent 3,469,661 bytes received 448 bytes 2,313,406.00 bytes/sec Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: total size is 4,794,812 speedup is 1.38 Feb 11 00:00:50 etnas2 systemd-journald[588]: Time spent on flushing to /var/log/journal/1141762e43884d8b9eb5d35b11be4daa is 55.926ms for 1057 entries. Feb 11 00:00:50 etnas2 systemd-journald[588]: System Journal (/var/log/journal/1141762e43884d8b9eb5d35b11be4daa) is 17.4M, max 20.0M, 2.5M free. Feb 11 00:00:50 etnas2 systemd-journald[588]: Received client request to flush runtime journal. Feb 11 00:00:50 etnas2 systemd-journald[588]: Data hash table of /var/log/journal/1141762e43884d8b9eb5d35b11be4daa/system.journal has a fill level at 122.2 (5561 of 4551 items, 2621440 file size, 471 bytes per hash table item), suggesting rotation. Feb 11 00:00:50 etnas2 systemd-journald[588]: /var/log/journal/1141762e43884d8b9eb5d35b11be4daa/system.journal: Journal header limits reached or header out-of-date, rotating. After that no more messages, until the system gets booted again. The issue seems similar to this post. Power supply and system temperatures are fine, the system is running from EMMC memory so issues with SD cards are ruled out. When I boot off e.g. Jonathan Riek's Ubuntu 24.04 using the NVME drive, then all is fine: no nightly crashes. I don't recall this issue when I installed Armbian 24.11.2 back in December, so possibly it came when I upgraded to 24.11.3 using `apt upgrade` (but could be wrong!) I have added the cron job `*/1 * * * * /usr/bin/dmesg > $HOME/kernel-dmesg.txt` as suggested. Looking at `/etc/cron.d` and more precisely `armbian-trunctate-log`, I see that `armbian-trunctate-logs` runs every 15 minutes, but it invokes `armbian-ramlog` in practice only just after mignight probably because `/var/log` is over 75% full. Then `/usr/lib/armbian/armbian-truncate-logs` proceeds to synchronize (using `rsysnc`) the logs files in zram (`/var/log`). After that, the script calls `/usr/sbin/logrotate --force /etc/logrotate.conf` but this rotation takes place on `/var/log.hdd/`. Somehow that does not sound right... I would have thought it would be the other way around.... Finally, it just truncates the files in `/var/log`. That could be dangerous as processes have these files open... Logrotate sends a signal to processes to let them know they should reopen the log files. armbianmonitor -u Thanks in advance for any help.

Hi can anyone advise if they have come accross this issue. so somehow HDMIRX seems to be the hdmi input controller starts to freak out for no reason there is nothing plugged into it EVER and will randomly start to outpur this to console im thinking maybe the HDMIRX is faulty and want to remove it, I have tried removing it removed the DTB , decompiled and edited and removed it from DTB, tied to blacklist it but with no effect it does not stop spamming and the device [ 89.603095] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed! [ 89.613765] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed! [ 89.624917] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed! [ 89.635554] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed! [ 89.704256] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_controller_init wait timer base lock failed! not for my last attemt i want to check if anyone has the .config for the kernel and perhaps knows what the driver / module is called this way I am guaranteed i will not see it again. Note: I have reinsatlled multiple distros to check and it keeps happening randomly so any input on this would be great. Much appreciated and thanks in advance.

Hi, I've come from Joshua's 24.04 Server build. I was concerned that the support was dropping off as he's having a well deserved break. I've installed the latest Server build from here. https://dl.armbian.com/orangepi5-plus/Noble_current_server-kisak Works fine, have moved it to EMMC and removed the SD card. I use a USB power meter to see how much juice it uses. I noticed this build uses about 20 to 25% more when idle or under load compared to Josh's 6.1 kernel build. I am suspecting 6.12 has enabled more hardware in the OPi5+ and this is the reason. Is there a way to disable some of the HW to lower the idle power usage? On average it uses 5w on idle. Thanks. Loving the Armbian build.

I'm adding this here as I want to contribute to the community, but I'm still not sure how. I've been playing with Armbian Build lately and found it's great for quick build images for testing purposes before it's officially made available. So I started build my own images with i3, mate, kde, and I noticed that, in my personal taste, the one that was better suited for my needs was Sway, but there's no desktop image with it. So I built a Server version and start installing it. I know it may not be of interest of everybody, so I was planning to do it for myself, so I can continue building with the interface, but having Sway "automatically" installed. If/when I'm able to do this, I could put this in CSC mode in the repo, or I shouldn't do that as it's going to bloat the system more as there's no interest in having yet another WM/DE available? I'm thinking of this as an alternative to i3,as I noticed that, in my board, Wayland is performing much better than XOrg/X11.

I'm using Orange Pi 5 Plus, I've updated to latest by apt upgrade but seems to be stuck on old version as you can see 25.2.2 but kernel is still 6.1.75 : # uname -a Linux abeure 6.1.75-vendor-rk35xx #1 SMP Wed Aug 21 11:45:59 UTC 2024 aarch64 GNU/Linux # cat /var/log/apt/history.log Start-Date: 2025-02-25 01:00:39 Commandline: /usr/bin/unattended-upgrade Upgrade: armbian-firmware:arm64 (25.2.1, 25.2.2) End-Date: 2025-02-25 01:00:42 Start-Date: 2025-02-25 01:01:10 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-u-boot-orangepi5-plus-vendor:arm64 (24.11.1, 25.2.2) End-Date: 2025-02-25 01:01:11 Latest version https://www.armbian.com/orange-pi-5-plus/ does not seems to be fetched. Armbian 25.2.1 Bookworm Minimal / IOT Kernel: 6.1.99, Size: 295.5 MB, Release date: Feb 15, 2025 Can you explain what i've missed ?

Happy New Year for all, My old Samsung Monitor stopped working some days ago, and I dont know if it will be fixed, so I decided to buy a new LG 27'' Monitor. My Zorin OS and Windows on X64, Raspbian and Ubuntu On Raspberry PIs are working properly. But booting Armbian - Ubuntu 24.04 (Noble) on "Orange PI 5" and "Orange PI 5 Plus" My New monitor refuses to show any image (only black screen). "Orange PI OS XFCE" on "Orange PI 5" is OK on my new monitor. I took a litle look at boot files but I didn't find anything to fix this problem. Any idea to solve this problem??? Thanks, Cury

I have built quite a few Debian12 Desktop images from github.com/armbian/build for a Debian Bookworm/XFCE/Vendor Kernel environment and noticed that recent vendor kernels do not have I2C-2.M0 as a kernel module listed within armbian-config. It appears that only two kernel modules are to be found, one being Panthos, the other involving a change in frequence of some item. This image does include I2C-2.mo: Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.84_xfce_desktop.img which includes kernel: Linux Atlas 6.1.99-vendor-rk35xx #1 SMP Fri Feb 21 18:11:03 UTC 2025 aarch64 GNU/Linux But these images do not contain the I2C-2.m0 kernel modules: Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.84_xfce_desktop.img (same kernel build as Ambian 25.0.2.0-trunk listed above sans I2C-2-m0) Armbian-unofficial_25.05.0-trunk_Orangepi5-plus_bookworm_current_6.12.17_xfce_desktop.img Armbian-unofficial_25.05.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.99_xfce_desktop.img Is it now necessary to customize the compile options for the kernel and choose that module for compilation when building newer vendor images? It would make sense (to me at least) to have each build option to have vendor kernels contain the same precompiled kernel modules for simplicity sake. I'm not even sure if the I2C-2.m0 is available or an option in the later vendor kernels to build.

Hello all, i feel i may have made a fatal mistake. I was running Armbian Bookworm server on an Orange PI 5 Plus. All was well until the latest update. After updating, I thought i'd checkout what's changed in arbian-config. I enabled rolling releases and rebooted when prompted. Sadly, the OPI5+ now wont boot. Anything I can do? Or do I need to reinstall everything? Thanks in advaced for anyone taking the time to help Shad

Hi everybody, I installed Deb 12 Cinnamon Armbian flavor on an Orange PI 5 and Orange PI 5 Plus. This: dl.armbian.com/orangepi5-plus/Bookworm_current_cinnamon-backported-mesa I want to test 'virt-manager' but qemu is not available for installation. Error on console: packages are updated me@orangepi5-plus:~$ sudo apt install qemu [sudo] senha me: Lendo listas de pacotes... Pronto Construindo árvore de dependências... Pronto Lendo informação de estado... Pronto package qemu is not available, mas é referenciado por outro pacote. Isto pode significar que o pacote está faltando, ficou obsoleto ou está disponível somente a partir de outra fonte E: O pacote 'qemu' não tem candidato para instalação Is there a chance to have qemu available. armbianmonitor -u https://paste.next.armbian.com/egexohofom Thanks, Cury

I have a new Orange Pi 5 plus 16GB. Seems a pretty cool board and I want to replace my old Rpi 4 for Media center and Home assistant. I tried several distribution but can't get all my stuff working. The OPI5+ is attached to an onkio 5.1 receiver and the receiver go to a FHD TV. What is want to achieve is in Kodi 1. play video with GPU 2. libCec in Kodi to control Onkio volume 3. Passthrough audio Is there a working solution? Thank you

Hello everyone, This is my 1st post on the forum. My intention with this post is not to report a specific issue that I am running into, but more because I would like to collect info and suggestions from people with more experience than myself. I've recently received an Orange Pi 5 Plus and have spent a bit of time exploring operating systems suitable for this system and have settled on the Armbian solution. I'm a HW designer by trade, and have done some SW work, but I do not consider myself proficient in SW at all. I find my way around things, but that's about as far as it goes.... For the my planned use of the OPi5+, I will need eMMC boot (for the improved OS performance and longevity) and access to the various interfaces (mainly SPI and I2C) on the GPIO header. What I have discovered so far: - Version 6.1 of the Armbian built kernel supports the GPIO interfaces quite well (I haven't actually communicated with anything yet, just got the interfaces showing up in /dev), but I could not get it to see the eMMC storage on the board. I tried various different options and flavours of the 6.1 images and I never saw /dev mmcblk0 listed. - Version 6.10 kernel builds were successful at accessing the eMMC (/dev/mmcblk0 was present) and I have successfully transferred the OS to the eMMC storage on the board. However this version of the kernel has a limited number of device tree overlays (mostly different UART options, and one I2C option). I'm assuming that the 6.10 kernel is quite a new build and that more support for the board's IO should be available soon. Did I overlook something on the 6.1 version regarding the eMMC support? Am I missing something regarding overlays in the 6.10 build? My thinking is to stay with 6.10 as it supports eMMC and it's the newest kernel version. Cheers Volt