If there's no wl.ko on my system... where is the kernel loading it from?
Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If there's no wl.ko on my system... where is the kernel loading it from?
Hi!
I'm having this fight with broadcom's STA drivers. They keep crashing my machine on Natty (using the bcmwl package from repositorioes)... so I decided to build it myself from the source from broadcom's page but I've been unable to keep the kernel from loading a certain wl module that I just can't find.
The bcmwl package has been removed, made sure the ko is not on the module directory anymore, even checked that it's not on the initramfs image but still when the computer boots, the module has been loaded (even though it has been blacklisted on /etc/modprobe.d/blacklist.conf).
WHat am I missing? Why is the kernel loading this module nevertheless?
May be there is some other module that is dependent on this on, which is causing this also to be loaded, (Which modprobe would do).
So if you know any other dependent modules try blacklisting them too and try.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.