Slackware This Forum is for the discussion of Slackware Linux.
|
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
03-11-2014, 08:30 PM
|
#1
|
Member
Registered: Sep 2008
Distribution: Slackware
Posts: 156
Rep:
|
How to control which device driver should be loaded to use?
My HP notebook has a "Broadcom Corporation BCM4322 802.11a/b/g/n Wireless" adapter, and my system is Slackware 14.1.
And, the default driver was not suite for that device, i have to install a new module named wl from slackbuilds.org: broadcom-sta-6.30.223.141.
Then, I have to run two command every time of booting the system:
/sbin/modprobe -r b44 b43 b43legacy ssb brcmsmac
/sbin/modprobe wl
And, I don't like that, I hope the system can do all works by itself, recognize the device and load the right driver. Or is there a way that, I can control which drivers should be loaded or not?
|
|
|
03-11-2014, 10:05 PM
|
#2
|
LQ Guru
Registered: Jan 2009
Location: Japan
Distribution: Mostly Debian and CentOS
Posts: 6,726
|
Hi,
yes you can blacklist the b44 (and friends) and tell the system to load wl at boot time. Exactly how to do that is distro specific, and not being a slacker I don't know the answer off the top of my head. However, I do know of the existence of the much touted slackbook, so I had a look:
http://www.slackbook.org/html/system...KERNEL-MODULES
An explicit answer is not given there, but the very last sentence provides a tantilising hint :-)
HTH,
Evo2.
|
|
|
03-11-2014, 10:11 PM
|
#3
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
Quote:
Originally Posted by evo2
Exactly how to do that is distro specific, and not being a slacker I don't know the answer off the top of my head.
|
Then why did you answer on a Slackware forum?
I'm certainly willing to believe that you mean well, but perhaps you should provide advice about things for which you do have knowledge.
|
|
|
03-11-2014, 10:18 PM
|
#4
|
Senior Member
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860
|
Quote:
Originally Posted by kcynice
My HP notebook has a "Broadcom Corporation BCM4322 802.11a/b/g/n Wireless" adapter, and my system is Slackware 14.1.
And, the default driver was not suite for that device, i have to install a new module named wl from slackbuilds.org: broadcom-sta-6.30.223.141.
Then, I have to run two command every time of booting the system:
/sbin/modprobe -r b44 b43 b43legacy ssb brcmsmac
/sbin/modprobe wl
And, I don't like that, I hope the system can do all works by itself, recognize the device and load the right driver. Or is there a way that, I can control which drivers should be loaded or not?
|
In this case, you would want to blacklist the b44, b43, b43legacy, ssb, and brcmsmac kernel modules by adding them to /etc/modprobe.d/blacklist.conf (or by adding an additional file in the same directory which does so) and by adding a new file in the same directory that contains a line such as "alias <devicename> wl" where <devicename> is probably wlan0.
Please read the modprobe.d man page by running the command . (That's what the README file in /etc/modprobe.d tells you to do.)
If you have further questions about this, please ask. Someone around here will answer you.
|
|
|
03-11-2014, 10:28 PM
|
#5
|
LQ Guru
Registered: Jan 2009
Location: Japan
Distribution: Mostly Debian and CentOS
Posts: 6,726
|
Hi,
Quote:
Originally Posted by Richard Cranium
Then why did you answer on a Slackware forum?
|
- Because the question had gone unanswered for more than 1.5 hours (on a subforum that is usually extremely active)
- The question was of a general nature (although the answer is distro specific)
- The answer could be found in the documentation with a matter of minutes - it is usually best to show people how to find a solution instead of just handing it to them.
Quote:
I'm certainly willing to believe that you mean well, but perhaps you should provide advice about things for which you do have knowledge.
|
See the above.
Cheers,
Evo2.
|
|
|
03-11-2014, 10:46 PM
|
#6
|
LQ Guru
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,564
|
Edit:
/etc/modprobe.d/blacklist.conf
and add these lines:
Code:
blacklist b44
blacklist b43
blacklist b43legacy
blacklist ssb
blacklist brcmsmac
udev will then autoload the wl driver from now on.
|
|
|
03-11-2014, 11:08 PM
|
#7
|
Member
Registered: Sep 2008
Distribution: Slackware
Posts: 156
Original Poster
Rep:
|
Quote:
Originally Posted by Richard Cranium
In this case, you would want to blacklist the b44, b43, b43legacy, ssb, and brcmsmac kernel modules by adding them to /etc/modprobe.d/blacklist.conf (or by adding an additional file in the same directory which does so) and by adding a new file in the same directory that contains a line such as "alias <devicename> wl" where <devicename> is probably wlan0.
Please read the modprobe.d man page by running the command . (That's what the README file in /etc/modprobe.d tells you to do.)
If you have further questions about this, please ask. Someone around here will answer you.
|
Thanks for your reply, I have a look from "man modprobe.d" and add a file at /etc/modprobe.d, named wireless.conf:
Code:
blacklist b44 b43 b43legacy ssb brcmsmac
install wl
and got a warning at booting time:
Code:
libkmod: kmod_config_parse: /etc/modprobe.d/wireless.conf line 2: ignoring bad line starting with 'install'
libkmod: kmod_config_parse: /etc/modprobe.d/wireless.conf line 2: ignoring bad line starting with 'install'.
|
|
|
03-12-2014, 01:10 AM
|
#8
|
Member
Registered: Aug 2012
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 961
|
Maybe isn't the case for this broadcom driver, but I have a fax-modem card driver that
isn't loaded automatically, so I added the driver in /etc/rc.d/rc.modules-...
Am I right doing this? So far it's working.
|
|
|
All times are GMT -5. The time now is 04:22 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|