Description of problem: I can connect to my wireless network (WEP) using the command line tools, but NM doesn't seem to be able to connect. Wired networking works just fine. Version-Release number of selected component (if applicable): NetworkManager-0.5.1-18.cvs20060301 kernel-2.6.15-1.1996_FC5 How reproducible: Always Steps to Reproduce: 1. Turn on my iBook 2. Get prompted for WEP key; enter it 3. Watch spinning icon ... it ends with the no connection icon Actual results: No wireless connection Expected results: Connect to wireless network just as I can do with iwconfig Additional info: See attached /var/log/messages (stripped of what I think is irrelevant information)
Created attachment 125538 [details] /var/log/messages
Adding as blocker for FC5. Feel free to remove if this isn't important enough for a blocker.
*** This bug has been marked as a duplicate of 180369 ***
Please try this again with the 2.6.16-1.2070 or later kernel, which has a bunch of fixes to make bcm43xx less picky about the order in which various initialisation functions are performed.
Are those fixes that were included in verision 2.6.16-1.2070 this still valid for kernels version 2.6.17? It seems to screw up pretty dramatically with version 2.6.17-1.2145 and 2157 here ... I'm just wondering if those patches got removed or otherwise went unchecked ?
(In reply to comment #5) > Are those fixes that were included in verision 2.6.16-1.2070 this still valid > for kernels version 2.6.17? It seems to screw up pretty dramatically with > version 2.6.17-1.2145 and 2157 here ... I'm just wondering if those patches got > removed or otherwise went unchecked ? I actually have pretty good luck at home and work but had a terrible time at OLS last week. I assumed it was very touchy about APs but maybe it's something else.
Ubuntu seems to have patched wpa_supplicant and NetworkManager to fix this... https://launchpad.net/distros/ubuntu/+source/network-manager/+bug/42504 But I'm not sure what was part of this "update" that fixed their issues...