From: Pedro Lopez-Cabanillas <plcl@telefonica.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug loads USB audio before local audio
Date: Wed, 30 Apr 2003 19:02:35 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105172941515841@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105172715013227@msgid-missing>
On Wednesday 30 April 2003 20:24, Joshua Pollak wrote:
> Short of hacking the system's boot process up, is there a way to ensure
> that the emu10k1 sound card will always be connected to the primary
> /dev/mixer devices, while the USB ones will be on the secondary ones?
Another trick can be to include 'audio' in your '/etc/hotplug/blacklist' file.
Add only the word 'audio' without '.o' in an empty line. This will prevent
hotplug to load this module. You can do it later, by hand, with 'modprobe
audio'.
Regards,
Pedro
--
ALSA Library Bindings for Pascal
http://alsapas.alturl.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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 prev parent reply other threads:[~2003-04-30 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 18:24 Hotplug loads USB audio before local audio Joshua Pollak
2003-04-30 18:31 ` Greg KH
2003-04-30 18:32 ` Joshua Pollak
2003-04-30 18:33 ` Bill Nottingham
2003-04-30 18:46 ` Joshua Pollak
2003-04-30 19:02 ` Pedro Lopez-Cabanillas [this message]
2003-05-01 6:14 ` Christian Zoz
2003-05-01 15:32 ` Joshua Pollak
2003-05-01 15:38 ` David Brownell
2003-05-01 18:57 ` Pedro Lopez-Cabanillas
2003-05-02 5:06 ` Christian Zoz
2003-05-02 7:24 ` Oliver Neukum
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=marc-linux-hotplug-105172941515841@msgid-missing \
--to=plcl@telefonica.net \
--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).