From: Mark Knecht <markknecht@attbi.com>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Takashi Iwai <tiwai@suse.de>,
martin-langer@gmx.de,
Alsa-Devel <alsa-devel@lists.sourceforge.net>,
swpatrick@earthlink.net
Subject: Re: alsasound init script (Re: possible problems with rc6 aplay )
Date: 16 Dec 2002 13:18:47 -0800 [thread overview]
Message-ID: <1040073528.1312.18.camel@Godzilla> (raw)
In-Reply-To: <20021216152035.CZFC3512.sccrgwc01.attbi.com@newmx1.fast.net>
On Mon, 2002-12-16 at 07:23, Paul Davis wrote:
> >> that reminds me. the last version of the alsasound script that i saw
> >> did something very dangerous. it seemed to try to install *every*
> >> snd-card module it could find. if you have a system with an ISA bus,
> >> this can prove fatal to the system - many ISA device probes will kill
> >> the machine if the device is not present.
> >
> >well, you can find that the alsasound script tries to load the modules
> >aliased as "snd-card-[0-9]", not the all snd-card-* modules.
> >remember that there is no module named as such. that means, if such a
> >module is found, it was certainly configured by some means.
>
> ah. sorry, i missed the -c on modprobe. i take it all back :(
>
> --p
I wonder if this could have anything to do with a different problem I'm
seeing. I have a HDSP 9652 and a MidiMan 2X2 interface. The HDSP is
installed by alsaconf. The 2X2 is installed usign Fernando's
instructions from the Planet.
When I do a cold boot, the HDSP is always recognized first, and then the
MidiMan comes up as card 2, at least by reading the numbers of the
devices in /dev/snd. However, if I reboot, many times the system makes
the 2X2 card 1 and the HDSP card 2, and that breaks a lot of this
software.
What would cause this to happen and how could I stop it?
I have found that everything seems to work fine if I remember to unplug
the 2X2 when the reboot begins, but sometimes I don't remember and have
to go through one more boot cycle.
Cheers,
Mark
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
next parent reply other threads:[~2002-12-16 21:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021216152035.CZFC3512.sccrgwc01.attbi.com@newmx1.fast.net>
2002-12-16 21:18 ` Mark Knecht [this message]
2002-12-17 2:51 ` alsasound init script (Re: possible problems with rc6 aplay ) Paul Davis
2002-12-17 3:46 ` Mark Knecht
2002-12-17 11:06 ` Takashi Iwai
2002-12-17 19:36 ` Fernando Pablo Lopez-Lezcano
2002-12-18 10:46 ` Takashi Iwai
2002-12-18 11:17 ` Takashi Iwai
2002-12-18 13:11 ` Mark Knecht
2002-12-20 15:10 ` Takashi Iwai
2002-12-20 16:10 ` Clemens Ladisch
[not found] <E18PTTN-0004YV-00@sc8-sf-list2.sourceforge.net>
2002-12-20 22:53 ` Pedro Lopez-Cabanillas
2002-12-23 13:44 ` Takashi Iwai
2002-12-23 17:18 ` Patrick Shirkey
2002-12-16 13:57 possible problems with rc6 aplay Takashi Iwai
2002-12-16 14:29 ` Paul Davis
2002-12-16 14:53 ` alsasound init script (Re: possible problems with rc6 aplay ) Takashi Iwai
2002-12-16 15:23 ` Paul Davis
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=1040073528.1312.18.camel@Godzilla \
--to=markknecht@attbi.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=martin-langer@gmx.de \
--cc=paul@linuxaudiosystems.com \
--cc=swpatrick@earthlink.net \
--cc=tiwai@suse.de \
/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