Please report here https://github.com/armbian/imager/issues

Thank you to everyone who spent time reading my post, and contributing to it. Having had some free days I decided to give it another try and experimented my helios64 with some of the newer images, none of which worked perfectly (my main requirement is OMV plus its miniDLNA, and couldn't get this installed on noble or trixie, although they were booting and working just fine), eventually running now some bookworm from eMMC and while it seems stable there are some performance issues* (need to re-read that bookworm issues thread again as I did not try all the fixes yet, including the dtb one). *By performance issues I mean some apparently slow reading/writing to eMMC, and network performance on 2.5gb, which I know were thoroughly discusses on that thread, just need to spend more time on trying them out I guess. I'm still a newbie into all this stuff and I was reading a lot again before the new tests. Would anyone be able to recommend some version of an archived bookworm image that I should start from? My device is connected to the router via the 1gb interface, and I have a second cable going directly to my desktop via the 2.5gb interface that lands into a 2.5gb USB-c network card. I don’t have the 2.5gb hardware fix done as when I installed it years ago it was working fine on buster with this layout and my router is 1gb only anyway. In any case, I still have the SD card with the prior setup untouched, so can revert back to it, was just thinking it makes more sense to try something new. Happy new year all of you!

@Thermitenjoyer You should be able to just flash it with balena etcher. https://mega.nz/fm/z3w0BTra I uploaded my radxa and orangepi image to mega, im working on NVMe support for orangepi currently, but I dont have the board on hand so im unable to test my kernel-patches. My changes are on github too: https://github.com/rvdr/build/tree/spi-nvme-patches Booting via NVMe works fine when using the sd card for the bootloader, but for some reason I get Kernel panics (not syncing: hung_task: blocked tasks) when using the spi flash for the bootloader.

modprobe parameter should be crystal=1, not crystal_26M_en anymore (see here) Otherwise you could try led-conf6 overlay (but I don't know if it fits your board...) which has the attribute esp,crystal-26M-en = <1> in the device tree to set the crystal to 26 MHz

By the way, the "tag" says "solved", but that is not true. A tag was required for submission and "solved" was the only selection available in the drop down and the text box was not editable.