[SOLVED] lm_sensors partially working

hotsauce · #1 29th July 2011, 04:39 AM

I'm having trouble figuring out how to get lm_sensors to give me the temp of my cpu. In particular, it seems to detect the sensors just fine, but upon running "sensors" after I go through the process of "sensors-detect "and updating my "/etc/sysconfig/lm_sensors"; the CPU sensor "k10temp-pci-00c3" for an AMD chip is not giving me the temp. In bios temp readings are fine. The pci adapter is for a nvidia card, which reports temp correctly elsewhere. Any help or pointers appreciated.

"sensors" command output:

Code:

k10temp-pci-00c3
Adapter: PCI adapter
temp1:         +0.0°C  (high = +70.0°C)

Here is my /etc/sysconfig/lm_sensors just after

Code:

# Generated by sensors-detect on Thu Jul 28 22:19:36 2011
# This file is sourced by /etc/init.d/lm_sensors and defines the modules to
# be loaded/unloaded.
#
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).

HWMON_MODULES="f71882fg"

# For compatibility reasons, modules are also listed individually as variables
#    MODULE_0, MODULE_1, MODULE_2, etc.
# You should use BUS_MODULES and HWMON_MODULES instead if possible.

MODULE_0=f71882fg

As we can see, the AMD cpu (k10temp-pci-00c3 ) sensor does not make it into the file, but does show up when running the "sensors" command.

marriedto51 · #2 29th July 2011, 09:05 AM

As you probably know, the file /etc/sysconfig/lm_sensors controls which kernel modules are loaded when lm_sensors starts up (at boot). You need to look at the file /etc/sensors3.conf to determine how sensors displays its output: which temperatures are reported and so on.

Check that you have the k10temp kernel module: /lib/modules/kernel-version/kernel/drivers/hwmon/k10temp.ko (this should just be part of the kernel package).

You could try manually editing your /etc/sysconfig/lm_sensors to have the lines

Code:

HWMON_MODULES="f71882fg k10temp"
...
MODULE0=f71882fg
MODULE1=k10temp

You may also need to edit /etc/sensors3.conf to get sensible output. Look for a section that starts something like

Code:

chip "k10temp-*"

(If there is no such section you may need to create one.) You could look at the man page for sensors3.conf, or try to dig out the information from the lm_sensors website.

Luke M · #3 29th July 2011, 07:05 PM

I had a similar problem, but sensors started working after a reboot.

hotsauce · #4 30th July 2011, 04:25 AM

Well unfortunately it hasn't just startign working for me yet. Here's what I have done so far:

edited /etc/sensors3.conf with:

Code:

chip "k10temp-*"

  label temp1 "CPU Temp"

as per this fairly informative page: http://www.scientificlinuxforum.org/....php/t415.html. It was the only reference to a k10temp setting for that file I found. And there was no previous k10 reference in the file on my machine.

I did try adding k10temp and k8temp, separately, in the MODULES settings inside: /etc/sysconfig/lm_sensors.

