Ehud Gavron wrote: > Feedback: the make files work. > > However... this version of the driver is unusable. It's worse than the > one I downloaded March 30th (latest 2.6.20). Dell 1390 (BCM4311). By > worse I mean that I won't stay associated with an AP; it reverts to > previous ESSID even after associating with new AP new ESSID, and it > reverts to having previous WEP key set even with explicit "iwconfig eth1 > key off". It also keeps turning the interface off (dmesg: bcm43xx: > Radio turned off) and requires ifconfig eth1 up to get it refired. > Most important: an rmmod bcm43xx hung the system completely and it > needed a cold-start to continue. > Tested at the Golden Nugget and McCarran airport... so I know it's not > any idosyncracy of MY networks ;)
Perhaps that is your penalty for computing rather than gambling. :-) I'm a resident of Nevada and we need the gaming tax income. I don't know about the system hang when rmmod'ing the driver. I do that all the time here without any problems. There probably is some time window that you were unlucky enough to hit. Issuing an ifdown before the rmmod should fix that. I have not tested trying to change AP's. What support software were you using? Was it just plain ifup/ifdown or something else like NetworkManager? Have you been able to associate with several AP's with the older version? I don't know of anything in either bcm43xx or softmac that would cause it to try automatic roaming or change the ESSID. Perhaps someone else in the list knows better. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
