How about going a step further and explaining how to keep these modules from loading in the first place? Every time I boot I have to go to a console prompt and unload the OSS drivers manually and then rmmod/insmod the alsa drivers. I've searched through all of my startup files and I can't find any reference to the oss modules anywhere. They are not referred to within my modprobe.conf/modules.conf either. It's funny how the system knows which modules I don't want and manages to load them after every reboot. I realize I can blacklist them, but then my log fills up with errors as this ghost script attempts to load them anyway. Any ideas on where to look?

-Gary


On Tue, 2003-09-23 at 04:28, Nick Peaden wrote:
If your kernel modules fail to load, it is probably due to OSS drivers
being loaded when you try to modprobe alsa in! UNload OSS and REload ALSA.



------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user

_________________________________________________________________
Instant message with integrated webcam using MSN Messenger 6.0. Try it now FREE! http://msnmessenger-download.com




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to