On Mon, 21 Aug 2000, you wrote:
> >
> > and it worked fine :-/ I did have to add ext2 support because
> > my dinky test initrd is ext2, but that's all that's different.
> > Hmm.. maybe minix fs is busted? Can you try an ext2 initrd?
>
> minix fs has been busted in several recent kernels. It's pretty much
> unmaintained these days.
>
> -hpa
Okay, let's take that out of the equation. I just rebuilt a kernel using e2fs
and then recreated initrd.gz as a e2fs filesystem.
Same result. (Might just leave the e2fs, as it is only 199 bytes larger then
the minix one, once compressed)
So, to reiterate the present state:
Using syslinux 1.48, on a VFAT floppy (1743k)
kernel bzimage
append= console=tty0 initrd=initrd.gz root=/dev/ram0
(no ./linuxrc)
simple file system in minix or e2fs on a 4096 filesystem, compressed using
gzip -9 initrd
2.2 kernel works ---- 2.4 kernel fails
Both have VFAT, [minix|e2fs], ramdisk, initrd support built in
2.4 fails with a device not present..
Mike, you have a working version.. let's see if we can move towards each
other and see where it breaks. Can you set up syslinux 1.48 on a VFAT
(1743k) floppy, and then copy your initrd.gz and kernel onto it to see if
yours still works? (Make sure to use a bzImage)
BTW, 32 mG ram over here in the test machine. Pentium 100 with kernel
compiled as if a 486
--------------------------------------------------------
Michael Peddemors - Senior Consultant
Unix Administration - WebSite Hosting
Network Services - Programming
Wizard Internet Services http://www.wizard.ca
Linux Support Specialist - http://www.linuxmagic.com
--------------------------------------------------------
(604) 589-0037 Beautiful British Columbia, Canada
--------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Aug 23 2000 - 21:00:08 EST