Well, hello again. And here I thought my computer was running like a dream.

Picked up a new soundcard today, because, well, the one in my box was from 2000, and SuSE doesn't like it. Kind of like it doesn't like this one. (Old card was some weird Esoniq thing).

Okay, so, I get the card, put it in, etc, and the speakers crackle a little when I plug them in, which I take as a good sign, and I configure it with yast, which goes nicely, except it thinks my card is an LS and not an SE. But I get no sound, and kmix still only recognizes my onboard sound (which I've been using for months and is dreadful- nvidia nForce2, I think). So I disabled the onboard, and now kmix tells me it can't find the mixer, whatever that means.

So I do some googling, and run alsaconf, which appears to set up my card, except that during the test I hear nothing. And kmix still says no, and so does AlsaMixer. Actually, here's exactly what it says:

And Amarok says to me:

However, after running alsaconf, I started hearing static on the speakers. Not loud, just enough that I know they're on. Like they're turned up high but there's no sound to them- even though they're not up high.

So. What do I do? I'd really like to not have to go back to onboard sound. It does terrible things to my mic (noise so loud when you try to record that it overwhelms the recording).

I'd be more than happy to provide you with any additional information you might need.

EDIT: Ran alsaconf again, and this time the test sound played. Very, very loudly. Other errors still stand, though.

In YaST when you go into the soundcard setup under advanced there may be some additional options for difficult cards - can't remember exactly what's there but you could try tweaking those to see if that helps. If alsaconf can get it to work then it should be possible to get YaST to get it to start each time. Good luck!

Whenever I configure the card with alsaconf, it's -unconfigured- with yast. Like, I'll set it up in yast, run alsaconf, and when I go back to yast, it's no longer set up.

The advaced setup says "there are no options for this module".

Are you sure that the card was properly installed? What do you get if you run lspci -v? Does the card show up or not?

Just fixed the problem. Installed the developmental alsa packages, ran alsa conf again, and now everything is perfectly functional. My other alsa packages were from a repo, and I've heard it works better if you install from source. And, what do you know! It does. Thank you guys for your help anyway, though. It gave me the inspiration to NOT just chuck it back in the box and take it back to the store.

The only problem I have NOW is that the card is nicer than my speakers, which will be solved with the next influx of cash.

How did you go about fixing your problem? I have the same exact problem as you and would like to know how you were able to fix it.

Sent you a message. In case you didn't get it...

I just installed the developmental packages from the ALSA website. Downloaded the source tarballs and compiled the same way I would any other tarball- however, I did it with the arguments for my soundcard. I think the different chipset arguments are in the ALSA wiki. Right here. And then removed the RPMs that came with my SuSE install with Smart (you can also use Yast/Zen, if that still works for you), so I wouldn't have conflicting libraries.. And then I restarted, opened a terminal (Yakuake, Konsole, X Terminal, whichever you prefer), and ran .

Configured the soundcard, restarted again, and everything worked just fine.

I deeply apologize if that makes no sense at all. If it doesn't, you'd be better off asking someone with better Linux-fu, as I'm just a user, and I can only explain things as they work for me, not how they really work. Which means I don't know how to describe it simpler. ^^;

it makes sense but still doesn't work though i have't deleted the rpms yet.