OK, it seems we possibly have two bugs -- one in NM, and one in the driver? If so, could someone who is still experiencing this bug change the status back to Confirmed?
To get my card working, I installed b43-fwcutter, which automatically downloaded and extracted some firmware, then I removed network-manager, then I used the System -> Network GUI to configure an access point.
According to /lib/modules/2.6.24-12-generic/modules.pcimap, my card (PCI ID 14e4:4320) is associated with bcm43xx and ssb -- but bcm43xx is blacklisted in /etc/modprobe.d/blacklist, so the ssb module gets loaded. I guess ssb must decide which of the b43, b43legacy drivers gets loaded, and this is what is going right for me but wrong for you? If so, this looks like a problem that needs to go up to the b43/ssb developers...
OK, it seems we possibly have two bugs -- one in NM, and one in the driver? If so, could someone who is still experiencing this bug change the status back to Confirmed?
To get my card working, I installed b43-fwcutter, which automatically downloaded and extracted some firmware, then I removed network-manager, then I used the System -> Network GUI to configure an access point.
According to /lib/modules/ 2.6.24- 12-generic/ modules. pcimap, my card (PCI ID 14e4:4320) is associated with bcm43xx and ssb -- but bcm43xx is blacklisted in /etc/modprobe. d/blacklist, so the ssb module gets loaded. I guess ssb must decide which of the b43, b43legacy drivers gets loaded, and this is what is going right for me but wrong for you? If so, this looks like a problem that needs to go up to the b43/ssb developers...