I have a strange problem I don't believe I had with the old bcm43xx driver. I say don't *believe* because this problem is not consistent. I've had flawless operation, and then after rebooting for whatever reason, it will exhibit this strange behavior. What I get is a constant connect/disconnect from network-manager, and this in the kern.log:
system: ubuntu 7.10 with hand-built 2.6.24.3 utilizing the 'in-tree' b43 driver and recommended firmware on an Apple 15" Powerbook (PPC) with a broadcom 4306 built-in. WAP is WPA2 protected 802.11-G on a v.4 linksys wrt-54G with original firmware ( one of the recent v4 images). <snip> Feb 26 22:55:00 powderboogie kernel: [ 8664.987559] eth1: Initial auth_alg=0 Feb 26 22:55:00 powderboogie kernel: [ 8664.987582] eth1: authenticate with AP 00 :0f:66:0b:db:60 Feb 26 22:55:00 powderboogie kernel: [ 8664.989099] eth1: RX authentication from 00:0f:66:0b:db:60 (alg=0 transaction=2 status=0) Feb 26 22:55:00 powderboogie kernel: [ 8664.989111] eth1: authenticated Feb 26 22:55:00 powderboogie kernel: [ 8664.989119] eth1: associate with AP 00:0f :66:0b:db:60 Feb 26 22:55:00 powderboogie kernel: [ 8664.993057] eth1: RX ReassocResp from 00: 0f:66:0b:db:60 (capab=0x411 status=0 aid=1) Feb 26 22:55:00 powderboogie kernel: [ 8664.993068] eth1: associated Feb 26 22:55:04 powderboogie kernel: [ 8668.946684] eth1: RX deauthentication fro m 00:0f:66:0b:db:60 (reason=15) Feb 26 22:55:04 powderboogie kernel: [ 8668.946697] eth1: deauthenticated Feb 26 22:55:05 powderboogie kernel: [ 8669.943078] eth1: authenticate with AP 00 :0f:66:0b:db:60 Feb 26 22:55:05 powderboogie kernel: [ 8669.944685] eth1: RX authentication from 00:0f:66:0b:db:60 (alg=0 transaction=2 status=0) Feb 26 22:55:05 powderboogie kernel: [ 8669.944696] eth1: authenticated Feb 26 22:55:05 powderboogie kernel: [ 8669.944705] eth1: associate with AP 00:0f:66:0b:db:60 Feb 26 22:55:05 powderboogie kernel: [ 8669.947163] eth1: RX ReassocResp from 00:0f:66:0b:db:60 (capab=0x411 status=0 aid=1) Feb 26 22:55:05 powderboogie kernel: [ 8669.947172] eth1: associated Feb 26 22:55:05 powderboogie kernel: [ 8669.947185] eth1: switched to short barker preamble (BSSID=00:0f:66:0b:db:60) Feb 26 22:55:06 powderboogie kernel: [ 8670.741007] eth1: disassociate(reason=17) Feb 26 22:55:07 powderboogie kernel: [ 8671.532792] eth1: Initial auth_alg=0 Feb 26 22:55:07 powderboogie kernel: [ 8671.532813] eth1: authenticate with AP 00:0f:66:0b:db:60 Feb 26 22:55:07 powderboogie kernel: [ 8671.534335] eth1: RX authentication from 00:0f:66:0b:db:60 (alg=0 transaction=2 status=0) Feb 26 22:55:07 powderboogie kernel: [ 8671.534347] eth1: authenticated Feb 26 22:55:07 powderboogie kernel: [ 8671.534356] eth1: associate with AP 00:0f:66:0b:db:60 <snip> the access point is a linksys wrt-54g v.4 with original firmware. OSX doesn't seem to ever have any trouble with it. 2.6.24.x and b43 will occasionally work perfectly with it as well. I'm going to upgrade the firmware on the WAP to the latest tomato and see if that helps any. I'll report my findings here. also, I was wondering what the reason codes were (17 above). I've gotten reason=3 and reason=17. google didn't help me find anything useful here, and I looked through the source a bit as well. any ideas would be greatly appreciated. thanks. _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
