All Activity

@L. Jorge Soares Thanks a lot for testing both — genuinely, this is the most useful thing anyone can do for the project. 🙏 CLI: great to hear it boots and HDMI works on your setup — that's the first confirmation from hardware other than mine, so it means a lot. If you get time, I'd love to hear how it holds up (networking, USB, and the 4 GB variant if that's what you have). Root password: that's by design, not a bug. Root login is locked on purpose — the image ships with a default user / user account and SSH enabled, so an open root account would be a security hole. Use the user account with sudo: root shell: sudo -i (or sudo su) to set a root password if you really want one: sudo passwd root KDE image + Etcher error: let's pin it down. Full disclosure — I flash with dd myself, so I haven't actually run these images through BalenaEtcher; I'll test the Etcher path on my end to try to reproduce it. In the meantime, two quick checks: Verify the download — a truncated/corrupt download is the #1 cause of Etcher errors. The desktop image sha256 is: 63b0019423d2a320aaa5fe58df97db68823b353a30510ffa863fec475904e0ba Check yours: sha256sum on Linux/Mac, or certutil -hashfile <file> SHA256 on Windows. If it doesn't match, re-download. And thanks for the heads up — I'll also double-check on my end that the file on the release didn't get corrupted during upload. Card size — the desktop image is ~5.3 GB when written (bigger than the CLI one), so it needs an 8 GB or larger card. A smaller/oddly-sized card makes Etcher fail. If the checksum matches and the card is 8 GB+ but it still errors, it's most likely Etcher choking on the .xz — try Raspberry Pi Imager (Use custom → pick the .img.xz), Rufus (it writes in DD Image mode and takes the .xz directly), or on Linux just dd: xz -dc aurealnix-opi4a-debian13-v0.2.img.xz | sudo dd of=/dev/sdX bs=4M status=progress And if you can, paste the exact Etcher error text — that tells me straight away whether it's a size, decompression, or validation issue. Thanks again for digging in! 🙌

Mint packages its own Chromium as a deb package, whereas Ubuntu's Chromium is a snap (even `apt install` just installs a snap by default). So, all x64 packages work (and I confirmed by testing xtradeb PPA's x64 package, which works). However, it's also not ARM64 related, as the Chromium ARM64 Snap from Ubuntu 24.04 (I just tested that too) works perfectly fine. It's just the ARM64 deb package from xtradeb that seems broken, which is bizarre.

I had quick look at both new version 0.2 version. The CLI version boots up no issue, hdmi output works. Well test further. The KDE version, I get an error using BalenaEtcher writing the image to the SD. Also can you provide the root password? ( just notice Root is locked )

Meanwhile I did replace systemd-resolved on Trixie with resolvconf. Unfortunately, although the configuration now is (to my knowledge) mostly identical to the working Bookworm AP, it still does not work. When I connect a Debian system to both APs, the output of "ip r" is identical. Also the output of "dig <some server>". But "ping" works only partially for the Trixie AP: I get only a ping answer for the AP address. Same for traceroute. What I did observe using tcpdump: ssh communication with the Bookworm system gives "ack/seq pairs": 23:56:26.276869 IP 172.24.1.77.54840 > 192.168.178.29.22: Flags [.], ack 18029, win 537, options [nop,nop,TS val 1656092742 ecr 742514735], length 0 23:56:26.278437 IP 192.168.178.29.22 > 172.24.1.77.54840: Flags [P.], seq 18029:18105, ack 8352, win 344, options [nop,nop,TS val 742514737 ecr 1656092742], length 76 Whereas the same with the Trixie system gives (apparently much longer) sequences of only "seq" entries: 23:56:26.962828 IP 172.24.1.77.54840 > 192.168.178.29.22: Flags [P.], seq 9612:9648, ack 19365, win 537, options [nop,nop,TS val 1656093428 ecr 742515405], length 36 23:56:26.964613 IP 192.168.178.29.22 > 172.24.1.77.54840: Flags [P.], seq 19365:19401, ack 9648, win 344, options [nop,nop,TS val 742515423 ecr 1656093428], length 36 23:56:26.982677 IP 172.24.1.77.54840 > 192.168.178.29.22: Flags [P.], seq 9648:9684, ack 19401, win 537, options [nop,nop,TS val 1656093447 ecr 742515423], length 36 23:56:26.984461 IP 192.168.178.29.22 > 172.24.1.77.54840: Flags [P.], seq 19401:19437, ack 9684, win 344, options [nop,nop,TS val 742515443 ecr 1656093447], length 36 23:56:27.001390 IP 172.24.1.77.54840 > 192.168.178.29.22: Flags [P.], seq 9684:9720, ack 19437, win 537, options [nop,nop,TS val 1656093466 ecr 742515443], length 36 I guess I get some SD cards now and install different clean images to start from ...

