I did a clean install of SuSE 9.1 from DVD today, I did select "All of KDE"

Hit google when I noticed the exact same symptoms with my Audigy, no sound but it 'looks' like it works, driver loaded, etc.

Saw the bit about kdemultimedia3-mixer, and running alsaconf.

Here's what I did that seems to have fixed mine:

Popped open terminal, su to root, alsaconf, just ran through it, all the default choices seemed acceptable.

Immediately XMMS starts playing sound, KDE system notifications work, everything works.

I then removed (via YaST2) the kdemultimed3-mixer package, then I rebooted.

When the system came back up, I remapped the SMB share my MP3s are on, and loaded XMMS, and it plays fine.

If it matters, the system is:

Athlon XP 1700+
Shuttle AK31A (v3.1, KT266A)
512MB of PC2100 (random brand)
SB Audigy (OEM)
ASUS V8420 128MB
Seagate Barracuda 40GB ATA100

Kmix isn't the problem. It actually contains the gui frontend for speaker controls other than just the master. I stated out w/ no sound, using an Audigy 2, and made sure all alsa tools were installed. Next, I went into the control center, Sound & Multimedia, Sound System, Hardware tab, and selected the audio device from "autodect" to "Advanced Linux Sound...". Next I ran aslaconfig from a terminal. Finally, I ran Kmix, clicked Advanced in the lower-left corner, and made sure "3D Control" and "Audigy Analog" were selected. From there, I turned the volume up on pretty much everything (just to be safe), except for the master. Voila! Sound in Suse 9.1 using an Audigy 2. Haven't tried xmms, but I've read you have to make sure to select the ALSA pluging from its right-click menu...

I only deleted the mixer package because someone else (in another thread I think) had suggested that it might be making some configuration change that was a problem for Audigy users.

I must not use that program anyway, because I didn't notice anything missing after I deleted it. :)


As for xmms, after I got the sound working, I left its configuration at default (ie the Autodetect plugin).

I'm just glad the fix was relatively painless, whatever the proper fix is. :)

The advantage of having kmix is the control of other speakers (othere than just the main). So, if you want more than two speaker support, you might need kmix.... fyi. ;)

mine seemed to be playing out of all four, and that's all i have, so it already works the way I want, but but others with more complex systems I can see the need.

Yes, optimalprimer is right. The problem lies with a simple mixer setting in the alsa mixer. I had the same problem but found a solution on the internet:
The reason that for some of you deleting the kmix mixer package worked, is probably that that slider just wasn't there anymore to mess things up :)

Anyway, a bit late for this reply maybe but i thought i should mention it.

KMix solution
 

Hi, I had exactly the same problem you described. :confused:

The way solved it was to open KMIX (not KAMIX) and toggle the Analog/Digital Output Jack . You need to check the "Advanced" box of KMIX in order to do this.

So maybe you can also solve your problems using KMix, too.

I've also set KMix as my system tray volume control instead of KAMix.

Hope it helps

:newbie:

Hi - is there a common link here?
Kernel 2.6.x, SuSE, VIA onboard sound etc?

You have problems with a VIA onboard sound card?
I had some troubles getting VIA AC 97 to work but I finally got it by
- opening yast2 --> hardware --> sound
- setting the option "ac97_quirk" of the sound cart to "2"
- when exiting yast2 there must be a question whether the sound system shall be restarted. restart it and exit the sound configuration tool of yast2 (this is important).
- running alsamixer and unmuting and raising the following channels: "Master", "PCM", and "VIA DXS" (the latter won't be visible on startup so you have to scroll there first.)

The only problem I have now is that I always have to set these settings again when I restart my machine. I'm currently trying to find out how to access the sound configuration tool of yast2 by command line, so that I can do this automatically on every startup, but this seems to be difficult. Any hints are welcome.