HOW TO: Install and configure lm-sensors

[Ray_GTI-R]

Sorry to butt in ...
I have downloaded lm-sensors OK. I tried to run lm-sensors directly but failed ... more than once. After a few days (weeks? see Note, below.) I noticed that k-sensors had been installed. After a number of tries I can manually get k-sensors to work (see Note 2, Below) and it runs lm-sensors 100% perfectly functionally with 100% perfectly accurate readings.
My question:- how do I get k-sensors to start up automatically upon cold-boot/warm-boot?
I have tried various (non-expert Ubuntu/Linux user) methods... and failed.
TIA, Ray
(Note: My Ubuntu install is on a hardware testbench rig that is used infrequently, for proving various bits of kit as received ... hence the need for lm-sensors and the uncertainty of exact diary.)
(Note 2: How I get k-sensors to run, manually ...
Accessories
Terminal
"ksensors"
{wait for lm-sensors to complete initialising and display the results]
Exit)

[petrasflorin]

FATAL: Error inserting w83627ehf (/lib/modules/2.6.32-5-686/kernel/drivers/hwmon/w83627ehf.ko): Device or resource busy

[warfie]

it8718-isa-0228
Adapter: ISA adapter
in0: +1.25 V (min = +0.00 V, max = +4.08 V)
in1: +1.95 V (min = +0.00 V, max = +4.08 V)
in2: +3.20 V (min = +0.00 V, max = +4.08 V)
in3: +2.82 V (min = +0.00 V, max = +4.08 V)
in4: +2.90 V (min = +0.00 V, max = +4.08 V)
in5: +3.10 V (min = +0.00 V, max = +4.08 V)
in6: +4.08 V (min = +0.00 V, max = +4.08 V) ALARM
in7: +3.22 V (min = +0.00 V, max = +4.08 V)
Vbat: +3.38 V
fan1: 0 RPM (min = 0 RPM)
fan2: 1726 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
temp1: +43.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
temp2: +42.0°C (low = +127.0°C, high = +80.0°C) sensor = thermal diode
temp3: +90.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor
cpu0_vid: +1.250 V



errrr.... any idea what "Temp1, Temp2, Temp3" are? which is the CPU? and what the heck could be running at 90°C?!?!
Could it really be that there is no 12v line? and no -5v?

Looks a little strange to me...

Cheers!

[AttilaSVK]

Hi all!

Yesterday I put together a small server with a Gigabyte H67M-D2-B3 motherboard and a Core i3 2100 CPU running 32-bit Ubuntu Server 10.10. Everything works flawlessly, I have only problem with lm-sensors, more particularly I cannot load the it87 module.

If I execute the

modprobe it87

command, this is what I get:

FATAL: Error inserting it87 (/lib/modules/2.6.35-28-generic-pae/kernel/drivers/hwmon/it87.ko): No such device

When I did

sensors-detect

the script that came with Ubuntu didn't find anything, so I downloaded the newest script which detected the CPU thermal diode (coretemp) and a ITE IT8728F Super IO Sensors, which needs the module it87.

I tried to google around, but after almost two hours of searching, I couldn't find anything.
Anyone with an idea?

PS: excuse me if I didn't post this to the correct topic - I'm new here.

[miegiel]

Hi all!

Yesterday I put together a small server with a Gigabyte H67M-D2-B3 motherboard and a Core i3 2100 CPU running 32-bit Ubuntu Server 10.10. Everything works flawlessly, I have only problem with lm-sensors, more particularly I cannot load the it87 module.

If I execute the

modprobe it87

command, this is what I get:

FATAL: Error inserting it87 (/lib/modules/2.6.35-28-generic-pae/kernel/drivers/hwmon/it87.ko): No such device

When I did

sensors-detect

the script that came with Ubuntu didn't find anything, so I downloaded the newest script which detected the CPU thermal diode (coretemp) and a ITE IT8728F Super IO Sensors, which needs the module it87.

I tried to google around, but after almost two hours of searching, I couldn't find anything.
Anyone with an idea?

PS: excuse me if I didn't post this to the correct topic - I'm new here.

Welcome to ubuntuforums

For intel CPUs the coretemp should get the CPU temps.

I didn't take a good look at your motherboard, but if the chips on the motherboard are relatively new (or new revisions) it's possible that the linux modules/drivers only support essential functions yet. Maybe ubuntu 11.04 (to be released this month) will bring relief. Often full hardware support lags behind what you've been used to in windows (blame the manufacturers).

[AttilaSVK]

Welcome to ubuntuforums

For intel CPUs the coretemp should get the CPU temps.

