Search the Community

Hello, I've been using https://joshua-riek.github.io/ubuntu-rockchip-download/boards/orangepi-5-plus.html with a custom kernel that I built to activate my TPM2.0 device and it works. Now I'm asked to use an UEFI compatible image with my Orange Pi 5 Plus. So what I did is more or less the same thing that in here But instead of the legacy kernel I used the 6.1.115-rockchip-vendor-rk35xx kernel and my device booted, I got an HDMI output, etc. And then I updated it to my custom kernel (6.1.0-1027-rockchip) that has the necessary configurations to allow TPM over SPI. Now I'm trying to activate my TPM2.0 as I did before. To do that I added my compiled *.dtbo (rk3588-spi0-tpm-cs1.dtbo) to /boot/dtb/rockchip/overlay and activated it with armbian-config. After reboot this is my /boot/armbianEnv.txt orangepi@uefi-arm64:~$ cat /boot/armbianEnv.txt verbosity=1 bootlogo=true console=both extraargs=cma=256M overlay_prefix=rk3588 fdtfile=rockchip/rk3588-orangepi-5-plus.dtb rootdev=UUID=3e555b58-fdf4-4e2f-a3af-a8ecfd8034b6 rootfstype=ext4 overlays=spi0-tpm-cs1 param_spidev_spi_bus=0 However I still can't see my tpm under /dev/. I don't know what I'm missing, I'm quite new to this sorry Thank you for your time

Hi all, digging into the Orange Pi 6 Plus specs for a potential build. Can anyone confirm the M.2 slots (the two Key-M 2280 ones) are PCIe Gen 4 with x4 lanes each? Official docs mention NVMe support but are light on details. I'm curious if this could handle a low-end GPU like an RX 570 (or even lower) through an NVMe-to-PCIe adapter/riser—thinking for light gaming or compute tasks. Has anyone tried eGPU setups on this board or similar ARM SBCs? What about power delivery, drivers, and performance? Running Linux (Ubuntu/Debian probably). Thanks for any insights or benchmarks!

In settings -> keyboard -> view and customize shortcuts -> launchers -> search I am trying to set this to Windows Key + S, it doesn't register the windows key at all as being pressed, so what keyboard do I choose to be able to use the full k400r keyboard inclusive of the windows key. Many thanks Newbie (please be nice, I'm new to Armbian and SBC's)

Hi , I am trying to configure orangepi to turn on and turn off tv. I installed and used cec-ctl to register the boad as playbac device. And then was able to put the TV on standby mode via sudo cec-ctl --device /dev/cec0 --standby --to 0 but not able to find how to turn ON the TV. Can someone please help. Thanks Manish

Hi Guys, I just did a new custom Armbian build ./compile.sh BOARD=orangepi5-plus BRANCH=vendor RELEASE=noble KERNEL_ONLY=yes KERNEL_CONFIGURE=no. The image is Armbian-unofficial_25.11.0-trunk_Orangepi5-plus_noble_vendor_6.1.115_cinnamon_desktop and when I installed it on orangepi I see it is not supporting Panfrost/Mail: glxinfo | grep -E "OpenGL renderer|OpenGL version" OpenGL renderer string: llvmpipe (LLVM 20.1.2, 128 bits) OpenGL version string: 4.5 (Compatibility Profile) Mesa 25.0.7-0ubuntu0.24.04.2 but for older image Old_Armbian-unofficial_25.08.0-trunk_Orangepi5-plus_noble_vendor_6.1.115_cinnamon_desktop All was well glxinfo | grep -E "OpenGL renderer|OpenGL version" OpenGL renderer string: Mali-G610 (Panfrost) OpenGL version string: 3.1 Mesa 25.0.7-0ubuntu0.24.04.2 I did need to enable "ARM Mail Display Processor" under Device Drivers -> Graphics support -> ARM devices before I perform custom build. And I did this for both OS version 25.11.0 and 25.08.0. But newer version is not able to use it. Thanks Manish

I've heard people say that the Orange Pi is a "budget alternative" to the Raspberry Pi. On one hand, the Raspberry Pi has an excellent community, with a large user base that could really help you in your learning journey. On the other hand, the Orange Pi offers great value for money, and it's really tempting because the Raspberry Pi can be a bit pricey. What's your suggestion?

Hello, I just got a wifi 7 adapter (QCNCM865) and I was thinking the ath12k driver was available starting from kernel 6.13, I'm running the edge kernel 6.16.4 and the ath12k driver is failing to load and I can't find any wireless drivers in /usr/lib/modules/6.16.4-edge-rockchip64/kernel/net/wireless. Do I need to rebuild the kernel with the ath12k driver? or is there a kernel version available with that driver? Thanks for your help!

Hi Guys, I just did a new custom Armbian build ./compile.sh BOARD=orangepi5-plus BRANCH=vendor RELEASE=noble KERNEL_ONLY=yes KERNEL_CONFIGURE=no. The image is Armbian-unofficial_25.11.0-trunk_Orangepi5-plus_noble_vendor_6.1.115_cinnamon_desktop and when I installed it on orangepi I see it is not supporting Panfrost/Mail: glxinfo | grep -E "OpenGL renderer|OpenGL version" OpenGL renderer string: llvmpipe (LLVM 20.1.2, 128 bits) OpenGL version string: 4.5 (Compatibility Profile) Mesa 25.0.7-0ubuntu0.24.04.2 but for older image Old_Armbian-unofficial_25.08.0-trunk_Orangepi5-plus_noble_vendor_6.1.115_cinnamon_desktop All was well glxinfo | grep -E "OpenGL renderer|OpenGL version" OpenGL renderer string: Mali-G610 (Panfrost) OpenGL version string: 3.1 Mesa 25.0.7-0ubuntu0.24.04.2 I did need to enable "ARM Mail Display Processor" under Device Drivers -> Graphics support -> ARM devices before I perform custom build. And I did this for both OS version 25.11.0 and 25.08.0. But newer version is not able to use it. Thanks Manish

due to network limitations， how to compile Ubuntu 22.04 Gnome OS image in offline mode, build.sh need to download many debs，can I download them in advance，then install them locally. I have already downloaded kernel and uboot.

Hardware: OrangePI-5-Plus (rk3588), with "32 GB" of RAM Operating System: Debian Trixie (pure, except EFI boot and Armbian edge kernel) Root File System: Ext4 (encrypted) Desktop: KDE Plasma 6.3.6 (wayland, GDM3), KDE Frameworks version: 6.13.0, QT version: 6.8.2 EFI Source: https://github.com/edk2-porting/edk2-rk3588 The boot messages, after a few starts (spaced apart) of the low-memory-monitor.service, say there's a failure to start it. After booting is complete, here's a screenshot of the output of: systemctl status low-memory-monitor.service This error didn't show up until I installed a number of packages. I tracked down the offending package from the Trixie repository: Package: xfsprogs Version: 6.13.0-2+b1 Size: 4774 kB Description: A set of commands to use the XFS filesystem, including mkfs.xfs Once this package was removed, the error vanished, and a repeat of the above Status command reported low-memory-monitor-service as active and okay. I also found that, while the error occurred with the Armbian edge 6.16.4 kernel, it did NOT occur with the Debian 6.16.3 kernel. Kernel With The Error (kernel source: Armbian trixie) --------------------- Package: linux-image-edge-rockchip64 (Armbian Linux edge kernel image 6.16.4-edge-rockchip64) Version: 25.8.1 Size: 282 MB Kernel Without The Error (kernel source: Debian trixie-backports) ------------------------ Package: linux-image-6.16.3+deb13-arm64-unsigned (Linux 6.16 for 64-bit ARMv8 machines) Version: 6.16.3-1~bpo13+1 Size: 210 MB I also briefly tried regressing the Armbian edge kernel from 25.8.1 (6.16.4) to the previously available version of 25.5.2, which was 6.16.0-rc3 (I think). The error occurred with that kernel as well. An Effect of This Bug (Possibly) When this error was showing up, I was once using the internet (firefox-esr package version 140.3.1esr-1~deb13u1) for a while, when after closing it, I discovered that my desktop background image had changed on its own. I could not change it back, no matter what I did (in the KDE settings gui). I could change it to something else, but whenever I changed it back, the altered image returned instead of what it should have been. But once I rebooted, the background was back to normal. While this one experience (very much an outlier) may not be conclusive, it is indicative of a possible memory leak.

Hey @amazingfate, I have an issue with the build-in IR receiver on my OPI5+: ##O#O## OS: Armbian 25.8.1 noble aarch64 ####### Host: Orange Pi 5 Plus ########### Kernel: 6.1.115-vendor-rk35xx ############# Uptime: 2 mins ############### Packages: 1934 (dpkg), 5 (snap) ################ Shell: bash 5.2.21 ################# Resolution: 3840x2160 ##################### DE: GNOME 46.0 ##################### WM: Mutter ################# WM Theme: Adwaita Theme: Adwaita [GTK2/3] Icons: Adwaita [GTK2/3] Terminal: x-terminal-emul CPU: (8) @ 1.800GHz Memory: 2585MiB / 15957MiB After a reboot it works just fine, but once I suspend/resume it stops working. Logs look clear of errors. I have tried to troubleshoot with ChatGPT but goin' in circles and gave up. Lastly ended up with some speculations from it like: static int rockchip_pwm_remotectl_resume(struct device *dev) { struct remotectl_dev *rc_dev = dev_get_drvdata(dev); // Re-init or restart the device if (rc_dev && rc_dev->restart) rc_dev->restart(rc_dev); return 0; } static const struct dev_pm_ops rockchip_pwm_remotectl_pm_ops = { .resume = rockchip_pwm_remotectl_resume, }; static struct platform_driver rockchip_pwm_remotectl_driver = { .probe = rockchip_pwm_remotectl_probe, .driver = { .name = "rockchip_pwm_remotectl", .pm = &rockchip_pwm_remotectl_pm_ops, }, }; Do you think this is the problem, or if not can I share some details so you can try to find it?

##O#O## OS: Armbian 25.8.1 noble aarch64 ####### Host: Orange Pi 5 Plus ########### Kernel: 6.1.115-vendor-rk35xx ############# Uptime: 1 day, 8 hours, 17 mins ############### Packages: 1852 (dpkg), 5 (snap) ################ Shell: bash 5.2.21 ################# Resolution: 3840x2160 ##################### DE: GNOME 46.0 ##################### WM: Mutter ################# WM Theme: Adwaita Theme: Adwaita [GTK2/3] Icons: Adwaita [GTK2/3] Terminal: x-terminal-emul CPU: (8) @ 1.800GHz Memory: 7245MiB / 15957MiB FreeRDP client: freerdp2-wayland: Инсталирана: 2.11.5+dfsg1-1build2 Кандидат: 2.11.5+dfsg1-1build2 Таблица с версиите: *** 2.11.5+dfsg1-1build2 500 500 http://ports.ubuntu.com noble/universe arm64 Packages 100 /var/lib/dpkg/status --------------------------------------------------------------------------------------------------------- This is Build configuration: BUILD_TESTING=OFF BUILTIN_CHANNELS=ON HAVE_AIO_H=1 HAVE_EXECINFO_BACKTRACE=1 HAVE_EXECINFO_BACKTRACE_SYMBOLS=1 HAVE_EXECINFO_BACKTRACE_SYMBOLS_FD=1 HAVE_EXECINFO_H=ON HAVE_EXECINFO_HEADER=1 HAVE_FCNTL_H=1 HAVE_GETLOGIN_R=1 HAVE_GETPWUID_R=1 HAVE_INTTYPES_H=1 HAVE_JOURNALD_H=TRUE HAVE_MATH_C99_LONG_DOUBLE=1 HAVE_PIXMAN_REGION=OFF HAVE_POLL_H=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK=ON HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIBS= HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL=1 HAVE_SYSLOG_H=1 HAVE_SYS_EVENTFD_H=1 HAVE_SYS_FILIO_H= HAVE_SYS_MODEM_H= HAVE_SYS_SELECT_H=1 HAVE_SYS_SOCKIO_H= HAVE_SYS_STRTIO_H= HAVE_SYS_TIMERFD_H=1 HAVE_TM_GMTOFF=1 HAVE_UNISTD_H=1 HAVE_XI_TOUCH_CLASS=1 WITH_ALSA=ON WITH_CAIRO=ON WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLANG_FORMAT=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CUPS=ON WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_RDPGFX=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF_AVAILABLE=0 WITH_DEBUG_URBDRC=OFF WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_EVENTFD_READ_WRITE=1 WITH_FAAC=OFF WITH_FAAD2=OFF WITH_FFMPEG=OFF WITH_GFX_H264=OFF WITH_GPROF=OFF WITH_GSM=OFF WITH_GSSAPI=OFF WITH_ICU=ON WITH_INTERNAL_MD4=OFF WITH_INTERNAL_MD5=OFF WITH_IPP=OFF WITH_JPEG=ON WITH_KERBEROS=ON WITH_LAME=OFF WITH_LIBRARY_VERSIONING=ON WITH_LIBSYSTEMD=ON WITH_MACAUDIO=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_OPENCL=OFF WITH_OPENH264=OFF WITH_OPENSLES=OFF WITH_OPENSSL=ON WITH_OSS=ON WITH_PAM=ON WITH_PCSC=ON WITH_PROFILER=OFF WITH_PROXY=OFF WITH_PULSE=ON WITH_SAMPLE=OFF WITH_SANITIZE_ADDRESS=OFF WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_MEMORY=OFF WITH_SANITIZE_MEMORY_AVAILABLE=1 WITH_SANITIZE_THREAD=OFF WITH_SANITIZE_THREAD_AVAILABLE=1 WITH_SERVER=ON WITH_SERVER_CHANNELS=ON WITH_SERVER_INTERFACE=ON WITH_SHADOW=ON WITH_SMARTCARD_INSPECT=OFF WITH_SOXR=OFF WITH_SSE2=OFF WITH_SWSCALE=OFF WITH_THIRD_PARTY=OFF WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK_AVAILABLE=1 WITH_VERBOSE_WINPR_ASSERT=ON WITH_WAYLAND=ON WITH_WINPR_TOOLS=ON WITH_X11=ON WITH_XCURSOR=ON WITH_XDAMAGE=ON WITH_XEXT=ON WITH_XFIXES=ON WITH_XI=ON WITH_XINERAMA=ON WITH_XKBFILE=ON WITH_XRANDR=ON WITH_XRENDER=ON WITH_XSHM=ON WITH_XTEST=ON WITH_XV=ON WITH_ZLIB=ON Hi guys, I am using `wlfreerdp` to access remote Win 11 but the client I have installed does not support hwacc and is laggy on 4K monitor. Network is 1G LAN. I have already built Moonlight with ffmpeg/rkmpp hwacc and it works amazing. Can anyone advice if I can do the same, building the FreeRDP client with hwacc? CC:@amazingfate (I know u know how to do it ;) )

Sorry if I have come to the wrong place. A friend has given me an Orange Pi 5 Plus, fitted with a 1GB SSD, and I have been trying to get it started up. According to its previous owner, the SSD had been completely erased (I don't know why). It had no SD card with it when I got it. I downloaded the online instruction manuals, and set about trying to start it up, using a suitable 32GB SD card. I first tried with (OrangePi) Ubuntu, but ran into problems using Balena Etcher. It apparently transfers the Ubuntu Image to the SD card, but just as it appears to complete the process of verification, it produces a helpful error message ('There was an Error'....). I also tried with other OSes, with the same result, so it seems to be either me or the OPi which is having problems. After a bit of research, I found a description of using the Linux command 'dd' to transfer an image, so I did this, under a machine with Linux Mint - this appeared to go OK. I then plugged in the SD card, and powered up the OPi. After a delay, I get what looks like a Ubuntu 'splash' page on screen, and it appears to go through an installation process (? not sure if thats whats happening). However, after several minutes, there is a message saying there is an error, and a desktop session will be started to allow debugging - but I can't get anything else to happen. I have asked the previous owner, but he says probably the bootloader is missing. (I suspect he never got it running). Here I come unstuck - I can't find any info on bootloaders - like what it is, where to get it, what to do with it, etc, so I am hoping someone here can point me in the right direction. I have gone through the instruction manual, but it seems to be slightly out of date, and I had no success using its instructions. Ideally, I would like to boot the OPi from the SSD, if that is possible, but have no idea how to go about this - and there seems to be a great deal of conflicting (wrong?) info online. I did try the Orange Pi 'official' forums, but got lost in the chinese messages which came up.

HW: OrangePi5 Plus 32 32 GB RAM 512 GB NVME 5K Monitor Image: Armbian_25.8.1_Orangepi5-plus_trixie_vendor_6.1.115_xfce_desktop.img prepare system before each case dd if=u-boot-V2024.04-orangepi5-plus-spi.img of=/dev/mtdblock0 flash_erase /dev/mtd0 0 0 case 1: 1. copy image to 64GB uSD 2. booting 3. system comes up with xfce 4. sudo apt-get -y update; apt-get -y upgrade 5. reboot 6. system comes up, without desktop. system is reachable with ssh case 2: 1. copy image to 64GB uSD 2. booting 3. system comes up with xfce 4. armbian-install 5. choose boot from mtd flash 6. choose nvme0n1p1 6. update mtdblock0 7. reboot 8. system comes up, without desktop. system is reachable with ssh any idea whats going wrong?

the issue is as follows: 1. When using the Type-C interface to connect to an external monitor, the display works normally if the monitor is connected after the development board has started. 2. If the monitor is disconnected and then reconnected after approximately several hours (possibly more than 6 hours), the display fails to show any image. I used the `armbianmonitor -u` command, and it output the following URL. https://paste.armbian.com/foyecusoju If the Type-C interface is functioning normally, the latest output from `dmesg -w` would show the following: [ 1155.922647] xhci-hcd xhci-hcd.15.auto: xHCI Host Controller [ 1155.922692] xhci-hcd xhci-hcd.15.auto: new USB bus registered, assigned bus number 7 [ 1155.922885] xhci-hcd xhci-hcd.15.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0002008002010010 [ 1155.922937] xhci-hcd xhci-hcd.15.auto: irq 116, io mem 0xfc000000 [ 1155.923133] xhci-hcd xhci-hcd.15.auto: xHCI Host Controller [ 1155.923152] xhci-hcd xhci-hcd.15.auto: new USB bus registered, assigned bus number 8 [ 1155.923173] xhci-hcd xhci-hcd.15.auto: Host supports USB 3.0 SuperSpeed [ 1155.923455] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01 [ 1155.923476] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1155.923491] usb usb7: Product: xHCI Host Controller [ 1155.923502] usb usb7: Manufacturer: Linux 6.1.115-vendor-rk35xx xhci-hcd [ 1155.923515] usb usb7: SerialNumber: xhci-hcd.15.auto [ 1155.924750] hub 7-0:1.0: USB hub found [ 1155.924811] hub 7-0:1.0: 1 port detected [ 1155.925434] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM. [ 1155.925607] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01 [ 1155.925625] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1155.925638] usb usb8: Product: xHCI Host Controller [ 1155.925649] usb usb8: Manufacturer: Linux 6.1.115-vendor-rk35xx xhci-hcd [ 1155.925660] usb usb8: SerialNumber: xhci-hcd.15.auto [ 1155.928950] hub 8-0:1.0: USB hub found [ 1155.929019] hub 8-0:1.0: 1 port detected [ 1156.590377] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 3840x2160p60, type: 10(if:DP0, flag:0x0) for vp2 dclk: 533120000 [ 1156.590574] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] dclk_out2 div: 2 dclk_core2 div: 2 [ 1156.590639] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] set dclk_vop2 to 533120000, get 533119995 [ 1156.621808] dw-dp fde50000.dp: full-training link: 4 lanes at 5400 MHz [ 1156.635430] dw-dp fde50000.dp: clock recovery succeeded [ 1156.644918] dw-dp fde50000.dp: channel equalization succeeded [ 1156.657348] rockchip-vop2 fdd90000.vop: [drm] vop enable intf:200 [ 1157.337766] dw-dp fde50000.dp: test_type0 is not support [ 1157.339516] dw-dp fde50000.dp: test_type0 is not support [ 1159.801886] usb 7-1: new high-speed USB device number 2 using xhci-hcd [ 1159.942247] usb 7-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11 [ 1159.942271] usb 7-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 1159.942278] usb 7-1: Product: USB 2.0 Hub [ 1159.978762] hub 7-1:1.0: USB hub found [ 1159.978833] hub 7-1:1.0: 4 ports detected [ 1160.375255] usb 7-1.3: new full-speed USB device number 3 using xhci-hcd [ 1160.583425] usb 7-1.3: New USB device found, idVendor=222a, idProduct=0001, bcdDevice= 0.02 [ 1160.583438] usb 7-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1160.583441] usb 7-1.3: Product: ILITEK-TP [ 1160.583443] usb 7-1.3: Manufacturer: ILITEK [ 1160.653326] input: ILITEK ILITEK-TP as /devices/platform/usbdrd3_0/fc000000.usb/xhci-hcd.15.auto/usb7/7-1/7-1.3/7-1.3:1.0/0003:222A:0001.0005/input/input26 [ 1160.708695] input: ILITEK ILITEK-TP Mouse as /devices/platform/usbdrd3_0/fc000000.usb/xhci-hcd.15.auto/usb7/7-1/7-1.3/7-1.3:1.0/0003:222A:0001.0005/input/input28 [ 1160.709353] hid-multitouch 0003:222A:0001.0005: input,hiddev97,hidraw2: USB HID v1.10 Mouse [ILITEK ILITEK-TP] on usb-xhci-hcd.15.auto-1.3/input0 If it is not functioning normally, it will not output any content.

On the OrangePI-5-Plus, using an edge kernel, I've found that the desktop environment's GPU rendering works very smoothly on Wayland, in KDE 6 on Debian Trixie. It renders much more smoothly than gnome with Wayland (it's been my experience that the edge kernel is the only one that works). But I've encountered a major rendering bug. It only appears in Trixie KDE Plasma 6 with Wayland rendering. It does not appear when using x11 or when using either rendering in gnome. Nor does it appear at all in Bookworm. I have tried all kinds of things to "fix" these to no avail, including installing more wayland and mesa packages, then upgrading them to stable backports and then even to unstable testing (forky) versions. I've also tried the Debian unstable edge kernel from testing (6.16.3) as well as the Armbian stable edge kernel (6.16.4) with the same results. I installed Debian Trixie using the Debian .iso installer (w/ EFI boot), then upgraded to their edge/testing kernel (6.16.3) from their testing/forky repository. The bug showed up in pure Debian without a drop of Armbian. Then I installed the Armbian stable edge kernel (6.16.4) to replace the Debian edge/testing kernel in that installation. The bug remained. The rendering bug also showed up in the release version of Armbian Trixie 25.8.1 using the Armbian edge kernel. KDE 6 Wayland Render Bug Symptom: The [ALT-TAB] Task-Switcher's Text Labels (see screenshot #1) The major place this bug shows up is in the task switcher (using ALT-TAB). The window labels, instead of rendering as textual fonts, they render as blocks. I tried several things with the fonts, from changing their type and size, turning on/off anti-aliasing, to changing the desktop themes, and so on. I also tried using different "task switchers" from the list. All I got were the same blocks -they just appeared in different sizes and positions with no other changes. So I'm reasonably sure the rendering issue has nothing to do with fonts, desktop themes, Plasma settings, etc. KDE 6 Wayland Render Bug Symptom: glmark2 (x11) verses glmark2-wayland (see screenshots #2 and #3) Using the command-line utility: glmark2, there's an x11 version and a Wayland version. The each render to an 800x600 window. Normally the only visual difference between them is that the Wayland version has no window borders around it. But with this bug, the Wayland version renders significantly smaller on the screen, and also at a significant performance reduction (>50%). Conclusion I already know it isn't an Armbian issue. I don't believe it's a kernel issue either. I'm reasonably sure it has nothing to do with fonts, themes, or Plasma settings. In my internet searches, I have found no other reports of this specific rendering bug that I think are relevant to whatever is happening now. I did find some vague statements about there still being some "issues" with rendering in the upgrade from KDE 5 (using QT5 libraries) to KDE 6 (using QT6 libraries). I also read that KDE Plasma 6 has a somewhat unique interface or relationship with Wayland and uses its own protocols with it. I think this explains why the bug doesn't show up in gnome, and also helps to isolate, to a degree, where the bug actually is. From what I've read, apparently this issue shows up differently on different systems? It is my impression that these specific symptoms of this bug may be unique to this hardware (Rockchip rk3588 SoC) or GPU (MALI-G610 (built-in)), even though it is a clearly a software bug. Operating System: Debian GNU/Linux 13 KDE Plasma Version: 6.3.6 KDE Frameworks Version: 6.13.0 Qt Version: 6.8.2 Kernel Version: 6.16.4-edge-rockchip64 (64-bit) Graphics Platform: Wayland EDIT: P.S. I just ran Fedora's KDE Plasma 6 image. There were about a thousand updates to run on it. Plasma 6.3.4 (think) upgraded to version 6.4. And their mainline kernel (6.14 upgraded to 6.16.7 I think). The rendering bug I mentioned here did not show up either before or after those updates. So it appears the issue isn't with KDE Plasma itself either, that it's apparently on Debian's end. I noticed some of the (Debian) packages are specifically to bridge 5 and 6. I would guess that's where the problem is - apparently they didn't make a clean break. Screenshot #1: [ALT-TAB] task-switcher Screenshot #2: glmark2 Screenshot #3: glmark2-wayland

Hello, dear armbian community. I am using Orange Pi 5 plus, and I want to use kernel-6.16-5-edge-rockchip64 by armbian, as works much better than actual mainline (I have broken HDMI sound, buggy OpenGL, no power profiles) I, however, want to build kernel for different distro (OpenSUSE Tumbleweed, aka binpkg-rpm). Where do I get kernel sources to do this? (And is it the right place to ask this question?)

I made a configuration via armbian-config, but the camera does not work, here are the messages /sys/bus/i2c/drivers/ov13855 3-0036 bind uevent unbind sudo i2cdetect -y 3 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- UU -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- 58 -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- dmesg | grep ov13855 [ 14.074752] platform csi2-dphy0: Fixed dependency cycle(s) with /i2c@feab0000/ov13855-1@36 [ 14.338234] ov13855 3-0036: driver version: 00.01.04 [ 14.338301] ov13855 3-0036: Failed to get power-gpios, maybe no use [ 14.338330] ov13855 3-0036: Looking up avdd-supply from device tree [ 14.338336] ov13855 3-0036: Looking up avdd-supply property in node /i2c@feab0000/ov13855-1@36 failed [ 14.338365] ov13855 3-0036: supply avdd not found, using dummy regulator [ 14.338418] ov13855 3-0036: Looking up dovdd-supply from device tree [ 14.338424] ov13855 3-0036: Looking up dovdd-supply property in node /i2c@feab0000/ov13855-1@36 failed [ 14.338434] ov13855 3-0036: supply dovdd not found, using dummy regulator [ 14.338454] ov13855 3-0036: Looking up dvdd-supply from device tree [ 14.338459] ov13855 3-0036: Looking up dvdd-supply property in node /i2c@feab0000/ov13855-1@36 failed [ 14.338468] ov13855 3-0036: supply dvdd not found, using dummy regulator [ 14.338484] ov13855 3-0036: could not get default pinstate [ 14.338487] ov13855 3-0036: could not get sleep pinstate [ 14.348869] ov13855 3-0036: Detected OV00d855 sensor, REVISION 0xb0 [ 14.863602] ov13855 3-0036: Consider updating driver ov13855 to match on endpoints [ 14.863609] rockchip-csi2-dphy csi2-dphy0: dphy0 matches m00_b_ov13855 3-0036:bus type 5 with the original distribution the camera works

Hello everyone, I flashed the armbian into my tf cand and inserted it into my OrangePi 5 Plus, with my fans inserted to the specific socket on board (2pin, 1.25mm, 5V, PWM3_IR_M1). However, when I booted it, the fans was running constantly instead of controlled by temperature dynamically, like the official OS images that did only the fans running when the temperature over 50 celsius. I wanna know how to configure my OS to enable the temperature-controlled fans like the official images. The offical documents shows: Linux uses the default pwm-fan drivers to control thye fans and the device tree was defined in orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts Here is the code: fan: pwm-fan { compatible = "pwm-fan"; #cooling-cells = <2>; pwms = <&pwm3 0 50000 0>; cooling-levels = <0 50 100 150 200 255>; rockchip,temp-trips = < 50000 1 55000 2 60000 3 65000 4 70000 5 >; status = "okay"; }; Here are some descriptions regarding some columns: pwms = <&pwm3 0 50000 0>：The fans use pwm3. cooling-levels = <0 50 100 150 200 > 255>：Used to configure the speed levels (duty cycle of PWM). The number and magnitude of the levels can be customized. 6 levels are configured, with the speed range from 0 to 255. rockchip,temp-trips：Used to configure the correspondence between CPU temperature and fan speed levels. This can be adjusted according to actual needs. In the above configuration, 50°C corresponds to level 1, and 70°C corresponds to level 5. Thank you very much.

Hi. I am not complaining. I just would like to understand why I must deactivate https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu/ if I want watching video on Youtube. If it's needed to disable this repo for watching video. I am ok. But why I can't read video with package from this repo? https://paste.armbian.com/vaxedisuda

Is there an overlay or any other way of getting the Orange Pi 5 Plus to work with a 1024x600 display?

Hello, Im trying to compile armbian without internet connection in local. For first time, I connected to internet and compiled a minimal image for Orange pi 5 plus successfully. cache folder is 14 GB now. When I cut off internet connection and start ./compile.sh, compile process stucks. See log below. [🌱] artifact [ firmware :: firmware() ] [🌱] Using cached [ GIT_INFO_ARMBIAN_FIRMWARE ] [🌱] Reversioning package [ re-version 'armbian-firmware(deb)::1-SAfc30-B6c7f-R448a' to '25.5.1' ] [🌱] artifact [ armbian-base-files :: armbian-base-files() ] curl: (7) Couldn't connect to server [🚸] Could not find package filename for 'base-files' in distro repo [ looking for base-files, found_package_filename is ] [🚸] Command failed, retrying in 15s [ apt_find_upstream_package_version_and_download_url base-files ] My configuration below. BOARD=orangepi5-plus BRANCH=vendor RELEASE=bookworm KERNEL_CONFIGURE=no INSTALL_HEADERS=no SHARE_LOGS=no BUILD_DESKTOP=no BUILD_MINIMAL=yes REMOVE_APT_PACKAGES="" IGNORE_UPDATES=yes OFFLINE_WORK=yes USE_MAINLINE_GOOGLE_MIRROR="yes" OFFLINE_DEPLOY=yes APT_PROXY_DISABLED=yes APT_OFFLINE_MODE=yes CLEAN_LEVEL=none USE_TORRENT=no KERNEL_USE_GIT_SHALLOW=yes KERNEL_GIT=shallow I tried every possible (I dont know if they are working) argument within my config. Tried docker and non-docker build. I think its not downloading files after first build but still needs internet. Any help appreciated.

Hi Guys, Here is my requirements for an electron app running Armbian OS on orangepi5 plus to support: Need GPU hardware acceleration to play video Need HDMI audio And possible NPU support. I really need help, I did lots of custom builds to find solution support all my above requirement and I found Armbian-unofficial_25.08.0-trunk_Orangepi5-plus_noble_edge_6.16.0-rc7_cinnamon_desktop.img. But my electron add crashes after running say 8 hrs or so, means it is not very stable for us [83833:0723/100030.362659:ERROR:ssl_client_socket_impl.cc(877)] handshake failed; returned -1, SSL error code 1, net_error -202 [83790:0723/101648.420086:ERROR:zygote_communication_linux.cc(296)] Failed to send GetTerminationStatus message to zygote [83790:0723/101648.423629:ERROR:network_service_instance_impl.cc(612)] Network service crashed, restarting service. [83790:0723/101648.434571:ERROR:zygote_communication_linux.cc(296)] Failed to send GetTerminationStatus message to zygote [83790:0723/101648.439553:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.440252:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.440865:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.441459:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.442003:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.442527:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.443115:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.443586:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.444045:ERROR:gpu_process_host.cc(947)] GPU process launch failed: error_code=1002 [83790:0723/101648.444060:FATAL:gpu_data_manager_impl_private.cc(420)] GPU process isn't usable. Goodbye. I did try other custom build as below, but either they are lacking HDMI audio or GPU hardware acceleration. Please help with this. Thanks Manish

Is there an Armbian image with home assistant that isn't minimalistic? or Is there a way to install HA on a more robust desktop armbian 25.2 image for the Orange Pi 5 Plus? I feel the orange pi 5 is robust enough to handle HA under a desktop Armbian environment than other SBCs.

i also have issues to move the system to the nvme ssd 😞 my base is the Armbian 25.5.1 with 6.1.115 (vendor kernel) image .... "copied" (usbimager) it to the sdcard and its booting ... 🙂 so I upgraded the system on the sdcard, still running 🙂 I read some posts and advices .... so I partioned the nvme with one big partition (/dev/nvme0n1p1) running armbian-install choosing option 7, (loading/upgrading bootloader to mtd ) after this i choose option 4 (boot from mtd, system on sata, usb ... ) only possible selection was /dev/nvme0n1 ... looked ok said yes to everything no Error system goes to shutdown /power off removed power, removed sdcard plugin power again .... and ... no boot 😞 serial console saying: DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18 ch0 ttot10 ch1 ttot10 ch2 ttot10 ch3 ttot10 ch0 ttot18 LPDDR4X, 2112MHz channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch1 ttot18 channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch2 ttot18 channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch3 ttot18 channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB Manufacturer ID:0xff DQS rds:h1,h1 CH0 RX Vref:27.1%, TX Vref:21.8%,22.8% DQ rds:h1 l0 h2 l0 h1 h5 l0 l0, l0 h3 l0 h3 h7 h2 l0 h1 DQS rds:l0,h1 CH1 RX Vref:28.5%, TX Vref:23.8%,23.8% DQ rds:h1 h2 h1 h3 h1 h3 l0 h1, h1 h4 h1 h4 h1 h3 l0 h4 DQS rds:l0,h1 CH2 RX Vref:27.5%, TX Vref:23.8%,22.8% DQ rds:h1 h3 h2 h1 h1 h6 h4 h1, h1 h2 h6 l0 h6 h2 h6 h3 DQS rds:h1,l0 CH3 RX Vref:29.7%, TX Vref:21.8%,20.8% DQ rds:h5 h3 h2 h1 h3 h2 h2 h2, h5 h2 h1 h2 h4 l0 l0 h5 stride=0x2, ddr_config=0x4 hash ch_mask0-1 0x20 0x40, bank_mask0-3 0xa00 0x1400 0x2800 0x0, rank_mask0 0x401000 change to F1: 528MHz ch0 ttot10 ch1 ttot10 ch2 ttot10 ch3 ttot10 change to F2: 1068MHz ch0 ttot14 ch1 ttot14 ch2 ttot14 ch3 ttot14 change to F3: 1560MHz ch0 ttot16 ch1 ttot16 ch2 ttot16 ch3 ttot16 change to F0: 2112MHz ch0 ttot18 ch1 ttot18 ch2 ttot18 ch3 ttot18 out U-Boot SPL board init U-Boot SPL 2017.09-armbian-2017.09-S3e40-P187d-He5fc-Ve691-Bb703-R448a (May 30 2025 - 10:51:06) sfc cmd=03H(6BH-x4) Trying to boot from MMC2 MMC: no card present mmc_init: -123, time 0 spl: mmc init failed with error: -123 Trying to boot from MTD2 Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Checking atf-1 0x00040000 ... sha256(7612223b82...) + OK ## Checking uboot 0x00200000 ... sha256(11a994b967...) + OK ## Checking fdt 0x00354c30 ... sha256(e3b0c44298...) + OK fdt_record_loadable: FDT_ERR_BADMAGIC ## Checking atf-2 0xff100000 ... sha256(70505bb764...) + OK fdt_record_loadable: FDT_ERR_BADMAGIC ## Checking atf-3 0x000f0000 ... sha256(b2af21b504...) + OK fdt_record_loadable: FDT_ERR_BADMAGIC Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000) Total: 496.285/765.931 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-868-g040d2de11:derrick.huang, fwver: v1.48 NOTICE: BL31: Built : 15:02:44, Dec 19 2024 INFO: spec: 0x1 INFO: code: 0x88 INFO: ext 32k is valid INFO: ddr: stride-en 4CH INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0 INFO: l3 cache partition cfg-0 INFO: system boots from cpu-hwid-0 INFO: disable memory repair INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001 INFO: dfs DDR fsp_params[0].freq_mhz= 2112MHz INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz INFO: BL31: Initialising Exception Handling Framework INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 No valid device tree binary found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED. For sandbox, use -d <file.dtb> initcall sequence 00000000002d2af8 failed at call 00000000002c502c (err=-1) ### ERROR ### Please RESET the board ### if im boot with sdcard in the system and mount /dev/nvm0n1p1 there is the whole system .... inklusive /boot und boot/dtb ..... what didd I miss ? Does anyone hav a link to a working tutorial ?