@Nick_Sl @bickns — no more waiting, the headless build is up. 🙂 It's a CLI / headless image for the Orange Pi 4A: pure Debian 13 (a debootstrap minbase — bare on purpose, add the rest with apt), the full mainline 6.18.38 kernel, SSH on from first boot. 146 MB compressed, idles at ~180 MB of RAM. Same kernel as the desktop image (HDMI, WiFi/BT, gigabit ethernet, USB, thermal + CPU/GPU frequency scaling) — just no desktop. It's the ...-cli-v0.2.img.xz asset here (the desktop image is on the same page): https://github.com/ut-slayer/orangepi-4a-mainline/releases/tag/v0.2 Whoever gives it a spin: I'd really appreciate the feedback — especially if something doesn't work quite right. A lot of this only shakes out once other people run it on their own boards, so bug reports are genuinely welcome (here or on the GitHub issues). @bickns — "no special requests, apt adds the rest later" was exactly the design goal, so we're on the same page: it's a minimal base and nothing more. If you're still doing your own build for the Armbian-stable PR, the tip stands — for a headless target you can drop the whole display/GPU series (drm/sun4i + iommu + clk), which is where most of your ~20 rejects were coming from; you only need the dts + the ethernet/wifi/usb/thermal/cpufreq bits. One thing that's right up your alley given your outdoor-audio project: the A523 analog codec now has a working driver (ported from the BSP). Headphone output and jack-detect are validated on hardware; mic capture is wired in the driver but I couldn't bench-test it (no onboard mic here). You'd be the ideal person to confirm whether capture works — if it does, that's the last gap on this codec closed. @Nick_Sl — you said you could wait; turns out you don't have to. 🙂 If you're still up for testing, I'd genuinely love your results — flash it, SSH in, and tell me what breaks (especially on the 4 GB variant if that's what you have). Glad the board's out of the eBay pile.

i can wait

Use framework and DIY. That's what it is made for

that looks like a very ambitious undertaking

@xaja34 hi images appear here: https://github.com/armbian/community/releases orangepi 4 pro seems have debian image now (sadly dont have resolute image): Armbian_community_26.8.0-trunk.359_Orangepi4pro_trixie_vendor_6.6.98_minimal.img.xz @jshkol anyone knows if have gpu acceleration? thanks

@Nick_Sl @bickns — CLI/headless image is coming. It's the same debootstrap base and the same kernel, just without Plasma/Mesa/Discover, so it's mostly "subtracting", not extra work — a small ~300–500 MB image. Nick, I'll ping you when there's something to test. 🙂 Before I build it: is there anything you'd want baked in by default? Thinking headless/server use — things like NetworkManager vs systemd-networkd, docker/podman, python3, build tools, an ssh-only footprint, zram on by default, etc. If you tell me your use case I'll pick sane defaults rather than guessing. Good news on audio in the meantime: both HDMI and the analog 3.5 mm jack are working now (with jack-detect hotplug), so that's no longer a blocker for either image.

sudo ip link set dev wlp1s0 down sudo ip link set dev wlp1s0 address 02:00:00:00:00:01 sudo ip link set dev wlp1s0 up sudo systemctl restart NetworkManager

Same problem here. There are two other (older) threads without a real solution. Has anyone found a fix?

Hello @BipBip1981, with Kernel 6.18.35 / Armbian 26.5.1, are you using @iav's new DTP patch or the old DTP file? I'm not sure if it makes any difference, so I was curious what you're using.

Now that I posted this I revisited the debian install the only thing missing was to add the root partition before booting setenv bootargs root=/dev/sda3 rw Of course the networking does not work as the interfaces on the dtb are for freebsd If I manage to properly build this I will post the steps to create the installer (if possible having network enabled so netinst could be used arm debian has the drivers for the network controllers already compiled mv88e6xxx) and some kind of step by step guide how to

