alsamixer Doesn't save volume settings

alsamixer Doesn't save volume settings

[sumit kalra]

Hi,

I am running ALSA-1.0.4 on RedHat 8 Linux (kernel
2.4.18-14). 

I am trying to set the volume using "alsamixer" but
everytime I reboot the machine, the volume gets reset
to zero. I searched on google and got one solutions
but it doesn't seem to work for me: Running "alsactl
store" after increasing the volume - the command
completes properly (with no errors) but on reboot, the
volume setting are lost.

Any help is appreciated,
TIA
Sumit Kalra


	
	
		
____________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: alsamixer Doesn't save volume settings

[Ray Olszewski]

At 05:34 AM 5/7/2004 +0100, sumit kalra wrote:
>Hi,
>
>I am running ALSA-1.0.4 on RedHat 8 Linux (kernel
>2.4.18-14).
>
>I am trying to set the volume using "alsamixer" but
>everytime I reboot the machine, the volume gets reset
>to zero. I searched on google and got one solutions
>but it doesn't seem to work for me: Running "alsactl
>store" after increasing the volume - the command
>completes properly (with no errors) but on reboot, the
>volume setting are lost.

Odd. With normal operation of alsamixer, the most common changes are 
supposed to persist, even across a reboot ... even if you don't run alsactl 
manually.

Do any other changes you make to the settings (for example, turning various 
devices on and off, or setting the capture device) persist across a reboot, 
or are they too reset? (If you haven't tried changes other than volume, 
please do.)

After you run alsactl, does the config file (maybe /etc/sound.state, maybe 
/etc/asound.state) actually get created? Is it present (and unchanged - 
check the timestamp) after a reboot?

Is the "you" who runs alsactl root or an unprivileged userid? If the 
latter, that could be your problem; on my system, /etc/asound.state is 
owned by root and mode 644, so other userids cannot modify the file.

Are there any init scripts that affect alsa settings? Look for either alsa 
or alsasound in your init-script directory (I forget where RH puts this; my 
Debian systems use /etc/init.d) and see that both your default runlevel and 
the runlevel 6 (shutdown) call via symlinks whichever script is present 
(these scripts are supposed to run alsactl to save and restore settings).

Did you install a precompiled RPM, compile against your kernel from an RPM, 
or compile from non-RH source?



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: alsamixer Doesn't save volume settings

[sumit kalra]

Hi Ray,

Thnaks for your reply. Please see my answers embedded
below.


 --- Ray Olszewski <ray@comarre.com> wrote: > At 05:34
AM 5/7/2004 +0100, sumit kalra wrote:
> >Hi,
> >
> >I am running ALSA-1.0.4 on RedHat 8 Linux (kernel
> >2.4.18-14).
> >
> >I am trying to set the volume using "alsamixer" but
> >everytime I reboot the machine, the volume gets
> reset
> >to zero. I searched on google and got one solutions
> >but it doesn't seem to work for me: Running
> "alsactl
> >store" after increasing the volume - the command
> >completes properly (with no errors) but on reboot,
> the
> >volume setting are lost.
>
> Odd. With normal operation of alsamixer, the most
> common changes are
> supposed to persist, even across a reboot ... even
> if you don't run alsactl
> manually.
>
> Do any other changes you make to the settings (for
> example, turning various
> devices on and off, or setting the capture device)
> persist across a reboot,
> or are they too reset? (If you haven't tried changes
> other than volume,
> please do.)

All the settings including the capture device state
get reset after a reboot.


>
> After you run alsactl, does the config file (maybe
> /etc/sound.state, maybe
> /etc/asound.state) actually get created? Is it
> present (and unchanged -
> check the timestamp) after a reboot?

Yes, on running "alsactl", the file
"/etc/asound.state" gets created which remains
unchanged across the reboot.


>
> Is the "you" who runs alsactl root or an
> unprivileged userid? If the
> latter, that could be your problem; on my system,
> /etc/asound.state is
> owned by root and mode 644, so other userids cannot
> modify the file.

The root is running "alsactl" command. The file, even
in my case, is owned by root and has mode 644.


>
> Are there any init scripts that affect alsa
> settings? Look for either alsa
> or alsasound in your init-script directory (I forget
> where RH puts this; my
> Debian systems use /etc/init.d) and see that both
> your default runlevel and
> the runlevel 6 (shutdown) call via symlinks
> whichever script is present
> (these scripts are supposed to run alsactl to save
> and restore settings).

The script /etc/init.d/alsasound is present but
/etc/rc6.d/ and /etc/rc3.d/ directories don't have
symlinks to it. I created these links by hand, but it
didn't help.


>
> Did you install a precompiled RPM, compile against
> your kernel from an RPM,
> or compile from non-RH source?

I got the alsa drivers, library and utilities from the
alsa project website (alsa-project.org) as tarred
zips. I compiled and installed them as root.


Interestingly, after rebooting if I run "alsactl
restore" before runnign "alsamixer", my previous
settings are restored. This means that the file
/etc/asound.state is correctly storing the settings
across reboots but alsamixer is somehow not re-reading
it after rebooting. How do we get around this?

Thanks and regards,
Sumit Kalra


	
	
		
____________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: alsamixer Doesn't save volume settings

[Ray Olszewski]

At 10:27 AM 5/7/2004 +0100, sumit kalra wrote:
[...]
>The script /etc/init.d/alsasound is present but
>/etc/rc6.d/ and /etc/rc3.d/ directories don't have
>symlinks to it. I created these links by hand, but it
>didn't help.
>[...]
>Interestingly, after rebooting if I run "alsactl
>restore" before runnign "alsamixer", my previous
>settings are restored. This means that the file
>/etc/asound.state is correctly storing the settings
>across reboots but alsamixer is somehow not re-reading
>it after rebooting.

alsamixer is not supposed to re-read it. The alsasound init script runs 
"alsactl restore" to handle this ... and includes what looks like decent 
error handling, so it should log an error if it itself runs but cannot for 
some reason run alsactl.  So make sure it is running properly on init.

>How do we get around this?

Is 3 *really* the default runlevel on RH systems? (Debian uses 2.)

Did you install alsactl as /usr/sbin/alsactl (that is where the alsasound 
script expects to find it)?

Is the pseudo-directory /proc/asound present on your system (dieing 
silently if it is not is the one error-reporting weakness I can see in 
alsasound)?



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: alsamixer Doesn't save volume settings

[sumit kalra]

Hi Ray / Theo. Sean Schulze,

I finally managed to get alsamixer to retain the
volume settings across reboots. The problem was that
"alsactl restore" was not being run at boot time. My
initial thought was that this script doesn't need to
be re-run on every boot - but I guess it does.

Thanks for your help,
Regards,
Sumit Kalra


 --- Ray Olszewski <ray@comarre.com> wrote: > At 10:27
AM 5/7/2004 +0100, sumit kalra wrote:
> [...]
> >The script /etc/init.d/alsasound is present but
> >/etc/rc6.d/ and /etc/rc3.d/ directories don't have
> >symlinks to it. I created these links by hand, but
> it
> >didn't help.
> >[...]
> >Interestingly, after rebooting if I run "alsactl
> >restore" before runnign "alsamixer", my previous
> >settings are restored. This means that the file
> >/etc/asound.state is correctly storing the settings
> >across reboots but alsamixer is somehow not
> re-reading
> >it after rebooting.
> 
> alsamixer is not supposed to re-read it. The
> alsasound init script runs 
> "alsactl restore" to handle this ... and includes
> what looks like decent 
> error handling, so it should log an error if it
> itself runs but cannot for 
> some reason run alsactl.  So make sure it is running
> properly on init.
> 
> >How do we get around this?
> 
> Is 3 *really* the default runlevel on RH systems?
> (Debian uses 2.)
> 
> Did you install alsactl as /usr/sbin/alsactl (that
> is where the alsasound 
> script expects to find it)?
> 
> Is the pseudo-directory /proc/asound present on your
> system (dieing 
> silently if it is not is the one error-reporting
> weakness I can see in 
> alsasound)?
> 
> 
> 
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at
http://www.linux-learn.org/faqs 


	
	
		
____________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: alsamixer Doesn't save volume settings

[Theo. Sean Schulze]

Have you tried adding 'alsactl restore' in your rc.local on boot?

On Fri, May 07, 2004 at 05:34:47AM +0100, sumit kalra hunted and pecked out:
> Hi,
> 
> I am running ALSA-1.0.4 on RedHat 8 Linux (kernel
> 2.4.18-14). 
> 
> I am trying to set the volume using "alsamixer" but
> everytime I reboot the machine, the volume gets reset
> to zero. I searched on google and got one solutions
> but it doesn't seem to work for me: Running "alsactl
> store" after increasing the volume - the command
> completes properly (with no errors) but on reboot, the
> volume setting are lost.
> 
> Any help is appreciated,
> TIA
> Sumit Kalra
> 
> 
> 	
> 	
> 		
> ____________________________________________________________
> Yahoo! Messenger - Communicate instantly..."Ping" 
> your friends today! Download Messenger Now 
> http://uk.messenger.yahoo.com/download/index.html
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs

-- 
Theo. Sean Schulze
tschulze@teamfinders.org
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: alsamixer Doesn't save volume settings

[Dominique Sidiropoulos]

sumit kalra wrote:

>Hi,
>
>I am running ALSA-1.0.4 on RedHat 8 Linux (kernel
>2.4.18-14). 
>
>I am trying to set the volume using "alsamixer" but
>everytime I reboot the machine, the volume gets reset
>to zero. I searched on google and got one solutions
>but it doesn't seem to work for me: Running "alsactl
>store" after increasing the volume - the command
>completes properly (with no errors) but on reboot, the
>volume setting are lost.
>
>Any help is appreciated,
>TIA
>Sumit Kalra
>
>
>	
>	
>		
>____________________________________________________________
>Yahoo! Messenger - Communicate instantly..."Ping" 
>your friends today! Download Messenger Now 
>http://uk.messenger.yahoo.com/download/index.html
>-
>To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.linux-learn.org/faqs
>
>
>  
>
You should invoke somewhere (/etc/rc.local I think - but not sure) 
`alsactl restore' or something too.


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs