FredK

@Igor > There are few other things that would be nice to get working - I notice WOL service erroring out, fan support is unknown. Regarding "fan support": Fan was working correctly after installing fancontrol, see https://forum.armbian.com/topic/44379-fancontrol-bookworm-solved/#findComment-209055 (Thread is in Standard support->Other families->Helios 4)

@helios4user12 > I updated the sd card with the provided image via dd. Will this be a one time thing? Yes. In the meantime there were further updates and my Helios4 is still going strong.

@Igor After @Mangix's post I was able to fix my installation patching the bootloader. I'm aware that Helios4 is a dead-end and I plan to switch to a 64bit-SBC providing 4 or 5 SATA-ports (but I don't find a suitable board up to now).

@Mangix Thank you, that was simple. @Dee2022 What I did: Download of the 1st SolidRun image (... sd.kwb) Copy the image to SDcard containing unbootable Armbian 25.2 (on my Linux desktop using dd, SDcard available here at /dev/sdf) sudo dd if=u-boot-helios-4-sd.kwb of=/dev/sdf bs=512 seek=1 status=noxfer sudo sync Boot Helios4. Voilà.

@Igor Is a new update to 25.2 for Helios4 planned of the kernel binaries ? If so, when can this be expected? If not, what can I do? The post of @Josua-SR is marked as solution. But I have no idea what to do with the *.kwb files from SolidRun. In particular I never made a custom build.

Same here: "No boot after upgrade to Armbian 25.2.2". Same message: Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid The very "unfriendly" behaviour was the unattended-upgrade. Therefore I had no chance first to make an update of my 24.11 system with Linux 6.6.63-current-mvebu (see signature). I had to use for recovery the backup from 24.8 immediately before 24.11 in the pipeline. The recovered system is now Armbian 24.8 with Linux 6.6.47-current-mvebu. Any chance to get 24.11 again?

@pegamonstro I'm using a very similar configuration (see signature) but as a part of OMV. Last February I performed the upgrade to bookworm and OMV7 without any severe problem worth mentioning. mdadm and /proc/mdstat were present. The multiple device /dev/md0 is now present as /dev/md127. Perhaps it would help to install OMV7 to see whether your RAID5 can be recovered using OMV storage management.

@Igor Thank you for your comment and caveat. SATA port multiplication is definitely a no-go for my application (OMV6 + RAID5 with 4 8TB HDD). Is there any Armbian-based recommendation supporting 4 SATA ports "natively"? I want to avoid to go away from Armbian and looking for for a Mini-ITX based configuration (e.g. Intel N100).

I (still) use Helios4 which has been downgraded to "Community maintained" recently after Armbian 23.8.1. I'm aware that I have to migrate to a different HW later in 2025 because It's getting more difficult every day to deal with a 32-bit system using OMV (plus some docker based services) with Armbian. Question: Is there any good advice for a 64-bit HW supported by Armbian and (at least) 4 SATA ports?

bullseye is alive again.

Thank you and waiting for the re-creation ....

Support for bullseye dropped?

@Werner In Armbian Leaflet #8 from June 8th we read (bold typing by me): Now we are in week 5. Any news about Helios4 23.05 Bookworm?

@SvenHz Thank you to link to your work from last Friday. I decided for me to stay with bullseye until the repository update will be re-activated.

@SteeMan Thank you. The leaflet #8 explains the release situation sufficiently.