tis 2008-11-18 klockan 18:33 -0600 skrev Larry Finger: > Richard Jonsson wrote: > > Hi! > > > > I recently made a fresh install of ubuntu hardy, upgraded weeks later to > > intrepid. I have not had a working suspend for some time, but now this > > works. Including b43. > > > > However, after every other suspend (to ram) the status led indicates > > that rf-kill switch is in wlan enabled state, although it is not. No > > matter if I switch it on and off will it change the LED status. The > > system log says that hw status changed, and indeed wlan0 will show AP's > > in enabled state, but not in disabled state. > > > > I compared the dmesg outputs (posted below), and the only thing that > > differs is the last lines: > > > > Working: > > wlan0: authentication with AP 00:14:c1:1d:19:f0 timed out > > b43-phy0: Radio hardware status changed to DISABLED > > > > Non-working (order changed): > > b43-phy0: Radio hardware status changed to DISABLED > > wlan0: authentication with AP 00:14:c1:1d:19:f0 timed out > > > > Also, when LED is working, I get these messages a few seconds after each > > DISABLE, but not when LED is stuck: > > [86215.196059] b43-phy0: Radio turned on by software > > [86215.196078] b43-phy0: The hardware RF-kill button still turns the > > radio physically off. Press the button to turn it on. > > > > The LED used to work fine, but that was with an older ubuntu version, > > and I believe it doesn't have to be a change in b43 that cause this > > issue. > > I don't even try suspend/resume so I cannot help you there, but b43 cannot > control the radio hardware status enable/disable bit. It is read-only from the > driver. It must be the RFKILL or LED subsystems that are getting lost and/or > confused. > > If you unload b43 using 'sudo /sbin/modprobe -r b43' before suspending and > 'sudo > /sbin/modprobe b43' to load it after resuming, what happens? > > Larry > Thanks for the quick reply.
There is no difference, also I tested to unload and load b43 without suspend. The same thing happens. Turns out suspend has nothing to do with it. To summarize, every other load of b43 causes the LED to be always active. / Richard _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
