Ok, … that might explain a few things …
I note:
!!ALSA Version
!!------------
Driver version: 1.0.22.1
Library version: 1.0.24.1
Utilities version: 1.0.23
Clearly your driver was NOT updated to 1.0.24. Only the library. Thats not IMHO a good practise. If you are going to update the library you should also update the driver.
I also note HP-Pavilion KQ495AA-A2L a6500f on a 64-bit openSUSE-11.3 with the 2.6.34.7-0.7-desktop kernel. Wrt sound devices, I note:
!!Soundcards recognised by ALSA
!!-----------------------------
0 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xefff4000 irq 23
1 [DX ]: AV200 - Xonar DX
Asus Virtuoso 100 (rev 2) at 0xde00, irq 16
!!PCI Soundcards installed in the system
!!--------------------------------------
00:09.0 Audio device: nVidia Corporation MCP73 High Definition Audio (rev a1)
05:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio]
So it appears to me you have a sound device on the motherboard, and perhaps as well an PCI-e sound card. The first sound device is a Realtek ALC1200 and the second sound device a Xonar DX.
By default, sound will come out of the 1st sound device which your PC has setup as the nVidia MCP73 HDA (ALC1200) and NOT your Xonar DX. So its possible that was the original problem, and its now been made worse by the custom compile of the alsa library.
Plus, when I look in the 50-sound.conf configuration file:
cat /etc/modprobe.d/50-sound.conf
options snd slots=snd-hda-intel
# WL76.VpL4uDMMuV9:MCP73 High Definition Audio
alias snd-card-0 snd-hda-intel
I see no mention of the Xonar DX which makes me think it was not configured by yourself with the YaST configuration tool ? Did you try YaST > Hardware > Sound and make the Xonar DX the 1st sound device (see lower right corner for options of that menu) and also did you configure the Xonar DX in YaST ?
I also note many pulse audio applications, where pulse audio is a layer on top of alsa. I assume that means your PC has a gnome desktop. What did you do to try to configure gnome? Did you install and try the pavucontrol app ?
If the 1.0.24 alsa library has messed up the interface to the 1.0.22.1 alsa driver, I’m not sure what to recommend. A new install would be cleanest and dependant on how much custom configuring you have done possible quickest.
Else you could try to update alsa via rpm (instead of custom compiling) per the guidance here: SDB:Alsa-update - openSUSE … ie using that guide I linked, update libasound2, alsa-utils, alsa-oss, alsa-plugins, alsa-plugins-pulse-32bit, alsa-plugins-32bit, alsa-oss-32bit, alsa-devel, alsa-1.0.23, and alsa-plugins-pulse … and also install the alsa-driver-kmp-desktop version that is consistent with your kernel …
… but given whats been done so far, I don’t know if that will work. You still MUST ensure your default sound device is made the Xonar DX (although if you install pavucontrol one can tune that).
Something you MUST learn about Linux is there are risks when one custom compiles, which is multiplied 100 fold if one does not know what they are doing. Anything you custom compile is NOT handled by the rpm database that is behind openSUSE software management, and hence your install is now subject to all sorts of hiccups that an advanced user would handle with no problem, but would drive a new user to distraction and to leave Linux.
