Search the Community

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

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

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

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

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

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

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

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

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

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

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

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

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

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 http://github.com/armbian/build/archive/refs/tags/v25.5.0-trunk.67.tar.gz curl -LO http://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

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

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

Hi all, Testing this OP5, got a standard M2 NVMe SSD (this works on my OP5Plus) I have formatted to exFAT with windows, inserted on the OP5, loaded ArmbianOS on MicroSD, it boots fine but I cant get it to show the nvme drive using fdisk -l or lsblk It seem like its not detecting the m2 nvme ssd at all.. little help please ?

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

Hi all, I am trying to recover after a failed NVMe install. I have a working install on an SDCard, but I think my board no longer boots to SDCard, since I flashed the bootloader via armbian-install. I am not sure if my NVMe install is good or not, and I can't currently reflash it. So I think my best bet is to wipe the SPI, which I hope means the board will go back to booting from SDCard. That's question 1 - is that actually a valid solution? If I wipe the SPI will I be able to again boot to SDCard? I am able to get the board into Maskrom mode, and I can see it using the Windows tool. However, I believe that I need a "loader image" that I "download" into the tool before I can wipe the bootloader. The Rock5 SPI wipe guide posted elsewhere in this forum refers to rk3588_spl_loader_v1.08.111.bin, which I don't have, and I'm not sure that's the right loader for the OPi5. That's question 2 - is there a loader for the OPi5 and/or can the Rock5 loader be used here? The OPi5 Manual is very sparse about Maskrom info, it says how to get into that mode, but only gives instructions for flashing the board to Android. The Android download is not working right now (Google Drive quota) so I am not able to get that package, in case it happens to have a suitable loader image. Thanks for any replies in advance.

System Information: http://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 !