From: "Ivica Bukvic" <ico@fuse.net>
To: 'Fernando Pablo Lopez-Lezcano' <nando@ccrma.Stanford.EDU>
Cc: alsa-devel@lists.sourceforge.net, alsa-user@lists.sourceforge.net
Subject: RE: Midisport 2x2 spawns before Alsa, taking thedevice0 slot event though modules.conf puts snd-usb-midi as 3rd device ->result potential hardlocks when opening dsp
Date: Tue, 25 Feb 2003 22:46:40 -0500 [thread overview]
Message-ID: <000001c2dd49$ac11e440$aa1f830a@ICO> (raw)
In-Reply-To: <1046224546.31802.101.camel@cmn37.Stanford.EDU>
Thank you very much for your assistance!
Ico
> -----Original Message-----
> From: Fernando Pablo Lopez-Lezcano [mailto:nando@ccrma.Stanford.EDU]
> Sent: Tuesday, February 25, 2003 8:56 PM
> To: Ivica Bukvic
> Cc: alsa-devel@lists.sourceforge.net; alsa-user@lists.sourceforge.net
> Subject: Re: [Alsa-devel] Midisport 2x2 spawns before Alsa, taking
> thedevice0 slot event though modules.conf puts snd-usb-midi as 3rd
device
> ->result potential hardlocks when opening dsp
>
> > I was just wondering how can I force snd-usb-midi to assume device 2
> > slot, rather than the default 0 when spawning, since at boot time on
my
> > machine USB gets initialized before alsa and therefore if I have
> > Midisport 2x2 hooked up, it ends up being my default /dev/dsp device
> > (which actually does not exist) and that makes apps like pd hardlock
my
> > machine if trying to access them.
> >
> > So my question is twofold:
> >
> > 1) Is there anything I can configure about my boot process, where
Alsa
> > gets initialized before USB (I am assuming not, since Alsa does not
> > start until someone logs in, please correct me if I am wrong).
>
> Alsa is started (in the configurations I've seen) as a service and
that
> happens at boot time if the alsasound service is started (how that is
> configured depends on the distro - redhat uses the chkconfig program).
> If sound is only loaded when you are logging in then the alsasound
> script is not being executed on startup.
>
> You could blacklist the usb audio related modules so that they are
> started latter in the boot process by the alsasound script (just add
> usb-midi, audio and snd-usb-audio to /etc/hotplug/blacklist).
>
> > 2) Is there anything I can specify in my modules.conf or elsewhere
in
> > order to force the device to be used as snd-card-2 and not
snd-card-0 (1
> > I would like to reserve for hdsp).
>
> alias snd-card-1 snd-usb-audio
> alias sound-slot-1 snd-card-1
>
> and then...
> options snd-usb-audio index=1
>
> this assumes "cards_limit=2" in "options snd"
> -- Fernando
>
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
prev parent reply other threads:[~2003-02-26 3:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 23:25 Midisport 2x2 spawns before Alsa, taking the device0 slot event though modules.conf puts snd-usb-midi as 3rd device -> result potential hardlocks when opening dsp Ivica Bukvic
2003-02-25 23:56 ` [Alsa-user] " Mark Knecht
2003-02-26 1:55 ` Fernando Pablo Lopez-Lezcano
2003-02-26 3:46 ` Ivica Bukvic [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='000001c2dd49$ac11e440$aa1f830a@ICO' \
--to=ico@fuse.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@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 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.