I'm beginning to think that there may be more than one issue/bug that I
am seeing. One of them is almost certainly not even related to network-
manager; the other may be:
1) Often-times I will begin to see some log entries like these:
Jun 10 23:28:47 bethany-laptop kernel: [21350.320000] bcm43xx: IRQ_READY
timeout
Jun 10 23:28:50 bethany-laptop NetworkManager: <WARNING>^I
nm_device_802_11_wireless_scan (): could not trigger wireless scan on device
eth1: No such device
Once I begin to see these log entries (the "IRQ_READY timeout" one, in
particular), I cannot make any wireless connections, not using the command-line
WiFi tools nor using network-manager. This is the issue which *could be*
caused by network-manager; it's possible network-manager does something that
messes up the given device ("eth1", for me), but I'm beginning to think that it
may be a driver/kernel problem. I still don't understand what this "IRQ_READY"
business is, even after doing some Google'ing, so I'm not in a position to make
any calls on it. However, I am always able to work around this problem by
reloading the bcm43xx driver: "sudo rmmod bcm43xx; sudo modprobe bcm43xx".
2) The other problem is much less understood. The problem is that I
simply cannot connect to wireless networks sometimes, even though there
appears to be no problem with the device's configuration at the time
(AFAICT). It's *possible* that this isn't even a problem with my
computer, but one with the access points to which I'm trying to connect;
I don't think that's the case, though, from my (rather limited)
experiences. In the case of this problem, I am not able to connect to
an access point using the command-line tools nor using network-manager
(DHCP simply times out). I don't know for sure that this problem is
specific to unencrypted networks, either (!!). I need to try Phillip's
suggestion (above), but it is quite hard to test this stuff, as visiting
an area with proper access points for testing is time consuming... and
unreliable regardless of wireless device.
So, overall, my experience with this computer and its bcm43xx-based card
have just been plain *patchy*. I'm not sure what to make of it anymore.
Moving forward, I will look to try Phillip's suggestion, and I will
probably give the ndiswrapper approach a shot.
--
Unable to connect to unsecured/unencrypted wireless networks (bcm43xx-based
chips only?)
https://bugs.launchpad.net/bugs/73759
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
