Active threads

Since the hardware support for Rockchip SoCs in the mainline kernelis generally already very outstanding and their further development is also being actively pursued, I only have SBCs with integrated NPUs that are based on them. Among them are ODROID-M1, NanoPC-T6, and ROCK-5-ITX. But since the NPU is an integral part of the SoC, the board manufacturer and the design of the SBC are not necessarily of importance. As far as I understand, edge-class NPUs are best suited for computer vision tasks. I am therefore engaged in object detection: and super-resolution:

I'm having a problem with my Raspberry Pi 5, which I describe below. I have a DVR connected to it via Ethernet. If I connect both at the same time, dmesg reports a failure and I can't ping the DVR to establish a connection; I have to run `ifconfig eth0 down` and `ifconfig eth0 up`. Can anyone help or know if there's a bug in the kernel version? I'm using Ubuntu 22.04. jammy root:~# dmesg | grep eth0 [ 1.312167] macb 1f00100000.ethernet eth0: Cadence GEM rev 0x00070109 at 0x1f00100000 irq 108 (2c:cf:67:81:d6:2a) [ 3.237493] systemd[1]: Found device /sys/subsystem/net/devices/eth0. [ 3.453483] systemd[1]: Started ifup for eth0. [ 3.573655] macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL) [ 3.573668] macb 1f00100000.ethernet eth0: configuring for phy/rgmii-id link mode [ 6.441950] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [ 11.560707] macb 1f00100000.ethernet eth0: Link is Down [ 13.605678] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off root:~# ping 192.168.200.201 PING 192.168.200.201 (192.168.200.201) 56(84) bytes of data. ^C --- 192.168.200.201 ping statistics --- 6 packets transmitted, 0 received, 100% packet loss, time 13305ms root:~# ifconfig eth0 down root:~# ifconfig eth0 up root:~# dmesg | grep eth0 [ 1.312167] macb 1f00100000.ethernet eth0: Cadence GEM rev 0x00070109 at 0x1f00100000 irq 108 (2c:cf:67:81:d6:2a) [ 3.237493] systemd[1]: Found device /sys/subsystem/net/devices/eth0. [ 3.453483] systemd[1]: Started ifup for eth0. [ 3.573655] macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL) [ 3.573668] macb 1f00100000.ethernet eth0: configuring for phy/rgmii-id link mode [ 6.441950] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [ 11.560707] macb 1f00100000.ethernet eth0: Link is Down [ 13.605678] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [ 147.034711] macb 1f00100000.ethernet eth0: Link is Down [ 151.855860] macb 1f00100000.ethernet eth0: PHY [1f00100000.ethernet-ffffffff:01] driver [Broadcom BCM54213PE] (irq=POLL) [ 151.855871] macb 1f00100000.ethernet eth0: configuring for phy/rgmii-id link mode [ 152.869842] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off root:~# ping 192.168.200.201 PING 192.168.200.201 (192.168.200.201) 56(84) bytes of data. 64 bytes from 192.168.200.201: icmp_seq=1 ttl=64 time=1.01 ms 64 bytes from 192.168.200.201: icmp_seq=2 ttl=64 time=1.01 ms ^C --- 192.168.200.201 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 1.007/1.007/1.007/0.000 ms

On RK3568 the Panfrost driver needs the clk-scmi kernel module to be loaded. But is not build in 6.18 / 6.19 otherwise we get [ 13.370681] panfrost fde60000.gpu: get clock failed -517 [ 13.370717] panfrost fde60000.gpu: clk init failed -517 [ 13.485723] panfrost fde60000.gpu: get clock failed -517 [ 13.485761] panfrost fde60000.gpu: clk init failed -517 [ 13.503876] panfrost fde60000.gpu: get clock failed -517 [ 13.503918] panfrost fde60000.gpu: clk init failed -517 Thanks !

It not works for me. I followed the official document to flash the SPI: https://docs.radxa.com/en/cubie/a5e/getting-started/install-system/nvme-system/burn-spi However after I wrote the latest Armbian img into NVMe disk, it failed to boot: [132]HELLO! BOOT0 is starting! [135]BOOT0 commit : 33d8db429a-dirty [140]periph0 has been enabled [143]set pll end [145]PL gpio voltage : 3.3V [149]PMU: AXP2202 [154]PMU: AXP1530 [159]power mode:33, sys_vol:920 [164]vaild para:1 select dram para0 [167]dram_para[0]:0x4b0 [170]dram_para[1]:0x8 [172]dram_para[2]:0x7070707 [175]dram_para[3]:0xd0d0d0d [178]dram_para[4]:0xe0e [181]dram_para[5]:0x84848484 [184]dram_para[6]:0x310a [186]dram_para[7]:0x10001000 [189]dram_para[8]:0x0 [192]dram_para[9]:0x34 [194]dram_para[10]:0x1b [197]dram_para[11]:0x33 [199]dram_para[12]:0x3 [202]dram_para[13]:0x0 [204]dram_para[14]:0x0 [207]dram_para[15]:0x4 [209]dram_para[16]:0x72 [212]dram_para[17]:0x0 [214]dram_para[18]:0xe [216]dram_para[19]:0x0 [219]dram_para[20]:0x0 [221]dram_para[21]:0x26 [224]dram_para[22]:0x80808080 [227]dram_para[23]:0x6060606 [230]dram_para[24]:0x1f0b0503 [233]dram_para[25]:0x0 [236]dram_para[26]:0x3a000000 [239]dram_para[27]:0x802f3333 [242]dram_para[28]:0xc0c0bbbf [245]dram_para[29]:0x35352f31 [248]dram_para[30]:0xc64 [251]dram_para[31]:0x48484848 [254]board init ok [277]enable_jtag [279]boot param - This media is not supported [283]boot param - Media not supportedsunxi_bootparam_cpu_read...91 [290]boot param - magic error [293]DRAM BOOT DRIVE INFO: V0.67 [297]DRAM_VCC set to 1100 mv [424]DRAM retraining ten [550]DRAM retraining ten [567][AUTO DEBUG]32bit,1 ranks training success! [597]Soft Training Version: T2.0 [7728][SOFT TRAINING] CLK=1200M Stable memtest pass [7733]DRAM CLK =1200 MHZ [7736]DRAM Type =8 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [7747]phy_dfs_clk1 = 800M [8082]phy_dfs_clk2 = 400M [8176]phy_dfs_clk3 = 150M [8299]phy_dfs_clk0 = 1200M [8302]DRAM MDFS VERSION INFO: V0.660 [8306]DRAM MDFS time =39480 ns [8309]DRAM SIZE =2048 MBytes, para1 = 310a, para2 = 8000000, tpr13 = 6465 [8340]DRAM simple test OK. [8343]dram size =2048 [8350]nsi init 2023-2-23 [8353]spinor id is: ef 60 18, read cmd: 03 [8358]Succeed in reading toc file head. [8361]The size of toc is 1a0000. [8910]Entry_name = u-boot [8920]Entry_name = monitor [8924]Entry_name = scp [8928]Entry_name = dtb [8931]Jump to second Boot. NOTICE: BL31: OP-TEE 32bit detected NOTICE: BL31: U-BOOT 32bit detected NOTICE: BL31: v2.5(debug):a6e1826c1 NOTICE: BL31: Built : 10:10:43, Mar 28 2025 NOTICE: BL31: No DTB found. nsi init ok 2022-11-08 ERROR: Error initializing runtime service opteed_fast U-Boot 2018.07-9-boot-aw2501-g56bb8c6a2ea-dirty (Sep 16 2025 - 08:32:16 +0000) Allwinner Technology [09.082]CPU: Allwinner Family [09.085]Model: Radxa Cubie A5E I2C: ready [09.097]DRAM: 2 GiB [09.101]Relocation Offset is: 75e60000 [09.163]secure enable bit: 0 [09.166]PMU: AXP2202 [09.195][AXP2202] comm status : 0x0 = 0x20, 0x1 = 0x90 [09.200][AXP2202] onoff status: 0x20 = 0x4, 0x21 = 0x0 [09.205][AXP2202] reboot/charge status: 0xf0 = 0x0 [09.209]PMU: AXP1530 [09.212]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=600Mhz [09.219]gic: sec monitor mode SPI ALL: ready [09.224]flash init start [09.226]workmode = 0,storage type = 3 [09.231]spi sunxi_slave->max_hz:50000000 SF: write offset not multiple of erase size [09.771]spi sample_mode:0 sample_delay:1f [09.776]spi sunxi_slave->max_hz:50000000 SF: Detected w25q128fw( ) with page size 256 Bytes, erase size 64 KiB, total 16 MiB [09.788]sunxi flash init ok [09.797]Loading Environment from SUNXI_FLASH... OK [09.803]No ethernet found. [09.805]Failed to found available display route [09.810]Get sunxi drm device fail! [09.813]get secure storage map err [09.816]sunxi secure storage is not supported [09.820]usb burn from boot delay time 0 weak:otg_phy_config [09.830]usb prepare ok [10.133]overtime [10.138]do_burn_from_boot usb : no usb exist SF: write offset not multiple of erase size [10.189]get secure storage map err [10.192]secure storage init fail cann't get the boot_base from the env [10.201]update part info [10.212]update bootcmd pcie link up success PCIe speed of Gen2 [10.524]change working_fdt 0xbbe0fe18 to 0xbbddfe18 [10.532]## error: update_fdt_dram_para_from_bootpara : FDT_ERR_NOTFOUND [10.538]Invalid phandle:0 [10.540]only find 1073741818 phandle, format:endpoints=<&disp0_out_tcon0 &tcon0_out_rgb0>; [10.549]Failed to found available display route [10.553]chip id : 0x0000ff10 0x00004824 0x0000c31c 0x000023da [10.559]chip id : 0x0000ff10 0x00004824 0x0000c31c 0x000023da [10.564]Could not find nodeoffset for used ext pmu:reg-axp1530 [10.570]update dts curr_device:-1 No MMC device available Hit any key to stop autoboot: 0 starting USB... USB0: start sunxi USB-DRD... config usb clk ok sunxi USB-DRD init ok... USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found USB1: start sunxi USB1-Host... config usb clk ok sunxi USB1-Host init ok... USB EHCI 1.00 scanning bus 1 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: device type unknown ... is now current device ** Bad device usb 0 ** ** Bad device usb 0 ** No MMC device available Scanning PCI devices on bus 1 BusDevFun VendorId DeviceId Device Class Sub-Class _____________________________________________________________ 01.00.00 0x1217 0x8760 Mass storage controller 0x08 Device 0: Vendor: 0x1217 Rev: 10100080 Prod: NB3925D000028 Type: Hard Disk Capacity: 58999.9 MB = 57.6 GB (120831998 x 512) ... is now current device Scanning nvme 0:1... Found U-Boot script /boot.scr 4641 bytes read in 2 ms (2.2 MiB/s) ## Executing script at 4fc00000 subfdt=sun55i-a527-cubie-a5e.dtb U-boot loaded from SD Boot script loaded from nvme 239 bytes read in 1 ms (233.4 KiB/s) sun55i-a527-cubie-a5e.dtb: No match Load fdt: /dtb/allwinner/sun55i-a527-cubie-a5e.dtb 37110 bytes read in 4 ms (8.8 MiB/s) 16547680 bytes read in 141 ms (111.9 MiB/s) 39950848 bytes read in 264 ms (144.3 MiB/s) ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16547616 Bytes = 15.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK No Linux ARM Ramdisk Image Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... No MMC device available No MMC device available No ethernet found. missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-sunxi No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default No ethernet found. Config file not found => The firmware filename I downloaded is: Armbian_community_26.2.0-trunk.493_Radxa-cubie-a5e_trixie_edge_6.18.13_minimal.img.xz

nfs shares are now rudimentary implemented

use the images in this thread

I started down this path and realized that the patches are applied to downloaded linux kernel source. Normally, the kernel source is "cleaned" even if the build fails. I then found the sakura pi github page and the page has more recent commit than the Rock-s0, incorporates the kernel.dtsi while adhering the the u-boot requirements for rockpi's. U-boot for Rockpi. I'd like to base my build on the more up-to-date code. The easist way to do this is set CLEAN_LEVEL="" but I'm running into issues with the patches in GitHub: Sakura-Pi failing to apply. Essentially, I would iike to have the patches apply, not necessarily build and have the files generated by the patches remain. I have a large dtb file, extracted from Sovol's OEM firmware, that I would like to copy/paste into the generated *.dtb file, rename the *csc file and the defconfig file, and then generate a patch against clean source. Conceptually, this should work and I'm suprised it is this difficult to generate a new board for an existing family. Alternatively, a script could generate a file from a highlited portion of a patch and generate a file. Or is is possbile to run ./compile.sh a step at a time? It would be helpful in this setting, very instructive about the process and would narrow down build failures. Am I on the right path? Any step-by-step examples and or links to helpful scripts?

As champions of open source development in the embedded community, Collabora will be at Booth 4-404 with an impressive lineup of live demonstrations spanning graphics, machine learning, continuous testing, and real-world applications. View the full article

