Search the Community

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 connected an OV13850 camera to camera port 3. After enabling it in device tree config, I still can't see it in v4l2-ctl and other camera apps. dmesg | grep ov13850 shows nothing.

Hi, I attempted to build armbian for orange pi 5 with these steps (I'm on macos): multipass delete armbian-build multipass purge multipass launch -n armbian-build --disk 50G --mem 8G --cpus 4 multipass shell armbian-build sudo apt install curl build-essential bc bison flex libssl-dev chrpath cmake cpio wget xz-utils curl -LO https://github.com/armbian/build/archive/refs/tags/v25.5.0-trunk.67.tar.gz curl -LO https://github.com/armbian/build/archive/refs/tags/v25.5.0-trunk.32.tar.gz tar -xzvf v25.5.0-trunk.67.tar.gz cd build-25.5.0-trunk.67 ./compile.sh (select edge version for orange pi 5 in the cli) CTRL+D multipass transfer armbian-build:/home/ubuntu/build-25.5.0-trunk.67/output/images/Armbian-unofficial_25.02.0-trunk_Orangepi5_noble_edge_6.13.3_cinnamon_desktop.img . And for a reason I can't grasp, when I boot the orange pi 5 with the freshly flashed armbian.img on the SD card, the usb ports arent powering at all, so i can't use a keyboard, bluetooth or wifi dongles. But I can see armbian being displayed on the screen and asking for a new password On the nvme ssd, I have Ubuntu running and no issue with the usb ports. I wanted to try the native support for vulkan and 3588s in 6.13. Any idea? PS: I tried both v25.5.0-trunk.67 and v25.5.0-trunk.32, but the same issue arises

The latest version of RKNPU Driver is 0.9.8, 0.9.7 version doesn't works with rknn-llm or other projects.

Is anyone using the current Kodi Flatpak, Omega? I'm having issues viewing videos that have pixel format of yuv420p10le with the current apt repository Kodi Nexus. I thought to try Kodi Flatpak and it worked and I was able to view those yuv420p10le videos without issue. However, it was choppy and had high CPU usage...around 80% on many of the CPUs. I'm trying to figure that out. It's happening on all types of videos. All is played using software decoding. I've never gotten hardware decoding working. In the Kodi Nexus version I'm using it also software decoding but very low CPU usage. In any case, just want to see what experiences others are having.

Hi, after upgrading to Armbian 24.11.3 noble with 6.1 Kernel I have this problem that every time I turn off my TV that is connected to OPI with HDMI, then turning it back on again it will never have a HDMI signal. Same thing happens when I unplug the HDMI cable and plug it back in. I can reproduce it every single time - not just occasionally. It is not a hardware or cable problem, the exact same setup has worked flawlessly for long time with older Armbian and 5.1 kernel. I tried disabling all of the KDE power saving settings, also totally disabled kpowerdevil - with no change. SSH still works fine, the OS has not crashed. No new messages come to "dmesg" after tuning the TV off and on. Only thing that appear is in /var/log/syslog is when I turn the tv back ON again. Turning it off does not add any messages. 2025-02-06T13:21:23.984567+02:00 loovsys DiscoverNotifier[1979]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:21:23.984940+02:00 loovsys kded6[1877]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:21:23.985204+02:00 loovsys polkit-kde-authentication-agent-1[1929]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:21:23.985425+02:00 loovsys plasmashell[1897]: kde.plasmashell: requesting unexisting screen available rect -1 2025-02-06T13:21:23.985562+02:00 loovsys plasmashell[1897]: message repeated 3 times: [ kde.plasmashell: requesting unexisting screen available rect -1] 2025-02-06T13:21:23.986668+02:00 loovsys kalendarac[1985]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:21:23.986910+02:00 loovsys kactivitymanagerd[1904]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:21:23.987124+02:00 loovsys xdg-desktop-portal-kde[1930]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:21:23.991124+02:00 loovsys plasmashell[1897]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:21:23.991328+02:00 loovsys plasmashell[1897]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken. Or another time pretty similar 2025-02-06T13:26:53.652232+02:00 loovsys kactivitymanagerd[1880]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:26:53.653516+02:00 loovsys kalendarac[1964]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:26:53.654495+02:00 loovsys kded6[1852]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:26:53.655328+02:00 loovsys DiscoverNotifier[1957]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:26:53.656229+02:00 loovsys xdg-desktop-portal-kde[1905]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:26:53.657111+02:00 loovsys plasmashell[1868]: kde.plasmashell: requesting unexisting screen available rect -1 2025-02-06T13:26:53.657645+02:00 loovsys plasmashell[1868]: message repeated 3 times: [ kde.plasmashell: requesting unexisting screen available rect -1] 2025-02-06T13:26:53.658397+02:00 loovsys polkit-kde-authentication-agent-1[1904]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:26:53.665372+02:00 loovsys plasmashell[1868]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:26:53.665685+02:00 loovsys plasmashell[1868]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken. 2025-02-06T13:26:53.807759+02:00 loovsys plasmashell[1868]: message repeated 3 times: [ kf.plasma.quick: Exposed with no visual parent. Window positioning broken.] When plugging the HDMI cable back in: 2025-02-06T13:30:00.668173+02:00 loovsys kalendarac[1948]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:30:00.669049+02:00 loovsys DiscoverNotifier[1946]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:30:00.669745+02:00 loovsys kactivitymanagerd[1869]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:30:00.670412+02:00 loovsys kded6[1839]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:30:00.671016+02:00 loovsys xdg-desktop-portal-kde[1889]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:30:00.671596+02:00 loovsys polkit-kde-authentication-agent-1[1888]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:30:00.672173+02:00 loovsys plasmashell[1858]: kde.plasmashell: requesting unexisting screen available rect -1 2025-02-06T13:30:00.672548+02:00 loovsys plasmashell[1858]: message repeated 3 times: [ kde.plasmashell: requesting unexisting screen available rect -1] 2025-02-06T13:30:00.672946+02:00 loovsys plasmashell[1858]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 2025-02-06T13:30:00.688381+02:00 loovsys plasmashell[1858]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken. 2025-02-06T13:30:00.705197+02:00 loovsys plasmashell[1858]: message repeated 2 times: [ kf.plasma.quick: Exposed with no visual parent. Window positioning broken.] 2025-02-06T13:30:01.892282+02:00 loovsys CRON[6339]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) 2025-02-06T13:30:01.895234+02:00 loovsys CRON[6338]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi) 2025-02-06T13:30:02.361046+02:00 loovsys chronyd[1553]: Selected source 212.7.1.131 (0.ubuntu.pool.ntp.org) 2025-02-06T13:30:05.222767+02:00 loovsys plasmashell[1858]: The cached device pixel ratio value was stale on window update. Please file a QTBUG which explains how to reproduce. I also tried to switch between graphical and multi-user targets. (This works fine when the TV is never turned off - i can get the console and switch back to grapgical UI) systemctl isolate multi-user.target systemctl isolate graphical.target Issuing a reboot command will bring the display back. I do not have to power cycle the entire device to get the display back. I can also get back the display after I have lost signal by switching to the multi-user.target, unplugging and plugging back in the cable. After that i can also switch back to graphical.target and everything works. Only switching between graphical and multi-user afer losing the signal will not bring back the display. If I first switch to multi-user.target and then turn off the tv, then turning it back on the display works. I can also enable the graphical target again without problems. Then the following messages appear in syslog 2025-02-06T13:37:21.290588+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_disable] Crtc atomic disable vp0 2025-02-06T13:37:24.167556+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 3840x2160p60, type: 11(if:HDMI0, flag:0x0) for vp0 dclk: 594000000 2025-02-06T13:37:24.167664+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx_ropll_cmn_config bus_width:5aa320 rate:5940000 2025-02-06T13:37:24.167680+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy pll locked! 2025-02-06T13:37:24.167693+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] dclk_out0 div: 0 dclk_core0 div: 2 2025-02-06T13:37:24.167706+02:00 loovsys kernel: rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] set dclk_vop0 to 594000000, get 594000000 2025-02-06T13:37:24.167719+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: final tmdsclk = 594000000 2025-02-06T13:37:24.280906+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: don't use dsc mode 2025-02-06T13:37:24.280986+02:00 loovsys kernel: dwhdmi-rockchip fde80000.hdmi: dw hdmi qp use tmds mode 2025-02-06T13:37:24.281000+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: bus_width:0x5aa320,bit_rate:5940000 2025-02-06T13:37:24.281011+02:00 loovsys kernel: rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy lane locked! Also in the dmesg the following appears [ 293.342367] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_disable] Crtc atomic disable vp0 [ 296.325415] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] Update mode to 3840x2160p60, type: 11(if:HDMI0, flag:0x0) for vp0 dclk: 594000000 [ 296.326327] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx_ropll_cmn_config bus_width:5aa320 rate:5940000 [ 296.326706] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy pll locked! [ 296.327137] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] dclk_out0 div: 0 dclk_core0 div: 2 [ 296.327226] rockchip-vop2 fdd90000.vop: [drm:vop2_crtc_atomic_enable] set dclk_vop0 to 594000000, get 594000000 [ 296.327422] dwhdmi-rockchip fde80000.hdmi: final tmdsclk = 594000000 [ 296.438292] dwhdmi-rockchip fde80000.hdmi: don't use dsc mode [ 296.438342] dwhdmi-rockchip fde80000.hdmi: dw hdmi qp use tmds mode [ 296.438380] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: bus_width:0x5aa320,bit_rate:5940000 [ 296.438665] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy lane locked! As soon as I use the graphical target, then dmesg shows nothing and syslog only the messages I showed before. root@loovsys:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Armbian 24.11.3 noble Release: 24.04 Codename: noble root@loovsys:~# uname -a Linux loovsys.eu 6.1.84-vendor-rk35xx #1 SMP Thu Jan 9 02:09:01 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux Anyone experiencing similar issues or has any idea what could be the reason for it? Otherwise t

