[Pkg-alsa-devel] Bug#545415: alsa-base: alsa fails to respond until "alsa force-reload" is executed manually

Elimar Riesebieter riesebie at lxtec.de
Mon Sep 14 17:38:44 UTC 2009


* Niu Kun [090914 11:45 +0800]
> Elimar Riesebieter ??????:
[...]
> >At this state I can't see a reason why gnome is wineing about a
> >incorrectly working sound daemon, because none is running? There are
> >two more possible sounddaemons:
> >artsd -> whis depends on kde
> >jackd -> which is HighTec sound daemon
> >
> >To check it do:
> >
> ># ps aux | grep art
> ># ps aux | grep jack
> This is empty output.

Well, no sound daomon running. BTW, you don't need one to enjoy
sound.

[...]
> >Play a sound
> >
> ># mplayer your_soundfile
> >
> >Do you hear sound?
> I can hear sound.
> But there's an error in the output:
> [AO OSS]: audio_setup: Can't open audio device /dev/dsp: Device or
> resource busy.

Well, there runs a sound app which uses OSS. Please post the output
of:
# cat /etc/libao.conf
# cat $HOME/.libao
# dpkg -l | grep oss-compat
# ls -al /etc/modprobe.d/linux-sound-base*

> ># adjust controls in alsamixer
> >
> ># <CTRL> <ALT> 2
> ># alsamixer
> >
> >Hopefully nothing is mutet. If so, go to the control and just hit m.
> >
> >If you can hear sound, everthing should be ok.
> Yes. I can hear the sound. In fact, I just don't want to reload my
> alsa driver by running "alsa force-reload" manually each time I
> login Gnome.

As said before, your system seems to use OSS by default.

Elimar


-- 
  You cannot propel yourself forward by
  patting yourself on the back.





More information about the Pkg-alsa-devel mailing list