Hi: I am using the device hw:1,1, which is the C-Media sound card, as well as using ALSA 1.2.10. Of course, I tried simple -- sound was working "fine" on hw:0,1 (Intel integrated soundcard) without the .asoundrc file, then stopped working (no debug messages, no errors, nothing). I then tried to diagnose sound working with xmms, by toggling the hw devices that its ALSA output plugin sees and getting one to work. I then had to create an .asoundrc file to switch the defaults for my sound programs to work (amarok, KDE arts server). My issue is more fundamental: some device seems to "hog" ALSA; is there a way to debug the problem in a systematic way (error messages, logs, etc.) or is a "holistic" method, such as what I described above, as good as it will get? Thanks for any help.
Tanim > On Wed, 2006-04-05 at 17:53 +0200, Tanim Islam wrote: > > Hi: > > > > I have what I believe to be a generic problem on my Kubuntu breezy > > machine (Ubuntu 5.10), and I was wondering if there was a transparent way > > to debug ALSA. That is, is there a list of system log files that the ALSA > > daemon or its equivalent outputs? Also, i get the error that the sound > > device is busy. Is there a way to determine which application or service > > is hogging this sound resource? For reference, here is my asoundrc file > > If you have ALSA 1.0.9 or later multiple streams should work with > no .asoundrc. > > Which device is giving you the error? > > Lee ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
