All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: new scsi hardware detection in 2.4.7(pre)
Date: Mon, 30 Jul 2001 15:31:17 +0200	[thread overview]
Message-ID: <20010730153117.A2142@suse.de> (raw)
In-Reply-To: <20010723171019.A18135@suse.de> <22072.995939994@kao2.melbourne.sgi.com>
In-Reply-To: <22072.995939994@kao2.melbourne.sgi.com>; from kaos@ocs.com.au on Tue, Jul 24, 2001 at 11:59:54AM +1000

On Tue, Jul 24, Keith Owens wrote:

> On Mon, 23 Jul 2001 17:10:19 +0200, 
> Olaf Hering <olh@suse.de> wrote:
> >I get this on non-scsi systems with scsi compiled into the kernel:
> >
> >SCSI subsystem driver Revision: 1.00
> >request_module[scsi_hostadapter]: Root fs not mounted
> >request_module[scsi_hostadapter]: Root fs not mounted
> >request_module[scsi_hostadapter]: Root fs not mounted
> 
> The SCSI midlayer is trying to load the SCSI host adapter, that is an
> unavoidable side effect of including SCSI support.  Because no adapter
> is found, kmod tries to automatically load a module that can find a
> host adapter.  The "Root fs not mounted" message occurs when you try to
> load any module before / is mounted.

Does that make any sense? I mean, there are some scsi drivers, none of
them found a valid device, why do we look for more drivers? It would
make sense if there are no low level device drivers in the kernel
binary.


Gruss Olaf

-- 
 $ man clone

BUGS
       Main feature not yet implemented...

  reply	other threads:[~2001-07-30 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-23 15:10 new scsi hardware detection in 2.4.7(pre) Olaf Hering
2001-07-24  1:59 ` Keith Owens
2001-07-30 13:31   ` Olaf Hering [this message]
2001-07-30 13:39     ` Keith Owens
2001-07-30 17:30       ` majordomo kernel

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=20010730153117.A2142@suse.de \
    --to=olh@suse.de \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.