On 12/29/2016 03:21 PM, Mick wrote:
Hi All,
My sound has been behaving erratically for a while now, probably since
pulseaudio started being shipped with various desktop applications.
I had many similar issues years ago. I solved them by doing the following:
In /etc/pulse/daemon.conf, I've set:
flat-volumes = no
In /etc/pulse/default.pa, comment-out these entries:
#load-module module-device-restore
#load-module module-stream-restore
#load-module module-card-restore
Add the "alsasound" service to "boot" runlevel:
rc-config add alsasound boot
In /etc/conf.d/alsasound, set:
RESTORE_ON_START="yes"
SAVE_ON_STOP="yes"
Stop the alsasound service:
/etc/init.d/alsasound stop
Delete the currently saved mixer settings:
rm /var/lib/alsa/asound.state
Use alsamixer to configure your sound card to your liking (hit F6 first
and select the real device.)
Start the alsasound service:
/etc/init.d/alsasound start
Stop it again to save the current mixer settings:
/etc/init.d/alsasound stop
Change /etc/conf.d/alsasound to:
SAVE_ON_STOP="no"
You're done. Reboot to check if everything is working as intended.
What the above does is make PA not restore its own settings on boot,
make ALSA restore your preferred settings on boot but not save
alterations on shutdown (next reboot will restore your initial
settings.) It also disables the "flat volumes" feature of PA, which for
me at least resulted in many "RIP my ears" moments, and also makes the
volume mixer (KMix and pavucontrol in my case) behave very weirdly (it
seems I need to get a PhD from MIT first to figure out what the volume
settings do when "flat volumes" is on.)
Note that the above is only done once. Do it, and reboot. After that it
should work forever. When upgrading PA or ALSA, make sure to not
overwrite your custom /etc/ settings when running "dispatch-conf" or
"etc-update" (or whatever you're using.)
Hope this helps.
