Figured it out finally.
When you use RedBoot to create images loaded over the net, as well as
the partition length, it sets the "load size" for the partitions as
well, which do not (and cannot) get updated when new contents are
written in from linux. Specifically,
RedBoot> load -v -r -b 0x800000 -m http -h 192.168.1.1
/.../initrd.img-2.6.23-1-iop32x
RedBoot> fis create -l 0xd00000 -s 0xd00000 ramdisk
So the new, bigger initrd was only getting loaded into RAM as far as
the length of the old one.
For default installations where no half-witted redbooting has been
going on, the new kernels should work fine. Enjoy
M
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
