Thread: [Alsa-user] Unknown PCM default
Brought to you by:
perex
Menu
▾
▴
alsa-user
|
From: Carlos M. <ca...@ke...> - 2006-03-30 00:42:52
|
Hi All,
I'm getting the following error when using an alsa application:
ALSA lib pcm.c:2099:(snd_pcm_open_noupdate) Unknown PCM default
Error opening PCM device default
The output of the /proc files is:
# cat /proc/asound/cards
0 [siu-sh7343 ]: siu-sh7343 - Renesas sh7343 SIU
Renesas sh7343 SIU irq 108
# cat /proc/asound/devices
1: : sequencer
18: [0- 2]: digital audio playback
26: [0- 2]: digital audio capture
17: [0- 1]: digital audio playback
25: [0- 1]: digital audio capture
16: [0- 0]: digital audio playback
24: [0- 0]: digital audio capture
0: [0- 0]: ctl
33: : timer
Reading /cat/sndstat produces an error:
# cat /dev/sndstat
cat: /dev/sndstat: No such device
I searched for the solution to this problem but didn't find anything. If
anyone knows how to fix this problem please let me know.
Thanks,
Carlos Munoz
|
|
From: Lee R. <rlr...@jo...> - 2006-03-30 01:14:20
|
On Wed, 2006-03-29 at 16:49 -0800, Carlos Munoz wrote: > Hi All, > > I'm getting the following error when using an alsa application: > > ALSA lib pcm.c:2099:(snd_pcm_open_noupdate) Unknown PCM default > Error opening PCM device default > This is an incomplete driver - it sounds like the userspace component is missing. Please provide a pointer to the source. > The output of the /proc files is: > > # cat /proc/asound/cards > 0 [siu-sh7343 ]: siu-sh7343 - Renesas sh7343 SIU > Renesas sh7343 SIU irq 108 > What driver is this? I don't see it in the ALSA tree. There should be a file /usr/share/alsa/cards/SIU-SH7343.conf that defines the default PCM. > # cat /proc/asound/devices > 1: : sequencer > 18: [0- 2]: digital audio playback > 26: [0- 2]: digital audio capture > 17: [0- 1]: digital audio playback > 25: [0- 1]: digital audio capture > 16: [0- 0]: digital audio playback > 24: [0- 0]: digital audio capture > 0: [0- 0]: ctl > 33: : timer > > Reading /cat/sndstat produces an error: > > # cat /dev/sndstat > cat: /dev/sndstat: No such device > This is a legacy OSS interface and would only be available if snd-pcm-oss is loaded. > I searched for the solution to this problem but didn't find anything. If > anyone knows how to fix this problem please let me know. |
|
From: Carlos M. <ca...@ke...> - 2006-03-30 01:43:20
Attachments:
siu-sh7343.tar.gz
|
Lee Revell wrote: >On Wed, 2006-03-29 at 16:49 -0800, Carlos Munoz wrote: > > >>Hi All, >> >>I'm getting the following error when using an alsa application: >> >>ALSA lib pcm.c:2099:(snd_pcm_open_noupdate) Unknown PCM default >>Error opening PCM device default >> >> >> > >This is an incomplete driver - it sounds like the userspace component is >missing. Please provide a pointer to the source. > > > >>The output of the /proc files is: >> >># cat /proc/asound/cards >>0 [siu-sh7343 ]: siu-sh7343 - Renesas sh7343 SIU >> Renesas sh7343 SIU irq 108 >> >> >> > >What driver is this? I don't see it in the ALSA tree. There should be >a file /usr/share/alsa/cards/SIU-SH7343.conf that defines the default >PCM. > > > It is a new driver for the Renesas SH7343 Sound Interface Unit that I wrote. The product is a new cell phone with a LCD display that will play movie clips and audio to headphones. It worked well on my test board when I was using manually compiled alsa-lib and alsa-utils. Now I'm testing the software image that will be release to the customer and I get this errors. This image includes alsa libraries that were built by a different process (not sure about the differences though). Since the driver worked before, I think it might be a configuration problem... but I can't say for sure. Thanks, Carlos |
|
From: Carlos M. <ca...@ke...> - 2006-03-30 01:47:26
|
Carlos Munoz wrote: > Lee Revell wrote: > >> On Wed, 2006-03-29 at 16:49 -0800, Carlos Munoz wrote: >> >> >>> Hi All, >>> >>> I'm getting the following error when using an alsa application: >>> >>> ALSA lib pcm.c:2099:(snd_pcm_open_noupdate) Unknown PCM default >>> Error opening PCM device default >>> >>> >> >> >> This is an incomplete driver - it sounds like the userspace component is >> missing. Please provide a pointer to the source. >> >> >> >>> The output of the /proc files is: >>> >>> # cat /proc/asound/cards >>> 0 [siu-sh7343 ]: siu-sh7343 - Renesas sh7343 SIU >>> Renesas sh7343 SIU irq 108 >>> >>> >> >> >> What driver is this? I don't see it in the ALSA tree. There should be >> a file /usr/share/alsa/cards/SIU-SH7343.conf that defines the default >> PCM. >> >> >> > It is a new driver for the Renesas SH7343 Sound Interface Unit that I > wrote. The product is a new cell phone with a LCD display that will > play movie clips and audio to headphones. It worked well on my test > board when I was using manually compiled alsa-lib and alsa-utils. Now > I'm testing the software image that will be release to the customer > and I get this errors. This image includes alsa libraries that were > built by a different process (not sure about the differences though). > Since the driver worked before, I think it might be a configuration > problem... but I can't say for sure. > I forgot to mention that I hear noise if I cat a file to /dev/dsp or /dev/audio. Not sure it this means anything. Thanks, Carlos |
|
From: Lee R. <rlr...@jo...> - 2006-03-30 01:56:54
|
On Wed, 2006-03-29 at 17:50 -0800, Carlos Munoz wrote: > It is a new driver for the Renesas SH7343 Sound Interface Unit that I > wrote. This is a better question for the alsa-devel list than alsa-user. Just create the config file that defines a default PCM, or use hw:0,0 or plughw:0,0. Lee |
|
From: Lee R. <rlr...@jo...> - 2006-03-30 02:02:30
|
On Wed, 2006-03-29 at 17:50 -0800, Carlos Munoz wrote: > It is a new driver for the Renesas SH7343 Sound Interface Unit that I > wrote. The product is a new cell phone with a LCD display that will play > movie clips and audio to headphones. It worked well on my test board > when I was using manually compiled alsa-lib and alsa-utils. Now I'm > testing the software image that will be release to the customer and I > get this errors. This image includes alsa libraries that were built by a > different process (not sure about the differences though). Since the > driver worked before, I think it might be a configuration problem... but > I can't say for sure. > It sounds like alsa-lib is missing or incorrectly installed. Do /usr/share/alsa/alsa.conf and /usr/share/alsa/pcm/default.conf exist? Lee > Thanks, > > > Carlos |
|
From: Carlos M. <ca...@ke...> - 2006-03-30 02:15:44
|
Lee Revell wrote: > >It sounds like alsa-lib is missing or incorrectly installed. >Do /usr/share/alsa/alsa.conf and /usr/share/alsa/pcm/default.conf exist? > >Lee > > > No, they do not exist. I just remembered that I had copied the whole /usr/share/alsa directory to my development board. I will try that and let you know what I find. Thanks, Carlos |
|
From: Carlos M. <ca...@ke...> - 2006-03-30 02:26:40
|
Carlos Munoz wrote: > No, they do not exist. I just remembered that I had copied the whole > /usr/share/alsa directory to my development board. I will try that and > let you know what I find. > Yes, that did the trick. I copied the /usr/share/alsa directory to the board and everything is good now. I'll make sure we include this directory in the official software release. Thanks, Carlos |