From: Kristof Vansant <de_lupus@pandora.be>
To: linux-hotplug@vger.kernel.org
Subject: order of pci detection gives problem with sounddevices and
Date: Thu, 25 Nov 2004 02:46:30 +0000 [thread overview]
Message-ID: <1101350790.8381.12.camel@localhost.localdomain> (raw)
No sound because a not primary sound device is loaded and gets
device /dev/dsp1
Quotes from the bug reports:
Examples:
1) When my logitech orbit/sphere webcam is plugged on reboot, the
primary audio device is the USB Mixer, with only a microphone. That
leave me with no audio output.
Should the modules be loaded in a specific order? The webcam being one of the lasts.
2) Same error happens when bttv is detected before the sound card.
Solution?:
So, PCI ordering seems annoying. :-) Possibly an easier one: deprioritising USB
devices behind PCI devices. I had the same issue occur with my webcam USB
capture device.
Could hotplug or udev solve this problem or should this issue be resolved on a higher level??
related bug reports:
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id\x106748
https://bugzilla.ubuntu.com/show_bug.cgi?id\x1293
--
lupusBE (Kristof Vansant Belgium)
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
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-11-25 2:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 2:46 Kristof Vansant [this message]
2004-11-30 23:17 ` order of pci detection gives problem with sounddevices and applications Greg KH
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=1101350790.8381.12.camel@localhost.localdomain \
--to=de_lupus@pandora.be \
--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 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.