Werner

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....

moved ssh is enabled by default on all images. Check if there is further information in journal why it did not start.

moved

Hi, Unfortunately this is not the case (yet). Tags are more or less just for archiving the state of the build framework at a certain point of time (usually at release). Due to its design we are not there yet to have working tags that could reproduce older images. It is our goal to have this working at some point but things are processing very slow. VERSION doesn't do anything and is pure cosmetics.

Probably Armbian also needs a dedicated image for that or some dirty hackjob to allow both variants to boot. Anyway I don't think somebody will waste time on this task...

Which branch did you try? vendor? edge? legacy?