linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Norris <haphazard@kc.rr.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: debian-user <debian-user@lists.debian.org>
Subject: 2.6.0-test1: some modules refuse to autoload
Date: Thu, 17 Jul 2003 16:51:39 -0500	[thread overview]
Message-ID: <20030717215139.GA19877@glitch.localdomain> (raw)

My apologies if this is a repeat... I originally sent it yesterday
evening, and haven't seen any sign of it on the list.

---

I'm starting to test out the 2.6.0-test1 kernel, and for the most part
everything is going smoothly.  There is one problem that has me
stumped, however... I can't seem to get module auto-loading to work for
the cdrom.  None of the other modules seem to have any trouble.

I'm currently running Debian sid, with module-init-tools 0.9.13-pre.
I've defined the alias "block-major-22 ide-cd", and verified that both
"modprobe -nv block-major-22" and "modprobe -nv ide-cd" give the
expected results.  When I try to mount a CD, however, I get the message
"/dev/hdc not a valid block device".  Browsing the system logfiles, I
don't see any indication that a module load was even attempted.
Everything works fine if I load the ide-cd module manually first.

I browsed the list archives and did some googling, but didn't find
anything which sounded similar.  Any idea what's wrong?

Thanx!

             reply	other threads:[~2003-07-17 21:39 UTC|newest]

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

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=20030717215139.GA19877@glitch.localdomain \
    --to=haphazard@kc.rr.com \
    --cc=debian-user@lists.debian.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).