I'm upgrading from 2.4.3 to 2.4.17 (rsync from mvista) on a Walnut-variant
board. The initrd seems to be getting corrupted. The kernel crashes during
the decompress or prints crc error or invalid compressed format
messages. I have allocated enough space by using the 'ramdisk=32000'
command
Since nobody with real knowledge of the problem has responded, I'll take a WAG.
This looks like a variation on a PPCBoot FAQ...
If I'm reading your numbers correctly, your linux kernel is loading from
0040 to 00A72890, but your initrd image is initially loaded at
00405200. If you do the
ramdisk image
Since nobody with real knowledge of the problem has responded, I'll take a
WAG.
This looks like a variation on a PPCBoot FAQ...
If I'm reading your numbers correctly, your linux kernel is loading from
0040 to 00A72890, but your initrd image is initially loaded at
00405200
On Thu, Jan 03, 2002 at 03:21:18PM -0800, Brian Kuschak wrote:
Changing the mktree.c file to put the entry point at 0x40 instead of
0x50 fixes the problem for me.
mktree takes an argument (last one, iirc) of an optional entry point.
The IBM Spruce platform takes advantage of this.
--
