Bug 129952 - Wireless link monitor applet always shows 100% signal quality
Summary: Wireless link monitor applet always shows 100% signal quality
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-applets (Show other bugs)
(Show other bugs)
Version: 1
Hardware: All Linux
Target Milestone: ---
Assignee: Mark McLoughlin
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2004-08-15 15:50 UTC by Daniel Roesen
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-16 08:15:01 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Daniel Roesen 2004-08-15 15:50:17 UTC
I'm using the prism54 driver for my NetGear WG511 card. This driver
reports statistics properly in /proc/net/wireless:

$ cat /proc/net/wireless
Inter-| sta-|   Quality        |   Discarded packets               |
 face | tus | link level noise |  nwid  crypt   frag  retry   misc |
  eth1: 0000  197.  194.  238.       0      0      0      0      0   

The problem at hand is, that the wireless monitor applet calculates
the link quality percentage with a quality value range of 0..92 in
mind and does NOT check the range reported by the driver as it
should. The prism54 reports values up to ~250. As a result, the link
quality percentage displayed virtually never goes below 100%.

The problem is know to the GNOME folks:
but it seems that they are too bored to fix it properly. :-)

Can we have a local fix in Fedora? Above bug reports includes a
proposed patch.

$ rpm -q gnome-applets

I guess the problem is also existent in FC2 and current rawhide,
so feel free to upgrade the report.

Comment 1 Mark McLoughlin 2004-08-16 08:15:01 UTC
As the upstream bug report suggest, the problem isn't an easy one, nor
is the patch workable since it will probably give worse results for
most cards.

The problem is relatively high on my priority list since the
gnome-netstatus applet has the same problem and I have a WG511 too,
but I'd prefer to track this upstream. No need to track the same
problem in two places.



Note You need to log in before you can comment on or make changes to this bug.