From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Tools to help install alsa.
Date: Tue, 07 Oct 2003 12:25:02 +0200 [thread overview]
Message-ID: <s5hd6d9mjk1.wl@alsa2.suse.de> (raw)
In-Reply-To: <3F81B0F2.1040600@superbug.demon.co.uk>
At Mon, 06 Oct 2003 19:14:10 +0100,
James Courtier-Dutton wrote:
>
> Hi,
>
> I have been helping a few people on #alsa on freenode.net.
> Some points to note: -
> 1) It seems that alsa does not work when compiled into the kernel, but
> does work as modules.
hmm, in the case of PCI cards, the built-in driver should work without
problems. in the case of ISA non-PnP cards, passing parameters is a
bit difficult, though.
> 2) For alsa to work in kernel 2.6, the first item in the OSS menu has to
> be set to M, otherwise module soundcore does not seem to exist. (This is
> unconfirmed, so might just be user error)
it must be ok without OSS.
> 3) It would be nice if there was a test tool.
> This test tool would test for: -
> a) See if the user has loaded the kernel modules, so that a "card"
> exists in /proc/asound.
> b) Test the mixer interface is functioning.
> c) Display alsa-driver, and alsa-lib version numbers.
> d) check access writes to /dev/snd/* are valid from the currently logged
> in user.
> e) check /etc/modules.conf contains all the correct alias statements, to
> ensure the sound modules will load up again after a reboot.
JFYI: in the future version of 2.6 (once Rusty's patchset is merged),
aliases can be removed from /etc/modprobe.conf, since there are
built-in aliases now.
> f) check /etc/modules.conf is not still trying to load OSS drivers.
> g) Make a simple test, by playing some white noise out of each speaker
> in turn, allowing for up to 6 speakers. Let the test go in a loop, so
> that the user can adjust mixer settings until they hear sound.
> h) Provide some test so that alsa-lib can detect if interrupts are
> actually reaching the sound card or not. Some bugs in ACPI might mean
> that interrupts are not forwarded correctly.
>
> After these tests, it could produce a nice simple message, telling the
> user what to do next to fix it.
>
> Cheers
> James
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2003-10-07 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 18:14 Tools to help install alsa James Courtier-Dutton
2003-10-06 18:23 ` Måns Rullgård
2003-10-07 10:25 ` Takashi Iwai [this message]
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=s5hd6d9mjk1.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=James@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.