After an upgrade some time ago, my system no longer initializes
the sound system. It was posted before that this could be overcome
by removing the alsa modules manually, then running udevtrigger.
Currently, whenever I reboot, I run alsaconf until it removes the
modules, then escape and run udevtrigger. This works, but is
there a way to restore automatic initialization on boot? I'm
running Debian Sid, kernel 2.6.23. Thanks for any help.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
11-16-2007, 06:51 PM
Florian Kulzer
Sound initialization (alsaconf) difficulty
On Fri, Nov 16, 2007 at 13:34:00 -0600, Russ Cook wrote:
> After an upgrade some time ago, my system no longer initializes
> the sound system. It was posted before that this could be overcome
> by removing the alsa modules manually, then running udevtrigger.
> Currently, whenever I reboot, I run alsaconf until it removes the
> modules, then escape and run udevtrigger. This works, but is
> there a way to restore automatic initialization on boot? I'm
> running Debian Sid, kernel 2.6.23. Thanks for any help.
Reboot the system and run these two commands (without changing anything
about ALSA):
lsmod | grep snd
ls -l /dev/snd* /dev/dsp
Post the output here and also tell us which sound card you are using
(i.e. post the relevant part of your "lspci" output).
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
11-16-2007, 07:39 PM
Russ Cook
Sound initialization (alsaconf) difficulty
Florian Kulzer wrote:
On Fri, Nov 16, 2007 at 13:34:00 -0600, Russ Cook wrote:
After an upgrade some time ago, my system no longer initializes
the sound system. It was posted before that this could be overcome
by removing the alsa modules manually, then running udevtrigger.
Currently, whenever I reboot, I run alsaconf until it removes the
modules, then escape and run udevtrigger. This works, but is
there a way to restore automatic initialization on boot? I'm
running Debian Sid, kernel 2.6.23. Thanks for any help.
Reboot the system and run these two commands (without changing anything
about ALSA):
lsmod | grep snd
ls -l /dev/snd* /dev/dsp
Post the output here and also tell us which sound card you are using
(i.e. post the relevant part of your "lspci" output).
My motherboard is an ASUS A8N32-SLI Deluxe, with integrated
Realtek ALC850 codec.
Output of lsmod | grep snd is attached as file 'sound'
Output of ls -l /dev/snd* /dev/dsp is attached as file 'sndlist'
Thanks for any help, as now my workaround no longer seems
to work.
On Fri, Nov 16, 2007 at 14:39:47 -0600, Russ Cook wrote:
> Florian Kulzer wrote:
>> On Fri, Nov 16, 2007 at 13:34:00 -0600, Russ Cook wrote:
>>
>>> After an upgrade some time ago, my system no longer initializes
>>> the sound system. It was posted before that this could be overcome
>>> by removing the alsa modules manually, then running udevtrigger.
>>> Currently, whenever I reboot, I run alsaconf until it removes the
>>> modules, then escape and run udevtrigger. This works, but is
>>> there a way to restore automatic initialization on boot? I'm
>>> running Debian Sid, kernel 2.6.23. Thanks for any help.
I missed this initially: Where does the 2.6.23 kernel come from? Did you
check if the problem is also present with a normal Debian kernel?
[...]
> My motherboard is an ASUS A8N32-SLI Deluxe, with integrated
> Realtek ALC850 codec.
I would like to see the output of
lspci | egrep -i 'audio|s(ou)?nd|media'
> Output of lsmod | grep snd is attached as file 'sound'
> Output of ls -l /dev/snd* /dev/dsp is attached as file 'sndlist'
That looks OK on first sight, assuming you indeed have an intel8x0 card.
I would now be interested to see the output of these two commands:
cat /dev/sndstat
cat /proc/asound/cards
Also, with which application(s) do you have problems? What happens if
you try the basic ALSA tools, e.g. if you run "speaker-test"?
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
11-16-2007, 09:30 PM
Russ Cook
Sound initialization (alsaconf) difficulty
Florian Kulzer wrote:
On Fri, Nov 16, 2007 at 14:39:47 -0600, Russ Cook wrote:
Florian Kulzer wrote:
On Fri, Nov 16, 2007 at 13:34:00 -0600, Russ Cook wrote:
After an upgrade some time ago, my system no longer initializes
the sound system. It was posted before that this could be overcome
by removing the alsa modules manually, then running udevtrigger.
Currently, whenever I reboot, I run alsaconf until it removes the
modules, then escape and run udevtrigger. This works, but is
there a way to restore automatic initialization on boot? I'm
running Debian Sid, kernel 2.6.23. Thanks for any help.
I missed this initially: Where does the 2.6.23 kernel come from? Did you
check if the problem is also present with a normal Debian kernel?
[...]
My motherboard is an ASUS A8N32-SLI Deluxe, with integrated
Realtek ALC850 codec.
I would like to see the output of
lspci | egrep -i 'audio|s(ou)?nd|media'
Output of lsmod | grep snd is attached as file 'sound'
Output of ls -l /dev/snd* /dev/dsp is attached as file 'sndlist'
That looks OK on first sight, assuming you indeed have an intel8x0 card.
I would now be interested to see the output of these two commands:
cat /dev/sndstat
cat /proc/asound/cards
Also, with which application(s) do you have problems? What happens if
you try the basic ALSA tools, e.g. if you run "speaker-test"?
The kernel was compiled from source, obtained from ftp.kernel.org.
I began with the config file in /boot from vmlinuz-2.6.21-2-amd64 , and
edited with 'make xconfig' I still had sound after installing and booting
this kernel, although I had to use alsaconf to remove the sound modules,
followed by udevtrigger to install them.
attached in order is output from your three requests above,
Trying to run speaker-test gives a series of errors of the form:
Alsa lib pcm_dmix.c:866snd_pcm_dmix_open) unable to open slave
Playback open error: -16,Device or resource busy
On Fri, Nov 16, 2007 at 16:30:44 -0600, Russ Cook wrote:
> Florian Kulzer wrote:
>> On Fri, Nov 16, 2007 at 14:39:47 -0600, Russ Cook wrote:
>>> Florian Kulzer wrote:
>>>> On Fri, Nov 16, 2007 at 13:34:00 -0600, Russ Cook wrote:
[...]
>>> My motherboard is an ASUS A8N32-SLI Deluxe, with integrated
>>> Realtek ALC850 codec.
[...]
>> That looks OK on first sight, assuming you indeed have an intel8x0 card.
[...]
> The kernel was compiled from source, obtained from ftp.kernel.org.
> I began with the config file in /boot from vmlinuz-2.6.21-2-amd64 , and
> edited with 'make xconfig' I still had sound after installing and booting
> this kernel, although I had to use alsaconf to remove the sound modules,
> followed by udevtrigger to install them.
>
> attached in order is output from your three requests above,
>
> lspci | egrep -i 'audio|s(ou)?nd|media'
>
> 00:0d.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2)
AFAICT, snd_intel8x0 is indeed the correct driver for this card. If you
google for this lspci output you find a MEPIS page where they claim that
the card works without problems with this driver.
> cat /dev/sndstat
> cat /proc/asound/cards
That looks good, too: One audio device, one midi device, a timer, two
mixers. (Disclaimer: I have no experience with midi devices, but I don't
see why a midi device should interfere with your sound output.)
> Trying to run speaker-test gives a series of errors of the form:
> Alsa lib pcm_dmix.c:866snd_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:
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
11-17-2007, 11:51 AM
Russ Cook
Sound initialization (alsaconf) difficulty
Florian Kulzer wrote:
On Fri, Nov 16, 2007 at 16:30:44 -0600, Russ Cook wrote:
Florian Kulzer wrote:
On Fri, Nov 16, 2007 at 14:39:47 -0600, Russ Cook wrote:
Florian Kulzer wrote:
On Fri, Nov 16, 2007 at 13:34:00 -0600, Russ Cook wrote:
[...]
My motherboard is an ASUS A8N32-SLI Deluxe, with integrated
Realtek ALC850 codec.
[...]
That looks OK on first sight, assuming you indeed have an intel8x0 card.
[...]
The kernel was compiled from source, obtained from ftp.kernel.org.
I began with the config file in /boot from vmlinuz-2.6.21-2-amd64 , and
edited with 'make xconfig' I still had sound after installing and booting
this kernel, although I had to use alsaconf to remove the sound modules,
followed by udevtrigger to install them.
attached in order is output from your three requests above,
AFAICT, snd_intel8x0 is indeed the correct driver for this card. If you
google for this lspci output you find a MEPIS page where they claim that
the card works without problems with this driver.
cat /dev/sndstat
cat /proc/asound/cards
That looks good, too: One audio device, one midi device, a timer, two
mixers. (Disclaimer: I have no experience with midi devices, but I don't
see why a midi device should interfere with your sound output.)
Trying to run speaker-test gives a series of errors of the form:
Alsa lib pcm_dmix.c:866snd_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.
Thanks for your continued interest in helping me solve this.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
11-17-2007, 01:44 PM
Florian Kulzer
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:866snd_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).
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
11-17-2007, 06:21 PM
Russ Cook
Sound initialization (alsaconf) difficulty
Florian Kulzer wrote:
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:866snd_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).
You were right on all counts. Killing esd restored sound on
my system. I don't log in via gdm. I start up in text mode,
and run 'startx' to start X11. Gnome comes up with it. Now
I need to learn what the pros and cons are of letting esd
run, and how to make every other sound app play well
with it.
Thanks for your help!
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
11-17-2007, 07:24 PM
Florian Kulzer
Sound initialization (alsaconf) difficulty
On Sat, Nov 17, 2007 at 13:21:32 -0600, Russ Cook wrote:
[...]
> You were right on all counts. Killing esd restored sound on
> my system. I don't log in via gdm. I start up in text mode,
> and run 'startx' to start X11. Gnome comes up with it. Now
> I need to learn what the pros and cons are of letting esd
> run, and how to make every other sound app play well
> with it.
>
> Thanks for your help!
You are welcome. Here are some suggestions for further reading:
Sound initialization (alsaconf) difficulty
snd_pcm_dmix_open) unable to open slave
