Martin Habets wrote:

What is the name of your cd player application? (it's more than likely
that I'm not familiar with it). Maybe it uses the OSS emulation, so check
it's setup if it has any.


I've tried the cd players that come as a standard part of KDE (KsCD) and Gnome. Haven't been able to get into any of their config files, at least not in the gui. And while they both readily play music cd--no sound.

One very interesting development: I discovered I have Totem dvd player on the system, so popped in a dvd. Surprise! movie played--with sound!

If you use KDE or Gnome you may have a sound deamon running that needs
to be reconfigured. I'm not familiar with these, but you can find out who
is using/blocking the sound device by doing:

lsof | egrep "/dev/snd|/dev/audio"

You may want to run this while playing a CD.


Thanks for the tip. Here's output:

While playing a music cd in KsCD [no sound]:

[EMAIL PROTECTED]:~$ lsof | egrep "/dev/snd|/dev/audio"
kdeinit 5189 harvey 10u CHR 116,0 2425 /dev/snd/controlC0
[EMAIL PROTECTED]:~$


While playing music cd in Totem Movie Player (Movie Player using xine-lib ver 1.0.0) [sound normal]:

[EMAIL PROTECTED]:~$ lsof | egrep "/dev/snd|/dev/audio"
kdeinit 5189 harvey 10u CHR 116,0 2425 /dev/snd/controlC0
totem 6414 harvey mem CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6414 harvey 21u CHR 116,0 2425 /dev/snd/controlC0
totem 6414 harvey 23u CHR 116,0 2425 /dev/snd/controlC0
totem 6414 harvey 33u CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6415 harvey mem CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6415 harvey 21u CHR 116,0 2425 /dev/snd/controlC0
totem 6415 harvey 23u CHR 116,0 2425 /dev/snd/controlC0
totem 6415 harvey 33u CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6416 harvey mem CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6416 harvey 21u CHR 116,0 2425 /dev/snd/controlC0
totem 6416 harvey 23u CHR 116,0 2425 /dev/snd/controlC0
totem 6416 harvey 33u CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6421 harvey mem CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6421 harvey 21u CHR 116,0 2425 /dev/snd/controlC0
totem 6421 harvey 23u CHR 116,0 2425 /dev/snd/controlC0
totem 6421 harvey 33u CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6422 harvey mem CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6422 harvey 21u CHR 116,0 2425 /dev/snd/controlC0
totem 6422 harvey 23u CHR 116,0 2425 /dev/snd/controlC0
totem 6422 harvey 33u CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6423 harvey mem CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6423 harvey 21u CHR 116,0 2425 /dev/snd/controlC0
totem 6423 harvey 23u CHR 116,0 2425 /dev/snd/controlC0
totem 6423 harvey 33u CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6424 harvey mem CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6424 harvey 21u CHR 116,0 2425 /dev/snd/controlC0
totem 6424 harvey 23u CHR 116,0 2425 /dev/snd/controlC0
totem 6424 harvey 33u CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6425 harvey mem CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6425 harvey 21u CHR 116,0 2425 /dev/snd/controlC0
totem 6425 harvey 23u CHR 116,0 2425 /dev/snd/controlC0
totem 6425 harvey 33u CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6427 harvey mem CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6427 harvey 21u CHR 116,0 2425 /dev/snd/controlC0
totem 6427 harvey 23u CHR 116,0 2425 /dev/snd/controlC0
totem 6427 harvey 33u CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6434 harvey mem CHR 116,16 2492 /dev/snd/pcmC0D0p
totem 6434 harvey 21u CHR 116,0 2425 /dev/snd/controlC0
totem 6434 harvey 23u CHR 116,0 2425 /dev/snd/controlC0
totem 6434 harvey 33u CHR 116,16 2492 /dev/snd/pcmC0D0p
[EMAIL PROTECTED]:~$


Lot more going on with the latter, but I don't know how to interpret the results. Main thing I notice is that /dev/snd/pcmC0D0p is now in on the act as well as /dev/snd/controlC0.

Here's the contents of the /dev/snd directory:

[EMAIL PROTECTED]:~$ ls -l /dev/snd/
total 0
crw-rw----  1 root audio 116,  0 2005-01-09 18:18 controlC0
crw-rw----  1 root audio 116, 16 2005-01-09 18:18 pcmC0D0p
crw-rw----  1 root audio 116, 33 2005-01-09 18:18 timer

I don't know why "total 0" when there are 3 files listed. But I know that "c" implies a character device, assisting communication betw kernel & hardware devices.

I've never been able to ring the system bell in 2.6, but haven't bothered
to figure out why cause I hate the thing.

That's good info to have. I don't espec want the system bell around--was just using it as a way to test for sound.

So the short answer is that your kernel, modules and alsa are okay. Must
be application problems.


Any idea based on the above where I might go from here?

Thanks again, Martin.

--Harvey






--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to