HOW TO: Install and configure lm-sensors

[Chupa]

The reason is that the Asus P5B line uses the `Winbond W83627DHG Super IO' chip. The w83627EHG driver included with Feisty's 2.6.20-15 kernel is an older version of the driver which lacks DHG support. The new 2.6.21 kernel includes proper support - the updated driver wasn't complete until mid February, which was too late to be included in Feisty. I am not going to risk all the incompatibilities/breaking things by installing the .21 kernel, maybe we will get lucky and someone will release a patch to make the new driver work with the older kernel?

I have 2.6.21 kernel installed. The quest is why sensors are shown in gkrellm and not shown in sensors?

[gosh3t0]

Im.. newbie. I have ubuntu edgy for a week. I tried this howto... but... something isn't right . Look what i've done ,and help me if you can. I've installed lm-sensor ... make the script executable and typed sensors-detect
gosh3t0@gosh3t0-desktop:~$ sudo sensors-detect
# sensors-detect revision 4348 (2007-03-18 02:45:21 -0700)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. 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.
Do you want to probe now? (YES/no): y
Probing for PCI bus adapters...
Use driver `i2c-nforce2' for device 0000:00:01.1: nVidia Corporation nForce4 SMBus (MCP)

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

We are now going to do the I2C/SMBus adapter probings. Some chips may
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.

Next adapter: NVIDIA i2c adapter 2 at 5:00.0 (i2c-4)
Do you want to scan it? (YES/no/selectively): y

