b43 not working on rev 02 Broadcom Chipsets

Bug #219986 reported by gururise
4
Affects Status Importance Assigned to Milestone
b43-fwcutter (Ubuntu)
New
Undecided
Unassigned
Nominated for Hardy by gururise

Bug Description

Binary package hint: b43-fwcutter

I have a HP dv6000 notebook running Turion x2 processor. It uses a Broadcom BCM 4312 wireless chipset.

lspci gives:
03:00.0 Network controller: Broadcom Corporation BCM4312 802.11a/b/g (rev 02)

Upon installation of Hardy Release Candidate, I noticed the wireless was not working. The b43-fwcutter package was not installed, so I installed it via apt-get. Upon installation, it downloaded the 4.80.53.0 firmware and finished the installation. I rebooted, and still not wireless.

I noticed the b43 module was not loaded, so I did a: sudo modprobe b43
In the dmesg, I get the following errors:
[ 251.146715] b43: Unknown symbol rfkill_unregister
[ 251.146905] b43: Unknown symbol ieee80211_free_hw
[ 251.146964] b43: Unknown symbol ieee80211_alloc_hw
[ 251.147051] b43: Unknown symbol ieee80211_register_hw
[ 251.147094] b43: Unknown symbol led_classdev_unregister
[ 251.147156] b43: Unknown symbol ieee80211_generic_frame_duration
[ 251.147203] b43: Unknown symbol ieee80211_wake_queue
[ 251.147322] b43: Unknown symbol __ieee80211_get_tx_led_name
[ 251.147368] b43: Unknown symbol input_allocate_polled_device
[ 251.147432] b43: Unknown symbol ieee80211_tx_status_irqsafe
[ 251.147545] b43: Unknown symbol __ieee80211_get_rx_led_name
[ 251.147591] b43: Unknown symbol input_free_polled_device
[ 251.147754] b43: Unknown symbol ieee80211_ctstoself_get
[ 251.147872] b43: Unknown symbol ieee80211_start_queues
[ 251.147962] b43: Unknown symbol rfkill_free
[ 251.148021] b43: Unknown symbol ieee80211_stop_queue
[ 251.148111] b43: Unknown symbol ieee80211_stop_queues
[ 251.148156] b43: Unknown symbol ieee80211_get_hdrlen
[ 251.148203] b43: Unknown symbol __ieee80211_get_assoc_led_name
[ 251.148254] b43: Unknown symbol rfkill_allocate
[ 251.148298] b43: Unknown symbol rfkill_register
[ 251.148400] b43: Unknown symbol ieee80211_unregister_hw
[ 251.148488] b43: Unknown symbol input_register_polled_device
[ 251.148535] b43: Unknown symbol ieee80211_rts_get
[ 251.148579] b43: Unknown symbol led_classdev_register
[ 251.148628] b43: Unknown symbol input_unregister_polled_device
[ 251.148673] b43: Unknown symbol ieee80211_register_hwmode
[ 251.148800] b43: Unknown symbol ieee80211_rx_irqsafe

Revision history for this message
gururise (gururise) wrote :

Just another tidbit of information. Yesterday, I installed Fedora 9 Preview Release on the same laptop, and also used the b43-fwcutter. The wifi worked perfectly with Fedora 9, so I believe there is something in Ubuntu causing these unknown symbols.

Revision history for this message
gururise (gururise) wrote :

I tried replacing the older broadcom firmware with the newer 4.150.10.5 version, and I still have the same problem.

Revision history for this message
Marcus Asshauer (mcas) wrote :

Thank you for reporting this bug. I use the b43-fwcutter with the following card:
Network controller: Broadcom Corporation BCM4318.
I have no problems with this card.

Revision history for this message
slush (slush) wrote :

I have 08:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01) on my HP nc6320.

After yesterday's installation of 8.04 RC, Broadcom was detected automatically and after Next->Next->Finish installation was Wifi working perfectly. So I cannot confirm this bug.

Revision history for this message
gururise (gururise) wrote :

Ok, I believe I found the cause of this problem. It seems that Kernel 2.4.24 and lower do not have supporting drivers for the Broadcom 4311 and 4312 (rev 02) chipset.

After compiling and installing Kernel 2.4.25, my broadcom 4312 (rev 02) worked fine using the new drivers. Would it be possible to either:
1) Backport the new b43 driver subsystem from 2.4.25, which supports the newer rev 02 chipset
-or-
2) Get a 2.4.25 kernel (possibly in Universe) for Hardy

This will affect a majority of new HP Laptop users that are running AMD processors.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.