Igor

I can confirm that Armbian_community_25.5.0-trunk.4_Helios4_noble_current_6.6.75.img.xz does not boot on Helios-4 with the same error described above:
 
Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing...  
I spent the weekend investigating a similar issue with upstream Debian and upstream u-boot that turned out to be after a certain size of mmc access data would be corrupted. Disabling the SDHCI_SDMA function in u-boot helped:
https://lore.kernel.org/r/20250208-a388-kerneladdr-v2-1-17c01313eba2@solid-run.com
 
Finally I pushed this and other changes to the SolidRun vendor fork for the Armada 388 System on Module (as used on Helios-4), and attempted booting the same armbian image again. This time boot succeeded:
 
BootROM - 1.73 Booting from SPI flash U-Boot SPL 2024.04 (Feb 08 2025 - 13:12:00 +0000) High speed PHY - Version: 2.0 Detected Device ID 6828 board SerDes lanes topology details: | Lane # | Speed | Type | -------------------------------- | 0 | 6 | SATA0 | | 1 | 5 | USB3 HOST0 | | 2 | 6 | SATA1 | | 3 | 6 | SATA3 | | 4 | 6 | SATA2 | | 5 | 5 | USB3 HOST1 | -------------------------------- High speed PHY - Ended Successfully mv_ddr: 14.0.0 DDR3 Training Sequence - Switching XBAR Window to FastPath Window DDR Training Sequence - Start scrubbing DDR3 Training Sequence - End scrubbing mv_ddr: completed successfully Trying to boot from SPI U-Boot 2024.04 (Feb 08 2025 - 13:12:00 +0000) SoC: MV88F6828-A0 at 1600 MHz DRAM: 2 GiB (800 MHz, 32-bit, ECC enabled) Core: 30 devices, 20 uclasses, devicetree: separate MMC: mv_sdh: 0 Loading Environment from SPIFlash... SF: Detected w25q32 with page size 256 Bytes, erase size 4 KiB, total 4 MiB *** Warning - bad CRC, using default environment Model: Helios4 Board: Helios4 Net: Warning: ethernet@70000 (eth1) using random MAC address - 86:69:49:e4:c6:90 eth1: ethernet@70000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2996 bytes read in 17 ms (171.9 KiB/s) ## Executing script at 00200000 Boot script loaded from mmc 158 bytes read in 13 ms (11.7 KiB/s) 28834 bytes read in 32 ms (879.9 KiB/s) 8146813 bytes read in 807 ms (9.6 MiB/s) 8550096 bytes read in 850 ms (9.6 MiB/s) Working FDT set to 100000 Kernel image @ 0x800000 [ 0x000000 - 0x8276d0 ] ## Loading init Ramdisk from Legacy Image at 01800000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 8146749 Bytes = 7.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 00100000 Booting using the fdt blob at 0x100000 Working FDT set to 100000 Loading Ramdisk to 0f83b000, end 0fffff3d ... OK Loading Device Tree to 0f7cb000, end 0f83afff ... OK Working FDT set to f7cb000 Starting kernel ... Loading, please wait... Starting systemd-udevd version 255.4-1ubuntu8.5
Binaries for reference:
https://images.solid-run.com/A38X/U-Boot/v2024.04/2025-02-08_695f767/u-boot-helios-4-sd.kwb
https://images.solid-run.com/A38X/U-Boot/v2024.04/2025-02-08_695f767/u-boot-helios-4-spi.kwb

Compatible field is reserved for almost identical boards or when image supports more devices, like Raspberry Pi 3 and 4. Base image is for Rpi4 but Rpi3 is also compatible.
 
Other two fields are deprecated as content is generated automatically. For customization of build targets, check this https://github.com/armbian/os/wiki

UPDATE: I managed to make it work eventually.
Here is an updated tutorial: https://gitlab.com/peltho/rock-5c-lite-u-boot-spi

A quick look at the shell code makes me think that it is a different purpose compared to how I use virtualization. I use only HW accelerated based virtualization, so -enable-kvm flag is missing, but might be added by virt-install. Also mostly Arm on Arm although I also use x86 on x86 as well. I do not use qcow2, but just flat images or a physical SD-card or NBD or LVM.
 
Before I got my Rock3A, I downloaded the Armbian Noble image for it (was 6.6.62) but put a 6.12 *rk3588 kernel on it as well. With the default Armbian U-Boot for QEMU I could then prepare everything and already 'run' my Rock3A as a VM on NanoPi-R6C like this:
taskset --cpu-list 0-3 qemu-system-aarch64 \ -M virt -cpu host -enable-kvm -m 2048 -smp 4 \ -bios u-boot.bin \ -drive if=none,file=rock3a.img,format=raw,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -netdev bridge,id=hn1 -device virtio-net,netdev=hn1,mac=xx:xx:xx:xx:xx:xx \ -nographic The taskset is needed if host runs 6.1.x  vendor kernel and also makes it more realistic w.r.t. speed as then the VM gets 4x Cortex-A55, same as real Rock3A.
The 6.12/rk3588 kernel (inside the VM) was needed as that one has all included w.r.t. machine virt (same as vanilla Debian Bookworm kernel).
 
A note is that I later on added Btrfs support to a custom build u-boot for QEMU and converted Ext4 in rock3a.img into Btrfs, but principle is the same. Btrfs offers online shrink and differential snapshots that I use for remote backups. And with a MAC-address equal to the real Rock3A, it is easy flipping between real and VM.
 
Also note is that the following file needs to be created on the host, assuming it uses br0 as base for network I/O:
# cat /etc/qemu/bridge.conf allow br0  
To use full graphics in VM and for multi-year running VM on my RPi4B, I also use virsh and UEFI. But usually only CLI is needed.

hi @jock
 
I agree that changing the SMD 0201 parts is a real challenge - for this reason I used 0402's soldered them direct to the level shifter and run a tiny wire to the 5V source.
I'm thinking that an SoC side strong pull-up would do the trick eventually and remove R90611/12 entirely. But I haven't test this - but will do that with the next PCB I get on my table.
 
The Level-shifter is a Texas Instruments TX0102DCU with and with OE is high the internal 10K pull ups are enabled.  That might me not enough for the external monitor so the 6.8k has been applied.
Same for the SoC side, 10K only , so I support the internal SDA/SCL lines with the light diving strength of 2ma.
Datasheet:
8.3.5 Pullup or Pulldown Resistors on I/O Lines Each A-port I/O has an internal 10-kΩ pullup resistor to VCCA, and each B-port I/O has an internal 10-kΩ pullup resistor to VCCB. If a smaller value of pullup resistor is required, an external resistor must be added from the I/O to VCCA or VCCB (in parallel with the internal 10-kΩ resistors). Adding lower value pull-up resistors will effect VOL levels, however. The internal pull-ups of the TXS0102 are disabled when the OE pin is low.  
I would say it doesn't hurt to add the changes to the DTS for the i2c7_xfer pinctrl. But without fixing the Pull-up value on the 5V it will not improve anything.
 
Yes it is tiny tiny.

Do the same for max:
https://github.com/armbian/os/commit/45e7773d8fa023f3c5fb3c9c1402bf3616c59031
and wait for next automated rebuild cycle of community maintained images.
 
Then download pre-configured Gnome desktop image and forget about any other browser then preinstalled one. Also forget general understanding about desktop Linux on PC ... this is embedded Linux / custom hardware world, where things are "a bit" different. Developing and keeping functional desktop image was already on the level of miracle considering that we are operating with big negative budget and absolute absence of any support from HW dealer that makes big sales ... which are crushing ability of making things better. For you and for us.
 
Or dive into https://docs.armbian.com/Developer-Guide_Overview/

Make them build & boot able within the build framework
https://github.com/armbian/build
When you confirms, open a PR https://github.com/armbian/build/pulls and change config file from .eos to .csc and automation will become to produce images.

Successfully tested on the Orange Pi 5 with Ubuntu Noble minimal mainline image. Note that this image kernel panics every now and then on bootup (something to do with power management and interrupts). Disabling networking seems to solve the issue
 
The automated script now supports configuring the network interface on the target using ifupdown. This is primarily useful for statically configured setups

Thank you for quick reply. Haven't even thought it's not supported.
 
PS: I wanted to thank the developers for such build / config tool! It worked like a charm as I decided to upgrade from Ubuntu xenial.

Wow, unbelievable. But happy to see it is so actively maintained.
I don't mind being on beta for time being and I am fine with updating this often. I actually enjoy receiving updates, since I decided to switch to beta and keep the kernel unfrozen.
Worst case scenario - if some beta breaks my back, I will just restore whole SD card to a few month old backup and update to latest stable.
I do not have anything useful on my board that changes over time.
 
Lets consider this topic closed.

After applying patch from previous post, it updated to latest version without complaining about unhealthy status:

Link removed. That's all i can do for the time being.
 
@darkside40 Thanks!

Copy that, @Igor. Just learning my way around here.
 
Hopefully my donation will help a little!
 
I appreciate you and your team. Armbian is a great gift to the SBC community.

