Frédéric Mahé

Now fixed on main for the whole family (CBSIZE=1024, tested on a BPI-F3 with a 265-char line): https://github.com/armbian/build/pull/11257

Still relevant on main: orangepirv2.csc and orangepir2s.csc (spacemit family, SRC_EXTLINUX="yes", same k1_defconfig with CONFIG_SYS_CBSIZE=256) boot via extlinux with the same 223-char append line. Tested on a BPI-F3 (265-char line boots with CBSIZE=1024): https://github.com/armbian/build/pull/11257

The 26.8.3 BPI-F3 image ships linux-image-current-spacemit 26.8.3 with kernel 6.18.45, but apt.armbian.com serves 6.18.44 under the same version: ``` $ apt-cache show linux-image-current-spacemit=26.8.3 | grep Filename Filename: pool/main/l/linux-6.18.44/linux-image-current-spacemit_26.8.3_riscv64__6.18.44-....deb $ apt list --upgradable | grep linux-image linux-image-current-spacemit/trixie 26.8.3 riscv64 [upgradable from: 26.8.3] ``` apt upgrade then installs 6.18.44, while /boot/dtb still points to dtb-6.18.45-current-spacemit (the dtb package, also 6.18.44 in the repo, is not upgraded). Workaround: apt-mark hold linux-image-current-spacemit linux-dtb-current-spacemit.

The 26.8.x BPI-F3 images boot via extlinux, and the vendor U-Boot has CONFIG_SYS_CBSIZE=256. pxe_utils.c rejects a longer append line (bootarg overflow, serial only), so a headless board just never boots. The default line is already 223 chars: adding systemd.log_target=kmsg printk.devkmsg=on (265) was enough to trigger the issue. Suggestions: raise CONFIG_SYS_CBSIZE in the board's U-Boot config, and/or drop splash plymouth.ignore-serial-consoles from minimal images (Plymouth is not installed). I can send a PR setting CONFIG_SYS_CBSIZE=1024 in the spacemit U-Boot config, if still relevant now that main boots via boot.scr.