On Tuesday 02 October 2007, Jason wrote: > I have the kernel loaded and running via serial/TFTP into an NSLU2. It > may not be configured correctly (duh), and the kernel command line might > not be correct (also, duh). I've tried so many variants of the two, I > can't see straight. I've also tried a gzip'd ramdisk, bzip2'd ramdisk, > and a cpio ramdisk. Nothing works. /sbin/init is in the ramdisk. > /dev/console and /dev/null are there also.
what's in the ramdisk is irrelevant here as your kernel is failing to load it up in the first place ... it could be filled with monkeys and you'd get the same error ;) what if you add rootfstype=ext2 and you dont gzip the ramdisk ? long run you should consider switching to initramfs ... it's a ton easier than dickin around with initrd's -mike
signature.asc
Description: This is a digitally signed message part.
