On Wed, 2006-09-27 at 15:01 +0200, Michael Buesch wrote: > On Wednesday 27 September 2006 14:47, Johannes Berg wrote: > > On Wed, 2006-09-27 at 14:41 +0200, Michael Buesch wrote: > > > > and bcm43xx on hibernate blacklist, but who cares...) > > > > > Ok, thanks for testing. > > > I will build a patch suitable for submission to linville. > > > It would be good if you could also test this final patch. > > > > But that time without having it on the blacklist please ;) > > > > blacklist -> module is unloaded before suspending -> no real test > > We are talking about different things here. > hibernate != suspend > I think he's talking about suspend to disk. > > But what happens, if you _don't_ put bcm43xx on the hibernate > blacklist?
With all the latest patches, it doesn't comeback/reassociate on wakeup (but doesn't crash neither, and that could just be an issue with wpa_supplicant not re-associating). It's still better than before as an ifdown/ifup will work, while before I had to rmmod/modprobe to get the driver back into working conditions. Ben. _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
