Werner

Focal is EOL. There are no further updates anyways.

Why not do these steps while building your own image? https://docs.armbian.com/Developer-Guide_User-Configurations/

No idea what this version is. Take out microsd and shove it into your laptop/PC (running Linux) and mount it. Then check whats wrong.

moved to offtopic

I don't know for sure but my guess is yes, you need the sd to hold the boot loader at least. NAND was supported only with stone-age 3.x kernels which have been abandoned years ago. Therefore this can no longer be used.

moved

moved

as mentioned except code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } .. everything should belong to your current user Take note of the permissions for code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } .. Which admin?

moved

Never heard of a service like this. If you want persistent iptables rules install code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } iptables-persistent package via apt. iptables is active already once the kernel module is loaded which most likely is by default.

Which is kind of odd since both Armbian and Joshua's work are very close kernel-wise.

Debian Buster is EOL. Remove Armbian related entries from apt sources and you are good to go. There won't be any further updates from Armbian for this userspace. https://docs.armbian.com/User-Guide_FAQ/#how-do-i-upgrade-from-armbian-buster-to-bullseye Debug boot issue: https://debug.armbian.de Put SD card into your Linux computer and mount it.

moved

If the image would have been made by us its download would be either from armbian.com or https://github.com/armbian/community/ or https://github.com/armbian/os and not from some random baidu/google drive.

I suggest to ask at the place where you got the image from. There no way we could tell in which way the source has been modified to create it.

Not support yet We also need some time to prepare and roll-over stuff to a new environment. Also check https://github.com/armbian/build/issues/6527

Just a pure guess but have you tried a more recent userspace like noble or trixie? Maybe the kernel isn't the issue but the software accessing it.

https://docs.armbian.com/Developer-Guide_Build-Preparation/

Well you can try to disable the mentioned switch and see what goes wrong when packaging happens. Then you need to figure out how to fix it.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

If the image in question is not at Github its gone. trunk images are not archived over longer period. The amount of storage needed for this task would be just insane.

This is not possible in an automated way. You can use the customization script mentioned here to adjust the image to your needs.

Did you try installing armbian-firmware-full via apt?

Ah okay. Trixie is an unsupported userspace anyways. So this might be fixed at some point on the way when it reaches stable.

have you tried to run dpkg-reconfigure openssh-server so a fresh bunch of keys is being generated? Seems like for some reason key generation fails on first boot....