next generation armbian-config still has some rough edges and constantly receiving fixes and improvements. If you can reproduce a special case where something doesnt work right, feel free to report at the github repo.

moved

Hi everyone, I'm experiencing a severe boot delay on my Banana Pi M5 running Server Armbian Image (v25.2.2 - Banana Pi M5 - Armbian Linux 6.12.21-current-meson64) when no HDMI monitor is connected. The board itself is working fine, but without an HDMI connection, the system takes several long minutes to complete the boot process. Details The system boots normally and quickly when an HDMI monitor is attached. However, without a monitor, in headless mode , the boot process is significantly delayed several minutes (approx. 4 minutes). Blue led blinking normaly. I've Tried modified /boot/armbianEnv.txt by setting: display_autodetect=false disablehpd=true hdmi_force_hotplug=1 Unfortunately, these changes did not resolve the boot delay issue. Do you please have any suggestions or insights on how to modify the boot process to fix this problem? Thank you in advance.

Hi everybody. I have one of these cards (along with many other OPis and RPis) and I was trying to use it for my Home Assistant installation, but OPi's Debian was not correctly complied so it did not work with ZIgbee USB adapters (and with many other things). I tested the Armbian imga someone put here, but I couldn't make it work. I tried to recompile OPis Debian and to my surprise it complied without any glitch and everything is working. As soon as I can (which may take some time) I'll try to build my own Armbian image. If I succeed I'll bring it here. This message was just to say that OPi's Debian is working fine when rebuilt from scratch, in case someone needs a working system right now. Best regards. Angel

Thanks for the reply! The mirror sync thing just was unfortunate timing hahah! 15 minutes later all was good. EXT4 install did work, gpu seems to work and performance seems to be "OK". I am seeing like 1700~ points on vkmark, whereas some are seeing about 2400~ points, which is a 40 percent difference? It is probably because of the whole vendor-mainline kernel thing, as far as I can see panthor is supposed to work on mainline, have no idea how the magician behind it make it run on vendor... btrfs is definitely broken though, maybe need a ext4 boot partition / btrfs root partition type combo to make it work? Ah also, armbian-config has some funny behavior when trying to switch overlays on/off. You can select the two overlays available (panthor and oc profile) but I can't seem to be able to click save no matter what I tried. Changing armbianEnv.txt works, but I guess this is an issue that needs to go on github... Anyways, thanks again, I guess this thread is done now...