On Fri, 2006-01-13 at 20:31 +0100, Takashi Iwai wrote:
> At Mon, 09 Jan 2006 12:24:21 +0000,
> James Courtier-Dutton wrote:
> > 
> > kunt1z wrote:
> > 
> > > Something happens...
> > > I run alsaconf, a script that modify /etc/modules.conf file, then I 
> > > restart /etc/init.d/alsasound service and I try to play a sound with 
> > > aplay. Here's what happens:
> > >
> > > $ aplay test.wav
> > > ALSA lib pcm_dmix.c:852:(snd_pcm_dmix_open) unable to open slave
> > > aplay: main:547: audio open error: No such file or directory
> > >
> > > What does it mean "unable to open slave"? And why it says "no such 
> > > file or directory"? Which file? The test.wav has correct path.
> > > I try to run as root speaker-test, the result is similar:
> > >
> > I agree. We should at least have alsa-lib report the filename it was 
> > trying to open.
> 
> You can see it when you set the environment variable
> LIBASOUND_DEBUG=2.  See alsa-lib/NOTES for details.

That's disabled by default, you have to build alsa-lib with
--with-debug=yes for it to work.

Lee



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to