|Summary:||No connection strength showen|
|Product:||[Fedora] Fedora||Reporter:||jim <fedorajim>|
|Component:||NetworkManager||Assignee:||Dan Williams <dcbw>|
|Status:||CLOSED NOTABUG||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2005-05-16 19:58:37 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description jim 2005-03-13 15:54:44 UTC
Description of problem: NM does't show connection strength Version-Release number of selected component (if applicable): NetworkManager-0.3.4-1.1.0.fc3 NetworkManager-gnome-0.3.4-1.1.0.fc3 How reproducible: Always Steps to Reproduce: 1.run NetworkManagerInfo 2. 3. Actual results: Expected results: show signal strength Additional info: When mouse hovers NM shows % connection if you click NM to show the list of networks when first connecting or after a connection has been made, doesn't show the connection strength in the bar. See image below
Comment 2 jim 2005-03-13 15:55:35 UTC
Created attachment 111945 [details] connection rate from mouse hover
Comment 3 Rene Rask 2005-03-25 09:50:52 UTC
Confirming this bug. Hardware: IBM X40, ipw2200 wireless. The problem occurred after updating from release 0.3.3-1.cvs20050119 to 0.3.4-1.1.0 in fedora core 3. I think this was working on an atheros based wireless card I was trying to get working the other day. I do remember thinking "hey, it shows signal strengt with this card", and I think it was before I tried downgrading NM to get around the "F... you. your dhcp server is sending on a wrong udp port" message.
Comment 4 Dan Williams 2005-05-05 19:36:23 UTC
only the latest ipw2200 & ipw2100 drivers actually provide usable strength... Can you try with one of those and see how it works?
Comment 5 jim 2005-05-05 21:38:14 UTC
drivers I am using ipw2200-firmware-2.2-5.at ipw2200-kmdl-2.6.11-1.14_FC3-1.0.0-23.rhfc3.at ipw2200-1.0.0-23.rhfc3.at meter in sustem tray shows strength but actual wireless network show none
Comment 6 Dan Williams 2005-05-16 19:58:37 UTC
Yeah, the scanning code that does strength is different than the code that gets the _current_ connection strength. This is a driver issue in ipw2200, and may already be fixed with later versions of the driver... I'm fairly sure ipw2200-1.0.3 will work.