ok. so i figured out that the soundcard in the system was a C-Media 8330 not an sb-16. i also figured out that fedora 2 DOES come with alsa kernel modules installed. it is just a matter of loading them and modifying modprobe.conf.
after boot with the following modprobe.conf file:
HTML Code:
<pre>
[root@localhost root]# more /etc/modprobe.conf
alias eth0 tulip
alias usb-controller uhci-hcd
# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-cmi8330
# module options should go here
# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
</pre>
i get the following messages from dmesg pertaining to the sound card:
HTML Code:
<pre>
isapnp: Scanning for PnP cards...
pnp: CMI8330 quirk - fixing interrupts and dma
isapnp: Card 'CMI8330. Audio Adapter'
isapnp: 1 Plug & Play card detected total
.
.
.
pnp: Device 00:01.00 activated.
pnp: Device 00:01.03 activated. (these are the last 2 kernel messages)
</PRE>
and the following output from lsmod:
HTML Code:
<pre>
[root@localhost root]# lsmod
Module Size Used by
snd_cmi8330 10564 0
snd_sb16_dsp 7680 1 snd_cmi8330
snd_ad1848_lib 12416 1 snd_cmi8330
snd_pcm 68872 3 snd_cmi8330,snd_sb16_dsp,snd_ad1848_lib
snd_page_alloc 7940 1 snd_pcm
snd_timer 17156 1 snd_pcm
snd_sb_common 12032 2 snd_cmi8330,snd_sb16_dsp
snd 38372 6 snd_cmi8330,snd_sb16_dsp,snd_ad1848_lib,snd_pcm,snd_timer,snd_sb_common
soundcore 6112 1 snd
parport_pc 19392 1
lp 8236 0
parport 29640 2 parport_pc,lp
autofs4 10624 0
sunrpc 101064 1
tulip 36256 0
floppy 47440 0
sg 27552 0
microcode 4768 0
dm_mod 33184 0
sr_mod 13348 0
sd_mod 16384 0
usb_storage 55392 1
scsi_mod 91344 4 sg,sr_mod,sd_mod,usb_storage
usblp 9476 0
uhci_hcd 23708 0
ipv6 184288 10
ext3 102376 3
jbd 40216 1 ext3
</pre>
so everything looks correct, but i still get no sound. i am running kernel2.6.5-1.358 and i have not run up2date yet.
has anyone else had problems with this driver? is there any workaround?
thanks much.
pete.