Larry Finger skrev: > Richard Jonsson wrote: >> flipping switch a few times, led unchanged >> [ 1534.770048] b43-phy0: Radio hardware status changed to ENABLED >> [ 1550.778511] b43-phy0: Radio hardware status changed to DISABLED >> [ 1562.783474] b43-phy0: Radio hardware status changed to ENABLED >> [ 1565.788237] b43-phy0: Radio hardware status changed to DISABLED > > This sounds like an rfkill/led configuration problem. In your .config, > you should have > > CONFIG_MAC80211_LEDS=y > CONFIG_RFKILL=m > CONFIG_RFKILL_INPUT=m > CONFIG_RFKILL_LEDS=y > CONFIG_B43_LEDS=y > CONFIG_B43_RFKILL=y > Confirmed, but the problem for me is how to select MAC80211_LEDS and B43_LEDS. Searching in menuconfig I found this:
Symbol: B43_LEDS [=n] Symbol: RFKILL_LEDS [=n] with no more info below them. Then MAC80211_LEDS turned up this: Symbol: MAC80211_LEDS [=n] Prompt: Enable LED triggers Defined at net/mac80211/Kconfig:74 Depends on: NET && !S390 && MAC80211 && LEDS_TRIGGERS Location: -> Networking -> Networking support (NET [=y]) -> Wireless -> Generic IEEE 802.11 Networking Stack (mac80211) (MAC80211 [=y]) Selected by: IWL4965_LEDS && NETDEVICES && !S390 && IWL4965 || IWL3945_LEDS && NETDEVICES && !S390 && IWL3945 So without IWL4965 / IWL3945 MAC80211_LEDS can't be selected!! Selecting IWL3945 and IWL3945_LEDS and reloading menuconfig gives me: CONFIG_MAC80211_LEDS=y CONFIG_RFKILL=m CONFIG_RFKILL_INPUT=m CONFIG_RFKILL_LEDS=n CONFIG_B43_LEDS=y CONFIG_B43_RFKILL=y I still can't enable RFKILL_LEDS because I have no clue as to what else needs to be enabled :/ > I think those are all the configuration parameters relating to operation > of the LED. > > If you had the problem related to the HP recall, your interface wouldn't > show up in the lspci output. It might be intermittent. Furthermore, if > it were present at boot time so that b43 got loaded, and then > disappeared, the kernel would abort with the "caps lock" light flashing > at 1 Hz. > Thanks for the clarification. Will probably flash the bios at least to prevent a future failure. > If Linus's latest git still has the problem, please do a bisection. I > had a problem with interrupt routing on my other laptop, which kept it > from booting. That problem is now fixed. I thought it only affected the > PCMCIA bridges, but there could have been other side affects. I built > other kernels in the 2.6.25-git sequence, but never booted any of them > till this morning. > I will do a bisection then, as the problem is still present. regards, Richard _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev