Did you change the settings.s under 1/ or in the root of the unpack? I think there is a mention in the FAQ that it is the one under 1/ to fix.
-Tom On Tue, 22 Jul 103 [EMAIL PROTECTED] wrote: > Date: Tue, 22 Jul 103 18:05:23 -0400 (EDT) > From: [EMAIL PROTECTED] > To: Tom Oehser <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: [tomsrtbt] can pivot_root work? > > > Yup. Changed the kernel name in settings.s and changed line > 111 in buildit.s to read 'image=$MP/$KERNEL'. I think that should be > fine. I suppose I could explicitly say image=$MP/bzImage but I doubt > thats it. > -Jason > > > > > > > > Did you make the edit at line 111 of buildit.s and in settings.s > > to let the boot process know it is dealing with bzImage and a gzip > > filesystem, not bz2bzImage and a bzip2 filesystem? -Tom > > > > On Tue, 22 Jul 2003, Jason Verch wrote: > > > > > Date: Tue, 22 Jul 2003 15:00:20 -0400 (EDT) > > > From: Jason Verch <[EMAIL PROTECTED]> > > > To: [EMAIL PROTECTED] > > > Cc: [EMAIL PROTECTED] > > > Subject: Re: [tomsrtbt] can pivot_root work? > > > > > > I got a floppy built with a 2.4 kernel built. I struggled with > > > 2.4.20 for a while and just couldn't get it small enough, so > > > I switched to 2.4.9 and managed to get 850k or so kernel. I > > > also replaced busybox with a version that has pivot_root > > > compiled in. buildit.s and install.s worked fine, boots up ok > > > for a while, but then I get the same kernel panic. The last > > > few things I see are... > > > > > > RAMDISK: Compressed image found at block 946 > > > cramfs: wrong magic > > > FAT: bogus logical sector size 287 > > > Kernel panic: VFS: Unable to mount root fs on 01:00 > > > > > > Any ideas? Could the ramdisk somehow not be getting created > > > correctly? That would seem to be what the errors are implying, > > > but I'm not sure what I might have done wrong. Kernel has minix > > > and ramdisk support compiled in. > > > > > > Thanks, > > > -Jason > > > > > > > > > > > > > >
