Bug 183341

Summary:	ksysguard reporting wrong value for wireless signal and noise in dBm
Product:	[Unmaintained] ksysguard	Reporter:	Lubos Lunak <l.lunak>
Component:	general	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	amubtdx, richard.llom
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Proposed patch for ksysguard/ksysguardd/Linux/netdev.c

Description Lubos Lunak 2009-02-05 18:27:54 UTC

Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    SuSE RPMs

Forwarding from Novell bugzilla, http://bugzilla.novell.com/463370 (and I don't actually know what it is about). Quoting:

I found that wavemon was reporting the wrong value for dBm values when IW_QUAL_DBM is set by the driver. See SuSE Bug 463032.

The same problem is visible in the KDE4 (and KDE3 - see Bug 463369) performance monitor (ksysguard). The
metric localhost->Network->Interfaces->eth1->wifi->signal and noise are in dBm but are in the range of -350. This value should be 0x100 higher.

Comment 1 Alexis Murzeau 2012-11-16 21:49:02 UTC

Created attachment 75303 [details]
Proposed patch for ksysguard/ksysguardd/Linux/netdev.c

This patch add a condition on the value (signal level and noise level):
 - if the value is >= 64, the value is considered as a old type value and we subtract 0x100 as done before.
 - if this value is < 64, the value is considered as a dBm value and no operation are done.

64 is used as in iwlib.c in wireless_tools (version 29) in function iw_print_stats at line 1436
This way, possible dBm values are between -192 dBm and 63 dBm

Comment 2 Richard Llom 2019-03-12 21:27:59 UTC

I don't have an WLAN adapter connected.
Can someone confirm if this still is an issue?

Comment 3 Bug Janitor Service 2019-03-27 04:33:10 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Bug Janitor Service 2019-04-11 04:33:11 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!