From: Sam Liddicott <sam@Liddicott.com>
To: linux-hotplug@vger.kernel.org
Subject: cdrom devices missing
Date: Mon, 03 Jan 2005 12:31:38 +0000 [thread overview]
Message-ID: <crbdo8$q5n$1@sea.gmane.org> (raw)
udev makes my hard disk nodes device and partition nodes OK, but does
not create my cdrom device nodes at all.
I have a debian testing/unstable install that is a de-mepis-ized
latest-MEPIS installation.
I have debian udev_0.050 build from source (apt-get -b source)
My cdrom is on hdc, I even tried adding to rules.d
KERNEL="hdc" SYMLINK="dvd cdrom dvdrecorder cdrecorder"
but no joy
If I make device nodes by hand then mplayer et al work fine.
I had similar problems with my sound card until I listed my sound card
driver explicitly in /etc/modules - is this the correct procedure for
all hardware support with udev? I expected hotplug/udev to "discover"
the soundcard hardware and do all the right tricks with it like it does
for removable device, perhaps I am wrong?
However as the kernel already recognizes my cdrom and manually making
the device nodes is enough for things to work I can't see that adding
anything to /etc/modules would work here.
Sam
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2005-01-03 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 12:31 Sam Liddicott [this message]
2005-01-03 12:49 ` cdrom devices missing Stefan Schweizer
2005-01-03 12:55 ` Kay Sievers
2005-01-03 16:49 ` Sam Liddicott
2005-01-03 17:23 ` Kay Sievers
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='crbdo8$q5n$1@sea.gmane.org' \
--to=sam@liddicott.com \
--cc=linux-hotplug@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).