Using fam15h_power sensor in Ksysguard

Board index

Page 1 of 1 (7 posts)

Tags:

AndyW Registered Member Posts 10 Karma 0 OS	Using fam15h_power sensor in Ksysguard Tue May 08, 2012 9:19 pm I am running an AMD FX-6100 CPU in a Gigabyte GA-970A-DS3 m/b. This has a "fam15h_power" CPU power sensor which is detected by lm_sensors and displays output in sensors: Code: Select all `[root@localhost etc]# sensors fam15h_power-pci-00c4 Adapter: PCI adapter power1: 86.80 W (crit = 95.01 W)` However is doesn't appear in the Ksysguard sensor browser. Is this something that can be configured, or will it require development? Andrew
bcooksley Administrator Posts 19765 Karma 87 OS	Re: Using fam15h_power sensor in Ksysguard Wed May 09, 2012 11:14 am Can you check to see if KSysguard was compiled with LMSensors support on your system? KDE Sysadmin [img]content/bcooksley_sig.png[/img]
AndyW Registered Member Posts 10 Karma 0 OS	Re: Using fam15h_power sensor in Ksysguard Wed May 09, 2012 10:43 pm I didn't compile it from source myself; it is from a Fedora 16 package (ksysguard-4.8.2-3.fc16.x86_64). However I am pretty it is compiled with lm_sensors support, as other sensors controlled by lm_sensors (k10temp, nouveau and it8728) are available. I am not sure about the values displayed by those sensors, but that is an issue for lm_sensors rather than KDE...
bcooksley Administrator Posts 19765 Karma 87 OS	Re: Using fam15h_power sensor in Ksysguard Sat May 12, 2012 7:07 am Assuming LMSensors support is enabled, then this power sensor should be displayed. If you run "kdebugdialog", then enable all areas, is anything relevant output when you run KSysguard from a console (such as Konsole). KDE Sysadmin [img]content/bcooksley_sig.png[/img]
AndyW Registered Member Posts 10 Karma 0 OS	Re: Using fam15h_power sensor in Ksysguard Wed May 16, 2012 11:28 am Thanks - I tried all that, enabled all settings. No obvious error messages, but fam15h_power still not shown in sensor browser. Console output from starting ksysguard below: Code: Select all [root@localhost log]# ksysguard ksysguard(4956)/kio (KDirWatch) KDirWatchPrivate::KDirWatchPrivate: INotify available: true ksysguard(4956)/kdecore (KLocale) KLocalizedStringPrivate::toString: Trying to convert empty KLocalizedString to QString. ksysguard(4956)/kdecore (KLocale) KLocalizedStringPrivate::toString: Trying to convert empty KLocalizedString to QString. ksysguard(4956)/kdecore (KLocale) KuitSemanticsPrivate::parseOpenEl: "Tag 'style' is neither semantic nor HTML in message {<kuil><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC...}." ksysguard(4956)/kdecore (KLocale) KuitSemanticsPrivate::semanticToVisualText: "Markup error in message {<kuil>Filter which processes are shown by the text given here. The text can be ...}: Opening and ending tag mismatch.. Last tag parsed: td" ksysguard(4956)/kdecore (KLocale) KuitSemanticsPrivate::semanticToVisualText: "Markup error in message {<kuil><qt>Change which processes are shown, and how they are shown. The process...}: Opening and ending tag mismatch.. Last tag parsed: br" ksysguard(4956)/kdecore (KLocale) KuitSemanticsPrivate::semanticToVisualText: "Markup error in message {<kuil><qt>End the selected process. Warning - you may lose unsaved work.<br>Righ...}: Opening and ending tag mismatch.. Last tag parsed: br" ksysguard(4956)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added File "/root/.kde/share/apps/ksysguard/ProcessTable.sgrd" for "" ["KDirWatch-1"] ksysguard(4956)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added File "/root/.kde/share/apps/ksysguard/SystemLoad2.sgrd" for "" ["KDirWatch-1"] ksysguard(4956)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added File "/root/.kde/share/apps/ksysguard/Sheet 1.sgrd" for "" ["KDirWatch-1"] ksysguard(4956) LogFile::LogFile: Making sensor logger ksysguard(4956)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added File "/root/.kde/share/apps/ksysguard/Sheet 2.sgrd" for "" ["KDirWatch-1"] ksysguard(4956)/kdeui (KMainWindow) KMainWindow::applyMainWindowSettings: KMainWindow::applyMainWindowSettings "MainWindow" NB: Now on KDE 4.8.3 but problem still persists. Should I file a bug report?
bcooksley Administrator Posts 19765 Karma 87 OS	Re: Using fam15h_power sensor in Ksysguard Wed May 16, 2012 12:21 pm Yes, please file a bug report at this point. It is possible KSysguard is using lmsensors in a different manner to the CLI tools. KDE Sysadmin [img]content/bcooksley_sig.png[/img]
AndyW Registered Member Posts 10 Karma 0 OS	Re: Using fam15h_power sensor in Ksysguard Wed Jun 27, 2012 10:38 pm Raised as bug #302667 - apologies for delay in getting round to this.