System Information: https://paste.armbian.com/mozehisomu When i am trying to setup many vlan interfacces i have whis dmesg message: rk_gmac-dwmac fe1c0000.ethernet eth0: MAC_VLAN_Tag_Filter full (size: 4) interface info: ethtool -i eth0 driver: st_gmac version: Jan_2016 firmware-version: expansion-rom-version: bus-info: supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no I need about 20-30 vlan interfaces

Hi everybody, I installed Deb 12 Cinnamon Armbian flavor. This: dl.armbian.com/orangepi5-plus/Bookworm_current_cinnamon-backported-mesa When I open system setup there is no Idiom/Language Icon. So all apps remains in English. Even if I run "sudo dpkg-reconfigure keyboard-configuration" and "sudo dpkg-reconfigure locales" I found an issue running "armbian-config"/localization/change Keyboard layout, on console this msg "setupcon: We are not on the console, the console is left unconfigured." But if I run "sudo dpkg-reconfigure keyboard-configuration" from a terminal window no error. Thanks, Cury

Hello ! I've bought a Orange Pi 5 PRO board about 2 months ago . I've tryed all images (Linux and Android) from the official Orange Pi site . Later I tryed Armbian . In the end I've concluded that the best choice is Armbian 24.5.2 Noble Gnome ( Armbian_24.5.2_Orangepi5pro_noble_vendor_6.1.43_gnome-oibaf_desktop.img ). Using Armbian 24.5.2 Noble Gnome I got the best (the smoothest) video playback, both in video players and online (youtube) content . And it' s very responsive in operation, generally . I have one single issue : My MCE remote is not detected properly - the Play, Pause, Next, Previous, Forward, Rewind buttons did't perform any actions when I used Kodi video player . When I press any of these buttons I get a 🚫 (no entry) sign on the bottom of the screen . Only the following buttons are performing correctly : Power, Ok, Left, Right, Up, Down, back, and numeric keys . If I'm using other video players, like Celluloid, Vlc,Haruna, Smplayer, all the remote control's buttons performs as it should . The remote control's model number is HP TSGH-2401 with RF USB dongle . I tryed the remote and Kodi on different Linux images, even on Armbian_24.5.2_Orangepi5pro_noble_vendor_6.1.43_xfce-oibaf_desktop.img - it perform as it should, but all these Linux images have video playback issues (or maybe i'm too picky) . The problem with the remote control is present only on Armbian 24.5.2 Noble Gnome (which I preffered for it's video performance) . I tryed to fix the problem using inputlirc package, but with limited success . I also tried "Keymap editor " add-on for Kodi, but with almost none positive results . I attached 2 screenshoots with the the screen when I get a 🚫 (no entry) sign on the bottom of the screen . Please help me with some suggestions . Thank you in advance !

