Comment 38 for bug 109838

I have also seen this bug on my Sony Viao. I tried all the alsa reinstallation, m-a fixes, and several options before I found that I need to set the model=viao in /etc/modprobe.d/alsa-base. It fixed the issue for me, and from what I have read, this seems to be the fix that works most often for many different systems (model=[something] where [something] is the correct keyword for that system).

Since this bug seems to be affecting so many people, it seems like there should be some detection script that runs on installation and perhaps on kernel updates in order to correctly detect and set the model. Is such a fix possible?