| 1 |
On Sunday 26 February 2006 22:17, Ducky Z. wrote: |
| 2 |
> I'm using the modules provided by the kernel, which is 2.6.15. |
| 3 |
> alsa-lib is 1.0.10. |
| 4 |
This should be fine. |
| 5 |
|
| 6 |
> When I aplay a file, it shows: |
| 7 |
> |
| 8 |
> ALSA lib pcm_direct.c:900:(snd_pcm_direct_initialize_slave) unable to |
| 9 |
> install hw params |
| 10 |
> ALSA lib pcm_dmix.c:831:(snd_pcm_dmix_open) unable to initialize slave |
| 11 |
> aplay: main:544: audio open error: Inappropriate ioctl for device |
| 12 |
Hrm.... Is this being done as root? I think your /etc/asound.conf file might |
| 13 |
need some help. I'm not sure here, but it might not be able to play because |
| 14 |
the wrong information is in the asound.conf file. |
| 15 |
|
| 16 |
> > In addition to being unmuted are the outputs actually turned up? |
| 17 |
> |
| 18 |
> Output means? |
| 19 |
Means that PCM, MASTER are not set to 0 in alsamixer. You said earlier that |
| 20 |
they were unmuted and turned up so I think you have this covered, but you |
| 21 |
should double check. |
| 22 |
|
| 23 |
> > You appear to have the right modules loaded, but those dmesg errors are |
| 24 |
> > likely because the userland is having problems talking to the kernel. |
| 25 |
> |
| 26 |
> Is there any workaround? |
| 27 |
Well the workaround is to get programs using the alsa libraries to properly |
| 28 |
initialize the device. Not sure what the configuration issue is. |
| 29 |
|
| 30 |
-- |
| 31 |
Zac Slade |
| 32 |
krakrjak@××××××××××.net |
| 33 |
ICQ:1415282 YM:krakrjak AIM:ttyp99 |
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives