HOW TO: Install and configure lm-sensors

**keithjr** · June 11th, 2006

Well, if anybody is interested, I got vt1211 to actually work for Dapper and display a sensor readout. If anybody needs to know, PM me It doesn't help that the driver wasn't even included in the kernel even as high as 2.6.16. It's useless, though. The temp readout comes out completely wrong. The default equation in their vt1211 chip section always comes out with a negative number, and I'd have to take some spreadsheet data to try to find the linear equation to convert the raw data because a simple scaling factor (+x, -x) won't do it. Which means constantly restarting my system to read the correct values in the bios setup... yikes. Oh, and every value generates and alarm for Proc. temp, even if it is below the temp_high value, which somehow changes every time I change the calculate statement for the associated temperature. what the heck??

the people who make lm-sensors really need to get their act together. A week of work to get to this point and then have to give up is depressing.

**Evil Dax** · June 12th, 2006

I've upgraded from 5.10 to 6.06 this weekend, and now my fancontrol is stopped.
Sensors are OK:

Code:

w83627hf-isa-0290
Adapter: ISA adapter
VCore 1:   +1.62 V  (min =  +1.57 V, max =  +1.73 V)
VCore 2:   +2.62 V  (min =  +1.57 V, max =  +1.73 V)       ALARM
+3.3V:     +3.30 V  (min =  +3.14 V, max =  +3.47 V)
+5V:       +4.95 V  (min =  +4.76 V, max =  +5.24 V)
+12V:     +11.86 V  (min = +10.82 V, max = +13.19 V)
-12V:     -12.36 V  (min = -13.18 V, max = -10.80 V)
-5V:       -5.00 V  (min =  -5.25 V, max =  -4.75 V)
V5SB:      +5.46 V  (min =  +4.76 V, max =  +5.24 V)       ALARM
VBat:      +3.49 V  (min =  +2.40 V, max =  +3.60 V)
fan1:     2265 RPM  (min =    0 RPM, div = 4)
fan2:     4891 RPM  (min = 337500 RPM, div = 4)              ALARM
fan3:     5720 RPM  (min = 2836 RPM, div = 4)
temp1:       +47°C  (high =   +85°C, hyst =  +125°C)   sensor = thermistor 
temp2:     +58.0°C  (high =   +90°C, hyst =   +85°C)   sensor = thermistor      (beep)
temp3:     -48.0°C  (high =   +90°C, hyst =   +85°C)   sensor = thermistor 
vid:      +1.650 V  (VRM Version 9.0)
alarms:
beep_enable:
          Sound alarm enabled

But, when I run fancontrol:

Code:

Loading configuration from /etc/fancontrol ...

Common settings:
  INTERVAL=5

Settings for 2-0290/pwm2:
  Depends on 2-0290/temp1_input
  Controls 2-0290/fan1_input
  MINTEMP=40
  MAXTEMP=70
  MINSTART=50
  MINSTOP=50

Settings for 2-0290/pwm1:
  Depends on 2-0290/temp1_input
  Controls 2-0290/fan1_input
  MINTEMP=40
  MAXTEMP=70
  MINSTART=50
  MINSTOP=50

Settings for 9191-0290/pwm2:
  Depends on 9191-0290/temp1_input
  Controls 9191-0290/fan2_input
  MINTEMP=0
  MAXTEMP=70
  MINSTART=150
  MINSTOP=100

Settings for 9191-0290/pwm1:
  Depends on 9191-0290/temp1_input
  Controls 9191-0290/fan1_input
  MINTEMP=0
  MAXTEMP=70
  MINSTART=150
  MINSTOP=100

Enabling PWM on fans...
Starting automatic fan control...
cat: 2-0290/temp1_input: No such file or directory
Error reading temperature from /sys/bus/i2c/devices/2-0290/temp1_input
Aborting, restoring fans...
/usr/sbin/fancontrol: line 123: 2-0290/pwm2: No such file or directory
/usr/sbin/fancontrol: line 123: 2-0290/pwm1: No such file or directory
Verify fans have returned to full speed

Can anybody see what I've got wrong here?

**maddbaron** · June 12th, 2006

ok this is wayyy over my head lol can someone break it down please?

i installed this program from synaptic when i boot it fails to start.

what do i type in terminal to set it all up?

**BoomAM** · June 13th, 2006

Same as above.
The 'guide' isnt the best segmented and isnt the clearest as to whats ment to go in files and whats 'chat'. Good atempt though.
But regardless, im having nothing but problems.

Hows about a simplifed/clear guide for us n00bs?

**mdecandia** · June 16th, 2006

Hi All,
I've installed Ubuntu 6.06 on Hp nx8220. I have some problem with sensors.
I followed this how-to https://wiki.ubuntu.com/SensorInstal...=%28sensors%29

and sensors-detect have found this sensors:

-------------------------------------------------------------------------
ds1621-i2c-1-4f
Adapter: SMBus stub driver
temp: +0.00°C (low = +0.0°C, high = +0.0°C)

ds1621-i2c-1-4e
Adapter: SMBus stub driver
temp: +0.00°C (low = +0.0°C, high = +0.0°C)

ds1621-i2c-1-4d
Adapter: SMBus stub driver
temp: +0.00°C (low = +0.0°C, high = +0.0°C)

ds1621-i2c-1-4c
Adapter: SMBus stub driver
temp: +0.00°C (low = +0.0°C, high = +0.0°C)

lm92-i2c-1-4b
Adapter: SMBus stub driver
CPU Temp: +0.0000°C (high = +0.0000°C, low = +0.0000°C, crit = +0.0000°C, hyst = +0.0000°C)

lm92-i2c-1-4a
Adapter: SMBus stub driver
CPU Temp: +0.0000°C (high = +0.0000°C, low = +0.0000°C, crit = +0.0000°C, hyst = +0.0000°C)

lm92-i2c-1-49
Adapter: SMBus stub driver
CPU Temp: +0.0000°C (high = +0.0000°C, low = +0.0000°C, crit = +0.0000°C, hyst = +0.0000°C)

lm92-i2c-1-48
Adapter: SMBus stub driver
CPU Temp: +0.0000°C (high = +0.0000°C, low = +0.0000°C, crit = +0.0000°C, hyst = +0.0000°C)
-------------------------------------------------------------------------

As you can see the problem is that all sensors gives 0 and also limits are null.
Do you have this problem? Any Idea?

Thanks
Michele De Candia

**BoomAM** · June 16th, 2006

I followed the above guide as well, but im getting different problems.
I copyed that data into a txt file, saved it as mkdev.sh, saved it in home.
Ran 'chmod 755 mkdev.sh' from terminal.
Then ran './mkdev.sh'
It then chucked out a loat of '/dev.i2c-number' things, from 0-31.
I then did 'sensors-detect', said yes to the first question, and then it just errors saying 'no chips were detected'.

Ideas?

##EDIT##
I tryed doing 'sudo sensors-detect' and got a series of Y/N questions, as the guide says, i answered yes to them all, but now i just get the same as i got before, an error.

Heres what i do in terminal:

Code:

boomam@boomam-laptop:~$ chmod 755 mkdev.sh
boomam@boomam-laptop:~$ ./mkdev.sh
/dev/i2c-0
mknod: `/dev/i2c-0': Permission denied
boomam@boomam-laptop:~$ sudo ./mkdev.sh
/dev/i2c-0
/dev/i2c-1
/dev/i2c-2
/dev/i2c-3
/dev/i2c-4
/dev/i2c-5
/dev/i2c-6
/dev/i2c-7
/dev/i2c-8
/dev/i2c-9
/dev/i2c-10
/dev/i2c-11
/dev/i2c-12
/dev/i2c-13
/dev/i2c-14
/dev/i2c-15
/dev/i2c-16
/dev/i2c-17
/dev/i2c-18
/dev/i2c-19
/dev/i2c-20
/dev/i2c-21
/dev/i2c-22
/dev/i2c-23
/dev/i2c-24
/dev/i2c-25
/dev/i2c-26
/dev/i2c-27
/dev/i2c-28
/dev/i2c-29
/dev/i2c-30
/dev/i2c-31
boomam@boomam-laptop:~$ sudo sensors-detect
# sensors-detect revision 1.393 (2005/08/30 18:51:18)

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

 We can start with probing for (PCI) I2C or SMBus adapters.
 You do not need any special privileges for this.
 Do you want to probe now? (YES/no): y
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801FB ICH6
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

 To continue, we need module `i2c-dev' to be loaded.
 If it is built-in into your kernel, you can safely skip this.
i2c-dev is already loaded.

 We are now going to do the adapter probings. Some adapters may hang halfway
 through; we can't really help that. Also, some chips will be double detected;
 we choose the one with the highest confidence value in that case.
 If you found that the adapter hung after probing a certain address, you can
 specify that address to remain unprobed. That often
 includes address 0x69 (clock chip).

Next adapter: SMBus I801 adapter at 18a0
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x08
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x5c

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no): y
Probing for `National Semiconductor LM78'
  Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
  Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
  Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
  Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
  Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
  Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
  Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
  Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
  Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
  Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
  Trying general detect... Failed!
Probing for `ITE IT8712F'
  Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
  Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
  Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
  Trying address 0x0ca8... Failed!

Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (skipping family)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
  Failed! (skipping family)

Do you want to scan for secondary Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (skipping family)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
  Failed! (skipping family)

 Sorry, no chips were detected.
 Either your sensors are not supported, or they are
 connected to an I2C bus adapter that we do not support.
 See doc/FAQ, doc/lm_sensors-FAQ.html, or
 http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/lm_sensors-FAQ.html
 (FAQ #4.24.3) for further information.
 If you find out what chips are on your board, see
 http://secure.netroedge.com/~lm78/newdrivers.html for driver status.
boomam@boomam-laptop:~$

**digitalkarabao** · June 17th, 2006

lm-sensors is installed but whenever i run sensors-detect and answers yes to the questions..i receive the log below.

i was able to run lm-sensors unser breezy before.

Code:

auric@digitalpenguin:~$ su
Password:
root@digitalpenguin:/home/auric# sensors-detect
# sensors-detect revision 1.393 (2005/08/30 18:51:1

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-sis96x' for device 00:02.1: Silicon Integrated Systems SMBus Controller
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-sis96x' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is already loaded.

We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).

