Closed
Description
What happened?
On mvebu/Helios4, after upgrading to newer version of linux-image, U-Boot errors with the following message:
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
In short, the load addresses used by U-Boot are set too small as the newer kernel image overlaps with the load address range of the initial ramdisk. Based on the load order in the boot.cmd this will cause the loading of zImage to write onto the address range where the initial ramdisk was loaded. This will then (luckily!) cause bootz to complain that it cannot process the initial ramdisk image.
More details here: https://forum.armbian.com/topic/49440-helios4-doesnt-boot-after-upgrading-to-linux-6671-linux-image-current-mvebu_2520-trunk343/
How to reproduce?
Upgrade to newer/newest linux-image.
Branch
main (main development branch)
On which host OS are you running the build script and observing this problem?
Ubuntu 24.04 Noble
Are you building on Windows WSL2?
- Yes, my Ubuntu/Debian/OtherOS is running on WSL2
Relevant log URL
Code of Conduct
- I agree to follow this project's Code of Conduct