And I do have the k8 and k10 temp modules in: /lib/modules/kernel-version/kernel/drivers/hwmon/*.

lm_sensors is starting on boot (chkconfig lm_sensors on).

My motherboard is a MSI870A-G54 with an AMD Phenom II x6 (64bit). Not particularly sure what really to do with this. It is possible my mobo isn't supported. My mobo isn't in here:http://www.lm-sensors.org/wiki/Configurations/MSI. I suspect my /etc/sensors3.conf is incomplete. Still looking for any help or suggestions, thanks.

hotsauce · #5 1st August 2011, 07:42 AM

Well, with more searching around, it appears that the k10temp is not really supported. The "stock" k10temp actually has a line in it that disables it if/when it's loaded. And apparently, it wasn't ever really made to measure CPU temp. In saying that, there are a couple modes out there that I have tried. Accuracy seems disputable as it's not measuring temp, rather, it's using math to solve for temp based on voltages.

So, this is what I have done:

Code:

$ wget http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20080718/d51be536/attachment.bin
$ mkdir k10temp && mv attachment.bin k10temp/k10temp.c

Now create the Makefile with following lines:

    obj-m := k10temp.o
    KDIR := /lib/modules/$(shell uname -r)/build
    PWD := $(shell pwd)
    default:
    $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules

$ make -C /lib/modules/$(uname -r)/build M=$(pwd) modules
$ cp k10temp.ko /lib/modules/$(uname -r)/kernel/drivers/hwmon
$ depmod && modprobe k10temp

Problem is now, after doing that, there are no sensors found, and sensors detect say's this at the end of it's program output:

Code:

Driver `k10temp':
  * Chip `AMD Family 10h thermal sensors' (confidence: 9)

Driver `f71882fg':
  * ISA bus, address 0x600
    Chip `Fintek F71889ED Super IO Sensors' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): y
Job failed. See system logs and 'systemctl status' for details.
Unloading i2c-dev... OK

dmesg:

Code:

[43669.377870] i2c /dev entries driver
[43681.345062] f71882fg: Unsupported Fintek device: 0909
[43681.378380] k10temp: Unknown parameter `force'

systemctl:

Code:

sys-devi...d-card0.device loaded active plugged       /sys/devices/pci0000:00/0000:00:14.2/sound/card0
sys-devi...et-eth0.device loaded active plugged       /sys/devices/pci0000:00/0000:00:15.1/0000:05:00.0/net/eth0
sys-devi...y-ttyS1.device loaded active plugged       /sys/devices/platform/serial8250/tty/ttyS1
sys-devi...y-ttyS2.device loaded active plugged       /sys/devices/platform/serial8250/tty/ttyS2
sys-devi...y-ttyS3.device loaded active plugged       /sys/devices/platform/serial8250/tty/ttyS3
sys-devi...y-ttyS0.device loaded active plugged       /sys/devices/pnp0/00:05/tty/ttyS0
sys-devi...dm\x2d0.device loaded active plugged       /sys/devices/virtual/block/dm-0
sys-devi...dm\x2d1.device loaded active plugged       /sys/devices/virtual/block/dm-1
sys-devi...dm\x2d2.device loaded active plugged       /sys/devices/virtual/block/dm-2
sys-devi...dm\x2d3.device loaded active plugged       /sys/devices/virtual/block/dm-3
sys-devi...dm\x2d4.device loaded active plugged       /sys/devices/virtual/block/dm-4
sys-devi...dm\x2d5.device loaded active plugged       /sys/devices/virtual/block/dm-5
sys-devi...dm\x2d6.device loaded active plugged       /sys/devices/virtual/block/dm-6
sys-devi...dm\x2d7.device loaded active plugged       /sys/devices/virtual/block/dm-7
sys-devi...dm\x2d8.device loaded active plugged       /sys/devices/virtual/block/dm-8
sys-devi...boxnet0.device loaded active plugged       /sys/devices/virtual/net/vboxnet0
sys-devi...boxnet1.device loaded active plugged       /sys/devices/virtual/net/vboxnet1
sys-devi...ty-tty0.device loaded active plugged       /sys/devices/virtual/tty/tty0
sys-devi...ty-tty1.device loaded active plugged       /sys/devices/virtual/tty/tty1
sys-devi...y-tty10.device loaded active plugged       /sys/devices/virtual/tty/tty10
sys-devi...y-tty11.device loaded active plugged       /sys/devices/virtual/tty/tty11
sys-devi...y-tty12.device loaded active plugged       /sys/devices/virtual/tty/tty12

I followed instructions from here:http://blog.morrigan.ch/?p=9

Any thoughts, help, or opinions appreciated. Maybe some of you are familiar with what I have tried, or can better decode what I have posted...

LinuxClusters · #6 28th December 2012, 09:17 PM

I have a MSI 890FXA-GD70 and I was able to get lm-sensors to work just fine on both the K10temp and the f71882fg chips that are on that motherboard with a 3.6.11 kernel I built myself. I did have to add the following to the kernel command line in order to get the f71882fg module to load without a memory address conflict with the ACPI subsystem:

acpi_enforce_resources=lax

So now I get the following output when I run the sensors utility:

# sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +28.9°C (high = +70.0°C)
(crit = +90.0°C, hyst = +88.0°C)

f71889ed-isa-0600
Adapter: ISA adapter
in0: +1.68 V
in1: +1.10 V (max = +2.04 V)
in2: +1.54 V
in3: +0.95 V
in4: +1.10 V
in5: +0.04 V
in6: +1.10 V
in7: +1.59 V
in8: +1.64 V
fan1: 2772 RPM
fan2: 1950 RPM
fan3: 0 RPM ALARM
temp1: +25.0°C (high = +255.0°C, hyst = +251.0°C) ALARM (CRIT)
(crit = +255.0°C, hyst = +251.0°C) sensor = transistor
temp2: +26.0°C (high = +255.0°C, hyst = +251.0°C) ALARM (CRIT)
(crit = +255.0°C, hyst = +251.0°C) sensor = transistor
temp3: +29.0°C (high = +255.0°C, hyst = +253.0°C) ALARM (CRIT)
(crit = +255.0°C, hyst = +253.0°C) sensor = transistor

My /etc/sysconfig/lm_sensors file looks like the following:

# Generated by sensors-detect on Fri Dec 28 03:17:44 2012
# This file is sourced by /etc/init.d/lm_sensors and defines the modules to
# be loaded/unloaded.
#
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).

HWMON_MODULES="f71882fg"

# For compatibility reasons, modules are also listed individually as variables
# MODULE_0, MODULE_1, MODULE_2, etc.
# You should use BUS_MODULES and HWMON_MODULES instead if possible.

MODULE_0=f71882fg

BTW, there is a whole discussion on the lm_sensors mailing list archive regarding the issues with ACPI memory address conflicts with the f71882fg chip and driver. The thread is 10 - 15 posts long and is very interesting.

http://lists.lm-sensors.org/pipermai...ne/036574.html

hotsauce · #7 28th December 2012, 09:43 PM

Oh really? Wow. I'm gonna log over right now and take a look. I never really made too much forward progress with that.

---------- Post added at 03:43 PM ---------- Previous post was at 03:23 PM ----------

Okay, so I reinstalled lm_sensors for my arch type. I believe everything is working okay now. It seems to be seeing the correct modules and reporting "some temps". The temps look about right also.
sensors command:

Code:

radeon-pci-0100
Adapter: PCI adapter
temp1:        +41.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +32.4°C  (high = +70.0°C)

f71889ed-isa-0600
Adapter: ISA adapter
+3.3V:        +3.26 V  
in1:          +1.46 V  (max =  +2.04 V)
in2:          +1.11 V  
in3:          +0.87 V  
in4:          +0.59 V  
in5:          +1.27 V  
in6:          +1.54 V  
3VSB:         +3.26 V  
Vbat:         +3.18 V  
fan1:        1472 RPM
fan2:           0 RPM  ALARM
fan3:           0 RPM  ALARM
temp1:        +37.0°C  (high = +255.0°C, hyst = +251.0°C)  ALARM (CRIT)
                       (crit = +255.0°C, hyst = +251.0°C)  sensor = transistor
temp2:          FAULT  (high = +255.0°C, hyst = +251.0°C)
                       (crit = +255.0°C, hyst = +251.0°C)  sensor = transistor
temp3:        +31.0°C  (high = +255.0°C, hyst = +253.0°C)  ALARM (CRIT)
                       (crit = +255.0°C, hyst = +253.0°C)  sensor = transistor

And my /etc/sysconfig/lm_sensors:

Code:

# Generated by sensors-detect on Fri Dec 28 15:36:08 2012
# This file is sourced by /etc/init.d/lm_sensors and defines the modules to
# be loaded/unloaded.
#
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).

HWMON_MODULES="f71882fg"

# For compatibility reasons, modules are also listed individually as variables
#    MODULE_0, MODULE_1, MODULE_2, etc.
# You should use BUS_MODULES and HWMON_MODULES instead if possible.

MODULE_0=f71882fg

Perhaps there was an update in between then and now?

LinuxClusters · #8 28th December 2012, 11:46 PM

The actual update would have to be in the kernel since the modules for various switches are actually part of the kernel source. The lm_sensors package is simply the libsensors libraries and sensors-detect utilities.

hotsauce · #9 29th December 2012, 02:40 AM

Right, I would imagine a little deeper than the package itself. The current kernel version has jumped up considerably since the start of this post. Too bad I can't get individual core temps on a 1090T.

mikee · #10 29th December 2012, 04:34 AM

Did you run "sensors-detect"?
That's all I recall doing and mine works. I have a similar hex core processor here:

Code:

# Generated by sensors-detect on Tue Dec 11 18:57:09 2012
# This file is sourced by /etc/init.d/lm_sensors and defines the modules to
# be loaded/unloaded.
#
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).

HWMON_MODULES="it87"

# For compatibility reasons, modules are also listed individually as variables
#    MODULE_0, MODULE_1, MODULE_2, etc.
# You should use BUS_MODULES and HWMON_MODULES instead if possible.

MODULE_0=it87
[mejh@math16-16 ~]$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +39.0°C  (crit = +60.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +25.5°C  (high = +70.0°C)

george_toolan · #11 29th December 2012, 09:07 AM

Quote:

That's all I recall doing and mine works.

It does? I don't see any core temperatures in your output. It would look something like this:

Code:

Physical id 0:  +29.0°C  (high = +80.0°C, crit = +98.0°C)
Core 0:         +25.0°C  (high = +80.0°C, crit = +98.0°C)
Core 1:         +29.0°C  (high = +80.0°C, crit = +98.0°C)
Core 2:         +23.0°C  (high = +80.0°C, crit = +98.0°C)
Core 3:         +26.0°C  (high = +80.0°C, crit = +98.0°C)

mikee · #12 30th December 2012, 12:25 AM

Quote:

Originally Posted by george_toolan

It does? I don't see any core temperatures in your output. It would look something like this:

Code:

Physical id 0:  +29.0°C  (high = +80.0°C, crit = +98.0°C)
Core 0:         +25.0°C  (high = +80.0°C, crit = +98.0°C)
Core 1:         +29.0°C  (high = +80.0°C, crit = +98.0°C)
Core 2:         +23.0°C  (high = +80.0°C, crit = +98.0°C)
Core 3:         +26.0°C  (high = +80.0°C, crit = +98.0°C)

oh... I guess I didn't know how detailed it should be!
I figured the cpu was the first thing.

---------- Post added at 06:25 PM ---------- Previous post was at 09:00 AM ----------

I should read better sometimes!

Well teh lm_sensors site actually had a config for my motherboard.
I tried that and another poster's suggestion about the lax acpi.

I have a lot more info now!

Code:

[mejh@math16-16 ~]$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +32.0°C  (crit = +60.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +19.0°C  (high = +70.0°C)

it8716-isa-0e80
Adapter: ISA adapter
CPU core:      +1.14 V  (min =  +0.00 V, max =  +4.08 V)  ALARM
DRAM voltage:  +1.87 V  (min =  +1.70 V, max =  +1.90 V)  ALARM
+3.3V:         +3.33 V  (min =  +3.14 V, max =  +3.47 V)  ALARM
+5V:           +5.00 V  (min =  +4.76 V, max =  +5.24 V)  ALARM
+12V:         +12.03 V  (min = +11.39 V, max = +12.61 V)  ALARM
+1.1V:         +1.23 V  (min =  +1.04 V, max =  +1.15 V)  ALARM
Vbat:          +2.94 V  
CPU fan:      2156 RPM  (min =    0 RPM)
SYSTEM fan:   2445 RPM  (min =    0 RPM)
fan3:            0 RPM  (min =    0 RPM)
CPU temp:      +31.0°C  (low  = +127.0°C, high = +112.0°C)  sensor = thermal diode
System temp:   +31.0°C  (low  = +127.0°C, high = +112.0°C)  sensor = thermistor
cpu0_vid:     +0.375 V
intrusion0:   ALARM

hotsauce · #13 30th December 2012, 08:50 PM

Well awhile back ago the issue was getting a CPU reading at all from a 1090T. This has been resolved. What I was more recently referring to is individual core temps. I have had a long time understanding that you cannot read individual core temps in a 1090T. So it's not an issues that im looking to resolve. Yes, my most recent "sensors" output looks great, many other programs and systems monitors should be able to read the same type of stuff now. If I totally mistaken about individual core temps for this processor, please let me know.

Code:

radeon-pci-0100
Adapter: PCI adapter
temp1:        +40.5°C  

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +32.2°C  (high = +70.0°C)

f71889ed-isa-0600
Adapter: ISA adapter
+3.3V:        +3.26 V  
in1:          +1.48 V  (max =  +2.04 V)
in2:          +1.10 V  
in3:          +0.87 V  
in4:          +0.59 V  
in5:          +1.27 V  
in6:          +1.54 V  
3VSB:         +3.28 V  
Vbat:         +3.18 V  
fan1:        1466 RPM
fan2:           0 RPM  ALARM
fan3:           0 RPM  ALARM
temp1:        +37.0°C  (high = +255.0°C, hyst = +251.0°C)  ALARM (CRIT)
                       (crit = +255.0°C, hyst = +251.0°C)  sensor = transistor
temp2:          FAULT  (high = +255.0°C, hyst = +251.0°C)
                       (crit = +255.0°C, hyst = +251.0°C)  sensor = transistor
temp3:        +31.0°C  (high = +255.0°C, hyst = +253.0°C)  ALARM (CRIT)
                       (crit = +255.0°C, hyst = +253.0°C)  sensor = transistor

mikee · #14 30th December 2012, 09:26 PM

My processor is a 1045T, so I will just log interest with you as well. I'd guess it's the same family/issues.