Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@attbi.com>
To: Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Automounting my 1394 drives causes Alsa to not load...
Date: 01 Feb 2003 16:40:11 -0800	[thread overview]
Message-ID: <1044146411.1414.22.camel@Godzilla> (raw)
In-Reply-To: <1044131509.9480.23.camel@cmn37.Stanford.EDU>

On Sat, 2003-02-01 at 12:31, Fernando Pablo Lopez-Lezcano wrote:
> > 1) Old problem - if my MidiSport 2x2 is plugged in when I cold boot,
> > then Alsa gets loaded when the MidiSport is found. When I get to the
> > part of the boot process where Alsa is supposed to get started, I get a
> > 'Failed' message, telling me Alsa is already running. Even this is OK,
> > but then later when Linux attempt to load the HDSP 9652 drivers, they
> > fail one out of two times saying they cannot allocate memory.
> 
> I think the solution to this one is to "blacklist" the alsa driver so
> that hotplug does not load it while the system is starting up. To do
> that just add a line with "snd-usb-audio" to the end of 
>   /etc/hotplug/blacklist
> You probably already have "audio" and "usb-midi" there (the oss kernel
> modules that deal with usb audio and midi). 
> 
Fernando,
   Thanks! Early indications are that this helps. I'll keep an eye on it
and see how it goes.

Cheers,
Mark



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

      reply	other threads:[~2003-02-02  0:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-01 19:39 Automounting my 1394 drives causes Alsa to not load Mark Knecht
2003-02-01 20:31 ` Fernando Pablo Lopez-Lezcano
2003-02-02  0:40   ` Mark Knecht [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=1044146411.1414.22.camel@Godzilla \
    --to=markknecht@attbi.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=nando@ccrma.Stanford.EDU \
    /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