Bug 139771

Summary: NMI: inconsistent signal strength reporting
Product: [Fedora] Fedora Reporter: Zack Cerza <zcerza>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: rgjames
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-02-09 12:07:55 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:
Attachments:
Description Flags
screenshot of popup menu none

Description Zack Cerza 2004-11-17 22:49:58 UTC 
Description of problem:
NMI's tooltip and notification icon show my connection strength to a
WEPped net at 100%. The popup menu shows me at 0%. The net is working;
I'm sending this report over it.

Version-Release number of selected component (if applicable):
NetworkManager-0.3.2-3.cvs20041117
Comment 1 Zack Cerza 2004-11-17 22:50:41 UTC 
Created attachment 106924 [details]
screenshot of popup menu
Comment 2 Dan Williams 2005-01-29 22:00:23 UTC 
Yep, this sucks.  What driver?  Its really a mess right now, each
driver  is slightly different.  However, I've started trying to get a
handle on what each driver does for quality and how to work around them.
Comment 3 Ryan James 2005-02-09 09:23:00 UTC 
i'm using the default/included prism54 drivers and with the latest
networkmanager (0.3.3-1.cvs20050202.3.1) it's now reporting a signal strength of
~15% where it should be 100%.
Comment 4 Dan Williams 2005-02-09 12:07:55 UTC 
Unfortunately, the  prism54 driver is actually quite broken with respect to
signal quality and that's the part that needs to get fixed.  It doesn't conform
to the Wireless Extensions API.  Specifically, its signal quality calculation is
wrong, it doesn't give max quality, and it doesn't return correct signal levels
either.  I plan to take a shot at fixing it in the near future, but that's a
kernel bug and not NetworkManager...
Comment 5 Zack Cerza 2005-02-09 18:58:15 UTC 
dcbw, then shouldn't this bug be reassigned to kernel? unfortunately i 
have no way to test this anymore :(