From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Ivica Bukvic" 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 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <000001c2dd49$ac11e440$aa1f830a@ICO> References: <1046224546.31802.101.camel@cmn37.Stanford.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1046224546.31802.101.camel@cmn37.Stanford.EDU> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: 'Fernando Pablo Lopez-Lezcano' Cc: alsa-devel@lists.sourceforge.net, alsa-user@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org 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