Comment 43 for bug 198218

This is not an alsa-utils issue but a kernel issue (specifically alsa-kernel/driver). People are mistakenly thinking that restarting the alsa-utils initscript fixes things, but note that doing so only stores and restores, in that order, the volume levels. The reason that forcibly reloading the kernel driver via /sbin/alsa works is that doing so forces a complete reinit of the codec.

What will assist the bug triagers? Please run the alsa-info.sh script referenced in my profile, and attach the output (either codec dump or generated URL from script) to this bug.