How to install native broadcom drivers for BCM4311, BCM4312, BCM4321, and BCM4322

**n00bz** · September 16th, 2009

Originally Posted by Ayuthia

It means that you have a 32 bit machine. The 64-bit versions are x86_64 and ia64 and the 32-bit versions are i386, i486, i586, i686.

-.-" i'm an idiot....gahh back to the first step

**A_Fiachra** · September 21st, 2009

Originally Posted by mike_l

After searching for ways to get wireless working on my HP dv9000, I came across this thread. Apparently, Broadcom offers linux drivers for it's 802.11a/b/g/n cards (chipsets BCM4311, BCM4312, BCM4321, and BCM4322, in both 32 and 64 bit).

Figuring that there are other people out there with the same problem: here's the steps I took to install the native drivers:

Download the appropriate driver
I downloaded the 64 bit version of the driver from http://www.broadcom.com/support/802.11/linux_sta.php
It's important that you get the correct version, as the 32 and 64 bit versions are not compatible.
Make the .ko file
First, make a temporary directory
Code:
```
mkdir wdriver
```
... and place the downloaded package into it (hybrid-portsrc-_64_5_10_27_6.tar.gz, or hybrid-portsrc-x86_32_5_10_27_6.tar.gz for the 32 bit version)
Then 'cd' into the temporary directory and un-tar the file.
Code:
```
cd wdriver
tar -xzf hybrid-portsrc-x86_64_5_10_27_6.tar.gz
```
Now, we want to make the wl.ko file, so we enter:
(<2.6.xx.xx> is your kernel version: mine was "2.6.24-19-generic". Use tab-completion to find yours.)
Code:
```
make -C /lib/modules/<2.6.xx.xx>/build M=`pwd` clean
make -C /lib/modules/<2.6.xx.xx>/build M=`pwd`
```
You should now have a file "wl.ko" located in the temporary directory you created (wdriver).
Make sure that no other wireless drivers are installed
Enter: (Don't worry if there are any errors returned)
Code:
```
sudo rmmod bcm43xx
sudo rmmod b43
sudo rmmod b43legacy
```
I also uninstalled ndiswrapper, just to be sure:
Code:
```
sudo rmmod ndiswrapper
sudo apt-get remove ndiswrapper-common
```
Test the new wireless driver
Now, lets test out our new wireless driver. Enter:
Code:
```
sudo modprobe ieee80211_crypt_tkip
sudo insmod wl.ko
```
If it worked, and you can see/connect to wireless networks, you'll want to:
Make your changes permanent.
First, you may want to blacklist the old b43/b43legacy/bcm43xx drivers. Enter:
Code:
```
sudo gedit /etc/modprobe.d/blacklist
```
and add the following to the end of the file:
Code:
```
blacklist b43
blacklist b43legacy
blacklist bcm43xx
```
Now, let's move the wireless driver somewhere more permenant:
Code:
```
sudo mkdir /lib/modules/<2.6.xx.xx>/wlan
sudo mv wl.ko /lib/modules/<2.6.xx.xx>/wlan
```
Now, lets make it so that the driver and wireless encryption module are loaded on startup. Enter:
Code:
```
sudo gedit /etc/modules
```
and add
Code:
```
ieee80211_crypt_tkip
```
to the bottom.

Now run:
Code:
```
sudo gedit /etc/rc.local
```
and add
Code:
```
sudo insmod /lib/modules/<2.6.xx.xx>/wlan/wl.ko
```
at the end of the file, but before the line "exit 0"

That's it. If I've made any errors, please let me know. Thanks.

I've been following this thread with interest, since I have a wireless problem with the same card.

when I run make, I get:

Code:

 make -C /lib/modules/`uname -r`/build M=`pwd`
make: Entering directory `/usr/src/linux-headers-2.6.28-15-generic'
  LD      /home/alee/download/hybrid_wl/built-in.o
  CC [M]  /home/alee/download/hybrid_wl/src/wl/sys/wl_linux.o
  CC [M]  /home/alee/download/hybrid_wl/src/wl/sys/wl_iw.o
  CC [M]  /home/alee/download/hybrid_wl/src/shared/linux_osl.o
  LD [M]  /home/alee/download/hybrid_wl/wl.o
  Building modules, stage 2.
  MODPOST 1 modules
WARNING: modpost: missing MODULE_LICENSE() in /home/alee/download/hybrid_wl/wl.o
see include/linux/module.h for more information
  CC      /home/alee/download/hybrid_wl/wl.mod.o
  LD [M]  /home/alee/download/hybrid_wl/wl.ko
make: Leaving directory `/usr/src/linux-headers-2.6.28-15-generic'

Well, it's a warning ... I ignore it and move on ...

Code:

cat /etc/modules 
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

lp
wl

Ok, then, looking at my history I see

Code:

  481  sudo rmmod bcm43xx
  482  sudo rmmod b43
  483  sudo rmmod b43legacy
  484  rmmod ndiswrapper
  485  sudo apt-get remove ndiswrapper-common
  486  sudo modprobe ieee80211_crypt_tkip
  487  sudo insmod wl.ko 
  488  sudo depmod -a
  489  echo wl | sudo tee -a /etc/modules 
  490  sudo modprobe wl
  491  sudo insmod /lib/modules/`uname -r`/wlan/wl.ko
  492  sudo mkdir /lib/modules/`uname -r`/wlan/
  493  sudo mv wl.ko /lib/modules/`uname -r`/wlan/
  494  sudo insmod /lib/modules/`uname -r`/wlan/wl.ko
  495  iwlist channel
  496  iwlist
  497  iwlist scan

and iwlist scan reveals :

Code:

iwlist scan
lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

eth1      Interface doesn't support scanning.

pan0      Interface doesn't support scanning.

?????!!!!

So I try:

Code:

alee@dell-desktop:~/download/hybrid_wl$ sudo ifconfig eth1 down
alee@dell-desktop:~/download/hybrid_wl$ sudo dhclient -r eth1
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:22:5f:f9:80:9c
Sending on   LPF/eth1/00:22:5f:f9:80:9c
Sending on   Socket/fallback
alee@dell-desktop:~/download/hybrid_wl$ sudo ifconfig eth1 up
alee@dell-desktop:~/download/hybrid_wl$ sudo iwconfig eth1 essid "gone_viral"
alee@dell-desktop:~/download/hybrid_wl$ sudo iwconfig eth1 mode Managed
alee@dell-desktop:~/download/hybrid_wl$ sudo dhclient eth1
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:22:5f:f9:80:9c
Sending on   LPF/eth1/00:22:5f:f9:80:9c
Sending on   Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
resolvconf: Error: /etc/resolv.conf must be a symlink
 * Reloading /etc/samba/smb.conf smbd only
   ...done.

And ... nothing

Code:

$ sudo iwlist scan
lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

eth1      Failed to read scan data : Invalid argument

pan0      Interface doesn't support scanning.

alee@dell-desktop:~/download/hybrid_wl$

The Network Manager still says "Wireless Networks -> device not managed" and if I edit connections and create a wireless account for eth1, the Network Manager doesn't store it. That is, I open Network Manager again and the eth1 interface entry is gone!!!

I'm out in the weeds here.

Any help is greatly appreciated!

-- AF

**Ayuthia** · September 21st, 2009

Originally Posted by A_Fiachra

Code:

alee@dell-desktop:~/download/hybrid_wl$ sudo ifconfig eth1 down
alee@dell-desktop:~/download/hybrid_wl$ sudo dhclient -r eth1
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:22:5f:f9:80:9c
Sending on   LPF/eth1/00:22:5f:f9:80:9c
Sending on   Socket/fallback
alee@dell-desktop:~/download/hybrid_wl$ sudo ifconfig eth1 up
alee@dell-desktop:~/download/hybrid_wl$ sudo iwconfig eth1 essid "gone_viral"
alee@dell-desktop:~/download/hybrid_wl$ sudo iwconfig eth1 mode Managed
alee@dell-desktop:~/download/hybrid_wl$ sudo dhclient eth1
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth1/00:22:5f:f9:80:9c
Sending on   LPF/eth1/00:22:5f:f9:80:9c
Sending on   Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 16
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
resolvconf: Error: /etc/resolv.conf must be a symlink
 * Reloading /etc/samba/smb.conf smbd only
   ...done.

It looks like you might have a problem with /etc/resolv.conf. Have you modified it?

**A_Fiachra** · September 21st, 2009

Originally Posted by Ayuthia

It looks like you might have a problem with /etc/resolv.conf. Have you modified it?

Not intentionally.

NetworkManager added a few nameservers -- how rude! (I have been running ethernet on eth0)

But NM still says that the wireless card is not managed.

**Ayuthia** · September 21st, 2009

Originally Posted by A_Fiachra

Not intentionally.

NetworkManager added a few nameservers -- how rude! (I have been running ethernet on eth0)

But NM still says that the wireless card is not managed.

Can you post the results of the following:

Code:

lshw -C network
lsmod|grep -e b43 -e ssb -e wl -e ssb
dmesg|grep -e b43 -e wl

This will help us see what your wireless card is trying to use, what modules the system is trying to use, and if any error messages are showing up.

**A_Fiachra** · September 22nd, 2009

Happy to!

THanks for the assistance

Code:

sudo lshw -C network
  *-network               
       description: Wireless interface
       product: BCM4312 802.11b/g
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:0c:00.0
       logical name: eth1
       version: 01
       serial: 00:22:5f:f9:80:9c
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=wl0 driverversion=5.10.91.9 latency=0 module=wl multicast=yes wireless=IEEE 802.11bg
  *-network
       description: Ethernet interface
       product: 88E8040 PCI-E Fast Ethernet Controller
       vendor: Marvell Technology Group Ltd.
       physical id: 0
       bus info: pci@0000:09:00.0
       logical name: eth0
       version: 13
       serial: 00:25:64:56:59:35
       size: 100MB/s
       capacity: 100MB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.22 duplex=full firmware=N/A ip=192.168.1.101 latency=0 link=yes module=sky2 multicast=yes port=twisted pair speed=100MB/s
  *-network DISABLED
       description: Ethernet interface
       physical id: 2
       logical name: pan0
       serial: 46:12:a0:c7:a2:80
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes

Code:

sudo lsmod|grep -e b43 -e ssb -e wl -e ssb
wl                   1283488  0 
ieee80211_crypt        13444  2 ieee80211_crypt_tkip,wl

Code:

dmesg|grep -e b43 -e wl
[   12.067863] wl: module license 'unspecified' taints kernel.
[   12.070074] wl 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[   12.070327] wl 0000:0c:00.0: setting latency timer to 64
[  272.248462] wl 0000:0c:00.0: PCI INT A disabled
[  273.000329] wl 0000:0c:00.0: restoring config space at offset 0xf (was 0x100, writing 0x104)
[  273.000390] wl 0000:0c:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xf69fc004)
[  273.000402] wl 0000:0c:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
[  273.000419] wl 0000:0c:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100106)
[  273.000486] wl 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[  273.000497] wl 0000:0c:00.0: setting latency timer to 64
[ 3986.108450] wl 0000:0c:00.0: PCI INT A disabled
[ 3986.888321] wl 0000:0c:00.0: restoring config space at offset 0xf (was 0x100, writing 0x104)
[ 3986.888381] wl 0000:0c:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xf69fc004)
[ 3986.888393] wl 0000:0c:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
[ 3986.888410] wl 0000:0c:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100106)
[ 3986.888477] wl 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 3986.888489] wl 0000:0c:00.0: setting latency timer to 64

