StarSurfer

Version 20220419-current with 5.17.3 kernel and  new version of u-boot-2022.04.

version 20220428 with kernel 5.18-rc4 (edge) and 5.17.5 (current)

New version 20220408-edge with kernel 5.18-rc1

Version 20220419-edge with a 5.18-rc3 kernel and  new version of u-boot-2022.04.

Hello, @StarSurfer,
This is my fault, and something I'll need to repair for release.  I believe the fastest solution for you would be to mount your image and rename the file boot.scr.uimg to boot.scr .   This won't work because the boot.cmd was changed to use the newer u-boot default parameters.  Follow the directions below.
 
Alternately, if you flash the latest u-boot (2022.04) and wipe the environment variables according to instructions I haven't posted to the espressobin page yet, the u-boot 2022.04 default boot looks for the boot.scr.uimg file.
An initial pass of those instructions looks like, from the u-boot serial console:
- env default -a
- setenv ethaddr <YOUR_ADDR_HERE>
- saveenv

Since we build our own kernel instead of using Debian's upstream, sometimes the kernels are tuned to the device, and sometimes the kernels are detuned through mistake or optimization.  For instance, my own kernel builds have turned off a LOT of device drivers, it's the difference between a 180 minute build and a 25 minute build.
If you would like the Armbian builder to build modules that you use, please submit a PR against https://github.com/armbian/build/blob/master/config/kernel/linux-mvebu64-current.config or linux-mvebu64-edge.config.