Description of problem: Could not understand why b43 wireless module did not work on my laptop (Compaq V5214ea). Looking at dmesg kept on producing the message: b43-phy0: Radio hardware status changed to DISABLED The 'wireless enabled' light was ON, yet the Radio hardware was saying disabled. Pressed the Wireless enable light on the laptop (light goes off), and suddenly the Radio hardware was ENABLED. Laptop is running Fedora 8 - 2.6.24.5-85.fc8 - running Gnome 2.20.3. lspci reports: 06:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01) The network(s) are controlled by NetworkManager. The logic has been screwed somewhere. Version-Release number of selected component (if applicable): 1) b43 firmware is: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) How reproducible: Everytime Steps to Reproduce: 1. Start laptop with 2.6.24.5-85.fc8 2. Wireless 'light' on laptop starts at boot time (as specified in system-config-network-gui 3. Switching 'off' wireless light enables radio (according to dmesg) Actual results: Wireless light does not correspond to Wireless status Expected results: Wireless light ON = Radio ON Wireless light OFF = Radio OFF Additional info: From dmesg: Registered led device: b43-phy0:tx Registered led device: b43-phy0:rx Registered led device: b43-phy0:radio b43-phy0: Radio hardware status changed to DISABLED ADDRCONF(NETDEV_UP): wlan0: link is not ready eth1: no IPv6 routers present e100: eth1: e100_watchdog: link up, 100Mbps, half-duplex ADDRCONF(NETDEV_UP): eth1: link is not ready ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready input: b43-phy0 as /class/input/input12 b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) Registered led device: b43-phy0:tx Registered led device: b43-phy0:rx Registered led device: b43-phy0:radio b43-phy0: Radio hardware status changed to DISABLED ADDRCONF(NETDEV_UP): wlan0: link is not ready ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 17 [drm] Initialized drm 1.1.0 20060810 PCI: Setting latency timer of device 0000:00:02.0 to 64 [drm] Initialized i915 1.6.0 20060119 on minor 0 eth1: no IPv6 routers present nm-system-setti[2445]: segfault at 6d2e6b75 eip 001cf8ac esp bfddd890 error 4 e100: eth1: e100_watchdog: link up, 100Mbps, half-duplex eth1: no IPv6 routers present e100: eth1: e100_watchdog: link up, 100Mbps, half-duplex eth1: no IPv6 routers present eth1: no IPv6 routers present b43-phy0: Radio hardware status changed to ENABLED b43-phy0: Radio turned on by software wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:0f:b5:36:7a:0b wlan0: authenticate with AP 00:0f:b5:36:7a:0b wlan0: authenticate with AP 00:0f:b5:36:7a:0b wlan0: authentication with AP 00:0f:b5:36:7a:0b timed out wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:0f:b5:36:7a:0b wlan0: authenticate with AP 00:0f:b5:36:7a:0b wlan0: authenticate with AP 00:0f:b5:36:7a:0b wlan0: authentication with AP 00:0f:b5:36:7a:0b timed out eth1: no IPv6 routers present eth1: no IPv6 routers present eth1: no IPv6 routers present
Michael, have you heard of such a "reverse polarity" situation with the rfkill LED?
Well, this is easily possible, if the SPROM contains wrong information for the rfkill LED. There's a bit to flip polarity. Another possibility is that there's no SPROM value defined for the LED and the hardcoded fallback is not appropriate. In any case, please do a cat $(find /sys -name ssb_sprom) and send the result.
Michael, As requested - hope this makes sense to you: 0130000064133C100800BE0D00FFFFFF11430080020000000010001800000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0000FFFFFFFFFFFFFFFFFFFFFFFFFFFF1400BDA56AE5FFFFFFFFFFFFFFFFFFFFFFFFFFFF42303D15A0FA79FEFF83FFFF4AFFFFFFFFFFFFFF3EFF494A02FF45440CFFFFFFFFFF021C
yeah great. Can I have an lspci -vvn for the device?
Michael, Will get back to you on Tuesday 6th, and give you the details then. Thanks Max
Created attachment 304611 [details] Requested lspci -vvn
Created attachment 304864 [details] hp bitflip fix Please try whether this fixes it.
Max are you able to do a build with the patch from comment 7?
Hi John, An upgrade to F9 seems to have resolved my problem on this front. I was unable to build this into F8 [did not know how to do this]. Applogies I cannot progress this further. Max