I didn't take a good look at your motherboard, but if the chips on the motherboard are relatively new (or new revisions) it's possible that the linux modules/drivers only support essential functions yet. Maybe ubuntu 11.04 (to be released this month) will bring relief. Often full hardware support lags behind what you've been used to in windows (blame the manufacturers).

All right, it's not a big deal. For now it's enough to be able to check the CPU temp, because I'm a little bit paranoid about the system health, as I used to have a Dell PowerEdge 1550 server with two P3s (running Karmic Koala btw) which kept on shutting down because of overheating on hot summer days

[papampi]

Thanks for the great tut !
it seems I have my sensors running ok !

payam@payam-ubuntu:~$ sensors
atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage:     +1.24 V  (min =  +0.85 V, max =  +1.60 V)
 +3.3 Voltage:     +3.28 V  (min =  +2.97 V, max =  +3.63 V)
 +5 Voltage:       +5.09 V  (min =  +4.50 V, max =  +5.50 V)
 +12 Voltage:     +12.25 V  (min = +10.20 V, max = +13.80 V)
CPU FAN Speed:    1163 RPM  (min =  600 RPM)
CHASSIS FAN Speed:   0 RPM  (min =  800 RPM)
CPU Temperature:   +41.0°C  (high = +60.0°C, crit = +95.0°C)  

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +60.0°C  (high = +86.0°C, crit = +100.0°C)  

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +60.0°C  (high = +86.0°C, crit = +100.0°C)

but the conky show my cpu temp 0
any idea ?

[miegiel]

Thanks for the great tut !
it seems I have my sensors running ok !

payam@payam-ubuntu:~$ sensors
atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage:     +1.24 V  (min =  +0.85 V, max =  +1.60 V)
 +3.3 Voltage:     +3.28 V  (min =  +2.97 V, max =  +3.63 V)
 +5 Voltage:       +5.09 V  (min =  +4.50 V, max =  +5.50 V)
 +12 Voltage:     +12.25 V  (min = +10.20 V, max = +13.80 V)
CPU FAN Speed:    1163 RPM  (min =  600 RPM)
CHASSIS FAN Speed:   0 RPM  (min =  800 RPM)
CPU Temperature:   +41.0°C  (high = +60.0°C, crit = +95.0°C)  

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +60.0°C  (high = +86.0°C, crit = +100.0°C)  

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +60.0°C  (high = +86.0°C, crit = +100.0°C)

but the conky show my cpu temp 0
any idea ?

I use

${hwmon 1 temp 1}

in my conky. The first 1 is the number of the sensor (counting starts at 0), you have 3 sensors. The second 1 is is the number of the temperature "reading", some sensors read more than 1 temperature (counting starts at 1).

Here's my sensors output. I read my temp from the red sensor.

acpitz-virtual-0
Adapter: Virtual device
temp1:       +54.0°C  (crit = +96.0°C)                  

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +47.0°C  (crit = +100.0°C)                  

eeepc-isa-0000
Adapter: ISA adapter
fan1:       3926 RPM

Make sure you're not using a bogus sensor. Just because lm-sensors finds a sensor that puts out a temperature doesn't mean it's actually reading a temperature. Some sensors are just not connected.

This is a better thread for asking conky questions (and conky inspiration).

[Icche Ghuri]

but the conky show my cpu temp 0 any idea ?

Run this command in your terminal,

sensors | grep -A 0 'Core 0' | cut -c1-23

you'll get similar result like this,

Core 0:      +47.0°C

So, add this two lines(for tow cpu cores) in your conkyrc

CPU 0: ${execi 2 sensors | grep -A 0 'Core 0' | cut -c15-23}
CPU 1: ${execi 2 sensors | grep -A 0 'Core 1' | cut -c15-23}

you'll get result like this on your conky wall,

CPU 0: 48.0°C
CPU 1: 48.0°C

[miegiel]

Run this command in your terminal,

sensors | grep -A 0 'Core 0' | cut -c1-23

you'll get similar result like this,

Core 0:      +47.0°C

So, add this two lines(for tow cpu cores) in your conkyrc

CPU 0: ${execi 2 sensors | grep -A 0 'Core 0' | cut -c15-23}
CPU 1: ${execi 2 sensors | grep -A 0 'Core 1' | cut -c15-23}

you'll get result like this on your conky wall,

CPU 0: 48.0°C
CPU 1: 48.0°C

Using ${execi ..} to grep and cut info from sensors is a resource hog compared to using ${hwmon ...}.

Besides, how do you know he should use the coretemp-isa-0000 and coretemp-isa-0001 sensors and not the atk0110-acpi-0 sensor? From here I can't know which sensor puts out BS and which is accurate.