linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "\"Andrey Borzenkov\" " <arvidjaar@mail.ru>
To: linux-hotplug-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Fw: [Cooker] usb audio detection problem
Date: Tue, 05 Aug 2003 12:21:02 +0400	[thread overview]
Message-ID: <E19jx42-000Eex-00.arvidjaar-mail-ru@f25.mail.ru> (raw)



> 
> 
> > After a week of fighting with my new M-Audio USB Quattro device I have solved 
> > a problem with our hardwared detection.
> > I used the standard alsa configuration lines in /etc/modules.conf, i.e.
> > alias sound-slot-0 snd-usb-audio
> > above snd-usb-audio snd-pcm-oss
> > but when restarting alsa, the OSS driver was loading first (module name 
> > 'audio'), and then the alsa driver was unable to access the PCM stream.  By 
> > adding 'audio' to /etc/hotplug/blacklist, everything worked fine.
> > Is there some way to fix this permanently?
> > Is everyone else with usb-based audio currently forced to use OSS when 
> > Mandrake's default should be alsa?
> 
> both audio and snd-usb-audio modules have exactly the same matching
> criteria (in your case) and "audio" appears first in /lib/modules/`uname -r`/modules.usbmap so it wins.
> 
> I guess so far the ony "official" way is to blacklist it.

If having two modules with the same matching ids is expected,
what is normal way to prefer one of them? The problem currently
is system-wide usbmap is consulted first so there is actually
no way to override it.

This is under 2.4.21.

TIA

-andrey

                 reply	other threads:[~2003-08-05  8:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E19jx42-000Eex-00.arvidjaar-mail-ru@f25.mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --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).