View previous topic :: View next topic |
Author |
Message |
ian.au Guru
Joined: 07 Apr 2011 Posts: 591 Location: Australia
|
Posted: Wed Jan 18, 2012 3:55 am Post subject: Is alsaconf Save_On_Stop Deprecated? |
|
|
Have been updating scripts to tidy up after a change to Baselayout2 on a machine that hadn't synced for something like 256 days, now running through dispatch-conf, and am being advised that:
Code: |
--- /etc/conf.d/alsasound 2012-01-17 16:05:00.000000000 +1000
+++ /etc/conf.d/._cfg0000_alsasound 2012-01-18 13:06:16.000000000 +1000
@@ -13,7 +13,7 @@
RESTORE_ON_START="yes"
-SAVE_ON_STOP="yes"
+# SAVE_ON_STOP:
# Do you want to save changes made to your mixer volumes when alsasound
# stops?
# no - Do not save state
|
Which looks to me like it's not going to save my settings on reboot. Is this now the default condition or should I re-insert the SAVE_ON_STOP command in the script to retain my settings between sessions?
Sorry if this has been covered previously, but I recall I had problems with sound defaults on this machine when I built it a year ago, and I'd rather avoid them this time around.[/code]
Ian |
|
Back to top |
|
|
Logicien Veteran
Joined: 16 Sep 2005 Posts: 1555 Location: Montréal
|
Posted: Wed Jan 18, 2012 7:16 am Post subject: |
|
|
Hi,
what I do first is to save manually the mixer settings I set with the command alsactl . Then I set /etc/conf.d/alsasound with
Code: | SAVE_ON_STOP="no"
RESTORE_ON_START="yes" |
That way, no matter the mixer changes I made during the session, the channels will be restored like I did manually at boot time. _________________ Paul |
|
Back to top |
|
|
PaulBredbury Watchman
Joined: 14 Jul 2005 Posts: 7310
|
Posted: Wed Jan 18, 2012 7:14 pm Post subject: |
|
|
The problem with saving asound.state is that ALSA sometimes rearranges the mixers, between ALSA versions. So the asound.state file becomes invalid.
To workaround that, I just run amixer commands in a startup script. |
|
Back to top |
|
|
|