Bug 183653

Summary: bcm43xx works fine with iwconfig but not with NM
Product: [Fedora] Fedora Reporter: Andrew Overholt <overholt>
Component: NetworkManagerAssignee: Christopher Aillon <caillon>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: dwmw2, samuel.audet
Target Milestone: ---   
Target Release: ---   
Hardware: powerpc   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-08 18:37:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 150223    
Attachments:
Description Flags
/var/log/messages none

Description Andrew Overholt 2006-03-02 15:15:21 UTC 
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)
Comment 1 Andrew Overholt 2006-03-02 15:15:22 UTC 
Created attachment 125538 [details]
/var/log/messages
Comment 2 Andrew Overholt 2006-03-08 14:21:33 UTC 
Adding as blocker for FC5.  Feel free to remove if this isn't important enough
for a blocker.
Comment 3 Christopher Aillon 2006-03-08 18:37:14 UTC 

*** This bug has been marked as a duplicate of 180369 ***
Comment 4 David Woodhouse 2006-03-22 16:00:45 UTC 
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.
Comment 5 Samuel Audet 2006-07-25 18:47:30 UTC 
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 ?
Comment 6 Andrew Overholt 2006-07-25 18:53:09 UTC 
(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.
Comment 7 Samuel Audet 2006-07-25 22:06:31 UTC 
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...