From: Keith Owens <kaos@ocs.com.au>
To: Mike Castle <dalgoda@ix.netcom.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: modprobe problem with block-major-11
Date: Thu, 25 Oct 2001 15:51:36 +1000 [thread overview]
Message-ID: <24102.1003989096@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 24 Oct 2001 21:53:28 MST." <20011024215328.A195@thune.mrc-home.com>
On Wed, 24 Oct 2001 21:53:28 -0700,
Mike Castle <dalgoda@ix.netcom.com> wrote:
>Currently my modules.conf has:
>options ide-cd ignore=hdc # tell the ide-cd module to ignore h
>alias block-major-11 sr_mod # load sr_mod upon access of scd0
>pre-install sg modprobe ide-scsi # load ide-scsi before sg
>pre-install sr_mod modprobe ide-scsi # load ide-scsi before sr_mod
>pre-install ide-scsi modprobe ide-cd # load ide-cd before ide-scsi
Is that the complete modules.conf? The messages below imply that you
have other options and/or commands in there.
>Now, if I try something like ``head /dev/scd0'' I see the following in
>dmesg:
>SCSI subsystem driver Revision: 1.00
>Uniform CD-ROM driver unloaded
>
>And the following in /var/log/ksymoops:
>20011024 214049 start /sbin/modprobe -s -k -- block-major-11 safemode=1
>20011024 214050 probe ended
Check syslog for any error messages. The only unusual thing is that
modprobe is running in safe mode (user supplied input data) which
suppresses some command expansions. Post your entire modules.conf
exactly as is, i.e. read the file into your mail, do not cut and paste
it.
next prev parent reply other threads:[~2001-10-25 5:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 4:53 modprobe problem with block-major-11 Mike Castle
2001-10-25 5:51 ` Keith Owens [this message]
2001-10-25 7:52 ` Mike Castle
2001-10-25 13:03 ` Keith Owens
2001-10-25 16:39 ` Mike Castle
2001-10-25 18:20 ` Mike Castle
2001-10-25 18:51 ` Mike Castle
2001-10-25 8:09 ` Mike Castle
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=24102.1003989096@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=dalgoda@ix.netcom.com \
--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.