[U-Boot] Uboot is rejecting valid initramfs (compressed cpio) with "Wrong Ramdisk Image Format"
quwenruo.btrfs at gmx.com
Sat Oct 12 11:13:11 UTC 2019
On 2019/10/12 下午6:52, Qu Wenruo wrote:
> I'm using initramfs (gzipped cpio) to boot my board (RockPi4).
> The problem is, if initramfs is loaded other than old initrd, booti
> command will just fail with "Wrong Ramdisk Image Format".
Well, it looks like Uboot is using wrapped image created by mkimage to
add extra info.
Then I guess this is just my bad...
> I'm currently working it around by not using initramfs/initrd, and
> compile the fs module into the kernel.
> But that's really an ugly solution, and I'm surprised why Uboot is doing
> such check.
> As kernel has a much better support for initrd/initramfs, with different
> compression support and sanity check.
> I would argue the check in Uboot is completely useless, kernel can do
> the same thing and do it better, while the check is only prevent valid
> compressed initramfs.
> (Also in x86 world, most distros have already swtiched to initramfs)
> Can we just skip that check?
> U-Boot mailing list
> U-Boot at lists.denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: OpenPGP digital signature
More information about the U-Boot