I'm trying to do exactly this, I was able to build an arm64 Debian installer, and install it on the the m.2 storage. I've decided to start experimenting with armbian but have not got anywhere yet. If its worth anything this is how far i've got booting Debian for arm64 Marvell>>setenv initrd_high 0xffffffffffffffff Marvell>>setenv fdt_high 0xffffffffffffffff Marvell>>setenv ramdisk_addr_r 0x8000000 Marvell>> load scsi 0:2 ${kernel_addr_r} /vmlinuz 37605312 bytes read in 614 ms (58.4 MiB/s) Marvell>> load mmc 0:2 ${fdt_addr_r} /armada-3720-netgate-2100.dtb 13737 bytes read in 12 ms (1.1 MiB/s) Marvell>> load scsi 0:2 ${ramdisk_addr_r} /initrd.img 36549593 bytes read in 596 ms (58.5 MiB/s) Marvell>> booti ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r} ## Flattened Device Tree blob at 00c00000 Booting using the fdt blob at 0xc00000 Using Device Tree in place at 0000000000c00000, end 0000000000c065a8 Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 6.12.94+deb13-arm64 (debian-kernel@lists.debian.org) (aarch64-linux-gnu-gcc-14 (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP Debian 6.12.94-1 (2026-06-20) [ 0.000000] KASLR disabled due to lack of seed [ 0.000000] Machine model: Netgate 2100 [ 0.000000] efi: UEFI not found. [ 0.000000] OF: reserved mem: Reserved memory: No reserved-memory node in the DT [ 0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x00000000e7ffffff] [ 0.000000] NODE_DATA(0) allocated [mem 0xe7940280-0xe79439bf] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000000000000-0x00000000e7ffffff] [ 0.000000] DMA32 empty [ 0.000000] Normal empty [ 0.000000] Device empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000000000-0x0000000003ffffff] [ 0.000000] node 0: [mem 0x0000000005400000-0x00000000cfffffff] [ 0.000000] node 0: [mem 0x00000000e0000000-0x00000000e7ffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x00000000e7ffffff] [ 0.000000] On node 0, zone DMA: 5120 pages in unavailable ranges [ 0.000000] cma: Reserved 64 MiB at 0x00000000e0200000 on node -1 [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: Trusted OS resident on physical CPU 0x0 [ 0.000000] psci: SMC Calling Convention v1.1 [ 0.000000] percpu: Embedded 34 pages/cpu s101528 r8192 d29544 u139264 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: detected: ARM erratum 845719 [ 0.000000] alternatives: applying boot alternatives [ 0.000000] Kernel command line: [ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) [ 0.000000] Fallback order for Node 0: 0 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 879616 [ 0.000000] Policy zone: DMA [ 0.000000] mem auto-init: stack:all(zero), heap alloc:on, heap free:off [ 0.000000] software IO TLB: SWIOTLB bounce buffer size adjusted to 3MB [ 0.000000] software IO TLB: area num 2. [ 0.000000] software IO TLB: SWIOTLB bounce buffer size roundup to 4MB [ 0.000000] software IO TLB: mapped [mem 0x00000000cf800000-0x00000000cfc00000] (4MB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] ftrace: allocating 50860 entries in 199 pages [ 0.000000] ftrace: allocated 199 pages with 5 groups [ 0.000000] rcu: Hierarchical RCU implementation. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=2. [ 0.000000] Rude variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] RCU Tasks Rude: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=2. [ 0.000000] RCU Tasks Trace: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=2. [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode [ 0.000000] GICv3: 192 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] Root IRQ handler: gic_handle_irq [ 0.000000] GICv3: GICv3 features: 16 PPIs [ 0.000000] GICv3: GICD_CTRL.DS=0, SCR_EL3.FIQ=0 [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000d1d40000 [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 0.000000] arch_timer: cp15 timer(s) running at 12.50MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2e2049cda, max_idle_ns: 440795202628 ns [ 0.000000] sched_clock: 56 bits at 13MHz, resolution 80ns, wraps every 4398046511080ns [ 0.000560] Console: colour dummy device 80x25 [ 0.000574] printk: legacy console [tty0] enabled [ 0.002499] Calibrating delay loop (skipped), value calculated using timer frequency.. 25.00 BogoMIPS (lpj=50000) [ 0.002524] pid_max: default: 32768 minimum: 301 [ 0.005411] LSM: initializing lsm=lockdown,capability,landlock,yama,apparmor,tomoyo,bpf,ipe,ima,evm [ 0.006568] landlock: Up and running. [ 0.006578] Yama: disabled by default; enable with sysctl kernel.yama.* [ 0.006897] AppArmor: AppArmor initialized [ 0.006984] TOMOYO Linux initialized [ 0.007597] LSM support for eBPF active [ 0.008869] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 0.008926] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 0.012629] cacheinfo: Unable to detect cache hierarchy for CPU 0 [ 0.014344] rcu: Hierarchical SRCU implementation. [ 0.014392] rcu: Max phase no-delay instances is 1000. [ 0.014774] Timer migration: 1 hierarchy levels; 8 children per group; 1 crossnode level [ 0.016382] EFI services will not be available. [ 0.016923] smp: Bringing up secondary CPUs ... [ 0.017751] Detected VIPT I-cache on CPU1 [ 0.017833] GICv3: CPU1: found redistributor 1 region 0:0x00000000d1d60000 [ 0.017890] CPU1: Booted secondary processor 0x0000000001 [0x410fd034] [ 0.018133] smp: Brought up 1 node, 2 CPUs [ 0.018185] SMP: Total of 2 processors activated. [ 0.018195] CPU: All CPU(s) started at EL2 [ 0.018228] CPU features: detected: 32-bit EL0 Support [ 0.018239] CPU features: detected: 32-bit EL1 Support [ 0.018253] CPU features: detected: CRC32 instructions [ 0.018309] alternatives: applying system-wide alternatives [ 0.075040] node 0 deferred pages initialised in 56ms [ 0.075159] Memory: 3303084K/3518464K available (15680K kernel code, 3826K rwdata, 13964K rodata, 3072K init, 940K bss, 146392K reserved, 65536K cma-reserved) [ 0.076302] devtmpfs: initialized [ 0.081834] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.081914] futex hash table entries: 512 (order: 3, 32768 bytes, linear) [ 0.086738] 23328 pages in range for non-PLT usage [ 0.086766] 514848 pages in range for PLT usage [ 0.088412] pinctrl core: initialized pinctrl subsystem [ 0.089886] DMI not present or invalid. [ 0.093894] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.096297] DMA: preallocated 512 KiB GFP_KERNEL pool for atomic allocations [ 0.096977] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations [ 0.097924] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations [ 0.098133] audit: initializing netlink subsys (disabled) [ 0.098571] audit: type=2000 audit(0.096:1): state=initialized audit_enabled=0 res=1 [ 0.099860] thermal_sys: Registered thermal governor 'fair_share' [ 0.099879] thermal_sys: Registered thermal governor 'bang_bang' [ 0.099903] thermal_sys: Registered thermal governor 'step_wise' [ 0.099914] thermal_sys: Registered thermal governor 'user_space' [ 0.099925] thermal_sys: Registered thermal governor 'power_allocator' [ 0.100025] cpuidle: using governor ladder [ 0.100091] cpuidle: using governor menu [ 0.100186] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.100267] ASID allocator initialised with 65536 entries [ 0.101877] Serial: AMBA PL011 UART driver [ 0.105146] /soc/internal-regs@d0000000/interrupt-controller@1d00000: Fixed dependency cycle(s) with /soc/internal-regs@d0000000/interrupt-controller@1d00000 [ 0.105211] /soc/pcie@d0070000: Fixed dependency cycle(s) with /soc/pcie@d0070000 [ 0.105709] /soc/internal-regs@d0000000/interrupt-controller@1d00000: Fixed dependency cycle(s) with /soc/internal-regs@d0000000/interrupt-controller@1d00000 [ 0.112080] /soc/pcie@d0070000: Fixed dependency cycle(s) with /soc/pcie@d0070000 [ 0.112134] /soc/pcie@d0070000: Fixed dependency cycle(s) with /soc/pcie@d0070000/interrupt-controller [ 0.120245] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages [ 0.120290] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page [ 0.120303] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages [ 0.120314] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page [ 0.120327] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages [ 0.120338] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page [ 0.120350] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages [ 0.120361] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page [ 0.129959] ACPI: Interpreter disabled. [ 0.130924] iommu: Default domain type: Translated [ 0.130974] iommu: DMA domain TLB invalidation policy: strict mode [ 0.137841] pps_core: LinuxPPS API ver. 1 registered [ 0.137884] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.137910] PTP clock support registered [ 0.137953] EDAC MC: Ver: 3.0.0 [ 0.138537] scmi_core: SCMI protocol bus registered [ 0.141141] NetLabel: Initializing [ 0.141184] NetLabel: domain hash size = 128 [ 0.141194] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [ 0.141274] NetLabel: unlabeled traffic allowed by default [ 0.144587] vgaarb: loaded [ 0.148125] clocksource: Switched to clocksource arch_sys_counter [ 0.194400] VFS: Disk quotas dquot_6.6.0 [ 0.194566] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.196938] AppArmor: AppArmor Filesystem Enabled [ 0.197112] pnp: PnP ACPI: disabled [ 0.206822] NET: Registered PF_INET protocol family [ 0.207304] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear) [ 0.270460] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear) [ 0.270677] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.270838] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear) [ 0.271571] TCP bind hash table entries: 32768 (order: 8, 1048576 bytes, linear) [ 0.272800] TCP: Hash tables configured (established 32768 bind 32768) [ 0.273373] MPTCP token hash table entries: 4096 (order: 5, 98304 bytes, linear) [ 0.273682] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear) [ 0.273806] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear) [ 0.274227] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 0.274272] NET: Registered PF_XDP protocol family [ 0.274298] PCI: CLS 0 bytes, default 64 [ 0.274881] Trying to unpack rootfs image as initramfs... [ 0.281554] kvm [1]: nv: 554 coarse grained trap handlers [ 0.282145] kvm [1]: IPA Size Limit: 40 bits [ 0.285641] kvm [1]: vgic-v2@d1da0000 [ 0.285729] kvm [1]: GIC system register CPU interface enabled [ 0.285779] kvm [1]: vgic interrupt IRQ9 [ 0.285816] kvm [1]: Hyp nVHE mode initialized successfully [ 0.288612] Initialise system trusted keyrings [ 0.288739] Key type blacklist registered [ 0.292418] workingset: timestamp_bits=42 max_order=20 bucket_order=0 [ 0.292600] zbud: loaded [ 0.294214] fuse: init (API version 7.41) [ 0.295518] integrity: Platform Keyring initialized [ 0.295611] integrity: Machine keyring initialized [ 0.376869] Key type asymmetric registered [ 0.376929] Asymmetric key parser 'x509' registered [ 1.069734] Freeing initrd memory: 35692K [ 1.100634] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245) [ 1.100921] io scheduler mq-deadline registered [ 1.115509] ledtrig-cpu: registered to indicate activity on CPUs [ 1.115761] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 1.116059] advk-pcie d0070000.pcie: host bridge /soc/pcie@d0070000 ranges: [ 1.116183] advk-pcie d0070000.pcie: MEM 0x00e8000000..0x00e8ffffff -> 0x00e8000000 [ 1.116216] advk-pcie d0070000.pcie: IO 0x00e9000000..0x00e900ffff -> 0x00e9000000 [ 1.116502] advk-pcie d0070000.pcie: PHY unavailable (-19) [ 2.116674] advk-pcie d0070000.pcie: link never came up [ 2.117033] advk-pcie d0070000.pcie: PCI host bridge to bus 0000:00 [ 2.117066] pci_bus 0000:00: root bus resource [bus 00-ff] [ 2.117085] pci_bus 0000:00: root bus resource [mem 0xe8000000-0xe8ffffff] [ 2.117102] pci_bus 0000:00: root bus resource [io 0x0000-0xffff] (bus address [0xe9000000-0xe900ffff]) [ 2.117167] pci 0000:00:00.0: [11ab:0100] type 01 class 0x060400 PCIe Root Port [ 2.117199] pci 0000:00:00.0: PCI bridge to [bus 00] [ 2.117215] pci 0000:00:00.0: bridge window [io 0x0000-0x0fff] [ 2.117230] pci 0000:00:00.0: bridge window [mem 0x00000000-0x000fffff] [ 2.117247] pci 0000:00:00.0: bridge window [mem 0x00000000-0x000fffff 64bit pref] [ 2.118080] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 2.118248] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 2.118286] pci 0000:00:00.0: PCI bridge to [bus 01] [ 2.118307] pci_bus 0000:00: resource 4 [mem 0xe8000000-0xe8ffffff] [ 2.118323] pci_bus 0000:00: resource 5 [io 0x0000-0xffff] [ 2.118698] pcieport 0000:00:00.0: PME: Signaling with IRQ 32 [ 2.119184] pcieport 0000:00:00.0: AER: enabled with IRQ 32 [ 2.126274] mv_xor d0060900.xor: Marvell shared XOR driver [ 2.161710] mv_xor d0060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr ) [ 2.193689] mv_xor d0060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr ) [ 2.193936] debugfs: Directory 'd0060900.xor' with parent 'dmaengine' already present! [ 2.197771] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 2.201122] Serial: AMBA driver [ 2.201554] msm_serial: driver initialized [ 2.201666] SuperH (H)SCI(F) driver initialized [ 2.204642] mousedev: PS/2 mouse device common for all mice [ 2.209486] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 (0,8000003f) counters available [ 2.211682] NET: Registered PF_INET6 protocol family [ 2.241921] Segment Routing with IPv6 [ 2.242053] In-situ OAM (IOAM) with IPv6 [ 2.242152] mip6: Mobile IPv6 [ 2.242185] NET: Registered PF_PACKET protocol family [ 2.242432] mpls_gso: MPLS GSO support [ 2.253720] registered taskstats version 1 [ 2.254108] Loading compiled-in X.509 certificates [ 2.366829] Loaded X.509 cert 'Build time autogenerated kernel key: 3f09b375e8d2d562e2a3808cdf65e52339e5a933' [ 2.378691] Demotion targets for Node 0: null [ 2.379479] Key type .fscrypt registered [ 2.379514] Key type fscrypt-provisioning registered [ 2.516330] Key type encrypted registered [ 2.516391] AppArmor: AppArmor sha256 policy hashing enabled [ 2.516469] ima: No TPM chip found, activating TPM-bypass! [ 2.516485] ima: Allocated hash algorithm: sha256 [ 2.516543] ima: No architecture policies found [ 2.516616] evm: Initialising EVM extended attributes: [ 2.516628] evm: security.selinux [ 2.516638] evm: security.SMACK64 (disabled) [ 2.516647] evm: security.SMACK64EXEC (disabled) [ 2.516657] evm: security.SMACK64TRANSMUTE (disabled) [ 2.516667] evm: security.SMACK64MMAP (disabled) [ 2.516676] evm: security.apparmor [ 2.516685] evm: security.ima [ 2.516694] evm: security.capability [ 2.516703] evm: HMAC attrs: 0x1 [ 2.600612] d0012000.serial: ttyMV0 at MMIO 0xd0012000 (irq = 0, base_baud = 1562500) is a mvebu-uart [ 2.600692] printk: legacy console [ttyMV0] enabled [ 4.101860] clk: Disabling unused clocks [ 4.105987] PM: genpd: Disabling unused power domains [ 4.117167] Freeing unused kernel memory: 3072K [ 4.175939] Checked W+X mappings: passed, no W+X pages found [ 4.181850] Run /init as init process Loading, please wait... Starting systemd-udevd version 257.13-1~deb13u1 [ 5.586850] i2c i2c-0: PXA I2C adapter [ 5.767543] sdhci: Secure Digital Host Controller Interface driver [ 5.774088] sdhci: Copyright(c) Pierre Ossman [ 5.886076] sdhci-pltfm: SDHCI platform and OF driver helper [ 6.011197] xenon-sdhci d00d8000.sdhci: Unable to determine SoC PHY PAD ctrl type [ 6.036497] SCSI subsystem initialized [ 6.040731] mvneta d0030000.ethernet eth0: Using hardware mac address 90:ec:77:01:9f:a6 [ 6.052382] xenon-sdhci d00d8000.sdhci: probe with driver xenon-sdhci failed with error -22 [ 6.054114] (unnamed net_device) (uninitialized): fixed link full duplex 2500Mbps not recognised [ 6.073454] usbcore: registered new interface driver usbfs [ 6.085829] mvneta d0040000.ethernet eth1: Using hardware mac address 90:ec:77:01:9f:a7 [ 6.094463] usbcore: registered new interface driver hub [ 6.100878] usbcore: registered new device driver usb [ 6.217074] orion-ehci d005e000.usb: EHCI Host Controller [ 6.222996] orion-ehci d005e000.usb: new USB bus registered, assigned bus number 1 [ 6.231202] orion-ehci d005e000.usb: irq 45, io mem 0xd005e000 [ 6.252295] orion-ehci d005e000.usb: USB 2.0 started, EHCI 1.00 [ 6.261338] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.12 [ 6.270018] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 6.277541] usb usb1: Product: EHCI Host Controller [ 6.282601] usb usb1: Manufacturer: Linux 6.12.94+deb13-arm64 ehci_hcd [ 6.289406] usb usb1: SerialNumber: d005e000.usb [ 6.296654] hub 1-0:1.0: USB hub found [ 6.300715] hub 1-0:1.0: 1 port detected [ 6.403120] xhci-hcd d0058000.usb: xHCI Host Controller [ 6.409118] xhci-hcd d0058000.usb: new USB bus registered, assigned bus number 2 [ 6.417140] xhci-hcd d0058000.usb: hcc params 0x0a000998 hci version 0x100 quirks 0x0000000000000090 [ 6.417854] ahci-mvebu d00e0000.sata: supply ahci not found, using dummy regulator [ 6.426780] xhci-hcd d0058000.usb: irq 46, io mem 0xd0058000 [ 6.435267] ahci-mvebu d00e0000.sata: supply phy not found, using dummy regulator [ 6.441445] xhci-hcd d0058000.usb: xHCI Host Controller [ 6.448493] ahci-mvebu d00e0000.sata: supply target not found, using dummy regulator [ 6.453642] xhci-hcd d0058000.usb: new USB bus registered, assigned bus number 3 [ 6.461863] ahci-mvebu d00e0000.sata: AHCI vers 0001.0300, 32 command slots, 6 Gbps, platform mode [ 6.469469] xhci-hcd d0058000.usb: Host supports USB 3.0 SuperSpeed [ 6.478547] ahci-mvebu d00e0000.sata: 1/1 ports implemented (port mask 0x1) [ 6.478556] ahci-mvebu d00e0000.sata: flags: ncq sntf led only pmp fbs pio slum part sxs [ 6.501026] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.12 [ 6.508689] scsi host0: ahci-mvebu [ 6.509620] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 6.515027] ata1: SATA max UDMA/133 mmio [mem 0xd00e0000-0xd00e1fff] port 0x100 irq 47 lpm-pol 0 [ 6.520568] usb usb2: Product: xHCI Host Controller [ 6.520577] usb usb2: Manufacturer: Linux 6.12.94+deb13-arm64 xhci-hcd [ 6.520583] usb usb2: SerialNumber: d0058000.usb [ 6.547259] hub 2-0:1.0: USB hub found [ 6.551311] hub 2-0:1.0: 1 port detected [ 6.556177] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM. [ 6.564779] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.12 [ 6.573345] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 6.580828] usb usb3: Product: xHCI Host Controller [ 6.585876] usb usb3: Manufacturer: Linux 6.12.94+deb13-arm64 xhci-hcd [ 6.592625] usb usb3: SerialNumber: d0058000.usb [ 6.598483] hub 3-0:1.0: USB hub found [ 6.602534] hub 3-0:1.0: 1 port detected [ 6.996140] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 7.003506] ata1.00: ATA-9: TS32GMTS400S, S0903D, max UDMA/133 [ 7.009553] ata1.00: 62533296 sectors, multi 1: LBA48 NCQ (depth 32) [ 7.016683] ata1.00: Features: Dev-Sleep [ 7.021454] ata1.00: configured for UDMA/133 [ 7.026593] scsi 0:0:0:0: Direct-Access ATA TS32GMTS400S 3D PQ: 0 ANSI: 5 [ 7.102316] sd 0:0:0:0: [sda] 62533296 512-byte logical blocks: (32.0 GB/29.8 GiB) [ 7.110375] sd 0:0:0:0: [sda] Write Protect is off [ 7.115475] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 7.124963] sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes [ 7.151707] sda: sda1 sda2 sda3 sda4 [ 7.156761] sd 0:0:0:0: [sda] Attached SCSI disk [ 31.204156] rtc-pcf8563 1-0051: pcf8563_write_block_data: err=-121 addr=0e, data=03 [ 31.212138] rtc-pcf8563 1-0051: pcf8563_probe: write error [ 31.217824] rtc-pcf8563 1-0051: probe with driver rtc-pcf8563 failed with error -5 [ 31.226088] i2c i2c-1: PXA I2C adapter Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. No root device specified. Boot arguments must include a root= parameter. BusyBox v1.37.0 (Debian 1:1.37.0-6+b8) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) (initramfs) login (none) login: root Password: Login incorrect login[208]: invalid password for 'UNKNOWN' on 'ttyMV0' (none) login: frank Password: Login incorrect login[208]: invalid password for 'UNKNOWN' on 'ttyMV0' Here attached the device tree binary files from my device. those are for freebsd but fairly similar As I have not been able to login armada-3720-netgate-2100.dtb armada-3720-sg2100.dtb