Key is not deprecated, method is. On Noble / Sid and future.
 
sudo wget https://apt.armbian.com/armbian.key -O key sudo gpg --dearmor < key | sudo tee /usr/share/keyrings/armbian.gpg > /dev/null sudo chmod go+r /usr/share/keyrings/armbian.gpg sudo echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com $(lsb_release -cs) main $(lsb_release -cs)-utils $(lsb_release -cs)-desktop" | sudo tee /etc/apt/sources.list.d/armbian.list apt update  

Key is not deprecated, method is. On Noble / Sid and future.
 
sudo wget https://apt.armbian.com/armbian.key -O key sudo gpg --dearmor < key | sudo tee /usr/share/keyrings/armbian.gpg > /dev/null sudo chmod go+r /usr/share/keyrings/armbian.gpg sudo echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com $(lsb_release -cs) main $(lsb_release -cs)-utils $(lsb_release -cs)-desktop" | sudo tee /etc/apt/sources.list.d/armbian.list apt update  

Tutorial has been updated to include support for GPT-partitioned images

You already have best possible desktop on this hardware. Simple and fast XFCE. Changing desktop environment won't make any vivid difference. 
https://docs.armbian.com/#key-advantages
 
XUbuntu is more or less identical to Armbian Ubuntu with XFCE subtracted for some Canonical proprietary stuff.

LXDE vs. XFCE ... not worth the troubles maintaining yet another desktop. Difference is too small. We only keep XFCE, Gnome, Cinnamon and KDE Neon in good shape. The rest waits for enthusiast https://github.com/armbian/build/tree/main/config/desktop and you can always start with a minimal CLI image and build on top any desktop you want.

You already have best possible desktop on this hardware. Simple and fast XFCE. Changing desktop environment won't make any vivid difference. 
https://docs.armbian.com/#key-advantages
 
XUbuntu is more or less identical to Armbian Ubuntu with XFCE subtracted for some Canonical proprietary stuff.

LXDE vs. XFCE ... not worth the troubles maintaining yet another desktop. Difference is too small. We only keep XFCE, Gnome, Cinnamon and KDE Neon in good shape. The rest waits for enthusiast https://github.com/armbian/build/tree/main/config/desktop and you can always start with a minimal CLI image and build on top any desktop you want.

Try to rework the script:
https://github.com/armbian/build/blob/main/packages/bsp/nanopim4/nanopim4-pwm-fan.sh#L316
Perhaps expand it to support selecting CPU / hard drive ?

Key is not deprecated, method is. On Noble / Sid and future.
 
sudo wget https://apt.armbian.com/armbian.key -O key sudo gpg --dearmor < key | sudo tee /usr/share/keyrings/armbian.gpg > /dev/null sudo chmod go+r /usr/share/keyrings/armbian.gpg sudo echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com $(lsb_release -cs) main $(lsb_release -cs)-utils $(lsb_release -cs)-desktop" | sudo tee /etc/apt/sources.list.d/armbian.list apt update  

It should not be a problem. I already align my patches with armbian/main so this board is ready for 6.6 and 6.12. And testing images for major kernel bumps should not be a problem neither.
 
OK, I will try to do this.

The problem behind their promotion statement is that its a scam. Dietpi is bloated with proprietary scripts and they are removing packages that are dependencies for everything ... so it makes no sense at the end, just first installation of anything takes longer. But they can claim images has few MB less ... which is "better" and most of end users have no ability / interest to understand they have been conned.
https://docs.armbian.com/#comparison
Damages they create to open source, by playing dirty, that is beyond commenting.
 
 
This should also work OOB then
https://www.armbian.com/uefi-riscv64/
and you don't need to remove anything (from minimal Bookworm OS image, which is significantly lighter then Dietpi).
 
If you / anyone can confirm they are working well, we can move this to Supported section.

I just created a pull request for this. Apologies if I got the request wrong, it's been a long time since I created a PR on anything.

This was moved under a switch to prevent users for switching into kernels that are not meant for end-users.
https://github.com/armbian/build/blob/main/config/boards/rock-5b.conf#L7
 
And this
https://github.com/armbian/configng/blob/main/tools/modules/system/switch_kernels.sh
is the logic for anyone that might to change / improve this.

Hi,
 
I am trying to update the patch for kernels 6.10 and 6.11 (same code).
My first try was not successful (compile error), I will try again, I think I've understood what the patch will do, but there are a lot off differences between kernel versions 6.6 and 6.10, maybe some new lines need to be patched too.

Once it compiles and runs fine on my helios 4, I will provide the patch 😉
 
Kind regards,
Xavier.