On Sunday 04 July 2004 01:14 pm, Christoph Sticksel wrote: > Everything sound-related is loaded and lsmod shows a whole bunch of snd_* > modules, snd, soundcore, opl3sa2 and ad1848 are there as well.
> If I do a "modprobe -r opl3sa2" and reload it with "modprobe opl3sa2" I see I'm not familiar with that particular hardware, but this sounds like your problem right there. You need soundcore, and then every other module you load should start with snd-. You're trying to modprobe an OSS module (opl3sa2), and that's doomed to fail if you've got snd loaded already. Pick one or the other, and preferably pick ALSA (snd-opl3sa2). (It looks like maybe you want snd-ymfpci too, maybe? I don't know what modules you need, but looks like a likely candidate to me.) Are you by chance using the discover utility to auto detect your hardware? I've noticed it's not clever enough to realize that OSS and ALSA modules are oil and water, and it will load both unless you take steps to prevent this. It leaves you with a mess you can't get out of without rebooting. I don't use discover for this very reason. It's more trouble to coax it into not doing something stupid than it is to avoid it altogether. -- Michael McIntyre ---- Silvan <[EMAIL PROTECTED]> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]