Thank you very much. Unfortunately, Trixie won't start. BootROM - 1.73 Booting from MMC BootROM: Bad header at offset 00000200 … BootROM: Bad header at offset 02E00000 BootROM: Bad h Trying Uart

I need you to understand something very important: the manufacturer is infecting the boards with Java botnet software. All the software you should use is developed by the Armbian community. Welcome to the Armbian community! Now that you are a member, you must develop software that schedules the board's power-on.

Maybe see https://wiki.postmarketos.org/wiki/Medion_Chromebook_S2015_(google-veyron-mighty) It is RK3288, so an Armbian Rockchip kernel might do something, but I have no clue about DeviceTree and/or bootloader. Alpine is quite different from Armbian/Debian but maybe with that bootloader+kernel+DTB and Armbian rootfs it might do something, but make sure you have seril debug cable. In general might need to find solder points on motherboard/PCB or some specific resistor value on OTG ID pin.

Try to build from this PR: https://github.com/armbian/build/pull/9381 - use CURRENT branch - enable additional DEBUT if it doesn't proceed - leave u-boot as is or try with most recent

The issue was that these variables in the kernel config were set to 10. Setting them to 12 allowed uart10 to initilaize. CONFIG_SERIAL_8250_NR_UARTS=12 CONFIG_SERIAL_8250_RUNTIME_UARTS=12

Hello everyone Just would like to start a discussion about the current state of video acceleration (decoding only, h.265/h.264/av1). The soc (rk3588) recently got mainline support for these features in 7.0: https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md Has anyone tested this on a OPI5 already, especially using Kodi? Does this work ootb there now? Regards, XXXBold

Hi! I have an OrangePi3 (not Zero!) running Armbian (H6), with a TFT ILI9486 display connected via the 26-pin header. The screen works fine, but the XPT2046 touch controller does not initialize. Here’s the situation: CS0 on PH5, DC on PD16, RESET on PD21. XPT2046 (CS1) on PL8, IRQ on PD24. I tried adding XPT2046 to the overlay with all parameters configured (ti,x/y-min/max, pressure, swap-xy, etc.). The overlay compiles successfully, but when loading the module it says: ads7846 spi0.1: probe with driver ads7846 failed with error -22 I also tried loading the ads7846 module with parameters via modprobe — all parameters are ignored because the driver only supports configuration via Device Tree. Here is my current overlay: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h6"; fragment@0 { target = <&spi1>; __overlay__ { status = "okay"; cs-gpios = <&pio 7 3 0>; display: display@0 { compatible = "ilitek,ili9341"; reg = <0>; pinctrl-names = "default"; spi-max-frequency = <20000000>; txbuflen = <65536>; rotate = <90>; bgr = <0>; fps = <30>; buswidth = <8>; regwidth = <16>; height = <480>; width = <320>; dc-gpios = <&pio 3 16 0>; reset-gpios = <&pio 3 21 1>; debug = <3>; init = <0x10000b0 0x00 // Interface Mode Control 0x1000011 // Sleep Out 0x20000ff // Delay (255ms) 0x10000C0 0x0D 0x0D // Power Control 1 0x10000C1 0x43 // Power Control 2 0x10000C5 0x00 0x48 0x80 // VCOM Control 1 0x10000C7 0x00 // VCOM Control 2 0x1000036 0x28 // Memory Access Control (Rotação) 0x100003A 0x55 // Pixel Format Set (16bit) 0x10000B1 0xB0 0x11 // Frame Rate Control 0x10000F0 0x01 // Enable Extended Comand Set 0x10000F6 0x00 0x01 0x32 // SPI ilInterface Control 0x1000026 0x01 // Gamma Set 0x10000E0 0x0F 0x31 0x2B 0x0C 0x0E 0x08 0x4E 0xF1 0x37 0x07 0x10 0x03 0x0E 0x09 0x00 // Positive Gamma Correction 0x10000E1 0x00 0x0E 0x14 0x03 0x11 0x07 0x31 0xC1 0x48 0x08 0x0F 0x0C 0x31 0x36 0x0F // Negative Gamma Correction 0x10000B6 0x02 0x02 0x3B // Display Function Control 0x1000011 // Sleep Out 0x20000ff // Delay (255ms) 0x1000029>; // Display ON }; /* --- ADS7846 (XPT2046) --- */ ads7846: ads7846@1 { compatible = "ti,ads7846"; reg = <1>; pinctrl-names = "default"; spi-max-frequency = <1000000>; interrupt-parent = <&pio>; interrupts = <3 24 2>; pendown-gpio = <&pio 3 24 1>; cs-gpios = <&pio 11 8 0>; /* OPTIONS */ ti,x-min = /bits/ 16 <0>; ti,y-min = /bits/ 16 <0>; ti,x-max = /bits/ 16 <0xFFF>; ti,y-max = /bits/ 16 <0xFFF>; ti,pressure-min = /bits/ 16 <0>; ti,pressure-max = /bits/ 16 <0xFFF>; ti,x-plate-ohms = /bits/ 16 <400>; ti,swap-xy = <1>; }; }; }; }; Could anyone advise how to properly connect XPT2046 so that PD24 is used as IRQ? Is there a working example overlay for TFT ILI9486 + XPT2046 on OrangePi3 / H6? Or has anyone managed to use the touch controller via a module without overlay? Or is that simply impossible on this kernel? I would really appreciate any working examples or advice!