I don't know why, I think after doing "sudo apt update/upgrade" (but I'm not sure), the wiringOP library on "orange pi 5" with Armbian 23.02.2 doesn't work anymore. If I run the command "sudo gpio readall" I get the following output: Oops: Unable to determine board revision from /proc/device-tree/system/linux,revision or from /proc/cpuinfo -> No "Hardware" line -> You'd best google the error to find out why. Can anyone help me solve this problem?

Was using my Orange Pi 5 and it rebooted on it's own. After that, it continually reboots. Been running fine for months. Tried restarting a few times. Tried swapping SD cards. It looks like the power supply is OK, although I'll try swapping with another. I had just backed up the SD Card too. I'll try re-imaging an SD card, but I'm thinking the SD card may not be the issue. I hooked up my UART and captured output. At the end of each loop, it looks like it's saying "Starting Kernel" and then restarting. Captured output follows. Any ideas, suggestions or comments on what's happening. I'm thinking it's probably a hardware issue. I purchased on Amazon. Can't find out how long the warranty/if it's still under warranty. DDR V1.11 f1474cf52f cym 23/05/09-11:02:36 LPDDR4X, 2112MHz CH2 RX Vref:27.5%, TX Vref:19.8%,20.8% CH3 RX Vref:30.1%, TX change to F1: 528MHz change to F2: 1068MHz change to F3: 156out U-Boot SPL board init U-Boot SPL 2017.09 (Jun 30 2023 - 19unknown raw ID 0 0 0 unrecognized JEDEC id bytes: 00, 00, 00 TTrying fit image at 0x4000 sector ## Verified-boot: 0 ## Check## Checking uboot 0x00200000 ... sha256(bab9643a63...) + OK ## atf-3 0x000f0000 ... sha256(da90adf3a4...) + OK Jumping to U-B.622 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():vrt detected. INFO: ARM GICv3 driver initialized in EL3 INFOams[0].freq_mhz= 2112MHz INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz INFINFO: BL31: Initialising Exception Handling Framework INFO: initializing runtime service opteed_fast INFO: BL31: Prepar 0x200000 INFO: SPSR = 0x3c9 U-Boot 2017.09 (Jun 30 202CR: M/C/I Using default environment mmc@fe2c0000: 0, mmc@fe2Bootdev(atags): mmc 0 MMC0: Legacy, 52Mhz PartType: EFI DM: vCLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kerpll 1188000 KHz npll 24000 KHz ppll 1100000 KHz aclk_ceer_root 396000 KHz aclk_center_low_root 500000 KHz aclk_toot 396000 KHz Net: No ethernet found. Hit key to stop autobo-Boot script /boot.scr reading /boot.scr 3476 bytes read in 1 ded from mmc 0 reading /armbianEnv.txt 212 bytes read in 2 ms 15248365 bytes read in 1223 ms (11.9 MiB/s) reading /Image 34638336 bytes read in 2777 ms (11.9 MiB/s) reading /dtb/rockch234611 bytes read in 30 ms (7.5 MiB/s) ** Unable to read file /OK ## Flattened Device Tree blob at 0x0a100000 Booting usin000000000a1a1fff Adding bank: 0x00200000 - 0xf0000000 (size: 0xize: 0x03a00000) Adding bank: 0x4f0000000 - 0x500000000 (size: Total: 4379.611 ms Starting kernel ... DDR V1.11 f1474cf52f cym 23/05/09-11:02:36 LPDDR4X, 2112MHz cher ID:0x6 CH0 RX Vref:28.5%, TX Vref:20.8%,20.8% CH1 RX Vref:2 CH2 RX Vref:27.5%, TX Vref:20.8%,19.8% CH3 RX Vref:29.3%, TX change to F1: 528MHz change to F2: 1068MHz change to F3: 156out U-Boot SPL board init U-Boot SPL 2017.09 (Jun 30 2023 - 19Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Check## Checking uboot 0x00200000 ... sha256(bab9643a63...) + OK ## .902 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():vINFO: ddr: stride-en 4CH INFO: GICv3 without legacy suppo: system boots from cpu-hwid-0 INFO: idle_st=0x21fff, pd_ams[0].freq_mhz= 2112MHz INFO: dfs DDR fsp_params[1].freq_mhINFO: BL31: Initialising Exception Handling Framework INFO: U-Boot 2017.09 (Jun 30 2023 - 19:08:39 +0200) Model: OranCR: M/C/I Using default environment mmc@fe2c0000: 0, mmc@fe2Bootdev(atags): mmc 0 MMC0: Legacy, 52Mhz PartType: EFI DM: vCLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kerot 396000 KHz Net: No ethernet found. Hit key to stop autoboms (3.3 MiB/s) ## Executing script at 00500000 Boot script loa15248365 bytes read in 1223 ms (11.9 MiB/s) reading /Image 34638336 bytes read in 2776 ms (11.9 MiB/s) reading /dtb/rockch234611 bytes read in 29 ms (7.7 MiB/s) ** Unable to read file /p compressed) Data Size: 15248301 Bytes = 14.5 MiB LoOK ## Flattened Device Tree blob at 0x0a100000 Booting usinefe00000) Adding bank: 0x100000000 - 0x3fc000000 (size: 0x2fc00ize: 0x03a00000) Adding bank: 0x4f0000000 - 0x500000000 (size: Total: 4378.924 ms Starting kernel ...

Before writing I searched the forum a bit but couldn't find any recent posts about it. I have an OPI5 board and on NVME I would like to install armbian. I downloaded the image to micro sd and it boots fine. At this point I don't know what to do because I had to waste a lot of time on it some time ago and I don't remember the steps. With the armbian-config utility is it possible to clone the armbian release I am using on the micro sd? I remember that this wasn't possible some time ago. I would like to know specifically the steps to take and whether it is advisable to delete any old partitions on nvme. Thank you

Hey folks, im trying to compile a realtime kernel for mt orange pi 5. I plan to use it for djing. A fully preemptive kernel delivers better performance for this, as less xruns appear. I am following the official dev instructions and am using the docker method, Compiling only the kernel, not the entire armbian OS. I copied a realtime patch (actually I tried several sub versions of 5.10) from the kernel.org realtime project site into the userpatches directory (I looked up the correct orange pi 5 subfolder name but forgot it rn) but compiling throws me some errors. Has anyone succeeded in creating a kernel like this for the orange pi 5 and/or could give me any advice for doing so? I actually dont care much about the kernel version, I just need it to be fully preemptive .. Help is much apprecieated! Kenny

I have an Armbian installation on the NVMe drive and I'm trying to switch back to boot from SD card. In `armbian-config` I messed up the boot settings by leaving the root fs type unchanged, (SD card is in fat32 but NVMe partition is ext4). Now the board boots into initramfs prompt. Here's what I've already tried based on search and ChatGPT: Mount the NVMe partition to `/mnt` then chroot to it, this did work but the `/boot` partition was not mounted inside of the chroot so I can't fix boot env. I also tried `switch_root` but it's not available in the initramfs prompt. Update `/proc/cmdline` to change the root fs back to the Armbian partition, but `echo ... > /proc/cmdline` doesn't really do anything. Any ideas?

Hello everyone, I recently purchased an ili9488 touch screen for use with my Orange Pi 5, but I'm having trouble getting it to work. I've tried several solutions that I found online, but so far nothing has worked. Specifically, the screen isn't displaying any output when I connect it to my Orange Pi 5, and I'm not sure what steps to take next. https://a.aliexpress.com/_EQaN4gj - That is the screen I bought. For context,I have the latest version of the Armbian operating system installed. I've followed the instructions that came with the touch screen, and I've also tried several different solutions that I found online (including using the fbset command to adjust the display resolution, and updating the device tree overlay file). If anyone has any suggestions or advice for how I can troubleshoot this issue, I would be extremely grateful. I'm open to any possible solutions, and I'm willing to try anything to get this screen up and running. Thank you in advance for your help!

Please advise on how to fix this, thanks: Setting up rockchip-multimedia-config (1.0.2+jammy) ... dpkg-query: error: --listfiles needs at least one package name argument Use --help for help about querying packages. dpkg: error processing package rockchip-multimedia-config (--configure): installed rockchip-multimedia-config package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: rockchip-multimedia-config E: Sub-process /usr/bin/dpkg returned an error code (1)

flashed to m2 mvme, board attempts to boot , then after armbian logo it falls into busybox command prompt (

Couldn't booti from NVME with armbian-config or armbian-install, finally I could do it, a dirty easy and convoluted following way. No details about burning stuff This is what I did 1) boot system from fresh downloaded SD (Armbian Jammy Desktop) 2) NVME setup (sudo gparted) - if empty create a partition table (GPT) if not delete all partitions - create 256MB FAT16 partition (nvme0n1p1) - create EXT4 partition (nvme0n1p2) - optionally create more partitions (system recovery, backups ...) - format partitions nvme0n1p1 -> FAT16 - format partitions nvme0n1p2 -> EXT4 - check partitions (if old NVME) - label nvme0n1p1 as armbi_boot - label nvme0n1p2 as armbi_root 3) run sudo armbian-install - option 7 to flash mtdblock0 (bootloader install) - option 4 (to install system and boot from mtdblock0) choose nvme0n1p2 partition to install system don't POWEROFF, just EXIT 4) copy SD boot partition to nvme0n1p1 - sudo dd if=/dev/mmcblk1p1 of=/dev/nvme0n1p1 bs=1M status=progress - sudo sync 5) armbianExt.txt setup on NMVE - sudo mount /dev/nvme0n1p1 /mnt - check boot files/directories are already copied (ls -l /mnt) - blkid - copy (CTL_INS -> new UUID) of nvme0n1p2 UUID (without "") with your favourite editor: - sudo vi armbianExt.txt - replace rootdev=UUID=with new UUID (SHIFT-INS) - save (ESC :x) 6) - sudo poweroff - remove SD - press power button to restart Maybe this cam help someone

Hi there, I pourchased OPi5 (not preferred OPi5 Pro, because of Armbian lacking support), flashed Debian 24.8.1_bookworm_6.10.6_cinnamon_backported_mesa_desktop, configured (user, switch to static IP, user). Worked OK. Now, ssh'ing into showed "113 packages upgrade". Did "apt upgrade". Download OK, but when applying apgrade process hung twice: - once on "configuring libc", had to power off, then restarted (after an apt-get suggested in response to apt upgrade). Upgrade hung second time (no progress on bottom bar for hours, no new ssh session). - twice was on "configuring udev". After this, board is almost dead: - boots to animated Armbian logo, - then "flash" (the few lines on bootup) "failed" (too shot to see what failed). - then NO normal (text) bootup messages, - then blank screen with text cursor in left-upper corner, switching with totally blank screen (but monitor does NOT go to sleep) - graphic mode? I can remove uSD card (good, Samsung U1, 32GB), but what should I look for? Power seems not be problem, it is on it's own 5V/5A SMPS, heatsinks and fan. Laurent

I just upgraded to Arabian 24.5.1 using `apt-get upgrade` and now I cannot load ip_tables: # modprobe ip_tables modprobe: ERROR: could not insert 'ip_tables': Exec format error I’m not sure what to make of it.

