On Fri, 2014-12-19 at 13:38 +0800, Chen Baozi wrote:
> I’ve only booted the system by ‘bootz’ without initrd. If I load the raw
> initrd image (rather than ‘uInitrd”), when I use bootz, it would output:
>
> Wrong Ramdisk Image Format
> Ramdisk image is corrupt or invalid
>
> This is the reason that I’m still using bootm when initrd is needed.
bootz requires you to give the filesize for the raw initrd. e.g.
load $kernel_addr_r kernel
load $fdt_addr_r
load $ramdisk_addr_r
bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}
The ":${filesize}" is what I mean, it is implicitly set by load (and
similar commands) which is why initrd is loaded last in the above, so it
doesn't get clobbered.
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
