Hello.
I’ve decided to try Sparky SBC with latest DietPi. On my HDD i’ve found only v6.18 that is pretty old now. It suggests me to update to 6.35 but update fails. So I’ve just downloaded image from here: DietPi - Allo.com Web GUI Image
Burned it with Win32DiskImager to emmc and plugged in my Sparky. But there’s no luck with booting…
Am I doing something wrong or something wrong with OS in this image?
(With v6.18 img I’ve done the same routine and everything worked properly.)
@MichaIng can you have a look pls
Sorry for the late reply. Seems like the initramfs does not like the 64bit flag of the ext4 filesystem. I was actually keeping an old (obviously too old) initramfs in our firmware package. I’ll create new images to test, once with the flag removed, and once with an updated initramfs.
Build is running: DietPi-Build · MichaIng/DietPi@bff5a20 · GitHub
Once done, the new images can be found here: Index of /downloads/images/testing
Ok. Thanks a lot!
I’ll wait for the new image release and let You know if everything is booting and working.
The images are there already: Index of /downloads/images
Would be great if you could test them before I move them to stable downloads. I have no Sparky SBC to test myself 
.
Thanks. Hard to find out what FEATURE_R10 is, since this is not a name of any ext4 filesystem capability. But it seem to be the metadata_csum: linux - Centos 6.10 - Mount Backup Disk with Single partition - Server Fault
This also makes sense since metadata_csum is a new feature which depends on the 64bit feature.
This is actually a quite helpful feature to help against filesystem corruption, so instead of removing the capabilities, I’ll instead ship our image with an updated initramfs, which will be much larger (which was one reason I avoided it).
Strange, the initramfs did not contain a single kernel module. AFAIK it should not be required at all for mounting the rootfs, but the U-Boot build/env expects it. I generated an image with a tiny-initramfs build. @tenoritiger could you give this a try: https://dietpi.com/downloads/images/DietPi_SparkySBC-ARMv7-Bullseye.img.xz
If it does not boot, I’ll disable the metadata_csum ext4 flag and keep using the old/functional initramfs.
Many thanks! I’ll generate an Allo GUI image asap!
New Allo GUI image in place: https://dietpi.com/downloads/images/DietPi_SparkySBC-ARMv7-Bullseye_AlloGUI.img.xz
Nice, thanks again! Everything seems to be working fine. I’ll keep testing in different scenarios.