Interesting about that license warning ... the Broadcom driver builds with a warning that I can't clear up that shows up in dmesg.

Thanks again .. as you can see, I only have the wl driver installed -- I am starting to suspect the driver or the card is hosed.

--AF

**Ayuthia** · September 22nd, 2009

Originally Posted by A_Fiachra

Happy to!

THanks for the assistance

Code:

sudo lshw -C network
  *-network               
       description: Wireless interface
       product: BCM4312 802.11b/g
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:0c:00.0
       logical name: eth1
       version: 01
       serial: 00:22:5f:f9:80:9c
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=wl0 driverversion=5.10.91.9 latency=0 module=wl multicast=yes wireless=IEEE 802.11bg
  *-network
       description: Ethernet interface
       product: 88E8040 PCI-E Fast Ethernet Controller
       vendor: Marvell Technology Group Ltd.
       physical id: 0
       bus info: pci@0000:09:00.0
       logical name: eth0
       version: 13
       serial: 00:25:64:56:59:35
       size: 100MB/s
       capacity: 100MB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=sky2 driverversion=1.22 duplex=full firmware=N/A ip=192.168.1.101 latency=0 link=yes module=sky2 multicast=yes port=twisted pair speed=100MB/s
  *-network DISABLED
       description: Ethernet interface
       physical id: 2
       logical name: pan0
       serial: 46:12:a0:c7:a2:80
       capabilities: ethernet physical
       configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes

Code:

sudo lsmod|grep -e b43 -e ssb -e wl -e ssb
wl                   1283488  0 
ieee80211_crypt        13444  2 ieee80211_crypt_tkip,wl

Code:

dmesg|grep -e b43 -e wl
[   12.067863] wl: module license 'unspecified' taints kernel.
[   12.070074] wl 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[   12.070327] wl 0000:0c:00.0: setting latency timer to 64
[  272.248462] wl 0000:0c:00.0: PCI INT A disabled
[  273.000329] wl 0000:0c:00.0: restoring config space at offset 0xf (was 0x100, writing 0x104)
[  273.000390] wl 0000:0c:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xf69fc004)
[  273.000402] wl 0000:0c:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
[  273.000419] wl 0000:0c:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100106)
[  273.000486] wl 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[  273.000497] wl 0000:0c:00.0: setting latency timer to 64
[ 3986.108450] wl 0000:0c:00.0: PCI INT A disabled
[ 3986.888321] wl 0000:0c:00.0: restoring config space at offset 0xf (was 0x100, writing 0x104)
[ 3986.888381] wl 0000:0c:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xf69fc004)
[ 3986.888393] wl 0000:0c:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
[ 3986.888410] wl 0000:0c:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100106)
[ 3986.888477] wl 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 3986.888489] wl 0000:0c:00.0: setting latency timer to 64

