Comment 91 for bug 182716

Revision history for this message
Axel Knauf (axel-knauf) wrote : Re: bcm4306, bcm4309, bcm4311, bcm4312 with b43 : Authentification with AP doesn't work.

Hi.

I'd like to confirm the issue with the Asus-based bcm4318 card as already described in full length above. Some details follow, but nothing new which has not already been told.

Using a fresh installation of Kubuntu Hardy 8.04 on a Dell Inspiron 531.

~$ uname -a
Linux gromp 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux

~$ lspci -v
[snipped for brevity]
01:09.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
        Subsystem: ASUSTeK Computer Inc. Unknown device 100f
        Flags: bus master, fast devsel, latency 32, IRQ 17
        Memory at fddfe000 (32-bit, non-prefetchable) [size=8K]

~$ lshw -C network
WARNING: you should run this program as super-user.
  *-network
       description: Wireless interface
       product: BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
       vendor: Broadcom Corporation
       physical id: 9
       bus info: pci@0000:01:09.0
       logical name: eth1
       version: 02
       serial: ca:ff:ee:af:fe:01
       width: 32 bits
       clock: 33MHz
       capabilities: bus_master ethernet physical wireless
       configuration: broadcast=yes driver=bcm43xx driverversion=2.6.24-16-generic ip=192.168.2.102 latency=32 module=bcm43xx multicast=yes wireless=IEEE 802.11b/g

# blacklisted b43 abd b43legacy

# removed all additional firmware as extracted by b43-fwcutter during previous setup

# whitelisted bcm43xx

# added firmware as extracted by bcm43xx-fwcutter

~$ modprobe -r b43
~$ modprobe -r b43legacy
~$ lsmod | grep b43
[no output]

~$ modprobe bcm43xx
~$ lsmod | grep bcm
bcm43xx 141800 0
ieee80211softmac 34688 1 bcm43xx
ieee80211 38344 2 bcm43xx,ieee80211softmac

knetworkmanager now recognizes the card as eth1 and is able to associate with my AP (using WPA and everything).
Adding bcm43xx to /etc/modules does not resolve the issue during startup, I have to load the module by hand after the boot process in order to get it working. Seems to relate to the Asus hacks which Anmar talks about in [https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182716/comments/80 Comment 80] and the possible workaround modprobe'ing b43 in between and the using bcm43xx to get the card working at all.