Thanks for the datapoint. I went all the way back to 2.3.40 and still
could not get it working. The problem turned out to be GRUB. For some
reason GRUB will not load initrd images for 2.3.x. Syslinux works fine.
I'll report this to the GRUB folks.
Thanks,
Jeff
On Fri, Mar 31, 2000 at 10:43:10PM +0200, Martin Josefsson wrote:
> On Fri, 31 Mar 2000, Jeff Noxon wrote:
>
> > I need to get an initial ramdisk working in a recent 2.3.5x or later
> > kernel, but they're borken. :) I don't know when the bug first appeared.
> >
> > In rd.c (rd_open), the following code causes an oops and hangs the boot:
> >
> > /*
> > * Immunize device against invalidate_buffers() and prune_icache().
> > */
> > if (rd_inode[DEVICE_NR(inode->i_rdev)] == NULL) {
> > if((rd_inode[DEVICE_NR(inode->i_rdev)] = igrab(inode)) != NULL)
> > atomic_inc(&rd_inode[DEVICE_NR(inode->i_rdev)]->i_bdev->bd_openers);
> > }
> >
> > In the third line, i_bdev is null. Commenting out the code does not fix
> > the problem. (Instead I get a kernel panic that VFS cannot mount root
> > on 01:00.) The kernel never seems to identify that an initrd exists in
> > the first place. I'm using GRUB 0.5.94 to load a cramdisk. It works
> > fine with 2.2.14. At the very least, 2.3.51 and onward are broken.
>
> I just wanted to say that I'm building a bootdisk for a router with kernel
> 2.3.99pre3, I use initrd and it works just fine. the file that I'm using
> as initrd is a gzipped minixfilsystem.
>
> But I get a lot of these messages when I mount my file with
> minixfilesystem via loopback and write to it.
>
> I also get these when the bootdisk boots.
>
> But the initrd doesn't go OOPS on me at all.
>
> /Martin
>
> --
> The three best things about going to school are June, July, and August.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Mar 31 2000 - 21:00:30 EST