From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: order of pci detection gives problem with sounddevices and applications
Date: Tue, 30 Nov 2004 23:17:04 +0000 [thread overview]
Message-ID: <20041130231704.GA26424@kroah.com> (raw)
In-Reply-To: <1101350790.8381.12.camel@localhost.localdomain>
On Thu, Nov 25, 2004 at 03:46:30AM +0100, Kristof Vansant wrote:
> 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??
Yes udev can solve this. Make udev only create the /dev/dsp1 (or
whatever you want) for your pci sound card, and /dev/dsbfoo for the USB
device.
Good luck,
greg k-h
-------------------------------------------------------
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
prev parent reply other threads:[~2004-11-30 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 2:46 order of pci detection gives problem with sounddevices and Kristof Vansant
2004-11-30 23:17 ` Greg KH [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=20041130231704.GA26424@kroah.com \
--to=greg@kroah.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 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.