Red Hat Bugzilla – Bug 439153
b43 fails to load on kernel 22.214.171.124-58.fc8
Last modified: 2008-03-28 11:01:43 EDT
Description of problem:
The b43 module fails to load with kernel 126.96.36.199-58.fc8 complaining about a lot
of unknown symbols.
Tested on x86_64.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot the kernel
2. see it fail
b43 fails to load
b43 loads fine
05:00.0 Network controller: Broadcom Corporation BCM4312 802.11a/b/g (rev 01)
Subsystem: Dell Unknown device 0007
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at c0200000 (32-bit, non-prefetchable) [size=16K]
Capabilities:  Power Management version 2
Capabilities:  Message Signalled Interrupts: Mask- 64bit- Queue=0/0
Capabilities: [d0] Express Legacy Endpoint, MSI 00
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
Created attachment 299304 [details]
Log of the failure from dmesg
I can confirm this. b43 is busted in 188.8.131.52-58.fc8.
Even LED won't light up.
I'm not really sure why ieee80211 is being loaded at all. Anyway, I'll get a
fix for this into the fedora kernels as of -59.fc8 or later.
In the meantime, you can try:
modprobe -r ieee80211
Does that help?
(In reply to comment #3)
> I'm not really sure why ieee80211 is being loaded at all. Anyway, I'll get a
> fix for this into the fedora kernels as of -59.fc8 or later.
> In the meantime, you can try:
> modprobe -r ieee80211
> modprobe cfg80211
> modprobe b43
> Does that help?
Yes it does, I'm writing from kernel 184.108.40.206-58 right now.
Anyway, I get a strange warning when modprobing b43:
[root@dario-laptop ~]# modprobe b43
WARNING: Error inserting ieee80211
(/lib/modules/220.127.116.11-58.fc8/kernel/net/ieee80211/ieee80211.ko): Invalid module
Apart from this, wireless works fine as usual.
18.104.22.168-59.fc8 fixes it.
On the side note, I understand the rapid nature of wireless development, the
noise from b43 is too much.
[user@laptop ~]$ dmesg | grep b43 | wc -l
We don't have that many bugreports to justify this amount of debugging.
Can we have a special boot option to turn it off/on (with off by default).
I confirm -59 solves it