Sorry, but my issue started at about the same kernel revision, and doing the workaround (rmmod ssb && rmmod ndiswrapper && modprobe ndiswrapper && modprobe ssb) does work for me, as mentioned in my previous commend. So, that seems to indicate that it is, a the very least, a related issue.
You recommend using b43, which still does not work very well for me when using WPA2 -- I get slowness due to intermittent bad crypto rx failures, and it is a significant drain on my laptop's battery life (versus using ndiswrapper). I've been through this with my Canonical support rep doing back through dapper, edgy, and feisty; gusty was the first release where the wireless worked decently for me out-of-the-box. While I would love to use the b43 driver, it is believed to be suboptimal in my scenario by several people who should know. In short, I'm pretty sure this bug applies to my situation and b43 isn't an option. If you'd like me to still make a separate bug, I can, but I'm not sure why. -- ssb module breaks BCM4328 with ndiswrapper (regression from 2.6.24-10) https://bugs.launchpad.net/bugs/197558 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
