All Activity

My PBP died, so I can no longer test it myself. You can start by testing the PPSSPP aarch64 AppImage. https://github.com/hrydgard/ppsspp/releases A couple of years ago I had performance issues with the PPSSPP Flatpak on my Phytium D2000, so I built it on Ubuntu 22.04. I'm not sure if I followed the instructions for Qt, or for Linux. So you need to install the prerequisites and I guess it doesn't hurt to install the additional packages mentioned for Ubuntu. https://github.com/hrydgard/ppsspp/wiki/build-instructions#building-with-cmake-other-platforms-eg-linux

moved to tvboxes

Hi @BOFFBOY, have you managed to make it work? Having similar issue : tried with two different orange pi 5 , two different nvme SSDs, three different Power supplies up to 5V/5A and three armbian kernels: 5.10 | 6.1 and 6.18

You are telling me to forget the thing I suspect is the reason for the network not working correctly...? If it is "working perfectly", why does it not resolve addresses from the bpi? Why is your bpi setting 127.0.0.53 (witch would be incorrect even if you ran a dns server ON that device, it should then be 127.0.0.1 (or the device ip), potentially at port 53 but IIRC, port 53 IS dns requests and where it will go without defining it) as dns server and not 192.168.71.1? There you go, there is another culprit. If writing 4k in each iteration fails, but 512 works, 99,99% chance the reason is the sd card is starting to completely fail. Armbian imager would have told you verification failed when verifying the image after writing it, there is zero verification when using dd. There should be no issue writing 4096 bytes (4k) each iteration with dd on a functioning sd-card. Seems you are more interested in screaming and complaining than actually getting to the bottom of it all and set it up like a NORMAL network where NOTHING has to be done on the devices because the settings will be configured correctly with the dhcp lease. Btw, here is the dev documentation for armbian imager (and the source code ofc), took me 30 seconds to find... https://github.com/armbian/imager/blob/main/DEVELOPMENT.md Not sure what useful things you expect to find in there that is not mentioned in the help. It writes an image and does verification of that image (and you can download images), that's it. Good luck I guess, I have nothing further to add.

Hello armbian accomplices, I though I would share my little journey about getting this tablet rooted with magisk so that hopefully one day armbian could run on it. Steps: 1. on android become developer 2. enable oem bootloader unlocking in developer options 3. adb reboot bootloader 4. fastboot oem unlock 5. reboot, the os will be wiped 6. install Magisk apk from github releases 7. get Teclast T60 AI firmware from their site it contains Firmware.img 8. ./sunxi-fw extract -n "wty:init_boot.fex" -o stock_init_boot.img Firmware.img 9. transfer to device and patch with Magisk app 6. adb reboot bootloader 7. fastboot flash init_boot_a /path/to/magisk_patched_init_boot.img 8. fastboot flash init_boot_b /path/to/magisk_patched_init_boot.img 9. fastboot reboot Now do people know about what needs to be done to get xfce with armbian booted on this apparatus?? I think I need better AI agent for this than Deepseek as it is a bit sloppy as usual, Gemini Pro or Claude probably.

Okay I think you are right they are shifting the RAM GB numbers so 8 GB is actually 4 GB as the price suggests. Now now, what I ended up doing is I bought a Teclast T60 AI tablet(for 100 euro shipped in EU) with Allwinner A772 which is supported by armbian and comes with 6GB RAM. I do not know if I will be trying to boot armbian on it soon but I was able to root it with Magisk. It did went on quite a journey to get it rooted as I kind of soft bricked it at first. Deepseek was giving me little wrong information but we got there. I think I might need a more competent AI agent like Gemini pro to get display, touch, wifi, bluetooth etc. working with armbian. Perhaps I post about the rooting process elsewhere at some point. Here is some of the gear I have if people are interested: https://www.aliexpress.com/item/1005009330391341.html DUX DUCIS Foldable Bluetooth 5.0 Keyboard with Touchpad & Phone Holder For Phones Tablets PC iOS Android Windows Mac https://www.aliexpress.com/item/1005011827691576.html https://www.aliexpress.com/item/1005009419399930.html HGFRTEE 3840*2160 13.3inch 4K Portable Monitor All in all pretty pleased with it so far, not exactly Surface pro 5/7 which I also have and they all weight about 1000 grams but then on the other hand this tablet did not cost me hundreds of $ so I can be little less nervous about someone stealing it.

@jock Thank you, I will try.

After more than six successful years with Helios4, I have to say goodbye to this platform and the highly valued, helpful, and knowledgeable Armbian forum. With 32-bit, it’s no longer feasible to continue using it in the future. I have installed the 4 8TB hard drives from the NAS into an Odroid H4+ (Intel, 64-bit), installed OMV8, and on top of that, Nextcloud-AIO Hub 26 Winter and AdGuardHome. Thank you very much for your support over the past few years. btw. The Helios4 hardware (excluding the hard drives) is still available.

Hmm that doesn't look great. It looks like it is crashing at random places vs the same place every time. It makes you wonder if you have a true hardware problem (e.g. bad memory). Can you never make it to a login prompt? I would double check all your memory locations for the FDT, ramfs and kernel to make sure you aren't accidentally overlapping anywhere. And yes, I would avoid starting anything at 0. I actually found a kernel bug from doing that. You could also consider trying to load the kernel as an EFISTUB directly. I don't know if that's supported by armbian or not, but you could experiment. You do know you can save u-boot variables to the SPINOR storage so you don't have to type them in every time, right?

@mrdeathjr Mainline Linux support for the A733 is still in its early stages. I currently have a Armbian build using a collection of patches sourced from the kernel mailing lists. However, I’m getting a lot of errors and haven't managed to boot to a login prompt. https://oftc.catirclogs.org/linux-sunxi/2026-03-23 13:07 <indy> hi all, is there any a733 upstreaming effort? 13:29 <apritzel> indy: effort is underway: pinctrl is WIP (patches have been on the list), and the clock patches have recently been posted 13:30 <apritzel> RTC and AXP are on the list as well, that would conclude the basic necessities to get a DT merged that wouldn't break in the future 15:25 <indy> apritzel_, is it targeted for 7.0? 15:29 <apritzel> indy: no, that's way too late, v7.0 is due to be released in like three weeks already. It's even too late now for v7.1. 15:30 <apritzel> and it's the usual bottleneck: reviews ... I hope I find some time soon to look at the clock patches With @alexc hard work porting the v1.4.8 BSP driver to kernel 6.18, I was able to create a working Armbian build for the Radxa A7Z. https://github.com/NickAlilovic/build/tree/Radxa-mainline-WIP

In my personal opinion with lastest changes showed in kernel lore on a733 https://lore.kernel.org/linux-sunxi/?q=a733 kernel 7.1 give many things for a733

Hi.. I need de original firmware for android box Q17 Allwinner h313.. Someone can help me?

So I'm still doing s-thing wrong with dd. What is correct for this later spin? using 128GB cards.

your card imager needs a CLIBC_2_38, 3 versions newer than my bookworms 2-35, so I'm stuck at dd.

Because I know little to nothing about systemd, I have not touched it. If it is enabled, and IDK how to fix it if it was enabled in the .img. if so that is a bug & is a reason for a respin. Its finally done but probably won't mount as dmesg says it cannot find the ext4 file system. So another ugly thought crosses my curious mind, what is the DEFAULT file system, btrfs?

Please forget I ever mentioned dnsmasq, it exists only in the router where its working perfectly for 7 of the 8 machines here. w/o any man pages I haven't a clue how to run any of the systemd stuff so any config changes that need to be done after 1st boot in order to enable /etc/hosts for local lookups is equ to asking 10k monkeys to retype all of Shakespear's work w/o a single typo. We both know that aint gonna happen b4 the universe runs down in another 500 billion years, So, I am going to rewrite that img to a fresh 128G u-sd, change the /etc/hostname to amanda and rewrite the the /etc/hosts file with mine. Then you tell ME what to do via systemd to make a user "ping -c1 yahoo.com translate" to its dns address in <1.5 milliseconds. That rewrite will take at least an hour. maybe into 2 because the only wat to get a boot able image out of that respin is with dd if=/dev/zero bs=512 count=20 of=/dev/sdc to wipe the u-sd card. then dd if=Armbian_26.2.1_Bananapim5_noble_current_6.18.15_xfce_desktop.img bs=512 of=/dev/sdc option bs=4096 is much much faster, only about 12 minutes to write but will NOT boot nor will it mount as /dev/sdc1 to /mnt/sdc1 So ATM its being written at bs=512, hoping it will work. That takes well over an hour. You have an image writer, "Armbian.Imager_1.2.5_amd64.AppImage" which has no manpage, a useless help screen and has never written a bootable .img file to any sd card since I dl'd it in jan 25. I haven't even bothered to try it as it this time as apparently burns up any u-sd card I've tempted it with so good but cantankerous old dd to the rescue. That, and 45 years a DM-II is slowly taking my eyesight because of macular-degeneration, not your problem of coarse, but mine at 91 yrs old. But saying dd is slow is an understatement, glacial is a better description. from the shell doing the writing: root@coyote:/home/gene/Downloads/armbian# dd if=Armbian_26.2.1_Bananapim5_noble_current_6.18.15_xfce_desktop.img bs=512 of=/dev/sdc status=progress 6230856192 bytes (6.2 GB, 5.8 GiB) copied, 2939 s, 2.1 MB/s

