Re: Sound initialization (alsaconf) difficulty
On Sat, Nov 17, 2007 at 06:51:33 -0600, Russ Cook wrote:
> Florian Kulzer wrote:
>> On Fri, Nov 16, 2007 at 16:30:44 -0600, Russ Cook wrote:
[...]
>>> Trying to run speaker-test gives a series of errors of the form:
>>> Alsa lib pcm_dmix.c:866:(snd_pcm_dmix_open) unable to open slave
>>> Playback open error: -16,Device or resource busy
>>>
>>
>> OK, so some process might be blocking the sound devices; most probably a
>> sound daemon. (Are you running Gnome or KDE?) Post the output of this:
>>
>> lsof -w | egrep 'snd|dsp'
>>
>>
> Yes, I am running Gnome. The of output of running
> lsof -w | egrep 'snd|dsp' is
> esd 3912 russ 5w CHR 14,3 6406 /dev/dsp
>
> My user name is 'russ', and I am a member of 'audio' group.
As a quick test, I propose that you do this (as 'russ'):
pkill esd
This should shut down esd (Gnome's sound daemon). Check the output of
the "lsof ..." command again; it should be empty if no process accesses
the sound devices. Then you can test if your other applications can play
sound now. (Your earlier workaround of running alsaconf could also have
killed esd since it force-unloads all sound modules, which tends to kill
all processes that are accessing sound devices.)
Esd will probably run again the next time you start Gnome (logging in
via gdm, I assume). You can either try to deactivate esd in Gnome's
setup (I don't use Gnome so I don't know any details about this) or you
can try to configure your other applications to play sound via esd (how
to do that depends on which applications you use).
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Reply to: