Comment 21 for bug 194816

Ok, I have sound now! Thanks $1M for your help! But I had to reinstall my nvidia drivers for the appropriate kernel, since my screen resolution dropped. Got it fixed now....

I think I have a possible theory as to what happened. When I installed the closed source nvidia drivers, It must have picked up the (wrong) -386 kernel as a dependency since I see nvidia drivers for both in the synaptic package manager. This is still very dangerous, a total newbie could get totally messed up if they wound up with the wrong kernel by accident.

I guess the "bug" now is figuring out how somebody (me) could have subtly wound up installing an incorrect kernel with non-working sound modules. Why is the i386 version hanging around in the synaptic package manager? And if it is there for a good reason for it being there, shouldn't it be fully supported? ( sound modules and all ) As a suggestion, there probably should be more warning if dumb users like me are about to install a new default kernel from synaptic that sub-optimal or not recommended for your current hardware platform.