What up

I'm having some trouble getting my sound to work under alsa, and I could use some help narrowing down the cause.

I'm using Suse 10.0 (with KDE) and have two sound cards; an Audigy Value and an on-board sound chip (AC97), which is disabled in the bios.

I've downloaded the latest version of alsa and have selected it in the KDE control center and the sound works, but whenever I restart my PC it doesn't, and I have to reselect ALSA (when I actually press 'apply' after selecting it, a pop-up window titled 'restarting sound system' appears and just keeps cycling thorugh the progress bar over and over until I press 'cancel', but alsa seems to load anyway -- this doesn't happen when I chose OSS though).

I'm trying to understand what's causing this, and I'd like to know if there might be a conflict between the on-board audio and the Audigy, even though the former is disabled in the BIOS. The reason I think this might be an issue is because of what modprobe tells me; that the AC97 drivers snd_AC97_codec and snd_ac97_bus are loaded, along with snd_emu10k1.

Also, even after I've stopped all sound modules using 'rmmod', I can't delete my sound card from the Yast control center, and it says the card (audigy) isn't configured. When I try to configure it, I get "The kernel module snd_emu10k1 for sound support could not be loaded...", the weird thing being that modprobe says that it IS loaded.

Anyway, does anyone think this might be because of a hardware conflict between the two soundcards? And if so, how can I stop the AC97 codecs from loading? Is it normal for ALSA to load them even though the AC97 card is disabled in the BIOS?

Here are the contents of /etc/modprobe.d/sound if it helps:

alias snd-card-0 snd-emu10k1
alias sound-slot-0 snd-emu10k1