I’ve been through this before and successfully got sound working. After using the Live DVD to recover my system from fglrx’s doom, the sound is gone again. And now going through the same steps as before doesn’t seem to make it work anymore.
Its possible you may need to update your alsa to the 1.0.19 version of alsa, but note the “uname -a” command indicates your PC has the 184.108.40.206-3.2 kernel. Hence the alsa-driver-kmp-default-220.127.116.1190417_18.104.22.168_9.1-1.1.x86_64.rpm will NOT (or at least should NOT) install on your PC, as that is for a different kernel version. You need to pay attention to the versioning.
From what I have read, there is no longer alsa rpms (on the openSUSE build site maintained by the openSUSE alsa/dev) for the 22.214.171.124 kernel. Did you keep your own copy of those rpms? (I do most the time, for my 32-bit PC). Anyway if you do not want to compile your own alsa rpm for the 126.96.36.199 kernel, and IF an update to 1.0.19 of alsa is needed, you will either need to roll back to the older 188.8.131.52 kernel, or update to the 184.108.40.206 kernel, or find someone who has the rpms you want. Note either of kernel changes will possibly break your graphics again.
You could try to get your sound to work with the 1.0.17/1.0.18 alsa that you have installed, but I am not so convinced that will work. In terms of keeping your current kernel, and trying to get the sound to work, the ONLY idea I have, is for you to change your /etc/modprobe.d/sound file to the following, restart your PC, and test your sound (where I added “enable_msi=1”):
options snd-hda-intel enable_msi=1 model=hp
options snd slots=snd-hda-intel
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
After making/saving the change, reboot and test your sound.
Frankly, I do not think that will work. The kernel change has likely borked your sound, and you need an alsa version that is consistent with the kernel.
I actually found out that my kernel-default and the rest are still 220.127.116.11_9.1-1.1, with the exception for kernel-debug-extra and kernel-extra being 18.104.22.168-3.2 (iirc.) And it looks to me like the former version is required for the wl-broadcom I downloaded to work. I have recollections of not finding a version of wl-broadcom that wouldn’t trigger dependency conflicts, so I installed it anyway (this was before the fglrx mess.) But it didn’t work before I used the Live DVD to fix my system. Now it works, with my sound compromised.
I don’t need fglrx. I can live without it, but not without radeonhd. So I got rid of it.
I’ve just started using Linux recently and I still can’t tell the consequences of updating my kernel. If I decide to update it to 22.214.171.124, will I have to update everything else dependent upon it? I could risk downgrading my kernel-extra and kernel-debug-extra as well–what do you say?
PS: I have enable_msi=1 added but there’s still no sound.
I never install debug apps like kernel-debug-extra. If its not needed, then IMHO remove it. Did you also install kernel-debug? Because it should not be needed either. What is the output of:rpm -qa | grep kernel
As for updating a kernel, there is always a risk associated with that. If one is using proprietary drivers, they are typically broken by a kernel update. Which means if one is using proprietary graphic, sound, wireless, webcam, … drivers, by updating one’s kernel, they could be broken. Which could mean no graphics, no wireless, no sound, … etc … Sometimes (not always) if one is using the open source drivers (such as openGL or vesa) for graphics, then they are not broken by a kernel update. Similar for audio, sometimes if one is not using very new audio hardware, then a kernel update may not break one’s sound. But no guarantees.
Its best to prepare before hand when considering a kernel update. Surf for the experiences of others with the same hardware, with the new kernel. And backup key configuration files.