After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 424306 - signal strength for zydas devices is stuck at 100%
signal strength for zydas devices is stuck at 100%
Status: RESOLVED NOTGNOME
Product: NetworkManager
Classification: Platform
Component: nm-applet
0.6.6
Other All
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2007-03-29 22:39 UTC by Jean-François Fortin Tam
Modified: 2007-06-10 23:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screenshot (21.94 KB, image/png)
2007-03-29 22:39 UTC, Jean-François Fortin Tam
Details

Description Jean-François Fortin Tam 2007-03-29 22:39:05 UTC
Please describe the problem:
There seems to be a problem for nm to interpret the signal strength of my NIC (which is a zydas chipset). Interestingly enough, iwconfig reports the signal strength correctly, but nm-applet shows all the networks at 100%.

I will attach a screenshot that explains a lot better than I do.

Steps to reproduce:
plug in a zydas-based network card

Actual results:


Expected results:
see 100% for 380 and 76% for "default"

Does this happen every time?
yes

Other information:
$ lsusb
Bus 003 Device 007: ID 0ace:1211 ZyDAS 802.11b/g USB2 WiFi

$ lsmod
Module                  Size  Used by
zd1211rw               52868  0 

$ uname -r
2.6.20-13-generic
Comment 1 Jean-François Fortin Tam 2007-03-29 22:39:23 UTC
Created attachment 85545 [details]
screenshot
Comment 2 Dan Williams 2007-06-10 16:41:09 UTC
This is almost definitely a driver problem with the Zydas driver.  Should be filed as a kernel bug against your distro's kernel component.  Thanks!
Comment 3 Jean-François Fortin Tam 2007-06-10 16:44:43 UTC
Not sure. How come, as I said, iwconfig reports the signal level correctly? I can only interpret that the driver/kernel is correct but something is wrong with NM no?
Comment 4 Dan Williams 2007-06-10 23:53:22 UTC
iwconfig will report it correctly because that's for the current connection.  but 'iwlist <dev> scan' is what is reporting 100% all the time here for you, not iwconfig.

Note that even in that screenshot, the "Quality=" lines in the terminal are both 100%.  So both NM and iwlist are showing essentially the same quality, meaning that either the driver itself is having problems, or the driver legitimately thinks the connection quality _is_ 100%.
Comment 5 Jean-François Fortin Tam 2007-06-10 23:57:44 UTC
thanks for the explanation :) (and for the record, yes, the two wireless networks were assured to have different signal strengths)