I'd like to add my observations. The current version is 7.0.0-rc6-edge-sunxi64. The wireless interface is available, but if Ethernet is connected, it's impossible to connect to either interface via SSH. However, as soon as the Ethernet speed is set to 100, both interfaces become operational. Maybe this will help revive the hardware.

Does it? Does not look like 192.168.71.1 to me... And: That is not correct, that is the global scope, no ip can end with 0. Ehhh... What do you call dnsmasq on your router then?!? If you don't "maintain" that, yes, things like this can happen, especially since you have set the leases to never expire. I have no idea if this is the case, it's for YOU as sysadmin of your network to know. Nobody knows what you did after install. All that is known after all things written in this thread: You have a dhcp server you have a dns server (dnsmasq) you installed Armbian_26.2.1_Bananapim5_noble_current_6.18.15_xfce_desktop.img (that comes with network manager according to documentation) It seems you have systemd-networkd enabled Unless you can prove the default config was with both systemd AND network manager, YOU have made changes that breaks the installation. Nobody can answer what you did, only you. The normal way if having a local dns server (even if it ONLY forwards request to outside dns server) is to configure the resolving for local domains in the dns server and not touch it at device level. For example a consumer grade router, it will set dns to router ip in the dhcp lease and when requests come in, resolve with asking your ISP dns servers. Hence, if looking up what dns server is used on the devices, they will NOT point to your ISP dns servers (or google or cloudflare etc), it will point to your router ip. Lets say you have a pihole on your network that acts as dns server, then you configure the router (dhcp server) to point to THAT ip for dns, hence, the dhcp lease will deliver THAT ip. And then you configure the pihole to resolve local ip:s and what outside dns servers to use. The DEVICES will ONLY see the local ip where the pihole lives in this situation. Resolving domains to local ip:s (/etc/hosts on your device) has nothing to do with your dns detection failing. This is all pretty basic networking... Edit For reference, this is what your /etc/resolve.conf should look like (or similar) if you configure your dhcp server to point at the ip where dnsmaq lives (same ip as the router itself) then propagate those settings via the dhcp lease. Then nothing has to be done on any device except for resolving local ip:s if you refuse to do that with dnsmasq. If you configure dnsmasq to do that, resolving will be done on the router instead of the devices and absolutely nothing has to be done on any device. With systemd: # Generated by resolvconf domain home nameserver 192.168.71.1 With network manager: # Generated by NetworkManager search home nameserver 192.168.71.1 If you don't want to reinstall again, make sure systemd network services are disabled and network manager is enabled and then reboot. But be mindfull you might need physical access if network completely fails at boot. IIRC relevant services are (I could be wrong here, you should read up on documentation) systemd_networkd.service, systemd_resolved.service & networkmanager.service I'm in the middle of moving, so I only have an arch desktop and laptop up and running at the moment, so I can not confirm on any armbian installation that I provide 100% accurate information.

@bschnei - Yep.. it was modules, via uInitrd. Sadly the legacy config says the kernel bootarg param is 'initrd', so that lost me a good chunk of my life i'll never get back. using RAMDISK_START as the boot arg helped. This did, indeed, load the sata modules, which raised the disk. [EDIT: lol. RAMDISK_START apparently isn't even relevant? grep 'Unknown kernel command line parameters' *.log EspressoBin_Ultra-Bootlog.2026-04-03_001.log:[ 0.000000] Unknown kernel command line parameters "RAMDISK_START=0xa00000 biosdevname=0", will be passed to user space. EspressoBin_Ultra-Bootlog.2026-04-03_003.log:[ 0.000000] Unknown kernel command line parameters "RAMDISK_START=0xa00000 biosdevname=0", will be passed to user space. EspressoBin_Ultra-Bootlog.2026-04-03_004.log:[ 0.000000] Unknown kernel command line parameters "RAMDISK_START=0xa00000 biosdevname=0", will be passed to user space. Not sure why it's working now... ] In case this might help someone later, here's the uboot init config I used for the EspressoBin-Ultra to boot from NVMe / SATA / sda1 / SCSI: => setenv scsi_rootfs "UUID=8045e72d-9d9e-465c-a9ee-95cad5513ec8" => setenv scsi_boot_init 'scsi scan; scsi dev 0' => => setenv scsi_kernel_addr_r '0x7000000' => setenv scsi_kernel_name '/boot/Image' => setenv scsi_kernel_load "ext4load scsi 0:1 $scsi_kernel_addr_r $scsi_kernel_name" => setenv scsi_initrd_name '/boot/uInitrd' => setenv scsi_initrd_addr 0xa00000 => setenv scsi_initrd_load "ext4load scsi 0:1 $scsi_initrd_addr $scsi_initrd_name" => setenv scsi_fdt_name '/boot/dtb/marvell/armada-3720-espressobin-ultra.dtb' => setenv scsi_fdt_addr_r '0x6f00000' => setenv scsi_fdt_load "ext4load scsi 0:1 $fdt_addr_r $scsi_fdt_name" => setenv scsi_setbootargs "setenv bootargs $console root=$scsi_rootfs rw rootwait RAMDISK_START=$scsi_initrd_addr net.ifnames=0 biosdevname=0" => setenv scsi_booti "booti $kernel_addr_r $scsi_initrd_addr $fdt_addr_r" => setenv scsi_boot "$scsi_boot_init; $scsi_kernel_load; $scsi_initrd_load; $scsi_fdt_load; $scsi_setbootargs; $scsi_booti" => printenv scsi_boot scsi_boot=scsi scan; scsi dev 0; ext4load scsi 0:1 0x7000000 /boot/Image; ext4load scsi 0:1 0xa00000 /boot/uInitrd; ext4load scsi 0:1 0x6f00000 /boot/dtb/marvell/armada-3720-espressobin-ultra.dtb; setenv bootargs console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 root=UUID=8045e72d-9d9e-465c-a9ee-95cad5513ec8 rw rootwait RAMDISK_START=0xa00000 net.ifnames=0 biosdevname=0; booti 0x7000000 0xa00000 0x6f00000 => run scsi_boot And there we go: [ 3.783163] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 3.790704] ata1.00: ATA-11: ORICO, Y0908A0, max UDMA/133 [ 3.796101] ata1.00: 2000409264 sectors, multi 1: LBA48 NCQ (depth 32) [ 3.824725] ata1.00: configured for UDMA/133 [ 3.829607] scsi 0:0:0:0: Direct-Access ATA ORICO 8A0 PQ: 0 ANSI: 5 [ 3.839402] sd 0:0:0:0: [sda] 2000409264 512-byte logical blocks: (1.02 TB/954 GiB) [ 3.847435] sd 0:0:0:0: [sda] Write Protect is off [ 3.852470] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 3.861614] sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes [ 3.883685] sda: sda1 [ 3.886538] sd 0:0:0:0: [sda] Attached SCSI disk Sadly, the kernel is still panicing, during load.... which is basically where I started way back when using 2018 uboot version.... below is the summary, but attached are various boot logs. _001 and _004 are probably the only useful ones though. [ 6.518199] systemd[1]: Starting keyboard-setup.service - Set the console keyboard layout... [ 6.537048] SError Interrupt on CPU0, code 0x00000000bf000001 -- SError [ 6.537084] CPU: 0 UID: 0 PID: 171 Comm: 9 Tainted: G M 6.12.68-current-mvebu64 #5 [ 6.537096] Tainted: [M]=MACHINE_CHECK [ 6.537099] Hardware name: Globalscale Marvell ESPRESSOBin Ultra Board (DT) [ 6.537104] pstate: 20000000 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 6.537111] pc : 0000ffff9bb2be30 [ 6.537114] lr : 0000ffff9bb2d268 [ 6.537117] sp : 0000ffffea848f80 [ 6.537119] x29: 0000ffffea848f80 x28: 0000ffff9bb51540 x27: 0000ffff9a95b8c8 [ 6.537134] x26: 0000ffff9a880000 x25: 0000ffff9bb5eb70 x24: 0000000000000000 [ 6.537144] x23: 0000000000000000 x22: 0000000000000000 x21: 0000ffff9a9771e0 [ 6.537154] x20: 0000ffff9bb51540 x19: 0000000000000000 x18: 0000000000000fff [ 6.537163] x17: 0000000000000000 x16: 00000000ffffffff x15: 00000000000a6de8 [ 6.537173] x14: 0000000000000000 x13: 0000ffffea849080 x12: 0000ffff9bb4e000 [ 6.537183] x11: 0000000000000000 x10: 0000000000000000 x9 : 0000ffff9a88ae50 [ 6.537192] x8 : 000000000001169a x7 : 0000ffff9a9771e0 x6 : 0000ffff9bb5e000 [ 6.537202] x5 : 0000ffffea849080 x4 : 0000000000000000 x3 : 0000000000000000 [ 6.537211] x2 : 0000000000601588 x1 : 0000ffff9ae62860 x0 : 0000ffff9a95a8c0 [ 6.537223] Kernel panic - not syncing: Asynchronous SError Interrupt [ 6.537228] CPU: 0 UID: 0 PID: 171 Comm: 9 Tainted: G M 6.12.68-current-mvebu64 #5 [ 6.537236] Tainted: [M]=MACHINE_CHECK [ 6.537239] Hardware name: Globalscale Marvell ESPRESSOBin Ultra Board (DT) [ 6.537243] Call trace: [ 6.537248] dump_backtrace+0x98/0xf8 [ 6.537265] show_stack+0x20/0x38 [ 6.537272] dump_stack_lvl+0x34/0x90 [ 6.537283] dump_stack+0x18/0x28 [ 6.537290] panic+0x3a8/0x410 [ 6.537299] nmi_panic+0x48/0xa0 [ 6.537306] arm64_serror_panic+0x78/0x90 [ 6.537313] do_serror+0x44/0x80 [ 6.537320] __el0_error_handler_common+0x3c/0xa0 [ 6.537330] el0t_64_error_handler+0x10/0x20 [ 6.537340] el0t_64_error+0x190/0x198 [ 6.537350] SMP: stopping secondary CPUs [ 6.537373] Kernel Offset: 0x237629600000 from 0xffff800080000000 [ 6.537377] PHYS_OFFSET: 0xffffacdfc0000000 [ 6.537380] CPU features: 0x00,00000090,00200000,4200421b [ 6.537386] Memory Limit: none [ 6.742429] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]--- EspressoBin_Ultra-Bootlog.2026-04-03_001.log EspressoBin_Ultra-Bootlog.2026-04-03_002.log EspressoBin_Ultra-Bootlog.2026-04-03_003.log EspressoBin_Ultra-Bootlog.2026-04-03_004.log

Ooh interesting! The PBP in your video is using Manjaro though, can PPSSPP compile on Armbian? Perfect Dark aside, I haven't had any luck compiling other supposedly ARM64 compatible software like 2Ship2Harkinian etc through Armbian. If we can figure it out then maybe GoW will also be more playable on PBP through its own eventual native PC Port.

Hi Iuri, I had a similar issue for the rock3a, but I'm using a BigTreeTech 5" DSI display for use on a 3d printer. I've been dabbling in device drivers for 3 years with limited success, but I can say I recently got the 5" dsi display to work. All of my work is here: https://github.com/saltydog101/rock3a_dsi I had to load a new kernel module and then I was able to create a working dtbo for it. It was definitely more than I expected. That being said, when a vendor like Rockchip, Radxa or BigTreeTech decided to make a modification to the linux kernel and not have it committed to mainline, I don't think this is Armbian's issue at all. The engineers and community here do amazing work getting linux running on so many devices. You would normally have better luck looking at Radxa's discord and/or their documentation.

In this local network, there is only one name to address configured in dd-wrt. dnsmasq The only true dns server is at my ISP and its been that way here since RH5.0 in 1998. I have NO M$ experience in my personal history, coming into modern computing by way of a TRS-80 Color computer running os-9, to amigados, about 10 of them as I drug WDTV-5 into the computer age when I became the Chief Engineer in 1984, but I started computing in 1978 at KRCR-12 in Redding Kalipornia. Writing a utility to prepare an automatic station break machines tapes for air that ran on an RCA-1802 and 4k os static ram that cost $400 back then. But lets get back on topic. What I want for outside names NOT in /etc/hosts: the query gets passed to the router at 192.168.71,1:53 where dnsmasq checks to see if its in its cache, and failing that, fwds the query to the dns server at my ISP for resolution. That address is not known on my side of the router. This typically adds about 1.5ms to the ping time. And nowhere in that chain fails this sequence EXCEPT this new install on a bananapi-m5. And I don't have to screw around maintaining a separate dns server of any kind. That is several times the amount of monkey business of cp-ing a common hosts file around is. But you want to insist on a dns server behind every RJ-45 jack in the house. I don't understand the Why? This is simple, quick and bulletproof until somebody decides to fix a perceived security hole, WHICH DOES NOT EXIST IF the router is reflashed with dd-wrt. I have not been touched since finding out about it in yr 1999-2000. Including a decade of running my own web page right here on this machine, stopped only because the spiders refused to honor my robots.txt. So I was paying bandwidth penalties of $150 or more a month on an SS income with my upload bandwidth filled by the robots from mj12. Whoever the hell they are. M$ spiders were in there too. People interested in my stuff couldn't get a word in edgewise. So please tell me where in the resolv.conf area what to edit to make it work, cuz I'll do it and a chattr +i on it to make it permanent. But the fix for debian bookworm, didn't fix this.

@thanh_tan This looks like an AI-generated adaptation of my Radxa Cubie A7Z Armbian build. The Orange Pi 4 Pro uses the same Allwinner A733, so the family config is shared, but Radxa's BSP isn't directly compatible with the Orange Pi 4 Pro without board-specific modifications. Looking at the repo, it's very early stage — The write_uboot_platform() function is just a stub that does nothing, and it's relying on whatever bootloader is already on the SD card. I wouldn't expect it to actually boot on real hardware in its current state.

bellow the conclusion of 4 days of investigations and it works create dts file in tmp directory root@bananapim5:/home/gerard# cat meson-sm1-bananapi-m5-i2c0.dts /dts-v1/; /plugin/; / { compatible = "amlogic,meson-sm1"; fragment@0 { target-path = "/soc/bus@ffd00000/i2c@1d000"; __overlay__ { status = "okay"; clock-frequency = <100000>; pinctrl-names = "default"; pinctrl-0 = <&i2c2_pins>; }; }; fragment@1 { target-path = "/soc/bus@ff600000/bus@34400/pinctrl@40"; __overlay__ { i2c2_pins: i2c2_pins { mux { groups = "i2c2_sda_x", "i2c2_sck_x"; function = "i2c2"; bias-disable; drive-strength-microamp = <3000>; }; }; }; }; fragment@2 { target-path = "/soc/bus@ffd00000/i2c@1d000"; __overlay__ { #address-cells = <1>; #size-cells = <0>; rtc@68 { compatible = "maxim,ds3231"; reg = <0x68>; }; }; }; }; compile the dts on a tmp directory root@bananapim5:/home/gerard# dtc -@ -I dts -O dtb -o meson-sm1-bananapi-m5-i2c0.dtbo meson-sm1-bananapi-m5-i2c0.dts Copy the output to the /boot environnement root@bananapim5:/home/gerard# cp meson-sm1-bananapi-m5-i2c0.dtbo /boot/dtb-6.18.15-current-meson64/amlogic/overlay/meson-sm1-bananapi-m5-i2c0.dtbo modify the boot file /boot/armbianEnv.txt to setup the overlay root@bananapim5:/home/gerard# cat /boot/armbianEnv.txt verbosity=1 console=both overlay_prefix=meson fdtfile=amlogic/meson-sm1-bananapi-m5.dtb rootdev=UUID=d5516764-cadb-4a54-9453-6c500b56656c rootfstype=btrfs overlays=sm1-bananapi-m5-i2c0 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u root@bananapim5:/home/gerard# then a bad surprise the utility hwclock was not in the distro get the package util-linux-extra_2.39.3-9ubuntu6.3_arm64.deb and install it root@bananapim5:/home/gerard# wget http://launchpadlibrarian.net/801453777/util-linux-extra_2.39.3-9ubuntu6.3_arm64.deb --2026-04-03 10:46:26-- http://launchpadlibrarian.net/801453777/util-linux-extra_2.39.3-9ubuntu6.3_arm64.deb Resolving launchpadlibrarian.net (launchpadlibrarian.net)... 2620:2d:4000:1009::3b8, 2620:2d:4000:1009::13e, 185.125.189.229, ... Connecting to launchpadlibrarian.net (launchpadlibrarian.net)|2620:2d:4000:1009::3b8|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 122602 (120K) [application/x-debian-package] Saving to: ‘util-linux-extra_2.39.3-9ubuntu6.3_arm64.deb’ util-linux-extra_2.39.3-9ubuntu6.3_arm64.deb 100%[=========================================================================================================================================>] 119.73K --.-KB/s in 0.05s 2026-04-03 10:46:26 (2.42 MB/s) - ‘util-linux-extra_2.39.3-9ubuntu6.3_arm64.deb’ saved [122602/122602] root@bananapim5:/home/gerard# dpkg -i util-linux-extra_2.39.3-9ubuntu6.3_arm64.deb Selecting previously unselected package util-linux-extra. (Reading database ... 25343 files and directories currently installed.) Preparing to unpack util-linux-extra_2.39.3-9ubuntu6.3_arm64.deb ... Unpacking util-linux-extra (2.39.3-9ubuntu6.3) ... Setting up util-linux-extra (2.39.3-9ubuntu6.3) ... Processing triggers for man-db (2.12.0-4build2) ... root@bananapim5:/home/gerard# you can reboot the module for rtc is download automaticly no need load any module boot and hwclock command to test with the version and build used on my bpi m5 v26.2.1 for Banana Pi M5 running Armbian Linux 6.18.15-current-meson64 Packages: Ubuntu stable (noble) IPv4: (LAN) 192.168.1.243 IPv6: xxxxxxx Performance: Load: 19% Uptime: 1m Memory usage: 7% of 3.67G CPU temp: 41°C Usage of /: 5% of 14G Tips: Flash Armbian from macOS, Windows, and Linux https://tinyurl.com/mryujx5u Commands: Configuration: armbian-config Monitoring : htop Last login: Fri Apr 3 09:54:29 2026 from 192.168.1.101 root@bananapim5:~# hwclock -r -f /dev/rtc1 2026-04-03 11:15:15.211101+02:00 root@bananapim5:~# root@bananapim5:~# Story not finished I try to integrate rtc1 as a fallback to ntp and chrony unfortunatly i was not able to install chrony on this distro (the last one avalaible for m5) so I try apt update and apt upgrade surprise upgrade downgrade from 6.18.15 to 6.18.10 the system but install util-linux-extra and allow chrony installation After that I create the necessary service to boot with rtc1 then start chrony and update system clock with ntp or rtc1 depending of availablility of internet root@bananapim5:/etc/systemd/system# cat sync-* ds3231-rtc.service [Unit] Description=Synchronize RTC1 with system or NTP fallback After=chronyd.service [Service] Type=oneshot ExecStart=/usr/rtc/sync-rtc1.sh [Unit] Description=Run RTC1 sync every hour [Timer] OnBootSec=5min OnUnitActiveSec=5min Unit=sync-rtc1.service [Install] WantedBy=timers.target [Unit] Description=Synchronize system time from DS3231 RTC DefaultDependencies=no Before=sysinit.target [Service] Type=oneshot ExecStart=/sbin/hwclock -s -f /dev/rtc1 RemainAfterExit=yes [Install] WantedBy=sysinit.target root@bananapim5:/etc/systemd/system# cat /usr/rtc/sync-rtc1.sh #!/bin/bash # sync-rtc1.sh # Synchronisation RTC1 <-> système avec logging # Vérifie si Chrony a des sources NTP actives NTP_OK=$(chronyc tracking | grep 'Reference ID' | grep -v '0.0.0.0') if [ -n "$NTP_OK" ]; then # Chrony OK, mettre RTC1 à jour depuis l’heure système hwclock -w -f /dev/rtc1 logger -t sync-rtc1 "NTP actif : mise à jour RTC1 depuis l'heure système" else # NTP indisponible, remettre l’heure système depuis RTC1 hwclock -s -f /dev/rtc1 logger -t sync-rtc1 "NTP indisponible : mise à jour de l'heure système depuis RTC1" fi root@bananapim5:/etc/systemd/system# end of story. log of the result 2026-04-03T13:24:30.009238+02:00 bananapim5 sync-rtc1: NTP indisponible : mise à jour de l'heure système depuis RTC1 2026-04-03T13:24:30.013803+02:00 bananapim5 systemd[1]: sync-rtc1.service: Deactivated successfully. 2026-04-03T13:24:30.014705+02:00 bananapim5 systemd[1]: Finished sync-rtc1.service - Synchronize RTC1 with system or NTP fallback. 2026-04-03T13:29:35.005855+02:00 bananapim5 systemd[1]: Starting sync-rtc1.service - Synchronize RTC1 with system or NTP fallback... 2026-04-03T13:29:36.001355+02:00 bananapim5 systemd-resolved[1433]: Clock change detected. Flushing caches. 2026-04-03T13:29:36.010529+02:00 bananapim5 sync-rtc1: NTP indisponible : mise à jour de l'heure système depuis RTC1 2026-04-03T13:29:36.016160+02:00 bananapim5 systemd[1]: sync-rtc1.service: Deactivated successfully. 2026-04-03T13:29:36.016473+02:00 bananapim5 systemd[1]: Finished sync-rtc1.service - Synchronize RTC1 with system or NTP fallback. 2026-04-03T13:30:01.478054+02:00 bananapim5 CRON[2521]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) 2026-04-03T13:34:44.331407+02:00 bananapim5 systemd[1]: Starting sync-rtc1.service - Synchronize RTC1 with system or NTP fallback... 2026-04-03T13:34:45.001445+02:00 bananapim5 systemd-resolved[1433]: Clock change detected. Flushing caches. 2026-04-03T13:34:45.010331+02:00 bananapim5 sync-rtc1: NTP indisponible : mise à jour de l'heure système depuis RTC1 2026-04-03T13:34:45.015243+02:00 bananapim5 systemd[1]: sync-rtc1.service: Deactivated successfully. 2026-04-03T13:34:45.016212+02:00 bananapim5 systemd[1]: Finished sync-rtc1.service - Synchronize RTC1 with system or NTP fallback. 2026-04-03T13:36:55.097288+02:00 bananapim5 chronyd[1725]: chronyd exiting 2026-04-03T13:36:55.098535+02:00 bananapim5 systemd[1]: Stopping chrony.service - chrony, an NTP client/server... 2026-04-03T13:36:55.106444+02:00 bananapim5 systemd[1]: chrony.service: Deactivated successfully. 2026-04-03T13:36:55.107444+02:00 bananapim5 systemd[1]: Stopped chrony.service - chrony, an NTP client/server. 2026-04-03T13:36:55.130493+02:00 bananapim5 systemd[1]: Starting chrony.service - chrony, an NTP client/server... 2026-04-03T13:36:55.296466+02:00 bananapim5 chronyd[2559]: chronyd version 4.5 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG) 2026-04-03T13:36:55.297080+02:00 bananapim5 chronyd[2559]: Loaded 0 symmetric keys 2026-04-03T13:36:55.298281+02:00 bananapim5 chronyd[2559]: Frequency -22.284 +/- 4.769 ppm read from /var/lib/chrony/chrony.drift 2026-04-03T13:36:55.298541+02:00 bananapim5 chronyd[2559]: Using right/UTC timezone to obtain leap second data 2026-04-03T13:36:55.302159+02:00 bananapim5 chronyd[2559]: Loaded seccomp filter (level 1) 2026-04-03T13:36:55.308879+02:00 bananapim5 systemd[1]: Started chrony.service - chrony, an NTP client/server. 2026-04-03T13:37:00.601703+02:00 bananapim5 chronyd[2559]: Selected source 2620:2d:4000:1::41 (ntp.ubuntu.com) 2026-04-03T13:37:00.602025+02:00 bananapim5 chronyd[2559]: System clock TAI offset set to 37 seconds 2026-04-03T13:37:01.826456+02:00 bananapim5 chronyd[2559]: Selected source 2001:41d0:2:c837::123 (2.ubuntu.pool.ntp.org) 2026-04-03T13:40:11.651555+02:00 bananapim5 systemd[1]: Starting sync-rtc1.service - Synchronize RTC1 with system or NTP fallback... 2026-04-03T13:40:12.008233+02:00 bananapim5 sync-rtc1: NTP actif : mise à jour RTC1 depuis l'heure système 2026-04-03T13:40:12.011630+02:00 bananapim5 systemd[1]: sync-rtc1.service: Deactivated successfully. 2026-04-03T13:40:12.012299+02:00 bananapim5 systemd[1]: Finished sync-rtc1.service - Synchronize RTC1 with system or NTP fallback. 2026-04-03T13:45:01.529270+02:00 bananapim5 CRON[2593]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) 2026-04-03T13:45:12.987841+02:00 bananapim5 systemd[1]: Starting sync-rtc1.service - Synchronize RTC1 with system or NTP fallback... 2026-04-03T13:45:14.008414+02:00 bananapim5 sync-rtc1: NTP actif : mise à jour RTC1 depuis l'heure système 2026-04-03T13:45:14.012561+02:00 bananapim5 systemd[1]: sync-rtc1.service: Deactivated successfully. 2026-04-03T13:45:14.012904+02:00 bananapim5 systemd[1]: Finished sync-rtc1.service - Synchronize RTC1 with system or NTP fallback. 2026-04-03T13:45:14.013548+02:00 bananapim5 systemd[1]: sync-rtc1.service: Consumed 1.028s CPU time. 2026-04-03T13:45:37.968500+02:00 bananapim5 chronyd[2559]: Selected source 2620:2d:4000:1::40 (ntp.ubuntu.com) root@bananapim5:/etc/systemd/system#

That is supposed to be using network manager, again, see documentation Your question was about networking. How to configure your raid is a completely different question and has nothing to do with network. Since both systemd-networkd AND network manager (and you also mention dnsmasq) is enabled, you have most likely done changes to the system way outside of what you should. If you claim the image you downloaded CAME with all that installed and enabled by default, I would suggest you provide proof of that and then report back as a bug. As for your general network setup, I gave you my opinion earlier: Not on every specific device if there is a local dns server available on the network. Then it's normally done on the local dns itself by first checking local configs (like /etc/hosts) and if not available, resolve using online dns servers and then send the response to the device. And the dhcp server is obv configured to point to the local dns server. That way the configs gets propagated via the dhcp lease to all devices on the network.