Re: Problem with linux-kernel 22.214.171.124 for ibm-thinkpad t40?
Sorry that it took me so long to reply,
I just threw 126.96.36.199 in and voila - problems solved. My USB mouse even
works again. So I guess 188.8.131.52 just didn' like me (and vica versa, I
can tell you :)
Well at least now I know more about the sound setup in Linux :)
Thanks for explaining and helping out,
Koen Vermeer wrote:
On Wed, 2005-05-11 at 20:00 +0200, Christian Birkholm Clausen wrote:
I'm the one who didn't have /dev/dsp. So I recompiled the kernel with
Javier-Elias's config and /dev/dsp appeared. Kudos Javier! Good thing
(only now my USB mouse doesn't work, but that's a different story)
As long as you only use alsa, there is no use for /dev/dsp. In fact, it
may be easier trying to set things up without /dev/dsp, because then you
know for sure that you're using alsa instead of oss (legacy or
Still got 2 issues though:
When I boot my laptop, esd seems to use /dev/dsp - the music player
can't play because of this. The sound server reports something like it:
"The sound device is busy.." So when I *fuser /dev/dsp* and kill the PID
- it plays! But I have to do this everytime I boot. Is there a way to
get rid of this problem?
Just a shot in the dark: Is esd using alsa as the output device? I'm not
sure how to set that, though, but if it currently runs with -d /dev/dsp,
then it's using alsa.
Ofcourse, it you let esd use alsa, then the alsa device is blocked. So,
let your sound player output to esd (so esd can mix the streams), or set
up dmix (alsa plugin), which will then mix multiple alsa streams.
Another solution is to tell gnome not to autostart the sound server.
This will still give only one program at a time access to the alsa
My gnome-alsamixer settings keep changing back to default when I
boot/reboot, so I also have to reset these everytime. Anyone?
Is this really caused by gnome-alsamixer? I guess gnome-alsamixer isn't
running until you log into gnome, so I'm a bit confused about what you
mean by 'boot'. If you really mean 'boot', and it isn't caused by
gnome-alsamixer, then you might be able to fix this by
changing /etc/default/alsa (look for alsactl_store_on_shutdown).