hi. Please tell me, I installed the image and bootloader on the emmc (armbian) on the radxa 5t and now I can't install another one because the board doesn't want to start from the CD card. what should I do? Im try this but doesnt work https://docs.radxa.com/en/rock5/rock5t/low-level-dev/maskrom/erase

thnx. it seems latest working vendor kernel for 3566 is 6.1.115. i already tried rk35xx, with bigtreetech_cb2.dtb but it stops at u-boot (in uart console) using orangepi-3b it boots, but gives errors in dmesg. when i try to add fdtfile bigtreetech_cb2.dtb, it stops boot .... 47274496 bytes read in 3902 ms (11.6 MiB/s) Failed to load '/boot/dtb/rockchip/rk3566-bigtreetech-cb2.dtb' libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Trying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not apply to all boards. Unknown command 'kaslrseed' - try 'help' ..... but when i boot btt_cb2 as orangepi3b board, it boots and even shows mpp venc/dec/npu/whatever modules properly loaded. not checked yet if it works really maybe need to make some hybrid dtb from btt_cb2 and orange3b ========= btw, could You share what You do for 35xx board change? when i tried to change family rockchip64 to 35xx, it comiled, but not copied bigtreeetech_cb2.dtb to boot , and not boots ewven if i copy it by myself there

At this point, the most realistic path is to use hardware that is already officially supported. Bringing up new hardware or maintaining outdated vendor kernels requires significant engineering time and resources. Board enablement is not a small task. It involves ongoing maintenance, testing, integration work, and long-term support. This represents real cost for the project while public project funding is not even on the level to cover response of such ideas. If you are expecting someone will just emerge and spent months of his private time in exchange for: constant insults, hate and complete absence of financial coverage for the time spent (things are never in perfect state to satisfy over-spoiled customers of someone else) ... adjust expectations. We encourage users to choose hardware wisely - that already has active support and to contribute back to the project when possible. That is the only way we can avoid overextending limited resources, burnouts, collapse.

This Gdrive is empty now... Did we see any improvements for the Orange Pi 4A in the 26.2.1 release?

That's strange 🙂 ...we have the same kernel. Maybe something's broken in the system? But I haven't messed with Bluetooth in the system. I've only updated the system: apt update /apt upgrade /reboot 🙂 root@orangepi3-lts:~# rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth bluetooth unblocked unblocked 1 wlan phy0 unblocked unblocked .............................. bluetoothctl Waiting to connect to bluetoothd... it keeps reading but shows nothing? ................... bt-device -l ** ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self)) Bail out! ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self)) Aborted ............. Something must have broken in the system, but what and where? Can you give me the exact: Armbian image + version ... Contents of ..../lib/firmware/uwe5622/ also: armbianEnv.txt Output dmesg | grep -i uart i dmesg | grep -i bluetooth Maybe that will help me figure out where the errors are in my system? Or maybe I have Debian and you have Ubuntu? Ps. or, more simply, information from the file: diagnostics.txt command in terminal: ................. ( uname -a cat /etc/os-release ls -lh /lib/firmware/uwe5622/ lsmod | grep -iE "bt|sprd|uwe" dmesg | grep -i uart ls /dev/tty* | grep -i "ttyS\|ttyAMA\|ttyBT" cat /boot/armbianEnv.txt rfkill list hciconfig -a bluetoothctl list hcitool dev bt-device -l dmesg | grep -iE "bluetooth|uwe|sprd|hci" ) > diagnostics.txt .....................

