In the last mail Russell King - ARM Linux Admin said:
> Nicholas Clark writes:
> > If I make zImage then the bootloader says something like "invalid
> > compressed data" (err=1) and then halts the system.
>
> Hmm, sounds like the boot loader is not mapping the kernel correctly.
>
> > If I try vmlinux (is that the uncompressed kernel, or am I daft here)
> > it just locks up.
>
> This is the expected behaviour.
:-)
I've been told that I need to make Image so I did.
> > I've looked at the top of the zImage file and the first 4 bytes differ
> > between 2.2.1 and 2.0.35 but are the same between the 3 2.0.35 kernels
> > I have - has the format changed?
>
> Ever so slightly, but I wasn't aware that old loaders couldn't load it.
>
> > I tried downloading the bootladoer from the ARMlinux ftp site, but
> > it's dated 1997 so I don't think that'll help me.
>
> There are later - see /pub/armlinux/testing
Got one dated 21 Feb 1999 (IIRC)
using zImage
bootloader asks about arguments to kernel (as expected)
error about "invalid compressed data" (as above)
using Image as my kernel:
bootloader asks about arguments to kernel
system locks up after I press return (no text messages as linux starts)
I've tried rebuilding with my a.out-> elf cross compiler instead of my
elf native compiler, but no change to the above.
My zImage is 540000 ish bytes long, which Russell thinks is a bit short.
I did try answering M to as many configuration questions as I could.
I'm pretty much out of inspiration as to what to do next.
Nick
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
