From: XC <x.chantry@wanadoo.fr>
To: linux-hotplug@vger.kernel.org
Subject: /dev/sound/dsp is missing
Date: Sat, 16 Oct 2004 15:15:53 +0000 [thread overview]
Message-ID: <41713B29.7090300@wanadoo.fr> (raw)
[wait_for_sysfs] either wait_for_sysfs (udev 039) needs an update
to handle the device '/class/sound' properly (4) or the
sysfs-support of your device's driver needs to be fixed
I'm using alsa with oss emulation, and I lost my /dev/sound/dsp device
when I switched to 039.
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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:[~2004-10-16 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 15:15 XC [this message]
2004-10-16 16:43 ` /dev/sound/dsp is missing 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=41713B29.7090300@wanadoo.fr \
--to=x.chantry@wanadoo.fr \
--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).