Next adapter: NVIDIA i2c adapter 1 at 5:00.0 (i2c-3)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Success!
(confidence 8, driver `eeprom'), other addresses: 0x51 0x52 0x53 0x54 0x55 0x56 0x57
Probing for `Maxim MAX6900'... No

Next adapter: NVIDIA i2c adapter 0 at 5:00.0 (i2c-2)
Do you want to scan it? (YES/no/selectively): y

Next adapter: SMBus nForce2 adapter at f400 (i2c-1)
Do you want to scan it? (YES/no/selectively): y

Next adapter: SMBus nForce2 adapter at f800 (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x50
Handled by driver `eeprom' (already loaded), chip type `eeprom'

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no): y
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM78-J' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Probing for `Silicon Integrated Systems SIS5595'... No
Probing for `VIA VT82C686 Integrated Sensors'... No
Probing for `VIA VT8231 Integrated Sensors'... No
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `ITE'... No
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'... No
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... Yes
Found `Fintek F71872F/FG Super IO Sensors' Success!
(address 0x295, driver `f71805f')

Some CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no): y
AMD K8 thermal sensors... Success!
(driver `k8temp')
Intel Core family thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `NVIDIA i2c adapter 1 at 5:00.0'
Busdriver `UNKNOWN', I2C address 0x50 (and 0x51 0x52 0x53 0x54 0x55 0x56 0x57)
Chip `EDID EEPROM' (confidence: 8)
* Bus `SMBus nForce2 adapter at f800'
Busdriver `i2c-nforce2', I2C address 0x50
Chip `eeprom' (confidence: 6)

EEPROMs are *NOT* sensors! They are data storage chips commonly
found on memory modules (SPD), in monitors (EDID), or in some
laptops, for example.

Driver `f71805f' (should be inserted):
Detects correctly:
* ISA bus, address 0x295 (Busdriver `i2c-isa')
Chip `Fintek F71872F/FG Super IO Sensors' (confidence: 9)

Driver `k8temp' (should be inserted):
Detects correctly:
* Chip `AMD K8 thermal sensors' (confidence: 9)

I will now generate the commands needed to load the required modules.
Just press ENTER to continue:

To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# I2C adapter drivers
# modprobe unknown adapter NVIDIA i2c adapter 0 at 5:00.0
# modprobe unknown adapter NVIDIA i2c adapter 1 at 5:00.0
# modprobe unknown adapter NVIDIA i2c adapter 2 at 5:00.0
modprobe i2c-nforce2
modprobe i2c-isa
# Chip drivers
modprobe eeprom
modprobe f71805f
# Warning: the required module k8temp is not currently installed
# on your system. For status of 2.6 kernel ports check
# http://www.lm-sensors.org/wiki/Devices. If driver is built
# into the kernel, or unavailable, comment out the following line.
modprobe k8temp
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----

If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones! You really
should try these commands right now to make sure everything is
working properly. Monitoring programs won't work until the needed
modules are loaded.

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
gosh3t0@gosh3t0-desktop:~$ sudo gedit /etc/modules
gosh3t0@gosh3t0-desktop:~$ /etc/init.d/module-init-tools
open: Permission denied
* Loading manual drivers... open: Permission denied
[ ok ]
gosh3t0@gosh3t0-desktop:~$ sudo /etc/init.d/module-init-tools
* Loading manual drivers... [ ok ]
gosh3t0@gosh3t0-desktop:~$ sudo modprobe i2c-sensor
FATAL: Module i2c_sensor not found.
gosh3t0@gosh3t0-desktop:~$ sudo modprobe i2c-viapro
gosh3t0@gosh3t0-desktop:~$ sudo modprobe i2c-isa
gosh3t0@gosh3t0-desktop:~$ sudo modprobe it87
gosh3t0@gosh3t0-desktop:~$ sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
gosh3t0@gosh3t0-desktop:~$

[jegrcek]

Hi
i was folloving the guide on ubntuguide, but lm-sensors dont detect any sensors. What could be wrong?

jegrcek@ubuntu:~$ sudo /etc/init.d/module-init-tools
Password:
 * Loading kernel modules...                                                     * Loading manual drivers...                                             [ OK ] 
jegrcek@ubuntu:~$ sudo sensors -s
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
jegrcek@ubuntu:~$ sudo sensors-detect
# sensors-detect revision 4171 (2006-09-24 03:37:01 -0700)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. 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.
Do you want to probe now? (YES/no): y
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel ICH8

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.
Do you want to load `i2c-dev' now? (YES/no): y
Module loaded successfully.

We are now going to do the I2C/SMBus adapter probings. Some chips may
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.

Next adapter: NVIDIA i2c adapter 2 at 1:00.0
Do you want to scan it? (YES/no/selectively): y

Next adapter: NVIDIA i2c adapter 1 at 1:00.0
Do you want to scan it? (YES/no/selectively): y

Next adapter: NVIDIA i2c adapter 0 at 1:00.0
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x37
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Success!
    (confidence 1, driver `eeprom')
Probing for `EDID EEPROM'...                                Success!
    (confidence 8, driver `eeprom'), other addresses: 0x51 0x52 0x53 0x54 0x55 0x56 0x57
Probing for `Maxim MAX6900'...                              No

Next adapter: SMBus I801 adapter at 0400
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x08
Client found at address 0x22
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM78-J'...              No
Probing for `National Semiconductor LM79'...                No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83627HF'...                           No
Client found at address 0x30
Client found at address 0x50
Handled by driver `eeprom' (already loaded), chip type `eeprom'
Client found at address 0x69

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no): y
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM78-J' at 0x290...     No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No
Probing for `Winbond W83627HF' at 0x290...                  No
Probing for `Silicon Integrated Systems SIS5595'...         No
Probing for `VIA VT82C686 Integrated Sensors'...            No
Probing for `VIA VT8231 Integrated Sensors'...              No
Probing for `AMD K8 thermal sensors'...                     No
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `ITE'...                                      Yes
Found unknown chip with ID 0xa023
    (logical device B has address 0x290, could be sensors)
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       Yes
Found `Winbond W83627DHG Super IO Sensors'                  Success!
    (address 0x290, driver `w83627ehf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'...                                      No
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No

Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `eeprom' (should be inserted):
  Detects correctly:
  * Bus `NVIDIA i2c adapter 0 at 1:00.0'
    Busdriver `UNKNOWN', I2C address 0x50 (and 0x51 0x52 0x53 0x54 0x55 0x56 0x57)
    Chip `EDID EEPROM' (confidence: 8)
  * Bus `SMBus I801 adapter at 0400'
    Busdriver `i2c-i801', I2C address 0x50
    Chip `eeprom' (confidence: 6)

  EEPROMs are *NOT* sensors! They are data storage chips commonly
  found on memory modules (SPD), in monitors (EDID), or in some
  laptops, for example.

Driver `w83627ehf' (should be inserted):
  Detects correctly:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9)

I will now generate the commands needed to load the required modules.
Just press ENTER to continue: 

To make the sensors modules behave correctly, add these lines to
/etc/modules:

#----cut here----
# I2C adapter drivers
# modprobe unknown adapter NVIDIA i2c adapter 0 at 1:00.0
# modprobe unknown adapter NVIDIA i2c adapter 1 at 1:00.0
# modprobe unknown adapter NVIDIA i2c adapter 2 at 1:00.0
i2c-i801
# Chip drivers
eeprom
w83627ehf
#----cut here----


Do you want to add these lines to /etc/modules automatically? (yes/NO)y
jegrcek@ubuntu:~$ sudo /etc/init.d/module-init-tools
 * Loading kernel modules...                                                     * Loading manual drivers...                                             [ OK ] 
jegrcek@ubuntu:~$ sudo sensors -s
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
jegrcek@ubuntu:~$ sudo sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

[mrazster]

Just did this on my DFI NF4 Ultra-D ...and it works flawlessly, modules load perfectly everytime on reboot.

Thnx...a bunch.

[h0bbe]

I've followed both the HOW TO above an this one http://news.softpedia.com/news/How-t...tu-47205.shtml. But still don't get it working. My /etc/modules file looks like this:

# Generated by sensors-detect on Thu May 10 21:27:12 2007
# I2C adapter drivers
i2c-ali1535
# Chip drivers
eeprom

Does this mean anything I don't understand? There is no "2c-isa" as in the both HOW TO:s.

Please help me!

[bambit]

I'm running Feisty on a Toshiba Satellite Pro M10 and this is what I get after sensors-detect:

# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
#----cut here----
# I2C adapter drivers
# modprobe unknown adapter NVIDIA i2c adapter 0 at 1:00.0
# modprobe unknown adapter NVIDIA i2c adapter 1 at 1:00.0
# modprobe unknown adapter NVIDIA i2c adapter 2 at 1:00.0
# Chip drivers
# no driver for Smart Battery Charger yet
# Warning: the required module smartbatt is not currently installed
# on your system. For status of 2.6 kernel ports check
# http://www.lm-sensors.org/wiki/Devices. If driver is built
# into the kernel, or unavailable, comment out the following line.
smartbatt
#----cut here----

and then when I run sensors I get:

No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

I'm stumped and don't know what to do next. Please help.

[leona]

Hi, can someone help me out here.
This used to work for me, I had an Asus A8V VIA board, now I've upgraded to an Asus M2N-E boad NForce, and now non of the sensors are detected.
I reran the scripts, ran Sensor-detect, installed the required Kernal moduals, but alas when I do 'sensors' I get No Sensors Found,
What can I do to fix this?

[Browser_ice]

When I got to "3. Now run sensors-detect", I replied YES to the first 2-3 questions and then the whole graphic screwed up completly and I couldn't do anything else. I had to reboot completly. I'm typing on another PC cause I didn't know if I screwed up my Ubuntu or not.

Prior to this, I had installed xsensors, ksensors and hddtemp.

This is on an PC at the office. ITs an desktop IBM NetVista.



This is following a thread I did about this PC being extreamly slow after being left ON for a while.

[zipeppe]

No way for me
lm-sensors doesn't work on my laptop ASUS A6J.
"no sensor detected" as shown:

massimo@A6Ja:~$ sudo sensors-detect
# sensors-detect revision 4171 (2006-09-24 03:37:01 -0700)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. 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.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Sorry, no known PCI bus adapters found.

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

We are now going to do the I2C/SMBus adapter probings. Some chips may
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.

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM78-J' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Probing for `Winbond W83627HF' at 0x290... No
Probing for `Silicon Integrated Systems SIS5595'... No
Probing for `VIA VT82C686 Integrated Sensors'... No
Probing for `VIA VT8231 Integrated Sensors'... No
Probing for `AMD K8 thermal sensors'... No
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `ITE'... No
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'... No
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No

Sorry, no sensors were detected.
Either your sensors are not supported, or they are connected to an
I2C or SMBus adapter that is not supported. See doc/FAQ,
doc/lm_sensors-FAQ.html or http://www.lm-sensors.org/wiki/FAQ
(FAQ #4.24.3) for further information.
If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.

Please, could you help me?
Everything works fine with SpeedFan and Windows XP.

I am using ubuntu 7.04 x86
ZPP

[kwaanens]

I have an MSI s262 notebook. I tried running sensors-detect, checking if there was some modules that could be loaded, that isn't already. When rebooting, the computer hangs at the very start. I hold the start/stop button and shut the computer down. Now, when I restart, BIOS doesn't start. The power and wireless lights show up, and stay that way. HDD-light flashes once, then stops.
I did this twice. Both times with the same result. I got a little worried, since I had no idea what to do. So I ended up with the longshot of removing the battery, and putting it back. Then my computer starts.

Does anyone have an idea what to do? (For now, the solution is: never commit changes from sensors-detect...)
If anyone else is using the s262, what BIOS do you use? There's an update that I did not install, and I'm wondering if it's worth the bother (it's an update to get Vista going, and I'm mono-booting Feisty, so does it matter to me?)
Also the CPU temperature seems a bit high (stable at +/- 50 degrees C). Mind you, this is a 12,1 inch, so there's not much room inside, so hw is crowded, I guess that might account for some.

- Ketil