I cannot establish anything solid about that. The behavior is extremely unpredictable. It could work sometimes right away, sometimes I have to try to reconnect several times, sometimes I unload/reload the driver. At sometimes I tried the command 'sudo iwconfig eth0 ap any' which seemed to help, but again not 100% sure... The thing is that while it could work right away, it could also waste me over one hour of trying to connect, through which many times the system locks up and I have to hard shutdown. With the suspend it is the same: it could work right away, it could require reloading the module, and it could easily lock up the machine too... I have no real idea about what to do to fix this, but to maybe see what upstream has done to improve this and sync the driver with theirs.
-- bcm43xx in edgy doesn't connect to AP anymore https://launchpad.net/bugs/68704 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
