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

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]

Hi all,

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).

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).

Obviously the quick and dirty fix is to hook-up the midisport once I've
logged in and if the device was already hooked-up simply restart alsa
once the midisport was removed (which I am doing), but that seems like a
real hacky solution to this issue and does not address the root of the
problem.

Any help is greatly appreciated! Sincerely,


Ivica Ico Bukvic, composer, multimedia sculptor,
programmer, webmaster & computer consultant 
http://meowing.ccm.uc.edu/~ico 
============================ 
"To be or not to be" - Shakespeare
"To be is to do"     - Socrates
"To do is to be"     - Sartre
"Do be do be do"     - Sinatra
"2b || ! 2b"         - ?
"I am"               - God




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

RE: [Alsa-user] 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

[Mark Knecht]

Ivica,
   Welcome to _MY_ nightmare!!! I've been dealing with this for months!!

   Actually, your nightmare is a little different, but in my version, just
before the Frankenstein monster shows up, my HDSP 9652 won't initialize, the
system saying it doesn't have enough memory. Then, just as the monster
raises its arms to grab me, I do a warm boot and the monster goes away. Alsa
and Jack work wonderfully and the sky is blue...

   Oh yes, and sometimes my 1394 drives cannot be used either, until after
the same warm boot.

Mark

> -----Original Message-----
> From: alsa-user-admin@lists.sourceforge.net
> [mailto:alsa-user-admin@lists.sourceforge.net]On Behalf Of Ivica Bukvic
> Sent: Tuesday, February 25, 2003 3:26 PM
> To: alsa-devel@lists.sourceforge.net; alsa-user@lists.sourceforge.net
> Subject: [Alsa-user] 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
>
>
> Hi all,
>
> 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).
>
> 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).
>
> Obviously the quick and dirty fix is to hook-up the midisport once I've
> logged in and if the device was already hooked-up simply restart alsa
> once the midisport was removed (which I am doing), but that seems like a
> real hacky solution to this issue and does not address the root of the
> problem.
>
> Any help is greatly appreciated! Sincerely,
>
>
> Ivica Ico Bukvic, composer, multimedia sculptor,
> programmer, webmaster & computer consultant
> http://meowing.ccm.uc.edu/~ico
> ============================
> "To be or not to be" - Shakespeare
> "To be is to do"     - Socrates
> "To do is to be"     - Sartre
> "Do be do be do"     - Sinatra
> "2b || ! 2b"         - ?
> "I am"               - God
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Alsa-user mailing list
> Alsa-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-user
>
>




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: 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

[Fernando Pablo Lopez-Lezcano]

> 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

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

[Ivica Bukvic]

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