Re: kernel again
Quoting Gary Turner <kk5st@swbell.net>:
> On Wed, 13 Feb 2002 14:33:37 -0500, Bob Thibodeau wrote:
>
> >
> >I know this has been coming up, but the solutions I've seen offered
> >haven't worked for me.
> >
> >I'm trying to upgrade to 2.4.17 and getting the "vfs: cannot mount
> >root" error.
> >
> >I've tried with and without initrd support. The only difference being
> >whether the kernel can't mount root at 1:x or 3:x
> >
> >I've tried with and without make-kpg
> >
> >my 2.2 kernel still boots -- my lilo.conf is correct
> >
> >What have I missed?
>
> I recently had the same problem. Here is the solution for mine, and
> maybe yours, too. Thanks to Thomas Shemanske.
I did find that in the archives. Moving the initrd line into the
2.4.17 subsection was how I got my 2.2 booting again instead of using a
floppy. When I get back home and get some sleep, I'm going to try building
an initrd.img by hand. When I went into the mkinitrd script and removed the
'>/dev/null', I got an error message ln: file not found when it was trying
to link sh to ash (which is on my system).
As a side note, in my research, most of the kernel compile errors reported on
debian systems lately have been this exact problem. On comp.os.linux.misc I
didn't find anyone complaining about this particular error. Is there something
debian-specific going on?
Why do we suddenly have to use initrd, anyway?
Thanks,
Bob
> >To: Gary Turner <kk5st@swbell.net>
> >Subject: Re: kernel panic---operator panic too
> >From: "Thomas R. Shemanske" <trs@hecke.dartmouth.edu>
> >Date: Thu, 07 Feb 2002 14:47:14 -0500
> >
> >I think your initrd line is misplaced. Since some kernels do not need
>
> >the line, you probably want it with each lilo entry
> >
Reply to: