Here is a reply I received on the ALSA bug site. Seems to be in the same direction that s418 Woods responded. I haven't looked at my system yet but will do, to see what is there.
Hi JohnH and everyone who cares,
yesterday I installed the original SuSE kernel 220.127.116.11-31-default (from
DVD) as an alternate boot kernel. I did this manually by extracting the
files from RPM and copying the files to their destination location. (Seems
that Yast does not support installing alternate (older) kernels ).
And belive it or not, this was all I had to do and after a first reboot
(still booting the newer kernel 2.6.22-12-default) sound was back.
There was no obvious reason for this. First I finished alternate kernel
installation (grub, initrd and depmod) and then I tried to find out what
happened. But on next reboot, sound was muted again, regardless which
kernel I was booting. Restarting alsa at runtime did not help.
I found that there is one file in the rpm of kernel 18.104.22.168-31-default
which is now in use by both kernels: /etc/modprobe.d/module-renames. The
depmod -a (running 2.6.22-12-default) created new module dependencies
including this file). Maybe this muted sound again?
Commenting out everything in this file and updating dependencies : sound
Undo comments but not updating dependencies : sound is back again.
And sound is back again for both kernels!!
So for now all I can tell is that it does not look like a kernel bug.
Either no sound at all or sound from both kernels. Seems is has to do with
But I am still not convinced completely. Yesterday evening, I did not have
enough time to test all the combinations several times and see if behaviour
Is there anyone with a better guess?
This might be of help to some of you.