well, I've managed to download and compile my ALSA drivers and stuff, everything went just fine, I did it all by the book...

but when I ran the:
modprobe snd-opl3sa2;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe snd-seq-oss

it gave me a bunch of error messages:

/lib/modules/2.4.20-8/kernel/sound/isa/snd-opl3sa2.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.20-8/kernel/sound/isa/snd-opl3sa2.o: insmod /lib/modules/2.4.20-8/kernel/sound/isa/snd-opl3sa2.o: failed
/lib/modules/2.4.20-8/kernel/sound/isa/snd-opl3sa2.o: insmod snd-opl3sa2 failed



how do I fix this?

did you remember to modprobe soundcore before all the other ones?

I've had this, and usually its because your soundcard has allready been loaded (usually with the wrong driver, hence irq conflict message).

Check modules.conf and rc.local incase you have a conflicting driver in there. Once i removed that, everything modprobed perfectly. That was on both slack 9 and redhat 8 and 9.

Hope that helps.

jpbarto: yes, I did, and it outputted that it worked.. don't remember the exact version numers and stuff now, but I did..

Evilone: You may be right, but how do I know which drivers are the right ones and which ones are wrong?
Should I delete EVERYTHING in those files or what?
A few days ago, I did tamper with modules.conf, but now as I had problems with installing ALSA, I changed it back to the way it was before I changed it...
But what to do?

to see what modules are running type 'lsmod'. this will list all modules in your kernel. See any that look like sound drivers? All the presently installed sound drivers will / should reside in /lib/modules/<kernel-version>/kernel/drivers/sound

Evilone: good call about drivers already being loaded.
ziggamon: if lsmod proves unfruitful the drivers may be compiled into the kernel. However I'm not a Redhat guy so I'm not sure what is common practice for their kernels (do they go for lots of modules out the box or for a really-huge-support-everything kernel?)

yes, actually, when I ran lsmod I found many sound-related modules:


adlib_card 1252 0 (unused)
opl3 14784 0 [adlib_card]
sound 74228 0 [adlib_card opl3]
soundcore 6404 2 [sound]


what do I do with them now?

I tried to comment everything that had to do with sound drivers in modules.conf and now lsmod doesn't output any sound-related modules...

and the modprobe gives the same errors...

I wanna make sure I've got this str8...

you do a fresh reboot and there's no sound modules loaded because you commented them out in modules.conf.

then you modprobe soundcore and begin modprobing snd-opl3sa2 and then you still get the error mentioned in the first post. is that right?

what type of card do you have? I couldn't find any on alsa's matrix that uses the opl3sa2 driver.

scratch that... had to dig deeper.

actually, I hadn't modprobed soundcore since I commented away everything there was in modules.conf

now I tried to modprobe soundcore, and it didn't output a thing. Nothingl.

I have a Yamaha YMF719 I think, but I'm not sure

if you modprobe soundcore and it doesn't output anything... doesn't mean its not loaded... take a look as lsmod after you modprobe soundcore to see if its loaded.

You were right, after modprobing soundcore, it was found by lsmod...

but what do I do now?

now try to modprobe snd-opl3sa2 and cross your fingers.

nope... same errors as before