By default, ALSA drivers are "mute" after being loaded. If user starts
a mixer (e.g. alsamixer) to un-mute the audio channels and set the
mixers, these settings will not survive the next reboot and the
system's audio starts "mute" again.

Initscript "halt" contains the following lines for old OSS/Free audio
drivers, which save mixer settings on reboot/shutdown:

# Save mixer settings, here for lack of a better place.
grep -q "\(sparcaudio\|sound\)" /proc/devices
if [ $? = 0 -a -x /bin/aumix-minimal ]; then
   runcmd $"Saving mixer settings" /bin/aumix-minimal -f /etc/.aumixrc -S
fi

With ALSA, it should be similar, but done with "/usr/sbin/alsactl
store" (or amixer), which saves settings to /etc/asound.state. These
would be restored (via modprobe.conf) when the kernel modules are loaded.

Note that the following entry in /etc/modprobe.conf is not enough,
because reboot/shutdown does not unload kernel modules:

remove snd-ens1371 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-ens1371


Version-Release number of selected component (if applicable):
initscripts-7.48-1

How reproducible:
Always

Steps to Reproduce:
1. run alsamixer and change mixer settings
2. reboot
3. run alsamixer to verify mixer settings
    

Actual Results:  Mixer settings haven't survived the reboot.


Expected Results:  Mixer settings should have survived the reboot.


Additional info: Is "aumix" package still of use anywhere?