Interesting about that license warning ... the Broadcom driver builds with a warning that I can't clear up that shows up in dmesg.

Thanks again .. as you can see, I only have the wl driver installed -- I am starting to suspect the driver or the card is hosed.

--AF

The only thing that I can think of is that you might have multiple wl modules for the kernel installed. Can you check this:

Code:

ls -l /lib/modules/`uname -r`/wlan/wl.ko
ls -l /lib/modules/`uname -r`/volatile

I am guessing that it is using your compiled version since you did the insmod, but I am not for sure if the Ubuntu supplied one was currently loaded before you tried to load yours.

**A_Fiachra** · September 22nd, 2009

Originally Posted by Ayuthia

The only thing that I can think of is that you might have multiple wl modules for the kernel installed. Can you check this:

Code:

ls -l /lib/modules/`uname -r`/wlan/wl.ko
ls -l /lib/modules/`uname -r`/volatile

I am guessing that it is using your compiled version since you did the insmod, but I am not for sure if the Ubuntu supplied one was currently loaded before you tried to load yours.

Oh!

Yes, look :

Code:

$ ls -l /lib/modules/`uname -r`/wlan/wl.ko
-rw-r--r-- 1 alee alee 1382071 2009-09-21 05:47 /lib/modules/2.6.28-15-generic/wlan/wl.ko

