anttix

I can confirm that switching to network-manager seems to make the Bookworm image more stable on my hardware. @bobby3605 @bundle @Eatocee can you confirm if one of the two options below work for you as well. Use Debian Trixie image instead of Bookworm. These can be found by scrolling a bit further down on the official download page at https://www.armbian.com/bigtreetech-cb1/ OR switch to NetworkManager sudo apt install network-manager -y Change renderer from networkd to NetworkManager in /etc/netplan/10-dhcp-all-interfaces.yaml --- /etc/netplan/10-dhcp-all-interfaces.yaml.orig 2025-10-12 20:53:08.558759013 +0300 +++ /etc/netplan/10-dhcp-all-interfaces.yaml 2025-10-12 20:53:28.826717724 +0300 @@ -6,7 +6,7 @@ network: version: 2 - renderer: networkd + renderer: NetworkManager ethernets: all-eth-interfaces: match: Thank you!

@JohnTheCoolingFan I tested a Debian Trixie image from the website ( Armbian_25.8.1_Bigtreetech-cb1_trixie_current_6.12.35_minimal.img.xz ) and it seems to be stable even with the default configuration that uses systemd-networkd.

@JohnTheCoolingFan what image are you using? I can reproduce the issue consistently with Armbian_25.8.1_Bigtreetech-cb1_bookworm_current_6.12.35_minimal.img . This is the Minimal / IOT image one can grab from https://www.armbian.com/bigtreetech-cb1/ . Interestingly enough, the Minimal / IOT image does not use NetworkManager, it's configured with systemd-networkd backend (or "renderer" as they call it) for netplan. Perhaps this is the key difference: I saw a comment on a topic below stating that MainsailOS has added CB1 Trixie image which is forced to NetworkManager and it's claimed to be stable.

Small update. The hack below seems to work as well. $ sudo systemctl edit armbian-hardware-optimize.service Add the following content between comments [Unit] Before=basic.target systemd-networkd.service netplan-wpa-wlan1.service Please note that armbian-hardware-optimize was picked at random to force anything that touches wlan1 to wait until slightly later in the boot process. No tests were done to determine at what exact point in the boot process wlan is "safe" to interact with.

Couple of data points that may be helpful. Platform: BTT PI v1.2 D/C 2023.11.8 with the U2C CAN board Distro: Armbian 25.8.1 Bookworm Kernel: 6.12.43-current-sunxi64 Overlays: spidev0_0 1. Adding a sleep 5 hack did not work for me, however what does *seem* to work is inserting the following line to /etc/netplan/30-wifis-dhcp.yaml activation-mode: manual WiFi was still activated (which may be another bug) for at least 3 cold boots in a row (didn't have time to test more thoroughly). Here's a pastebin link from right after one such boot - https://paste.armbian.com/umijapukiy 2. The error from wpa_supplicant is CTRL-EVENT-SCAN-FAILED ret=-1 retry=1 .Same error code (-1) is also reported when attempting a manual scan pi@jubilee:~$ sudo iw wlan1 scan command failed: Operation not permitted (-1) 3. Broken state of the WiFi driver seems to be correlated with mmc errors in dmesg [ 11.490708] sunxi-mmc 4021000.mmc: data error, sending stop command [ 11.490745] sunxi-mmc 4021000.mmc: send stop command failed [ 11.490856] sunxi-mmc 4021000.mmc: data error, sending stop command [ 11.490880] sunxi-mmc 4021000.mmc: send stop command failed [ 11.491071] sunxi-mmc 4021000.mmc: data error, sending stop command [ 11.491098] sunxi-mmc 4021000.mmc: send stop command failed [ 11.491224] sunxi-mmc 4021000.mmc: data error, sending stop command [ 11.491248] sunxi-mmc 4021000.mmc: send stop command failed These are not present if wifi was activated successfully. Here's a pastebin link from right after such boot - https://paste.armbian.com/xovixuniti EDIT: Ran armbianmonitor -c overnight and the SD card seems fine The results from testing /dev/mmcblk0p2 (ext4): Data OK: 111.37 GB (233561400 sectors) Data LOST: 0.00 Byte (0 sectors) Average writing speed: 18.41 MB/s Average reading speed: 22.74 MB/s ... Health summary: OK 3. Reloading the kernel driver (8189fs) when it is already in a broken state is very slow and provokes a slew of mmc errors $ sudo /sbin/rmmod 8189fs pi@jubilee:~$ time sudo /sbin/modprobe 8189fs real 2m15.835s user 0m0.008s sys 0m0.048s $ dmesg .... [ 673.262192] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262286] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262379] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262471] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262563] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262656] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262716] ====>_BlockWrite 101 i:0 [ 673.262742] ====>_WriteFW 230 [ 673.263001] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.263088] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.263141] ====>_BlockWrite 101 i:0 [ 673.263162] ====>_WriteFW 230 Again the same problem is not present if WiFi was activated successfully after boot: Shutting down the interface and reloading the driver works just fine. Please let me know if there's anything else I can collect that can help to track this down. Given this is a fresh install and has no personal data in it yet, I can share my SD card image if that would be helpful.

Experiencing the same issue, wifi fails to activate for about 4 out of 5 boots or so.