Hi,
after upgrading to openSuSE 11.0 some hardware-sensors provided by the sensors-package are not listed in the “Sensor-Browser” of ksysguard anymore.
I’m using
both from openSuSE.
Using the “sensors”-command in a console, all hardware-sensors will be listed correctly.
Prior to the installation of 11.0 i ran openSuSE 10.2 and the “it87-sensors” were listed in ksysguard.
Any idea how to fix ?
Kind regards,
O
I’m posting a reply here months later because I just stumbled across at least one possible reason for this . . . I too lost the ksysguard display of lm_sensors and all I could find on it was a bug that was fixed in February.
I discovered looking at the kernel messages under Ctrl-Alt-F10 that ksysguardd was looking for its ksysguardrc config file under /usr/etc rather than /etc where it is and should be located. It’s this file that instructs ksysguardd to look for the lm_sensors output. Solution was a symlink /usr/etc/ksysguardrc pointing to /etc/ksysguardrc.
Hi,
“accidently” found my own thread again. Tried the symlink-solution. Unfortunately - except there’s no error message in the ALT-STRG-F10 screen anymore - ksysguard doesn’t list the hardware sensors.
Doesn’t matter, I’ll try 11.1 next day’s and see, if this subject maybe solved.
Regards,
pepun.
Ksysguard has been working fine for me since the above solution. I assume that sensors is working for you outside of ksysguard, otherwise of course won’t be picked up. Did you look in the ksysguardd file itself to insure the lmsensors is in the list? And that the daemon is being automatically run?
Hm, sensors daemon is running, i’m using ksensors applet in controlpanel and it works. Furthermore, yast claims it’s active.
In /etc/ksysguarddrc:
Sensors=ProcessList,Memory,Stat,NetDev,NetStat,Apm,Acpi,CpuInfo,LoadAvg,LmSensors,DiskStat,LogFile,DiskStats,Uptime,SoftRaid
Are you using OS 11.0 ?
Yes, 11.0. KDE 4.1.3. Same sensors list. You have the symlink, right? IIRC you have to add a new worksheet to get the sensor browser bar on the right.
Ok, i’m still using kde 3.5.9 with ksysguard 1.2.0. Maybe that’s the problem.
Yes, look into that. There was an upgrade to sensors. IIRC the version I have uses /etc/sensors3.conf, while the previous version used /etc/sensors.conf.
Is there a command to tell you which sensors do what? I installed a plasmoid that found 4 sensors and two ways to read each. So, it showed me 8 sensors but didn’t say what any of them were measuring.
There is the option to shut off any of the 8. But I don’t know which to pick.:\
Simply typing
sensors
in a console should give you something like:
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +31.0°C (high = +100.0°C, crit = +100.0°C)coretemp-isa-0001
Adapter: ISA adapter
Core 1: +32.0°C (high = +100.0°C, crit = +100.0°C)
You could try matching this up to the things you find in the plasmoid.
The program sensors-detect is run which attempts to find the sensors on your machine. There are typically 2-4, it depends entirely on the motherboard design. Each will have a kernel module, and sensors needs those to be configured in its /etc/sysconfig file. The modules also need to be loaded if they are not already being so (/etc/init.d/boot.local is useful for that).
Once you know the sensor devices, you need to find them in the /etc/sensors3.conf file. These device’s readings are dependent upon the motherboard circuitry and implementation - so a device on one board may use a different reporting formula than the same device mounted on another board. Sensors supports a number of mathematical methods of modifying the output variables, as well as suppressing unused readings and changing labels. It’s all documented in the file.
When sensors is run, it uses the configuration in the /etc/sensors3 file to determine what it will report and how. Once you have that working correctly from the command line, you will know what other programs (a plasmoid, superkaramba, kensors) should be reporting. But start by making sure all the base data is complete and correct.
Here’s what I did:
from a console I typed-
sensors
It responded that there were no sensors detected and I should try sensors-detect. So I typed:
sensors-detect
It gave me a long list of possible probes and I said yes to all of them. I didn’t get much out of the results, but the last thing that was asked was “Do you want to generate /etc/sysconfig/lm-sensors?” I said yes.
Next, I ran sensors again and again it found no sensors. So, I went to /etc/sysconfig/lm-sensors.
At the bottom of the file, it listed the modules that needed to be loaded.
MODULE_0=i2c-i801
MODULE_1=lm85
I didn’t hold out much hope since sensors-detect said something like these modules needed to be written. I thought that meant they were unavailable. But I tried:
modprobe i2c-i801
and
modprobe lm85
Next I ran sensors again. This time it came up with a list of sensors that were labeled so I could tell which was what. Now, I have to do this on the laptop that gave me the foggy answers.
Thanks!
Those two kernel modules are probably not being loaded. So additionally go to /etc/init.d/boot.local and add the modules there so they are loaded with every boot. Next look for those modules’ sections in /etc/sensors3.conf and make any changes you want/need to what sensors is reporting.
I tried this procedure on the laptop but did not get the same results. Running sensors gives me
acpitz-virtual-0
Adapter: virtual device
Then it lists 4 temperatures (all well below critical 
) as temp1, temp2 etc. I still don’t know where the readings are coming from. However, there is something new. I now have two new readings:
coretemp-isa-0000 and coretemp-isa-0001
Both say ISA adapter and I assume they are measuring 2 cores in my cpu. Each is at 16.0 C.
The 4 unlabeled temps go from 20 to 42 C.
Now I wonder, should I even care about this?
If you mean you tried using sensors on a different machine, then unless it is identical you would expect to see entirely different results - it all depends on the specific device (sensors can literally be a small chip on the motherboard or can be built into the circuitry of a larger device; typically a mobo has at least one discrete device on the board which measures voltage and temps, and there is another device at the cpu socket and/or in the cpu itself which measures its temps).
If you look in the /etc/sensors3.conf file you’ll see an explanation re the i2c bus which is often used to transport the sensor data plus the lm85 which is the actual sensor. The front section of the file gives examples of how calculations are performed/modified, labels are added/changed. Un-implemented sensor reading can be commented out (i.e., the mobo may not be designed to use all the readings a sensor is capable of). This is no different than sensor tools on Windows, where the application usually has to find/guess the sensors and guess the math used by the mobo. Sometimes the mobo bios has an option to display or already a page with voltages, temps, fans - this is your ref point for the accuracy of the lm_sensors setup, although bios’s are notorious for imprecise readings of their own sensors.
The sensors and readings you got on the laptop do look like a cpu sensor reading each core. The 16 C is probably correct if the cpu is low-power and/or power-modulating as many mobile cpu’s are now.
I hadn’t gotten so far as to worry about how the readings were calculated. My question was really much simpler. The desktop sensors were labeled, like cpu, hd, fan etc. Aside from the 2 core readings, the laptop sensors are labeled only 1, 2, 3, 4. I will look at the files you suggest and see if I can make more out of it.
The labels are extremely simple to change; in /etc/sensors3.conf.
Hi,
“accidently” found my own thread again. Tried the symlink-solution.
Unfortunately - except there’s no error message in the ALT-STRG-F10
screen anymore - ksysguard doesn’t list the hardware sensors.
Doesn’t matter, I’ll try 11.1 next day’s and see, if this subject maybe
solved.
Regards,
pepun.
user2304’s Profile: http://forums.opensuse.org/member.php?userid=3371
View this thread: http://forums.opensuse.org/showthread.php?t=387853
user2304;1923632 Wrote:
> Hi,
>
> “accidently” found my own thread again. Tried the symlink-solution.
> Unfortunately - except there’s no error message in the ALT-STRG-F10
> screen anymore - ksysguard doesn’t list the hardware sensors.
> Doesn’t matter, I’ll try 11.1 next day’s and see, if this subject maybe
> solved.
>
> Regards,
>
> pepun.
Ksysguard has been working fine for me since the above solution. I
assume that sensors is working for you outside of ksysguard, otherwise
of course won’t be picked up. Did you look in the ksysguardd file
itself to insure the lmsensors is in the list? And that the daemon is
being automatically run?
mingus725’s Profile: http://forums.opensuse.org/member.php?userid=604
View this thread: http://forums.opensuse.org/showthread.php?t=387853
Hm, sensors daemon is running, i’m using ksensors applet in controlpanel
and it works. Furthermore, yast claims it’s active.
In /etc/ksysguarddrc:
Sensors=ProcessList,Memory,Stat,NetDev,NetStat,Apm,Acpi,CpuInfo,LoadAvg,LmSensors,DiskStat,LogFile,DiskStats,Uptime,SoftRaid
Are you using OS 11.0 ?
user2304’s Profile: http://forums.opensuse.org/member.php?userid=3371
View this thread: http://forums.opensuse.org/showthread.php?t=387853