nand-sata-install has been a symlink to armbian-install for quite a while and yes, this tool didn't receive much love. However it could be replaced soon by this:https://github.com/armbian/configng/pull/951

@Sancho this is really cool, and helped to turn that device from paperweight to usable linux OS. Everything seems "ok", though wifi is jittery at best. I also tried building my own image from the github repo, but after completing the build and repack steps, it fails to send to the device. $ sudo ~/Linux_Upgrade_Tool/upgrade_tool uf output/factory/apftool-rs-patched/Armbian-unofficial_26.08.0-trunk_Linknlink-isg-box-se_bookworm_vendor_6.1.115-factorytool.img Loading firmware... Support Type:3528 FW Ver:c.0.00 FW Time:2026-07-16 02:46:46 Loader ver:1.04 Loader Time:2023-12-13 16:28:48 Start to upgrade firmware... Test Device Start Test Device Success Check Chip Start Check Chip Success Get FlashInfo Start Get FlashInfo Success Prepare IDB Start Prepare IDB Success Download IDB Start Download IDB Success Download Firmware Start Download Firmware Fail I'd love to experiment more with it, but no idea how to get past this part.

on my system nand-sata-install is just a link to armbian-install ls -l /usr/bin/nand-sata-install lrwxrwxrwx 1 root root 15 Nov 22 2025 /usr/bin/nand-sata-install -> armbian-install do you mean that the nand-sata-install part of armbian-install is not maintained

