From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: alsa questions?
Date: Fri, 18 May 2007 23:08:32 -0500 [thread overview]
Message-ID: <000f01c799cb$5d39ac20$ab00a8c0@tenstac> (raw)
In-Reply-To: <Pine.LNX.4.64.0705191217540.2730@janeway.homelinux.org>
The arecord error is meaningless since the alsa driver for the
card failed to load. It may be the case that udev is loading
driver modules in an order that is causing problems. It may
be useful to try booting without udev. Also in a situation like
this some manual loading of modules one by one might shed
some light on the situation.
lsmod will show loaded modules
insmod will install a module
rmmod will remove a module
modprobe is another way to load a module
You could try using rmmod to remove all audio related
drivers then start loading them one by one watching for
any error messages on load, something like
modprobe snd
modprobe soundcore
modprobe snd-ens1371
modprobe snd-emu10k1
modprobe snd-mixer-oss
modeprobe snd-seq-oss
modprobe snd-pcm-oss
Note there may be options on the modules for the card drivers
(ensoniq and sblive) that can tweak their configuration on load,
see the alsa pages for details. Also this may be useful
http://alsa.opensrc.org/MultipleCards
google alsa multiple sound cards
will reveal tons of more info including others' dual sound card
problems and solutions
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Amanda Tink
` Doug Sutherland [this message]
` Amanda Tink
` Doug Sutherland
` Amanda Tink
` Gene Collins
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='000f01c799cb$5d39ac20$ab00a8c0@tenstac' \
--to=doug@proficio.ca \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).