The fact that it happened on a fresh install on a totally different computer with perhaps a different card pretty much confirms a bug of some sort.
It perhaps isn't madwifi in general, but in some essence an inability for some function in the OS/Kernel to restart the wifi card out of suspend/hibernate in a way that it does when it boot. I can confirm that this issue happens with resuming from suspend AND hibernate... and in the latter, it is pretty much assured that power is cut completely to the wifi card. I don't feel like fiddling now because I got it working and that is the most important thing for now, but perhaps something that happens elsewhere during networking start/stop that in previous versions of Ubuntu would pull down/remove configuration for the entire interface and put it back up "fresh." It might speed things up for something that does not need two interfaces coming up (why does madwifi need a virtual device and separate front end anyway?) I think this because without the fix, this command will NOT bring up wifi0 with ath0 after suspend sudo /etc/init.d/networking force-reload nor will a combo of sudo /etc/init.d/networking stop sudo /etc/init.d/networking start So I don't even think it has anything to do with NetworkManager. WICD 1.4.2 also would attempt to reconnect to my essid, then just refuse as well. Mine card is a tp-link of some Atheros sort, but I don't recall - yanked the Broadcom out of my Acer Aspire LCi two years ago in favor of an Atheros card. Up to recently, it worked like a charm. Works well now, but it was about as much fiddling that I used to do with ndiswrapper with Ubuntu 6.10 -- madwifi cannot reconnect after resume from suspend https://bugs.launchpad.net/bugs/272300 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
