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

Forgot to include my modules.conf, so here it is:

#load hdsp mem before everything else
options snd-hammerfall-mem enable=1
options snd-hdsp line_outs_monitor=1

alias net-pf-4 ipx
alias autofs autofs4
probeall scsi_hostadapter ide-scsi
alias eth0 3c59x
#alias sound-slot-0 i810_audio
alias ieee1394-controller ohci1394
alias /dev/nvidia*   NVdriver

# ALSA portion
alias char-major-116 snd
alias char-major-14 soundcore
alias snd-card-0 snd-intel8x0
alias snd-card-1 snd-hdsp
alias snd-card-2 snd-usb-midi
options snd major=116 cards_limit=4 device_mode=0666 device_gid=0
device_uid=0
options snd-usb-midi vid=0x763 pid=0x1001 index=1

# OSS/Free portion
# CS4205
alias sound-slot-0 snd-card-0
alias sound-service-0-0 snd-mixer-oss
#alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
#alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss

#HDSP
alias sound-slot-1 snd-card-1
alias sound-service-1-0 snd-mixer-oss
alias sound-service-1-1 snd-seq-oss
alias sound-service-1-3 snd-pcm-oss
alias sound-service-1-8 snd-seq-oss
alias sound-service-1-12 snd-pcm-oss

#MIDISPORT
alias sound-service-2-1 snd-seq-oss
alias sound-service-2-8 snd-seq-oss

probeall usb-interface usb-uhci
#thought if I did usb-interface last that it would be superseded by
#the alsa, but that did not work



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