alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Zoltan Devai" <zdevai@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: [RFC] [PATCH 0/2] ASoC sound support forSMDK2440boards
Date: Wed, 30 May 2007 17:30:18 +0200	[thread overview]
Message-ID: <5b7270f40705300830g7aef9faajc0b9e82d6d983d@mail.gmail.com> (raw)
In-Reply-To: <AC2729D6E3A3314A922E4E0FBE513F65D6BE87@MAIL.eldorado.org.br>

2007/5/29, Jose Henrique Spahn Torres <jose.torres@eldorado.org.br>:
> I used speaker-test as indicated above and the result is:
>
> pendrive $ ./speaker-test -r 44100
>
> speaker-test 1.0.11
>
> Playback device is default
> Stream parameters are 44100Hz, S16_LE, 1 channels
> Using 16 octaves of pink noise
> ALSA lib pcm.c:2146:(snd_pcm_open_noupdate) Unknown PCM default
> Playback open error: -2,No such file or directory
> ALSA lib pcm.c:2146:(snd_pcm_open_noupdate) Unknown PCM default
> Playback open error: -2,No such file or directory
> ALSA lib pcm.c:2146:(snd_pcm_open_noupdate) Unknown PCM default
> Playback open error: -2,No such file or directory
> ALSA lib pcm.c:2146:(snd_pcm_open_noupdate) Unknown PCM default
> Playback open error: -2,No such file or directory
> ALSA lib pcm.c:2146:(snd_pcm_open_noupdate) Unknown PCM default
> Playback open error: -2,No such file or directory
>
> I have also tried:
>
> /pendrive $ ./aplay -f cd 01-jack_johnson-times_like_these-rns.wav
> ALSA lib pcm.c:2146:(snd_pcm_open_noupdate) Unknown PCM default
> aplay: main:547: audio open error: No such file or directory
> /pendrive $
>
> so I don't know what is happening here.
> Does anyone have any idea?

You seem to have two problems:
1. Using OSS applications which try to set the sample rate to 8000Hz,
which is not supported by the hardware
2. A non-working ALSA installation, with some alsa-lib or device file
misconfiguration

Try to fix both...

  reply	other threads:[~2007-05-30 15:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24 14:28 [RFC] [PATCH 0/2] ASoC sound support for SMDK2440 boards Zoltan Devai
     [not found] ` <AC2729D6E3A3314A922E4E0FBE513F65D1FD65@MAIL.eldorado.org.br>
2007-05-24 21:45   ` [RFC] [PATCH 0/2] ASoC sound support for SMDK2440boards Zoltan Devai
2007-05-25  9:51     ` Liam Girdwood
2007-05-25 10:52       ` Zoltan Devai
2007-05-25 11:16         ` Liam Girdwood
     [not found]     ` <AC2729D6E3A3314A922E4E0FBE513F65D1FE77@MAIL.eldorado.org.br>
     [not found]       ` <5b7270f40705250750u1ba4619dm973fcb297c8fefb1@mail.gmail.com>
     [not found]         ` <AC2729D6E3A3314A922E4E0FBE513F65D6B8B8@MAIL.eldorado.org.br>
     [not found]           ` <5b7270f40705251040r56bee4dfqdb2e66fd2b7fbdcd@mail.gmail.com>
2007-05-29 17:42             ` [RFC] [PATCH 0/2] ASoC sound support forSMDK2440boards Jose Henrique Spahn Torres
2007-05-30 15:30               ` Zoltan Devai [this message]
2007-05-30 15:42                 ` Graeme Gregory
2007-05-30 17:02                   ` [RFC] [PATCH 0/2] ASoC soundsupport forSMDK2440boards Jose Henrique Spahn Torres

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=5b7270f40705300830g7aef9faajc0b9e82d6d983d@mail.gmail.com \
    --to=zdevai@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /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 NNTP newsgroup(s).