hi. can you make only cli image? i will test it

Thanks @AurealNix - that's good intel. Only 20 of those patches of the 109 failed - I had a quick look through them and I can see you are looking to prioritise the GPU (all those GOOGLE_ flags to make youtube stream better etc) amongst other things. For my project I only needed to run headless so I could install your image and uninstall KDE if it didn't work out with my current prototype for this outdoor noise cancelling thing (I was attracted to the opi 4a because it had a bit more all round grunt) I figured I'd stick with armbian as it would have a better chance of the PR for changes to dtb etc being accepted into "stable".. I think I might go with your .dts and manually apply the changes to the other files and then build from there - used to have the stomach for this back in the day when I used to hack stuff before the internet, but I really need to get onto the noise cancelling project as my wife complains about the noise of the road when we have a BBQ outdoors and I reckon i could go some way to disturb that with some software. Your retro gaming image sounds top notch! I'm still to Master Halo 4 on the X-Box one given all these other distractions. The board is now in the bottom drawer for now as the DJI Mic Mini 2 just turned up today and the other board recognises it ok and its on to stage 2 of this prototype. Enjoy the football .. Cheers

you fancy a fun distraction rather than a frustrating one: I'm also putting together a retro-gaming image for this SoC (HDMI to the TV + a gamepad = a neat little emulation box, and it's the same chip as some of the new handhelds). Early days, but it's in the works — one more reason to keep the board out of the eBay pile. 🙂

Hi @bickns, thanks a lot for giving it a go! 🙏 The reason dropping them into userpatches/kernel/archive/sunxi-6.18 fails is that these aren't Armbian-style patches — they're a git format-patch series on top of plain vanilla 6.18.38 (base commit 1db74811b), meant to be applied to a clean tree in order. Armbian applies its own sunxi patch set first, so they conflict against that. I didn't use the Armbian build system at all — I built mainline from scratch: Clone/checkout vanilla 6.18.38, then git am /path/to/patches/0*.patch (all 106, in order). Copy opi4a_blindboot_defconfig into arch/arm64/configs/ and make opi4a_blindboot_defconfig. make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j$(nproc) Image dtbs modules Wrap it for the BSP U-Boot (this is the important bit — it only boots a legacy uImage): mkimage -A arm -O linux -T kernel -C none -a 0x41000000 -e 0x41000000 -d arch/arm64/boot/Image uImage Two things to know: A handful of the patches are BSP-U-Boot workarounds (static /memory, display FDT stubs, etc.) — only needed to boot under the proprietary BSP U-Boot. If you're on mainline U-Boot / a normal Armbian boot flow, you'd skip those. The README groups the patches by destination so you can see which is which. If you want to integrate into Armbian proper, the cleaner path is probably the board DTS + defconfig + the generic sunxi fixes as individual patches, rather than the whole display series in one go (that one's a big port of the minimyth2/Suess work and would need adapting to Armbian's tree). Happy to help however's useful — glad it's of interest!

Yes, I already forgot this and maybe more; Armbian uses this by default now AFAIK, so this is another issue like netplan; I normally do in-place dist-upgrades, so my older SBC's I bought when Buster was the current Debian version, so that is still somewhere in a tag in a image generation file or so, but os-release is 13 and kernel 6.18. But for 1 case, I did take a recent/new Armbian image (Trixie) and it did cost a lot of time as the default settings for that don't work properly in my home network, so after reading freedesktop.org docs and with extra setting in conf file, it worked. But openresolv and a fixed resolv.conf is a simpler base.

@AurealNix - great effort and thanks for putting me in touch with Claude 5, I was just using Gemini and it was struggling a fair bit!! In fact I had just put this board on ebay as it was causing too much distraction so your last two posts looked hopeful. Sorry my spanish isn't that great so I'll stick with English. I was hoping to just put these 106 patch files directly into the userpatches/kernel/archive/sunxi-6.18 folder and then run compile.sh with USER_PATCHES=yes, but that didn't work as patch files in that location seem to be tempremental and it couldn't find a lot of the targets. I tried removing the ones with errors which didn't work either, so went down the route of adding running compile.sh with kernel-patch parameter then copying your sun55i-t527-orangepi-4a.dts into ./cache/sources/linux-kernel-worktree/6.18__sunxi64__arm64/arch/arm64/boot/dts/allwinner/sun55i-t527-orangepi-4a.dts to get a new patch file, but this failed to compile likely because it doesn't have the changes you made to the .dtsi and other files . It would be good to know how you and Claude were building the kernel - I can see in your README that you are doing it directly into linux 6.18.38 tree, whereas I was working out of a clone of armbian in github. I would like to spend more time on this but need to get onto the real reason I bought the board (an outdoor noise cancelling project) so I'm going to use another board in the meantime. Cheers