$ ls -l /lib/modules/`uname -r`/volatile
total 2192
-rw-r--r-- 1 root root  216975 2009-09-21 18:44 ath_hal.ko
-rw-r--r-- 1 root root  124940 2009-09-21 18:44 ath_pci.ko
-rw-r--r-- 1 root root   18405 2009-09-21 18:44 ath_rate_amrr.ko
-rw-r--r-- 1 root root   25692 2009-09-21 18:44 ath_rate_minstrel.ko
-rw-r--r-- 1 root root   17528 2009-09-21 18:44 ath_rate_onoe.ko
-rw-r--r-- 1 root root   24120 2009-09-21 18:44 ath_rate_sample.ko
-rw-r--r-- 1 root root   15221 2009-09-21 18:44 wlan_acl.ko
-rw-r--r-- 1 root root   18459 2009-09-21 18:44 wlan_ccmp.ko
-rw-r--r-- 1 root root  247465 2009-09-21 18:44 wlan.ko
-rw-r--r-- 1 root root   16267 2009-09-21 18:44 wlan_scan_ap.ko
-rw-r--r-- 1 root root   26193 2009-09-21 18:44 wlan_scan_sta.ko
-rw-r--r-- 1 root root   22923 2009-09-21 18:44 wlan_tkip.ko
-rw-r--r-- 1 root root   17099 2009-09-21 18:44 wlan_wep.ko
-rw-r--r-- 1 root root   11249 2009-09-21 18:44 wlan_xauth.ko
-rw-r--r-- 1 root root 1381735 2009-09-21 18:44 wl.ko

So, what I should do is unload the module via modprobe, and install again.

But what about that strange license warning when I make Broadcom's wl and try to load it ..

Code:

 dmesg | grep wl
[   12.067863] wl: module license 'unspecified' taints kernel.

?

Thanks again.

-- AF

**A_Fiachra** · September 22nd, 2009

Still not working ...

This is odd:

Code:

$ sudo find /lib -name wl.ko -exec ls -l {} \;
-rwxr-xr-x 1 root root 1382071 2009-09-22 04:59 /lib/modules/2.6.28-15-generic/kernel/drivers/net/wireless/wl.ko
-rw-r--r-- 1 root root 1382071 2009-09-20 17:47 /lib/modules/2.6.28-15-generic/kernel/net/wireless/wl.ko
-rw-r--r-- 1 root root 1381735 2009-09-22 05:14 /lib/modules/2.6.28-15-generic/volatile/wl.ko

$ lsmod | grep wl
wl                   1283488  0 
ieee80211_crypt        13444  2 ieee80211_crypt_tkip,wl

I'm not even loading the module I built!

Reading modprobe manpage ...

**Ayuthia** · September 22nd, 2009

The Broadcom tainting the kernel is ok. It is a proprietary kernel module so it will get that message.

The only think that I can think of is to try and hide the wl.ko file that is currently found in /lib/modules/`uname -r`/volatile. Before doing it, remove the wl.ko module:

Code:

sudo modprobe -r wl

Then move the /lib/modules/`uname -r`/volatile/wl.ko file to a place that is not located in the /lib/modules folder and then run:

Code:

sudo depmod -a

It will rebuild the module dependencies in /lib/modules so that it will not see the Ubuntu supplied one.

Afterwards, try loading yours again and hopefully it will work.

Thread: How to install native broadcom drivers for BCM4311, BCM4312, BCM4321, and BCM4322

Thread Tools

Display

Re: How to install native broadcom drivers for BCM4311, BCM4312, BCM4321, and BCM432

Re: How to install native broadcom drivers for BCM4311, BCM4312, BCM4321, and BCM432

Re: How to install native broadcom drivers for BCM4311, BCM4312, BCM4321, and BCM432

Re: How to install native broadcom drivers for BCM4311, BCM4312, BCM4321, and BCM432

Re: How to install native broadcom drivers for BCM4311, BCM4312, BCM4321, and BCM432

Re: How to install native broadcom drivers for BCM4311, BCM4312, BCM4321, and BCM432

Re: How to install native broadcom drivers for BCM4311, BCM4312, BCM4321, and BCM432

Re: How to install native broadcom drivers for BCM4311, BCM4312, BCM4321, and BCM432

Re: How to install native broadcom drivers for BCM4311, BCM4312, BCM4321, and BCM432

Re: How to install native broadcom drivers for BCM4311, BCM4312, BCM4321, and BCM432

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions