All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Norris <haphazard@kc.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1: some modules refuse to autoload
Date: Wed, 23 Jul 2003 20:16:51 -0500	[thread overview]
Message-ID: <20030724011651.GA2435@glitch.localdomain> (raw)
In-Reply-To: <bfmsu5$l2k$1@gatekeeper.tmr.com>

On Wed, Jul 23, 2003 at 08:58:45PM +0000, bill davidsen wrote:
> Is hdd set to anything special? And is hdc set to cdrom? If not, try
> an explicit "hdc=cdrom" on the boot line. I have had to do this on
> several systems, in spite of dmesg telling me the kernel knows that
> it's a CD.

Thanx for the suggestion, but it unfortunately doesn't appear to have
made any difference. :-( The full kernel command-line was
"acpismp=force hdc=cdrom hdd=cdrom" (hdc is a DVD-ROM, and hdd is a
CD-RW).

   # mount /cdrom
   mount: /dev/hdc is not a valid block device
   # grep ide /proc/modules
   # mount -t iso9660 /dev/hdc /cdrom
   mount: /dev/hdc is not a valid block device
   # modprobe ide-cd
   end_request: I/O error, dev hdc, sector 0
   hdc: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
   Uniform CD-ROM driver Revision: 3.12
   end_request: I/O error, dev hdd, sector 0
   hdd: ATAPI 48X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
   # mount -t iso9660 /dev/hdc /cdrom
   mount: block device /dev/hdc is write-protected, mounting read-only
   ISO 9660 Extensions: Microsoft Joliet Level 3
   ISO 9660 Extensions: RRIP_1991A

I can't find any messages under /var/log or dmesg to indicate that a
module load was attempted for block-major-22 (or anything else, for
that matter).

I appreciate the suggestion, tho!

      reply	other threads:[~2003-07-24  1:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17 21:51 2.6.0-test1: some modules refuse to autoload Greg Norris
2003-07-23 20:58 ` bill davidsen
2003-07-24  1:16   ` Greg Norris [this message]

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=20030724011651.GA2435@glitch.localdomain \
    --to=haphazard@kc.rr.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.