Hello OPI5 users. Running Joshua Riek's Ubuntu distro, I keep getting stability issues. Perhaps because I keep using Xorg. Perhaps because hardware acceleration is buggy. In the past I used super stable Armbian OPI5 distro's without hardware acceleration. Infact I still use Armbian on another RK3588 box, I don't think it has EVER crashed, running docker, Mosquito, HomeAssistant, and a buch of other things. Now that my Orange Pi 5 gets a slightly more serious use as webserver, I really like to get rid of the unpredictable Xorg crashes, and gladly would sacrifice HW acceleration for stability. My situation is this: Using JR Ubuntu Because I want to use headless RealVNC (runs only under Xorg) for several devices I switched off Wayland Using a slightly hacked RealVNC server originating from Raspberry Pi Want to use OPI5 as a NodeJS + Nginx webserver serving Node apps now Any suggestions for a super stable uncrashable distro for the Opi5, for server use but with gui? I kind of hate to set everything up again, especially with the internal M.2 sata quirks, but I gotta have stability now. Hopefully I can ask a second question: is there an easy way to totally turn off HW acceleration in JR Ubuntu? Maybe I should try that first... Kind regards, Bas

Hi there, my new OPi5 with Armbian Bookworm Cinnamon mesa backoprted does not see my mPCIe SSD disk. Just got this: https://allegro.pl/oferta/nowy-superszybki-dysk-ssd-512gb-m-2-nvme-2242-9605598735 \ module, but it is not recognized by the system. Armbianmonitor output: https://paste.armbian.com/huhedogene lspci -v output: 0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 89 Bus: primary=40, secondary=41, subordinate=41, sec-latency=0 I/O behind bridge: [disabled] [16-bit] Memory behind bridge: [disabled] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Expansion ROM at f4200000 [virtual] [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=16/32 Maskable- 64bit+ Capabilities: [70] Express Root Port (Slot-), MSI 08 Capabilities: [b0] MSI-X: Enable- Count=128 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [148] Secondary PCI Express Capabilities: [180] L1 PM Substates Capabilities: [190] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?> Kernel driver in use: pcieport No new /dev/sd* , nor /dev/mmcblk* files. What am I missing? Is module faulty? (but it is new) Should I switch to another kernel? (Current is Linux orangepi5 6.10.6-current-rockchip-rk3588 #1 SMP PREEMPT Mon Aug 19 04:05:40 UTC 2024 aarch64 GN U/Linux ). Laurent

Hi guys, Would someone point me to where to get a particular distro, mainly looking for jammy_legacy_gnome-amazingfated_desktop for OPi 5 Pro ? I have jammy_legacy_5.10.160_gnome-amazingfated_desktop for Pi5 and Pi5 Plus but it does not work on the Pro version. thank you in advance.

How can I recover from this? I haven't rebooted: _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v24.8.4 for Orange Pi 5 running Armbian Linux 6.10.6-current-rockchip-rk3588 Packages: Debian stable (bookworm) IP addresses: (LAN) 192.168.1.2 10.8.0.1 (WAN) xxx.xxx.xxx.xxx Performance: Load: 1% Up time: 21 days 23:00 Memory usage: 10% of 15.35G CPU temp: 41°C Usage of /: 21% of 233G Tips: Support our work and become a sponsor https://github.com/sponsors/armbian Commands: System config : sudo armbian-config System monitor : htop Last login: Tue Oct 15 13:16:59 2024 from 192.168.1.28 rob@orangepi5:~$ sudo apt update [sudo] password for rob: Hit:1 http://deb.debian.org/debian bookworm InRelease Get:2 http://security.debian.org bookworm-security InRelease [48.0 kB] Get:3 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB] Get:5 http://deb.debian.org/debian bookworm-backports InRelease [59.0 kB] Get:6 https://packages.adoptium.net/artifactory/deb bookworm InRelease [7,517 B] Get:4 http://mirrors.jevincanders.net/armbian/apt bookworm InRelease [53.3 kB] Get:7 http://security.debian.org bookworm-security/main arm64 Packages [186 kB] Get:8 http://security.debian.org bookworm-security/main armhf Packages [186 kB] Get:9 http://deb.debian.org/debian bookworm-backports/main arm64 Packages.diff/Index [63.3 kB] Get:10 http://deb.debian.org/debian bookworm-backports/main armhf Packages.diff/Index [63.3 kB] Get:11 http://deb.debian.org/debian bookworm-backports/main arm64 Contents (deb).diff/Index [63.6 kB] Get:12 http://deb.debian.org/debian bookworm-backports/main all Contents (deb).diff/Index [63.6 kB] Get:13 http://deb.debian.org/debian bookworm-backports/main armhf Contents (deb).diff/Index [63.6 kB] Get:14 http://deb.debian.org/debian bookworm-backports/main arm64 Packages T-2024-10-21-1409.06-F-2024-10-15-2009.57.pdiff [11.0 kB] Get:14 http://deb.debian.org/debian bookworm-backports/main arm64 Packages T-2024-10-21-1409.06-F-2024-10-15-2009.57.pdiff [11.0 kB] Get:15 http://mirrors.jevincanders.net/armbian/apt bookworm/main all Packages [13.5 kB] Get:16 http://mirrors.jevincanders.net/armbian/apt bookworm/main armhf Packages [345 kB] Get:17 http://mirrors.jevincanders.net/armbian/apt bookworm/main arm64 Packages [935 kB] Get:18 http://deb.debian.org/debian bookworm-backports/main armhf Packages T-2024-10-21-1409.06-F-2024-10-15-2009.57.pdiff [10.9 kB] Get:18 http://deb.debian.org/debian bookworm-backports/main armhf Packages T-2024-10-21-1409.06-F-2024-10-15-2009.57.pdiff [10.9 kB] Get:19 http://mirrors.jevincanders.net/armbian/apt bookworm/main arm64 Contents (deb) [14.9 MB] Get:20 http://deb.debian.org/debian bookworm-backports/main arm64 Contents (deb) T-2024-10-19-0204.47-F-2024-10-15-2009.57.pdiff [265 B] Get:20 http://deb.debian.org/debian bookworm-backports/main arm64 Contents (deb) T-2024-10-19-0204.47-F-2024-10-15-2009.57.pdiff [265 B] Get:21 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-utils arm64 Packages [22.6 kB] Get:22 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-utils armhf Packages [52.5 kB] Get:23 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-utils arm64 Contents (deb) [28.4 kB] Get:24 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-utils armhf Contents (deb) [24.7 kB] Get:25 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-desktop armhf Packages [10.2 kB] Get:26 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-desktop all Packages [5,802 B] Get:27 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-desktop arm64 Packages [9,992 B] Get:28 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-desktop armhf Contents (deb) [29.4 kB] Get:29 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-desktop all Contents (deb) [1,309 B] Get:30 http://mirrors.jevincanders.net/armbian/apt bookworm/bookworm-desktop arm64 Contents (deb) [29.4 kB] Get:31 http://deb.debian.org/debian bookworm-backports/main all Contents (deb) T-2024-10-21-1409.06-F-2024-10-15-2009.57.pdiff [5,774 B] Get:31 http://deb.debian.org/debian bookworm-backports/main all Contents (deb) T-2024-10-21-1409.06-F-2024-10-15-2009.57.pdiff [5,774 B] Get:32 http://deb.debian.org/debian bookworm-backports/main armhf Contents (deb) T-2024-10-19-0204.47-F-2024-10-15-2009.57.pdiff [263 B] Get:32 http://deb.debian.org/debian bookworm-backports/main armhf Contents (deb) T-2024-10-19-0204.47-F-2024-10-15-2009.57.pdiff [263 B] Fetched 17.3 MB in 7s (2,576 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done 6 packages can be upgraded. Run 'apt list --upgradable' to see them. rob@orangepi5:~$ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: armbian-config armbian-firmware armbian-plymouth-theme armbian-zsh linux-dtb-vendor-rk35xx linux-image-vendor-rk35xx 6 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 138 MB of archives. After this operation, 15.9 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://armbian.tnahosting.net/apt bookworm/main arm64 armbian-config all 24.8.4 [136 kB] Get:6 http://armbian.chi.auroradev.org/apt bookworm/main arm64 linux-image-vendor-rk35xx arm64 24.8.4 [32.6 MB] Get:2 http://mirrors.jevincanders.net/armbian/apt bookworm/main arm64 armbian-firmware all 24.8.4 [91.6 MB] Get:3 http://mirrors.jevincanders.net/armbian/apt bookworm/main arm64 armbian-plymouth-theme all 24.8.4 [108 kB] Get:4 http://mirrors.jevincanders.net/armbian/apt bookworm/main arm64 armbian-zsh all 24.8.4 [11.8 MB] Get:5 http://mirrors.jevincanders.net/armbian/apt bookworm/main arm64 linux-dtb-vendor-rk35xx arm64 24.8.4 [2,135 kB] Fetched 138 MB in 3s (44.6 MB/s) (Reading database ... 109457 files and directories currently installed.) Preparing to unpack .../0-armbian-config_24.8.4_all.deb ... Unpacking armbian-config (24.8.4) over (24.8.3) ... Preparing to unpack .../1-armbian-firmware_24.8.4_all.deb ... Unpacking armbian-firmware (24.8.4) over (24.8.3) ... Preparing to unpack .../2-armbian-plymouth-theme_24.8.4_all.deb ... Unpacking armbian-plymouth-theme (24.8.4) over (24.8.3) ... Preparing to unpack .../3-armbian-zsh_24.8.4_all.deb ... Unpacking armbian-zsh (24.8.4) over (24.8.3) ... Preparing to unpack .../4-linux-dtb-vendor-rk35xx_24.8.4_arm64.deb ... Armbian 'linux-dtb-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'preinst' starting. Armbian 'linux-dtb-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'preinst' finishing. Unpacking linux-dtb-vendor-rk35xx (24.8.4) over (24.8.2) ... Preparing to unpack .../5-linux-image-vendor-rk35xx_24.8.4_arm64.deb ... Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'prerm' starting. Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'prerm' finishing. Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'preinst' starting. Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'preinst' finishing. Unpacking linux-image-vendor-rk35xx (24.8.4) over (24.8.2) ... Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'postrm' starting. Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'postrm' finishing. Setting up linux-dtb-vendor-rk35xx (24.8.4) ... Armbian 'linux-dtb-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'postinst' starting. Armbian: DTB: FAT32: moving /boot/dtb-6.1.75-vendor-rk35xx to /boot/dtb ... renamed 'dtb-6.1.75-vendor-rk35xx' -> 'dtb' Armbian 'linux-dtb-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'postinst' finishing. Setting up linux-image-vendor-rk35xx (24.8.4) ... Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'postinst' starting. dkms: autoinstall for kernel 6.1.75-vendor-rk35xx was skipped since the kernel headers for this kernel do not seem to be installed. update-initramfs: Generating /boot/initrd.img-6.1.75-vendor-rk35xx update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.75-vendor-rk35xx Image Name: uInitrd Created: Tue Oct 22 06:34:02 2024 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16110316 Bytes = 15732.73 KiB = 15.36 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.75-vendor-rk35xx to /boot/uInitrd ln: failed to create symbolic link '/boot/uInitrd': Operation not permitted update-initramfs: Symlink failed, moving /boot/uInitrd-6.1.75-vendor-rk35xx to /boot/uInitrd renamed '/boot/uInitrd-6.1.75-vendor-rk35xx' -> '/boot/uInitrd' update-initramfs: Armbian: done. Free space after deleting the package linux-image-vendor-rk35xx in /boot: 78.5M Armbian: FAT32 /boot: move last-installed kernel to 'Image'... renamed '/boot/vmlinuz-6.1.75-vendor-rk35xx' -> '/boot/Image' Armbian 'linux-image-vendor-rk35xx' for '6.1.75-vendor-rk35xx': 'postinst' finishing. Setting up armbian-zsh (24.8.4) ... Setting up armbian-config (24.8.4) ... Setting up armbian-firmware (24.8.4) ... Setting up armbian-plymouth-theme (24.8.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.142+deb12u1) ... ln: failed to create hard link '/boot/initrd.img-6.10.6-current-rockchip-rk3588.dpkg-bak' => '/boot/initrd.img-6.10.6-current-rockchip-rk3588': Operation not permitted update-initramfs: Generating /boot/initrd.img-6.10.6-current-rockchip-rk3588 grep: /boot/config-6.10.6-current-rockchip-rk3588: No such file or directory E: gzip compression (CONFIG_RD_GZIP) not supported by kernel update-initramfs: failed for /boot/initrd.img-6.10.6-current-rockchip-rk3588 with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) rob@orangepi5:~$ ls -l /boot total 104816 -rwxr-xr-x 1 root root 213 Sep 30 07:31 armbianEnv.txt -rwxr-xr-x 1 root root 38518 Feb 18 2023 boot.bmp -rwxr-xr-x 1 root root 3404 Feb 18 2023 boot.cmd -rwxr-xr-x 1 root root 3476 Feb 18 2023 boot.scr -rwxr-xr-x 1 root root 244731 Oct 18 04:11 config-6.1.75-vendor-rk35xx drwxr-xr-x 3 root root 4096 Oct 22 06:33 dtb -rwxr-xr-x 1 root root 39152128 Oct 18 04:11 Image -rwxr-xr-x 1 root root 28272711 Sep 30 07:29 initrd.img-6.10.6-current-rockchip-rk3588 -rwxr-xr-x 1 root root 16110316 Oct 22 06:34 initrd.img-6.1.75-vendor-rk35xx -rwxr-xr-x 1 root root 7371703 Oct 18 04:11 System.map-6.1.75-vendor-rk35xx -rwxr-xr-x 1 root root 16110380 Oct 22 06:34 uInitrd rob@orangepi5:~$

I run a audio loop code on a Raspberry pi 4/5 and Orange Pi 5. The latency of audio loop is 0.2 seconds on Raspberry pi but on orange pi it takes 1.2 seconds. For orange pi, i am facing this problem with different Operating systems as well apart from armbian. I've used Ubuntu, Orange Pi OS, Armbian. All have got this problem. The code I have attached. Since the issue is faced in multiple Operating System I strongly feel this has to do with the driver level softwares or directly related optimization from Rockchip. Can anyone guide what I could do audio-loop.cpp