[SOLVED] Re: Volume Control buttons not working after kernel upgrade

[<tomk@runbox.com>]

> On Tue, 1 Mar 2005, tomk wrote:
> 
> > Date: Tue, 01 Mar 2005 23:16:16 +0000 (GMT/IST)
> > From: tomk <tomk@runbox.com>
> > To: debian-user <debian-user@lists.debian.org>
> > Subject: Volume Control buttons not working after kernel upgrade
> > Resent-Date: Tue,  1 Mar 2005 17:16:29 -0600 (CST)
> > Resent-From: debian-user@lists.debian.org
> >
> > I'm running sid on my laptop, with a custom 2.6.9 kernel. Everything works fine.
> >
> > I've now compiled a 2.6.10 kernel, using the existing 2.6.9 config and "make oldconfig". Compilation was uneventful, and the laptop boots into 2.6.10 with no errors.
> >
> > I'm running alsa, and under 2.6.9, I could adjust the volume either with software (alsamixer, xfce4 volume control) or with hardware (Fn+PgUp/Fn+PgDn, or dedicated Volume Control buttons). Under 2.6.10, software volume control is fine, but if I try either of the hardware options, the machine locks up hard, and needs a reboot. After reboot, I can't see anything useful in the logs.
> >
> > If anyone has any suggestions, I'd appreciate it.
> >
> > Thanks
> > Tom K
> >
> Hi,
> have you looked at permissions for /dev/dsp (or your audio dev) and
> /dev/mixer ?
> 
> I have experienced that upgrading kernel or installing new has reset
> these permissions.
> 
> I'm using xmms for mp3, ogg, cd's and stuff and xine for movies, some
> times its enough to set permission on /dev/dsp to be able to control sound
> as user, but sometimes I have to instlal "mikmod" in addition to set
> permission on /dev/dsp. And......some times I also have to set the same
> permission on /dev/mixer to be able to control sound as logged in user.
> 
> /ernst-magne
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 
> 

Thanks for the suggestion, ernst, but it's not a permissions problem - if it was, software volume control wouldn't work either.

I've actually fixed it by compiling a 2.6.11 kernel - the source for this was released yesterday.

Thanks anyway
Tom K.