Werner

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

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?

Correct. Glad you made a backup beforehand.

You can put the microsd in your computer and check a few things like is /boot populated? does the UUID of the root partition match in armbianEnv.txt and /etc/fstab?

Both 5.10 and 6.1 are vendor bsp and have nothing in common with collabora/mainline. Their hw support status should be more or less identical. mainline is 6.8 or 6.9-rc

Hi, not sure if module blacklisting affects initramfs creation, however it should prevent the module being loaded at boot time. Did you check if this works as expected?

Hey, if this works for you just fine then there is not much to worry about. Consider either freezing firmware via armbian-config or create a backup of your OS before doing major updates like kernel since those nightly images feed themselves from the beta repository. Anyway you are free to build your own image using the build framework. Check the documentation, for standard images there isn't much to it. https://docs.armbian.com/Developer-Guide_Build-Preparation/ https://docs.armbian.com/Developer-Guide_Welcome/ In terms of kernel choice there isn't a perfect solution yet. Both legacy and vendor are, as their names imply, aged vendor bsp kernels which support most board functions but on the downside won't receive much attention in future. On the other hand there is edge which follows mainline as close as possible but is under heavy development to add missing board features and until completion, if this state is ever reached anyways, will take years at least. Basic functionality is there and its mostly fine for server tasks.

Never heard of. Therefore probably no ready-made images exists. https://docs.armbian.com/Process_Contribute/ https://docs.armbian.com/Developer-Guide_Adding-Board-Family/