Next adapter: SiS96x SMBus adapter at 0x0c00
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client found at address 0x10
Client found at address 0x30
Client found at address 0x31
Client at address 0x50 can not be probed - unload all client drivers first!
Client at address 0x51 can not be probed - unload all client drivers first!

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no):
Probing for `National Semiconductor LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8712F'
Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!

Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no):
Probing for `ITE 8702F Super IO Sensors'
Failed! (0xea11)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0xea11)
Probing for `ITE 8712F Super IO Sensors'
Failed! (0xea11)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
Failed! (0xea)
Probing for `Nat. Semi. PC87591 Super IO'
Failed! (0xea)
Probing for `Nat. Semi. PC87371 Super IO'
Failed! (0xea)
Probing for `Nat. Semi. PC97371 Super IO'
Failed! (0xea)
Probing for `Nat. Semi. PC8739x Super IO'
Success... (no hardware monitoring capabilities)
Probing for `Nat. Semi. PC8741x Super IO'
Failed! (0xea)
Probing for `Nat. Semi. PCPC87427 Super IO'
Failed! (0xea)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (0xea)
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
Failed! (0xea)
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed! (0xea)
Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
Failed! (0xea)
Probing for `SMSC 47S42x Super IO Fan Sensors'
Failed! (0xea)
Probing for `SMSC 47S45x Super IO Fan Sensors'
Failed! (0xea)
Probing for `SMSC 47M172 Super IO'
Failed! (0xea)
Probing for `SMSC LPC47B397-NC Super IO'
Failed! (0xea)
Probing for `VT1211 Super IO Sensors'
Failed! (0xea)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0xea)
Probing for `Winbond W83627THF Super IO Sensors'
Failed! (0xea)
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0xea)
Probing for `Winbond W83687THF Super IO Sensors'
Failed! (0xea)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0xea)
Probing for `Winbond W83697SF/UF Super IO PWM'
Failed! (0xea)
Probing for `Winbond W83L517D Super IO'
Failed! (0xea)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
Failed! (0xea11)

Do you want to scan for secondary Super I/O sensors? (YES/no):
Probing for `ITE 8702F Super IO Sensors'
Failed! (0xec11)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0xec11)
Probing for `ITE 8712F Super IO Sensors'
Failed! (0xec11)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (0xec)
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
Failed! (0xec)
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
Failed! (0xec)
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
Failed! (0xec)
Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
Failed! (0xec)
Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
Failed! (0xec)
Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
Failed! (0xec)
Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
Failed! (0xec)
Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
Failed! (0xec)
Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
Failed! (0xec)
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
Failed! (0xec)
Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
Failed! (0xec)
Probing for `Nat. Semi. PC87591 Super IO'
Success... but not activated
Probing for `Nat. Semi. PC87371 Super IO'
Failed! (0xec)
Probing for `Nat. Semi. PC97371 Super IO'
Failed! (0xec)
Probing for `Nat. Semi. PC8739x Super IO'
Failed! (0xec)
Probing for `Nat. Semi. PC8741x Super IO'
Failed! (0xec)
Probing for `Nat. Semi. PCPC87427 Super IO'
Failed! (0xec)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (0xec)
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
Failed! (0xec)
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed! (0xec)
Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
Failed! (0xec)
Probing for `SMSC 47S42x Super IO Fan Sensors'
Failed! (0xec)
Probing for `SMSC 47S45x Super IO Fan Sensors'
Failed! (0xec)
Probing for `SMSC 47M172 Super IO'
Failed! (0xec)
Probing for `SMSC LPC47B397-NC Super IO'
Failed! (0xec)
Probing for `VT1211 Super IO Sensors'
Failed! (0xec)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0xec)
Probing for `Winbond W83627THF Super IO Sensors'
Failed! (0xec)
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0xec)
Probing for `Winbond W83687THF Super IO Sensors'
Failed! (0xec)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0xec)
Probing for `Winbond W83697SF/UF Super IO PWM'
Failed! (0xec)
Probing for `Winbond W83L517D Super IO'
Failed! (0xec)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
Failed! (0xec11)

Sorry, no chips were detected.
Either your sensors are not supported, or they are
connected to an I2C bus adapter that we do not support.

help guys. this is the only bump i hit after installing dapper. everything is working fine.

**BoomAM** · June 17th, 2006

Ive done some searching around and aparentely theres rumors that the lm-sensors software isnt recommended for laptops, especially Thinkpads. Because they dont use sensors in the traditional sence, they access them via ACPI.
Can anyone confirm that