LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 03-11-2014, 07:30 PM   #1
kcynice
Member
 
Registered: Sep 2008
Posts: 94

Rep: Reputation: 16
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?
 
Old 03-11-2014, 09:05 PM   #2
evo2
Guru
 
Registered: Jan 2009
Location: Japan
Distribution: Debian, SL
Posts: 5,098

Rep: Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100
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.
 
Old 03-11-2014, 09:11 PM   #3
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,428

Rep: Reputation: 407Reputation: 407Reputation: 407Reputation: 407Reputation: 407
Quote:
Originally Posted by evo2 View Post
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.
 
Old 03-11-2014, 09:18 PM   #4
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,428

Rep: Reputation: 407Reputation: 407Reputation: 407Reputation: 407Reputation: 407
Quote:
Originally Posted by kcynice View Post
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
Code:
man modprobe.d
. (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.
 
Old 03-11-2014, 09:28 PM   #5
evo2
Guru
 
Registered: Jan 2009
Location: Japan
Distribution: Debian, SL
Posts: 5,098

Rep: Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100
Hi,
Quote:
Originally Posted by Richard Cranium View Post
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.
 
Old 03-11-2014, 09:46 PM   #6
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, Slackware-14.1, PCBSD-10.0
Posts: 2,860
Blog Entries: 15

Rep: Reputation: 743Reputation: 743Reputation: 743Reputation: 743Reputation: 743Reputation: 743Reputation: 743
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.
 
Old 03-11-2014, 10:08 PM   #7
kcynice
Member
 
Registered: Sep 2008
Posts: 94

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by Richard Cranium View Post
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
Code:
man modprobe.d
. (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'.
 
Old 03-12-2014, 12:10 AM   #8
Paulo2
Member
 
Registered: Aug 2012
Distribution: Slackware current(32) (started with 13.37(32))
Posts: 122

Rep: Reputation: 27
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
How to control the driver order be loaded by linux skiron.liu Linux - Hardware 5 04-06-2011 08:26 AM
How can I see what driver is loaded for a given device? lumix Linux - Hardware 5 03-17-2008 11:45 AM
Wrong driver loaded for USB device redwaterblues Linux - Hardware 0 04-29-2005 07:18 PM
remote control device driver infamous41md Programming 5 03-09-2004 11:47 AM
How to configure a eth0 device or driver to be loaded at boot montfer Linux - Networking 5 12-29-2003 03:19 AM


All times are GMT -5. The time now is 01:33 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration