From: Lee Revell <rlrevell@joe-job.com>
To: "Nambiar, Anil" <NambiarA@sharpsec.com>
Cc: "'alsa-devel@lists.sourceforge.net'" <alsa-devel@lists.sourceforge.net>
Subject: Re: Alsa-lib problem
Date: Tue, 09 Aug 2005 18:05:04 -0400 [thread overview]
Message-ID: <1123625105.19486.4.camel@mindpipe> (raw)
In-Reply-To: <6A09F73E2878E447BF6B87C43162C827021545A4@excwa1b2.sharpsec.com>
On Tue, 2005-08-09 at 17:57 -0400, Nambiar, Anil wrote:
> Hi,
>
> I am developing ALSA based sound driver for our arm based
> soc. The driver is built as part of the kernel rather than as a
> loadable module. If I run a simple wave player which has OSS based
> interface, it works fine. Even mplayer works fine in OSS emulation
> mode. But if I run any native alsa based player it gives error opening
> the device. For eg: running 'aplay -D default demo.wav" give the
> following error:
>
> ALSA lib pcm.c:2090:(snd_pcm_open_noupdate) Unknown PCM default
>
> aplay: main:533: audio open error: No such file or directory
It looks like alsa-lib is not finding the default PCM config for your
chip. Someone else developing a driver for ARM reported the same
problem.
Try stracing the aplay process, you will see alsa-lib trying to open the
various config files ~/.asoundrc, /etc/asound.conf, and (most
important) /usr/share/alsa/*, and compare the results to what you get
when you strace aplay on a known good driver like snd-intel8x0.
Lee
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-09 22:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 21:57 Alsa-lib problem Nambiar, Anil
2005-08-09 22:05 ` Lee Revell [this message]
2005-08-09 22:18 ` James Courtier-Dutton
2005-08-10 9:48 ` Takashi Iwai
2005-08-15 3:06 ` Compulab sound device Chow Raymond
2005-08-15 7:41 ` Clemens Ladisch
2005-08-15 8:39 ` Chow Raymond
2005-08-15 11:32 ` Clemens Ladisch
2005-08-16 7:04 ` Chow Raymond
2005-08-16 7:22 ` Clemens Ladisch
2005-08-16 12:58 ` Chow Raymond
2005-08-17 13:40 ` Clemens Ladisch
2005-08-19 12:47 ` Chow Raymond
2005-08-19 13:17 ` Clemens Ladisch
2005-08-19 13:24 ` Liam Girdwood
2005-08-19 13:51 ` Chow Raymond
2005-08-19 14:10 ` Liam Girdwood
2005-08-22 7:06 ` Chow Raymond
2005-08-23 3:57 ` Lee Revell
2005-08-23 9:13 ` Takashi Iwai
2005-08-23 9:49 ` Chow Raymond
2005-08-24 10:32 ` Chow Raymond
2005-08-24 12:04 ` Takashi Iwai
2005-08-25 1:45 ` Chow Raymond
2005-08-25 8:38 ` Clemens Ladisch
2005-08-25 8:52 ` Chow Raymond
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 22:47 Alsa-lib problem Nambiar, Anil
2005-08-10 0:44 Nambiar, Anil
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=1123625105.19486.4.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=NambiarA@sharpsec.com \
--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.