DKMS compilation per board, examples: https://github.com/armbian/build/blob/main/config/boards/radxa-cubie-a5e.csc#L20-L22 https://github.com/armbian/build/blob/main/config/boards/orangepirv2.wip#L13-L17 https://github.com/armbian/build/blob/main/extensions/radxa-aic8800.sh https://github.com/armbian/build/blob/main/extensions/bcmdhd-spacemit.sh

@Issou thanks for the feedback, I eventually got my hands on the Orange Pi zro I had in a remote location, I will make a fresh install and see how it behaves.

Testing the latest build: apt update && apt upgrade -y Hit:1 http://deb.debian.org/debian trixie InRelease Get:2 http://deb.debian.org/debian trixie-updates InRelease [47.3 kB] Get:3 http://security.debian.org trixie-security InRelease [43.4 kB] Get:4 https://github.armbian.com/configng stable InRelease [5,467 B] Get:5 http://deb.debian.org/debian trixie-backports InRelease [54.0 kB] Err:2 http://deb.debian.org/debian trixie-updates InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T13:39:41Z Verifying signature: Not live until 2026-03-02T13:39:55Z Err:3 http://security.debian.org trixie-security InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T02:15:55Z Verifying signature: Not live until 2026-03-02T02:15:55Z Err:4 https://github.armbian.com/configng stable InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Verifying signature: Not live until 2026-03-02T16:02:28Z Err:5 http://deb.debian.org/debian trixie-backports InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T13:39:27Z Verifying signature: Not live until 2026-03-02T13:39:49Z Get:6 http://fi.mirror.armbian.de/beta trixie InRelease [39.4 kB] Err:6 http://fi.mirror.armbian.de/beta trixie InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Verifying signature: Not live until 2026-03-02T08:25:38Z Fetched 190 kB in 1s (143 kB/s) All packages are up to date. Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: http://deb.debian.org/debian trixie-updates InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T13:39:41Z Verifying signature: Not live until 2026-03-02T13:39:55Z Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: http://security.debian.org trixie-security InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T02:15:55Z Verifying signature: Not live until 2026-03-02T02:15:55Z Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://github.armbian.com/configng stable InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Verifying signature: Not live until 2026-03-02T16:02:28Z Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: http://deb.debian.org/debian trixie-backports InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T13:39:27Z Verifying signature: Not live until 2026-03-02T13:39:49Z Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: http://fi.mirror.armbian.de/beta trixie InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Verifying signature: Not live until 2026-03-02T08:25:38Z Warning: Failed to fetch https://github.armbian.com/configng/dists/stable/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Verifying signature: Not live until 2026-03-02T16:02:28Z Warning: Failed to fetch http://beta.armbian.com/dists/trixie/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key DF00FAF1C577104B50BF1D0093D6889F9F0E78D5, which is needed to verify signature. Verifying signature: Not live until 2026-03-02T08:25:38Z Warning: Failed to fetch http://deb.debian.org/debian/dists/trixie-updates/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T13:39:41Z Verifying signature: Not live until 2026-03-02T13:39:55Z Warning: Failed to fetch http://deb.debian.org/debian/dists/trixie-backports/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T13:39:27Z Verifying signature: Not live until 2026-03-02T13:39:49Z Warning: Failed to fetch http://security.debian.org/dists/trixie-security/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2026-03-02T02:15:55Z Verifying signature: Not live until 2026-03-02T02:15:55Z Warning: Some index files failed to download. They have been ignored, or old ones used instead. Summary: Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0 root@radxa-cubie-a5e:~# armbianmonitor -u Collecting info and sending to paste.armbian.com, wait... https://paste.armbian.com/zefutefuzi Please post the URL in the forum where you've been asked for. https://paste.armbian.com/zefutefuzi

There aren't any Armbian builds for 5.15 is what I said. And it would be a lot of work to make that happen. Why do you want 5.15? How do you know that would work, when 6.12 doesn't?

You can just download rock-3a edge(6.18+) images (not vendor 6.1) and change the device tree entry (sdcard/boot/armbianenv.txt) to point to "rockchip/rk3566-radxa-cm3-io.dtb" . This seems to boot fine with majority of features working.