I am a member of the audio group. alsa is installed but alsaconf doesnot find anything. However, when i run a lspci -v it shows my soundblaster:

0000:02:02.0 Multimedia audio controller: Creative Labs [SB Live! Value] EMU10k1 X
Subsystem: Creative Labs: Unknown device 1003
Flags: bus master, medium devsel, latency 64, IRQ 185
I/O ports at dcc0 [size=32]
Capabilities: [dc] Power Management version 2

oh and nothing is evidently showing up in lsmod that has the snd prefix?!? Where the heck did I screw this up?

Please help!

thanks
murfman

good.If ur sound card is not supported,then the only option is to get newer kernel.
Because 2.6.8 is looks olderu know?How new is ur Board?

If you are not comfortable with compiling kernel,then only idea i can give u is get a ubuntu Linux either Live cd or Installable.And copy the kernel device drivers from /usr/modules/kernel{version} to ur Debian.Also make sure to copy initrd and vmlinuz from /boot..Make sure ur ubuntu is playing sound..

Or get newest alsamodules from net and compile it.
Hope this helps.

I am running a Creative SoundBlaster Live! it is probaly 4 or 5 years old now but still a good card. So updating the kernel is the only option that I have? Can you tell me what the problem is? Is it that alsa doesn't have the modules for this card or what? Just curious. Thanks,
MurfMan

try this..
The kernel driver name looks like "emu10k1".Try u have this module in running kernel.
Pls look at those url's.Its very easy to setup a sound.Also Search in Google a lot stuff u have."

I have a soundblaster 16 and 2.6.8-2 kernel and after using alsaconf or snd conf (can't remember) it works fine. I'm no 'pert but think I would use aptitude to reinstall the alsa packages again. Steve

OK this is what an lsmod says now:

snd_emu10k1 80776 0
snd_rawmidi 23204 1 snd_emu10k1
snd_pcm_oss 48168 0
snd_mixer_oss 16640 1 snd_pcm_oss
snd_pcm 85384 2 snd_emu10k1,snd_pcm_oss
snd_timer 23300 1 snd_pcm
snd_seq_device 7944 2 snd_emu10k1,snd_rawmidi
snd_ac97_codec 59268 1 snd_emu10k1
snd_page_alloc 11144 2 snd_emu10k1,snd_pcm
snd_util_mem 4608 1 snd_emu10k1
snd_hwdep 9092 1 snd_emu10k1
snd 50660 10 snd_emu10k1,snd_rawmidi,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_seq_device,snd_ac97_codec,sn d_util_mem,snd_hwdep
soundcore 9824 1 snd
e100 30080 0

but I still have no sound. When i run the alsaconf it will find nothing and wipe these modules out. The kernel doesn't need to be recompiled since ithas the soundcore loaded.

But I still have no sound..... Sorry for being dense here guys but I am just not getting it.

I think I would just check this,
launch XMMS
open pref's
Check is selected for ALSA
If not change to ALSA
try again after rebooting

Other than that no ideas. Personally I went through the same annoying dramas you are undergoing. I am a newby and it took me ages until I did the Kernel update Fun isn't it?

hey looks gr8 now.Yr modules are loaded.But i can warn that sometimes wrong modules getting loaded.I m not sure this one is correct.But we can check it out.
You told that u r not getting sound at all.fine.
what result u r getting running "alsamixer" command.I can really help if u post it.

Read my post in the thread listed below and check the contents of files under /proc/asound.
Another thing that shouldn't be missed out is, by default when alsa starts the first time, it starts with your soundcard muted. Therefore, you will need to use a mixer to unmute your soundcard - alsamixer would be a good choice.

You will need to have alsa and alsactl properly configured for soundcard to work and to make sure that alsa doesn't start with the soundcard muted every time you boot your system. Alsa comes with a utility called alsactl to store and restore the mixer settings.

i was unable to run alsamixer because it said that alsa was unable to find a device. I ended up getting pissed and installed the Ubuntu 6.02 install and it found all of my hardware on the first try lol go figure.

Thanks for the help guys!!