Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: Mark Knecht <markknecht@attbi.com>,
	martin-langer@gmx.de,
	Alsa-Devel <alsa-devel@lists.sourceforge.net>,
	swpatrick@earthlink.net
Subject: alsasound init script (Re: possible problems with rc6 aplay )
Date: Mon, 16 Dec 2002 15:53:14 +0100	[thread overview]
Message-ID: <s5h1y4it3qd.wl@alsa2.suse.de> (raw)
In-Reply-To: <E18NwBf-0003qc-00@sc8-sf-list1.sourceforge.net>

At Mon, 16 Dec 2002 09:29:05 -0500,
Paul Davis wrote:
> 
> >the standard alsasound init script can call a card-dependent script
> 
> 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.


ciao,

Takashi


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

  reply	other threads:[~2002-12-16 14:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-15 21:59 possible problems with rc6 aplay patrick reardon
2002-12-15 22:15 ` Mark Knecht
2002-12-16  3:13 ` Paul Davis
2002-12-16  4:38   ` Mark Knecht
2002-12-16 10:17     ` Martin Langer
2002-12-16 12:04       ` Mark Knecht
2002-12-16 13:49         ` Paul Davis
2002-12-16 13:57           ` Takashi Iwai
2002-12-16 14:29             ` Paul Davis
2002-12-16 14:53               ` Takashi Iwai [this message]
2002-12-16 15:23                 ` alsasound init script (Re: possible problems with rc6 aplay ) Paul Davis
2002-12-16 14:36         ` possible problems with rc6 aplay Martin Langer
2002-12-16 14:51           ` Paul Davis
     [not found]           ` <20021216144807.8950gmx1@mx005-rz3.gmx.net>
2002-12-17 17:54             ` clock mode problem [was: possible problems with rc6 aplay] Martin Langer
     [not found] <20021216152035.CZFC3512.sccrgwc01.attbi.com@newmx1.fast.net>
2002-12-16 21:18 ` alsasound init script (Re: possible problems with rc6 aplay ) Mark Knecht
2002-12-17  2:51   ` 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

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=s5h1y4it3qd.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=markknecht@attbi.com \
    --cc=martin-langer@gmx.de \
    --cc=paul@linuxaudiosystems.com \
    --cc=swpatrick@earthlink.net \
    /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