public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Raphael Schmid <raphael.schmid@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems with devfs (?)
Date: Fri, 05 Jan 2001 22:44:15 -0500	[thread overview]
Message-ID: <3A56948F.D4744CCF@torque.net> (raw)

Raphael wrote:

> I'm using ROCK Linux, which is built with devfs, originally Kernel
> 2.4.0-test9. This problem occurs, when I want to boot some Kernel after
> 2.4.0-test9, whereas building and installing the Kernel never is a problem.
>
> I enabled devfs support as well as the mounting of devfs at bootup in the
> configuration, just as it is with my "default"Kernel, next, I played around
> with lilo.conf (under normal circumstances a make bzlilo without any
> playing-around should do it, shouldn't it?)
> Then, as this also did show no success I tried passing root=/.....
> devfs=mount (<= don't nail me on this one, but I'm sure I did it the right
> way) at the LILO boot prompt.
> Whole story. Point. That's all. When trying to mount the root he hangs with
> "Kernel Panic: I have no root and I want to scream." Poor Kernel.
> Hope this helps anyone except me in any way (or perhaps I'm just too
> stupid).

I've been using kernels with devfs right through the test
series and now with lk 2.4.0 . The only hiccup was
when I upgraded to glibc 2.2 [RH 7.0 upgrade]. devfsd
seg faulted during bootup and I got a similar message
(because the kernel couldn't find /dev/sda3).

Don't know why but this line in /etc/devfsd.conf caused
devfsd to barf:
LOOKUP      ^cdrom$      CFUNCTION      GLOBAL    
       symlink ${mntpnt}/cdroms/cdrom0 $devpath

This line is almost straight out of Richard's doco.

You could try and identify your disk to lilo explicitly.
For example if it is normally at /dev/hda3 then try
something like this at the lilo prompt:
  linux root=/dev/ide/host0/bus0/target0/lun0/part3

If you can find the root partition that way, it will
probably fail later in the boot. To poke around with 
a statically linked shell trying adding to the above 
lilo prompt:
            init=/sbin/sash

Taking another tack, you could hope your root fs has a
normally populated /dev directory and try "devfs=nomount"
at the lilo prompt.

Doug Gilbert

-
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/

             reply	other threads:[~2001-01-06  4:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-06  3:44 Douglas Gilbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-06  1:58 Problems with devfs (?) Raphael Schmid

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A56948F.D4744CCF@torque.net \
    --to=dougg@torque.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raphael.schmid@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox