PDA

View Full Version : HOW TO: Install and configure lm-sensors



Pages : [1] 2

emperor
October 31st, 2004, 10:00 PM
Howto Install and Configure lm-sensors
========================

1. Install lm-sensors using apt-get or the Synaptic GUI.

sudo apt-get install lm-sensors


2. Run the mkdev.sh script in the lm-sensors source. It is extacted below:

a. Copy the script file below to a text editor and save it to a file named mkdev.sh.

#!/bin/bash

# Here you can set several defaults.

# The number of devices to create (max: 256)
NUMBER=32

# The owner and group of the devices
OUSER=root
OGROUP=root
# The mode of the devices
MODE=600

# This script doesn't need to be run if devfs is used
if [ -r /proc/mounts ] ; then
if grep -q "/dev devfs" /proc/mounts ; then
echo "You do not need to run this script as your system uses devfs."
exit;
fi
fi

i=0;

while [ $i -lt $NUMBER ] ; do
echo /dev/i2c-$i
mknod -m $MODE /dev/i2c-$i c 89 $i || exit
chown "$OUSER:$OGROUP" /dev/i2c-$i || exit
i=$[$i + 1]
done
#end of file

b. Make the file executable:

chmod 755 mkdev.sh

c. Run mkdev.sh from the current directory

sudo ./mkdev.sh


3. Now run sensors-detect and answer YES to all YES/no questions. I generally use the ISA bus rather than the SMBus bus, your choice to this question!. At the end of the detection phase, a list of modules that needs to be loaded will displayed. You will need to write these down or print the list for the next steps.

sudo sensors-detect

Below is an example of results from sensors-detect:
#************************************************* *****************************
To make the sensors modules behave correctly, add these lines to
/etc/modules:

#----cut here----
# I2C adapter drivers
i2c-viapro
i2c-isa
# I2C chip drivers
eeprom
it87
#----cut here----

Then, run /etc/init.d/module-init-tools

To make the sensors modules behave correctly, add these lines to
/etc/modprobe.d/local and run update-modules:

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


4. In this example, we add the modules in reverse order (order is critical!) in "/etc/modules".

#************************************************* ***********************
# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a "#", and everything on the line after them are ignored.

psmouse
mousedev
ide-cd
ide-disk
ide-generic
lp

#For lm-sensors, i2c modules
it87
i2c-viapro
i2c-isa

#end of file!
#************************************************* ****************


4. I found that there was no "/etc/modprobe.d/local" and that "alias char-major-89 i2c-dev" was already listed in "/etc/modprobe.d/aliases". So, nothing to do here.


5.Now load the modules manually using modprobe and update the dependencies.

sudo modprobe i2c-sensor
sudo modprobe i2c-viapro
sudo modprobe i2c-isa
sudo modprobe it87

sudo depmod -a <may not be needed!>
sudo update-modules <may not be needed!>


6. Now test the sensor output using the lm-sensors utility "sensors".

sensors

************************************************** *****************
it87-isa-0290
Adapter: ISA adapter
VCore 1: +1.57 V (min = +1.42 V, max = +1.57 V) ALARM
VCore 2: +2.66 V (min = +2.40 V, max = +2.61 V) ALARM
+3.3V: +6.59 V (min = +3.14 V, max = +3.46 V) ALARM
+5V: +5.11 V (min = +4.76 V, max = +5.24 V)
+12V: +11.78 V (min = +11.39 V, max = +12.61 V)
-12V: -19.14 V (min = -12.63 V, max = -11.41 V) ALARM
-5V: +0.77 V (min = -5.26 V, max = -4.77 V) ALARM
Stdby: +5.00 V (min = +4.76 V, max = +5.24 V)
VBat: +3.12 V
fan1: 3668 RPM (min = 0 RPM, div = :cool:
fan2: 0 RPM (min = 664 RPM, div = :cool: ALARM
fan3: 0 RPM (min = 2657 RPM, div = 2) ALARM
M/B Temp: +39C (low = +15C, high = +40C) sensor = thermistor
CPU Temp: +36C (low = +15C, high = +45C) sensor = thermistor
Temp3: +96C (low = +15C, high = +45C) sensor = diode
************************************************** ********************

7. Reboot Ubuntu and the sensors should now be detected during the boot process properly!

8. The sensor output may be tweaked by editing the "/etc/sensors.conf" file. It is possible to correct inacurate scaling too. For details check "man sensors.conf.

jgaynor
January 17th, 2005, 01:04 AM
EXCELLENT howto man - I had been struggling with this using the debian method but this worked without issue. Thanks again!

Tichondrius
January 17th, 2005, 12:26 PM
Works great, I was looking for something like this for overclocking...
But I did not understand what you said about the reverse order in /etc/modules. What exactly should be reversed ?

BTW, if you want a graphical output, try installing the "xsensors" package which uses lm-sensors.

Rule
January 17th, 2005, 01:04 PM
Well I gess I got it working for once but when I type in "sensors" mine comes out differant from your :confused:


eeprom-i2c-0-51
Adapter: SiS96x SMBus adapter at 0x0c00
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

eeprom-i2c-0-50
Adapter: SiS96x SMBus adapter at 0x0c00
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

woifi
January 17th, 2005, 01:39 PM
Well I gess I got it working for once but when I type in "sensors" mine comes out differant from your :confused:


eeprom-i2c-0-51
Adapter: SiS96x SMBus adapter at 0x0c00
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

eeprom-i2c-0-50
Adapter: SiS96x SMBus adapter at 0x0c00
Memory type: DDR SDRAM DIMM
Memory size (MB): 256
is this your full output? if yes, something went wrong ;)

it should look like this:

woifi@homer:~ $ sensors
Philips PAL_BG -i2c-2-61
Adapter: bt878 #0 [sw]

MSP3410D-i2c-2-40
Adapter: bt878 #0 [sw]

eeprom-i2c-2-50
Adapter: bt878 #0 [sw]
Unknown EEPROM type (0)

w83627hf-isa-0290
Adapter: ISA adapter
VCore 1: +1.74 V (min = +1.76 V, max = +1.94 V) ALARM
VCore 2: +1.25 V (min = +1.76 V, max = +1.94 V)
+3.3V: +3.22 V (min = +3.14 V, max = +3.47 V)
+5V: +4.87 V (min = +4.76 V, max = +5.24 V)
+12V: +12.71 V (min = +10.82 V, max = +13.19 V)
-12V: -12.77 V (min = -13.18 V, max = -10.80 V)
-5V: -5.55 V (min = -5.25 V, max = -4.75 V)
V5SB: +5.51 V (min = +4.76 V, max = +5.24 V)
VBat: +3.17 V (min = +2.40 V, max = +3.60 V)
fan1: 0 RPM (min = 3199 RPM, div = 2)
fan2: 0 RPM (min = 3040 RPM, div = 2)
fan3: 0 RPM (min = 13500 RPM, div = 2)
temp1: +25C (high = +15C, hyst = -3C) sensor = thermistor
temp2: +32.5C (high = +80C, hyst = +75C) sensor = thermistor
temp3: -46.0C (high = +80C, hyst = +75C) sensor = thermistor
vid: +1.850 V
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm disabled

eeprom-i2c-0-51
Adapter: SMBus Via Pro adapter at 0400
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

eeprom-i2c-0-50
Adapter: SMBus Via Pro adapter at 0400
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

hth

woifi

Rule
January 17th, 2005, 01:43 PM
well I did see some failures :( maybe thats why, i'm on an Averatec 6100 laptop. I also noticed in my bios it doesnt even tell me the temps :twisted: :-s

EDIT: when I try to run sensors-dectect and hit enter a few time I get


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.

also I attatched some of the errors I got before

barbarian
January 17th, 2005, 06:53 PM
eeprom-i2c-0-51
Adapter: SiS96x SMBus adapter at 0x0c00
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

eeprom-i2c-0-50
Adapter: SiS96x SMBus adapter at 0x0c00
Memory type: DDR SDRAM DIMM
Memory size (MB): 256


The same output for me..

Adapter: SMBus Via Pro adapter at 5000
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

eeprom-i2c-0-50
Adapter: SMBus Via Pro adapter at 5000
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

barbarian
January 18th, 2005, 09:13 AM
Noob qestion, but could You notice which place should I put mkdev.sh? usr/share/lmsensors?

emperor
January 18th, 2005, 08:40 PM
Noob qestion, but could You notice which place should I put mkdev.sh? usr/share/lmsensors?

You are just going to run the "mkdev.sh" file once, prior to executing sensors-detect.

I put the script file in a sub-directory in my home directory. However, for permanent storage, it can be put almost anywhere you have prev's.

barbarian
January 19th, 2005, 10:03 AM
Ok, thanx, I'll give a try once more..

*aLeX*
January 19th, 2005, 11:58 PM
Hi all!!

I had the same problem... than I tried to swap order in which modules were loaded and now it seems ok even if I get values only from the via module!

This is my output: (some values are a bit strange)



via686a-isa-6000
Adapter: ISA adapter
CPU core: +3.10 V (min = +3.07 V, max = +3.00 V) ALARM
+2.5V: +0.06 V (min = +3.08 V, max = +3.10 V) ALARM
I/O: +3.33 V (min = +4.01 V, max = +3.82 V) ALARM
+5V: +3.27 V (min = +3.08 V, max = +6.44 V)
+12V: +7.93 V (min = +11.77 V, max = +13.68 V) ALARM
CPU Fan: 0 RPM (min = 0 RPM, div = 2)
P/S Fan: 0 RPM (min = 0 RPM, div = 2)
SYS Temp: +23.9C (high = +146C, hyst = +146C)
CPU Temp: +23.9C (high = +141C, hyst = +146C)
SBr Temp: +24.9C (high = +20C, hyst = +34C) ALARM


and thi is the order in which i loaded the modules:



modprobe via686a
modprobe eeprom
modprobe i2c-viapro
modprobe i2c-isa

emperor
January 20th, 2005, 03:34 AM
Hi all!!

I had the same problem... than I tried to swap order in which modules were loaded and now it seems ok even if I get values only from the via module!

This is my output: (some values are a bit strange)
The values that are display are calculate from the raw sensor data and sometime the formula needs to be corrected. See "/etc/sensors.conf".

*aLeX*
January 20th, 2005, 11:01 AM
Thank you.. so now i try to trim them!

barbarian
January 20th, 2005, 10:06 PM
Finaly I'v got it, here's my output:
$ sensors
lm90-i2c-0-4c
Adapter: SMBus Via Pro adapter at 5000
M/B Temp: +46C (low = +0C, high = +70C)
CPU Temp: +50.6C (low = +0.0C, high = +70.0C)
M/B Crit: +95C (hyst = +85C)
CPU Crit: +95C (hyst = +85C)

kiwigander
March 1st, 2005, 01:30 AM
Thank you Emperor! Step-by-step instructions that 1) even I could follow and 2) gave a successful outcome on the first try.

RastaMahata
March 1st, 2005, 04:52 AM
well this doesnt work on my nforce2 chipset :(

it told me this:



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

#----cut here----
# I2C adapter drivers
i2c-nforce2
i2c-nforce2
i2c-isa
# I2C chip drivers
eeprom
w83627hf
#----cut here----

Then, run /etc/init.d/module-init-tools


To make the sensors modules behave correctly, add these lines to
/etc/modprobe.d/local and run update-modules:

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


so I did it, but I get to this point:



$ sudo modprobe w83627hf
FATAL: Error inserting w83627hf (/lib/modules/2.6.8.1-5-k7/kernel/drivers/i2c/chips/w83627hf.ko): No such device


what can I do? I'm a warty user.

rosslaird
March 1st, 2005, 07:47 AM
It doesn't work on my nforce chipset either -- but I have NEVER been able to get lm-sensors to work with my board in over two years of trying. I think it's an nforce-specific problem.

RastaMahata
March 1st, 2005, 06:45 PM
I got it! Just googling and reading the whole output of sensors-detect, I was able to install lm-sensors in my nforce2 chipset! Here's how I did it:

You can see here something fishy:

Probing for `Winbond W83627HF'
Trying address 0x0290... Success!
(confidence 8, driver `w83781d')

Anyway, I found out that w83627hf is not the right module needed for the nforce2 chipset! The right one is the driver suggested below, the w83781d.

So, here's the correct output needed:

# I2C adapter drivers
i2c-nforce2
i2c-nforce2
i2c-isa
# I2C chip drivers
eeprom
w83781d

copy that to /etc/modules

then issue these commands:

$ sudo modprobe i2c-isa
$ sudo modprobe i2c-nforce2
$ sudo modprobe w83781d
$ sudo modprobe eeprom
$ sudo /etc/init.d/module-init-tools
$ sudo update-modules

Then just run this:

$ sensors

And it should give you something like this:

w83627hf-isa-0290
Adapter: ISA adapter
VCore 1: +1.47 V (min = +1.14 V, max = +1.55 V)
VCore 2: +1.54 V (min = +1.14 V, max = +1.55 V) ALARM
+3.3V: +3.33 V (min = +2.82 V, max = +3.79 V)
+5V: +5.05 V (min = +0.00 V, max = +0.00 V) ALARM
+12V: +12.22 V (min = +0.00 V, max = +0.00 V) ALARM
-12V: -12.53 V (min = -14.91 V, max = -14.91 V) ALARM
-5V: -5.35 V (min = -7.71 V, max = -7.71 V) ALARM
V5SB: +5.43 V (min = +0.43 V, max = +0.00 V) ALARM
VBat: +3.04 V (min = +0.00 V, max = +0.00 V) ALARM
fan1: 0 RPM (min = -1 RPM, div = 2) ALARM
fan2: 3994 RPM (min = -1 RPM, div = 2) ALARM
fan3: 0 RPM (min = 3245 RPM, div = 4) ALARM
temp1: +34C (high = +0C, hyst = +0C) sensor = thermistor ALARM
temp2: +36.5C (high = +53C, hyst = +48C) sensor = thermistor
temp3: +37.0C (high = +53C, hyst = +48C) sensor = thermistor
vid: +1.350 V
alarms:
beep_enable:
Sound alarm disabled

eeprom-i2c-0-51
Adapter: SMBus nForce2 adapter at 5000
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

Although I'm not sure if that eeprom is right in there.. and all those "alarm" messages too

Cyberkef
March 3rd, 2005, 04:23 PM
...

c. Run mkdev.sh from the current directory

sudo ./mkdev.sh

...
I got stuck here #-o


cyberkef@CyberTrax2000:~/Desktop $ dir
mkdev.sh proxy.txt~
mkdev.sh~ Share\ 120GB.desktop~
mplayer~
cyberkef@CyberTrax2000:~/Desktop $ sudo ./mkdev.sh
sudo: unable to exec ./mkdev.sh: No such file or directory

The chmod is 755.

Hm, I don't see why he doesn't find the file, it is there! In the Desktop directory!
Even in another directory I have the same error :confused:

rosslaird
March 5th, 2005, 04:45 PM
Thanks, RastaMahata. Your instructions worked perfectly for me. I can now properly monitor my box, which is designed for silence and sits away in a drawer. I can't hear it, can't see it, and have had until now no input about what's going on inside of it. Now I know.

Cheers.

Ross

RastaMahata
March 5th, 2005, 05:15 PM
Thanks, RastaMahata. Your instructions worked perfectly for me. I can now properly monitor my box, which is designed for silence and sits away in a drawer. I can't hear it, can't see it, and have had until now no input about what's going on inside of it. Now I know.

Cheers.

Ross
no problem :P

fackamato
March 8th, 2005, 12:35 AM
How about a howto for the program that comes with lm-sensors - fancontrol? ;)

Sure many users who use Speedfan in windows wants some software to control their fans. :D

mario8723
March 17th, 2005, 09:29 AM
Some help here please...I get to the point where I have to modify the /etc/modprobe.d/local but I can't find it; doesn't seem to exist...Any suggestions would be most welcome!

I know I must be close, because I can run system apps from gdesklets now, where previously I couldn't. The only thing it doesn't seem to show is the temps...

fackamato
March 17th, 2005, 09:32 AM
Some help here please...I get to the point where I have to modify the /etc/modprobe.d/local but I can't find it; doesn't seem to exist...Any suggestions would be most welcome!

Don't you mean /etc/modules ? (where you put modules that should automatically load on boot)

mario8723
March 17th, 2005, 09:38 AM
I don't have that either. I do have modutils, but I'm looking in the /etc/ folder right now and I don't have modules. Did I do something wrong?

Hurky
April 5th, 2005, 01:55 PM
Hi, I get this error trying to install lmsensors... What am I doing wrong?


sudo apt-get install lm-sensors
Reading Package Lists... Done
Building Dependency Tree... Done
Package lm-sensors is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package lm-sensors has no installation candidate

jr_G-man
April 12th, 2005, 12:15 PM
Worked great for me on my KT400-based board. Thanks.

kuleali
April 12th, 2005, 03:10 PM
thanks!

jodsalz
May 18th, 2005, 07:40 PM
I used this howto and installed the right modules correctly, but when doing "sensors" I only can read "no sensors detected"... Any ideas? Use this thread: http://ubuntuforums.org/showthread.php?p=177493

Thanks!

fackamato
May 18th, 2005, 08:22 PM
I used this howto and installed the right modules correctly, but when doing "sensors" I only can read "no sensors detected"... Any ideas? Use this thread: http://ubuntuforums.org/showthread.php?p=177493

Thanks!

Didn't sensors-detect find anything?

jodsalz
May 18th, 2005, 10:28 PM
Didn't sensors-detect find anything?

Well, thats the problem! sensors-detect DID find something, and I loaded the proposed modules. Please take a look: http://ubuntuforums.org/showthread.php?p=177493

simple
June 13th, 2005, 12:28 AM
well I did see some failures :( maybe thats why, i'm on an Averatec 6100 laptop. I also noticed in my bios it doesnt even tell me the temps :twisted: :-s

EDIT: when I try to run sensors-dectect and hit enter a few time I get


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.

also I attatched some of the errors I got before
i get this too not using sudo first.. my mobo's spec asus goldfish mobo (http://h10025.www1.hp.com/ewfrf/wc/document?lc=en&lang=en&cc=us&product=449732&dlc=en&docname=c00300046)
with sudo i get
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus I801 adapter at 0400' (Algorithm unavailable)
Busdriver `i2c-i801', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus I801 adapter at 0400' (Algorithm unavailable)
Busdriver `i2c-i801', I2C address 0x52
Chip `SPD EEPROM' (confidence: 8)
will this get me to like.. tell temp and stuff?

simple
June 13th, 2005, 12:40 AM
simple@elemental:~$ sensors
eeprom-i2c-0-52
Adapter: SMBus I801 adapter at 0400
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

eeprom-i2c-0-50
Adapter: SMBus I801 adapter at 0400
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

simple@elemental:~$

must've have something the same as Rule.. if something went wrong, it's not my fault.. though because i did it exactally.. except i got now..


simple@elemental:~$ sudo /etc/init.d/module-init-tools
* Calculating module dependencies... [ ok ]
* Loading modules...
To make the sensors modules behave correctly, add these lines to
/etc/modprobe.d/local and run update-modules:

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

was i supposed to see that? i never saw anything like that.

simple
June 13th, 2005, 12:47 AM
i guess if you could take a quick look at the attachment, my chip isn't compatible ?
pc spec (http://h10025.www1.hp.com/ewfrf/wc/document?lc=en&lang=en&cc=us&product=449732&dlc=en&docname=c00280721)

electrosoccertux
June 18th, 2005, 05:00 AM
Hey, thank you so much for this guide.

icecube76
June 22nd, 2005, 11:45 AM
i have hp pavilion ze4900
and thats what i get
root@vega:/home/abdulsalam # sudo sensors-detect

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.

IF THIS IS AN IBM THINKPAD, PRESS CTRL-C NOW!
IBM Thinkpads have a severely broken i2c/SMBus implementation, just scanning
the bus will break your Thinkpad forever!
If this is a non-Thinkpad IBM, we still suggest you press CTRL+C. We have
had users reporting system breakage on other IBM systems as well.

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): no

As you skipped adapter detection, we will only scan already loaded
adapter modules.
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 1880
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x30
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!
Client found at address 0x69

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): no

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): no

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.
root@vega:/home/abdulsalam # sensors
eeprom-i2c-0-51
Adapter: SMBus I801 adapter at 1880
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

eeprom-i2c-0-50
Adapter: SMBus I801 adapter at 1880
Memory type: DDR SDRAM DIMM
Memory size (MB): 256

any help

aragorn2909
June 25th, 2005, 08:02 AM
Perhaps someone can help me here. I've gone through the steps here, but my actual cpu temp is not displayed


it8712-isa-0290
Adapter: ISA adapter
VCore 1: +1.79 V (min = +1.42 V, max = +1.57 V) ALARM
VCore 2: +0.00 V (min = +2.40 V, max = +2.61 V) ALARM
+3.3V: +6.56 V (min = +3.14 V, max = +3.46 V) ALARM
+5V: +4.92 V (min = +4.76 V, max = +5.24 V)
+12V: +12.48 V (min = +11.39 V, max = +12.61 V) ALARM
-12V: -27.36 V (min = -12.63 V, max = -11.41 V) ALARM
-5V: -13.64 V (min = -5.26 V, max = -4.77 V) ALARM
Stdby: +5.00 V (min = +4.76 V, max = +5.24 V)
VBat: +4.08 V
fan1: 4245 RPM (min = 0 RPM, div = 2)
fan2: 0 RPM (min = 2657 RPM, div = 2) ALARM
fan3: 0 RPM (min = 2657 RPM, div = 2) ALARM
M/B Temp: +52C (low = +15C, high = +40C) sensor = thermistor
CPU Temp: +34C (low = +15C, high = +45C) sensor = thermistor
Temp3: -1C (low = +15C, high = +45C) sensor = disabled

eeprom-i2c-0-50
Adapter: SMBus Via Pro adapter at e800
Memory type: DDR SDRAM DIMM
Memory size (MB): 512

How to enable "temp3" sensor?

DonVla
June 30th, 2005, 11:16 PM
great howto,

worked directly.

thank you!!!!


vlad

otherdave
July 10th, 2005, 11:50 PM
First off, this was awesome. I first looked at it and said "What? Scripts and stuff? Forget this..." and went off to do something else. I came back to it and actually READ through it and said "Oh this is nothing!" and it worked correctly for me the FIRST TIME. Excellent instructions.

Second off: Like some others here, I'm using an NForce 2 motherboard (Epox 8rDA+ or something). Does anyone know what the temp sensors map to? T1 is low (I'm guessing ambient temperature), t2 is high (cpu probably) and t3 is about 10 degrees (F) lower than t2 so I'm guessing it's either another chip or the mobo temp? Not sure. I can crack the case open and check the fan settings, but I'm not sure about the temperature sensors. Any ideas?

Thanks again for a simple and well-written guide.

Beire
July 18th, 2005, 05:56 PM
First off, this was awesome. I first looked at it and said "What? Scripts and stuff? Forget this..." and went off to do something else. I came back to it and actually READ through it and said "Oh this is nothing!" and it worked correctly for me the FIRST TIME. Excellent instructions.

Second off: Like some others here, I'm using an NForce 2 motherboard (Epox 8rDA+ or something). Does anyone know what the temp sensors map to? T1 is low (I'm guessing ambient temperature), t2 is high (cpu probably) and t3 is about 10 degrees (F) lower than t2 so I'm guessing it's either another chip or the mobo temp? Not sure. I can crack the case open and check the fan settings, but I'm not sure about the temperature sensors. Any ideas?

Thanks again for a simple and well-written guide.
are the the sensors that gdesklets use ?

all worked fine here , great how-to !

Is there also a sensor for the cpu-load ?

Stormy Eyes
July 21st, 2005, 11:16 PM
Thanks for the HOWTO, Emperor. Now I've got the CPU temperature module in Enlightenment 0.17 on Hoary working.

RJARRRPCGP
July 29th, 2005, 05:14 AM
After I install xsensors and then ran it, why this?

rjarrrpcgp@ubuntu:~$ sudo -s
root@ubuntu:~# xsensors
Sensor 'it8712' not supported by xsensors!


Is the hardware monitoring chip really rare? ](*,)

But, this is with Hoary! (I wished that they moved the lm-sensors topic to another forum)

umdzig
July 29th, 2005, 03:17 PM
I have a dell inspiron 8600. All i get when i try to use lm sensors is it says no sensors detected. Can someone tell me what driver i am supposed to use so i can get this to work correctly?

WTF_Shelley
July 30th, 2005, 10:33 PM
I get some weird results


Adapter: SMBus Via Pro adapter at 5000
+5V: +4.87 V (min = +6.71 V, max = +0.00 V)
VTT: +1.33 V (min = +2.55 V, max = +0.00 V)
+3.3V: +2.54 V (min = +3.68 V, max = +0.00 V)
+Vcore: +0.16 V (min = +3.02 V, max = +2.81 V)
+12V: +12.57 V (min = +12.82 V, max = +11.75 V)
-12V: -11.14 V (min = -9.60 V, max = -11.74 V)
-5V: -4.41 V (min = -3.64 V, max = -2.61 V)
fan1: 10546 RPM (min = 5335 RPM, div = 1) ALARM
fan2: 5769 RPM (min = 0 RPM, div = 1)
temp: -128.00C (hot: limit = -1C, hyst = -1C)
: (os: limit = +0C, hyst = -1C)
alarms: Board temperature input (LM75) ALARM


please help me :|

Fixed i just had to reorganize the module order

f1dave
July 31st, 2005, 06:02 AM
Sorry for listing yet another strange problem, but i set everything up, it worked beautifully and i got a lovely output of results when running sensors from console... But then upon rebooting I got a "fail" when the sensors tried to load- something about no limits set? And now i run sensors and get no output again! :S

Any ideas?

ankitrohatgi
August 13th, 2005, 07:48 AM
I installed lm-sensors by apt-get install lm-sensors. It's working fine, but I get the following error at the boot up:

i2c_adapter i2c-0: Error: command never completed

(in 10 consecutive lines)

Please help.

Thanks,
Ankit

antoniost
August 14th, 2005, 07:40 AM
I have almost done everything.
This is my output from "sensors-detect"

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

#----cut here----
# I2C adapter drivers
i2c-isa
# I2C chip drivers
w83627hf
#----cut here----

When i run "sensors" , i take :

antonios@homepc:~$ sensors
eeprom-i2c-0-52
Adapter: SMBus I801 adapter at 0400
Memory type: DDR SDRAM DIMM
Memory size (MB): 512


What must i put in /etc/modules and in what order ,to make this thing work ?
What about with the "modprobe orders" ? What is the correct sequence for this ?

Thanks , anyway.

GreyFox503
August 14th, 2005, 08:05 AM
I already have lm-sensors installed, but just a quick suggestion: add a brief description at the beginning of the HOWTO that describes what the heck lm-sensors is. If you didn't know what you're talking about, its not obvious, especially to a newbie.

bjweeks
August 14th, 2005, 09:04 AM
Has anybody got lm-sensors to work on a Asus A8N-Sli

Slugger
August 14th, 2005, 09:17 AM
Has anybody got lm-sensors to work on a Asus A8N-Sli
I havent gotten Im-sensors to work on a Asus A8N-Sli but maybe someone else has?

N8MAN1068
August 23rd, 2005, 06:36 PM
couldn't get this to work on a Dell Latitude C840, even though commands like
acpi -t show cpu temps

floflooo
September 8th, 2005, 07:34 AM
couldn't get this to work on a Dell Latitude C840, even though commands like
acpi -t show cpu temps
Same here for a Dell Latitude D600. I've tried the howto and the program sensors-detect didn't find any sensor.
I have done a bunch of research before posting and it's crazy that nobody can make lm_sensor work on Dell Laptops. :(

redmoon
September 14th, 2005, 05:03 AM
i have a question (ubuntu noob)

after i run sensors-detect, i am asked if i want the module results to be added to the /etc/modules file automatically...should i answer 'yes' to this question, and if so, does that mean i dont have to add the modules in 'reverse' manually as the HOWTO says? I also don't really understand what you mean by add the modules in reverse either... could you shed some light please? I only ask because I am getting funny results.

Cheers.

kemosabe79
September 29th, 2005, 02:39 AM
Nice Howto! This is the first time Ive been able to get this to work on my n-Force2 chipset. Thanks alot!:)

John.Michael.Kane
September 29th, 2005, 03:33 AM
this is the responce i get using acpi-t on a acer travelmate 290 centrino notebook. so what note books use lm- sensors
Battery 1: charged, 100%
No support for device type: thermal

casper_2095
October 2nd, 2005, 04:24 PM
The script in the first step of this how-to creates a bunch of entries /dev/i2c-___

What? Why?

I ask because I skipped this on my Hoary + ASUS A8V Deluxe and it seems to be working (mods i2c-viapro + i2c-isa + w83627hf) but now I'm afraid I'm missing out on something. :rolleyes:

Is this in the [english language] wiki anywhere?

floyd27
October 12th, 2005, 08:16 PM
Hi.
Just would like to know what in the conf. file I would have to change to get the right valuse to appear.
The current values are way off and i would like to set them.
I kow its a divider or multiplyer proble.

Its just that file is hudge and im not sure which ones to change..
These are what needs to be set..
m/b temp
cpu temp
fan speeds..
thanx

Unit #134679
October 13th, 2005, 12:44 AM
Great How To!

arunsub
October 15th, 2005, 08:22 PM
I tried this in Breezy. I got the following errors:
sudo ./mkdev.sh
/dev/i2c-0
mknod: `/dev/i2c-0': File exists

$sensors-detect
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.

It worked fine in Hoary, but not in Breezy. I know it's hoary tips and tricks, but won't it work in breezy?

Edit: everything worked fine after i used sudo.

angrykeyboarder
October 16th, 2005, 08:14 AM
All this for some little displays on my desktop. Not worth it. I'll wait a few years till it get's simpler.

And to think I thiought all I had to do was install lm_sensors to get that other stuff working....

Skatox
October 18th, 2005, 04:04 AM
It doesn't work for me in Breezy, too.

JimmyJazz
October 18th, 2005, 05:15 AM
no work for me in breezy HP pavilion zt3000

tschackomuizi
October 19th, 2005, 09:42 PM
oke: i installed lm_sensors in breezy 5.10 on a A2K Asus Motherboard. this is a nforce3 board. should also work on nforce2 ones
the sensors work. i didn't use the how-to exactly.

starting with root all commands:

$: synaptic
=> search for "lm_sensors" and install the package "wmtemp". this also
installs lm_sensors and all dependencies.

then detect your motherboard sensors with:

$: /usr/sbin/sensors-detect

type "YES" in each test. i got everything failed in "ISA" mode. so
In the end i choose "smbus". It will write some new lines in /etc/modules.

you can look in $: vim /etc/modules and see the added lines.
now you must load all of these added modules separately

$: modprobe XXXX

after that, if you type now the command $: sensors you get fine output.


my question is now... how can i change the fanspeed manually? i want to let the fanspeed rotate at a specific speed, as i know from "speedfan" in windows, where it worked. yes, not exactly the RPM, but ti change the % how fast it is rotating. ACPI is supported in my motherboard, powernow, also working and activated. which steps do i have to do for the manual control of the fanspeed?

yesplease
October 22nd, 2005, 11:17 PM
Thanks for your helpfull notes Tschackomuizi, I used them for a MSI K8N Neo2 plat. motherboard, nforce3. I got this output from sensors:

w83627thf-isa-0290
Adapter: ISA adapter
VCore: +1.09 V (min = +1.93 V, max = +1.93 V)
+12V: +12.40 V (min = +10.82 V, max = +13.19 V)
+3.3V: +3.12 V (min = +3.14 V, max = +3.47 V) ALARM
+5V: +4.93 V (min = +4.75 V, max = +5.25 V)
-12V: -14.91 V (min = -10.80 V, max = -13.18 V)
V5SB: +5.03 V (min = +4.76 V, max = +5.24 V)
VBat: +2.59 V (min = +2.40 V, max = +3.60 V)
fan1: 5075 RPM (min = 5232 RPM, div = 2)
CPU Fan: 3391 RPM (min = -1 RPM, div = 2)
fan3: 0 RPM (min = 675000 RPM, div = 2)
M/B Temp: +27&#176;C (high = +16&#176;C, hyst = +0&#176;C) sensor = thermistor
CPU Temp: +34.5&#176;C (high = +80&#176;C, hyst = +75&#176;C) sensor = diode
temp3: +27.5&#176;C (high = +80&#176;C, hyst = +75&#176;C) sensor = thermistor
vid: +0.000 V (VRM Version 9.0)
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm disabled

eeprom-i2c-0-51
Adapter: SMBus nForce2 adapter at 4c00
Memory type: DDR SDRAM DIMM
Memory size (MB): 512

eeprom-i2c-0-50
Adapter: SMBus nForce2 adapter at 4c00
Memory type: DDR SDRAM DIMM
Memory size (MB): 512

Not exactly what I expected because I chose SMbus output over ISA in sensors-detect, and the i2c drivers are for SMbus. Still most values are from isa.
The min and max values are sometimes strange, but it is a start.

Thanks again.

Klunk
October 24th, 2005, 07:33 PM
I installed lm-sensors and ran sensors-detect (on breezy) and I am getting some strange results.


w83782d-i2c-0-2d
Adapter: SMBus AMD756 adapter at 50e0
VCore 1: +1.76 V (min = +1.66 V, max = +1.82 V)
VCore 2: +2.48 V (min = +1.66 V, max = +1.82 V)
+3.3V: +3.31 V (min = +3.14 V, max = +3.46 V)
+5V: +4.95 V (min = +4.73 V, max = +5.24 V)
+12V: +12.28 V (min = +10.82 V, max = +13.19 V)
-12V: -11.95 V (min = -13.18 V, max = -10.88 V)
-5V: -5.00 V (min = -5.25 V, max = -4.75 V)
V5SB: +5.11 V (min = +4.73 V, max = +5.24 V)
VBat: +3.22 V (min = +2.40 V, max = +3.60 V)
fan1: 0 RPM (min = 2657 RPM, div = 2)
fan2: 0 RPM (min = 2657 RPM, div = 2)
fan3: 0 RPM (min = 664 RPM, div = 8)
temp1: +34&#176;C (high = +0&#176;C, hyst = +0&#176;C) sensor = thermistor
temp2: +58.0&#176;C (high = +90&#176;C, hyst = +88&#176;C) sensor = thermistor
temp3: +127.5&#176;C (high = +80&#176;C, hyst = +75&#176;C) sensor = diode ALARM
vid: +1.750 V (VRM Version 9.0)
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm disabled

eeprom-i2c-0-52
Adapter: SMBus AMD756 adapter at 50e0
Memory type: SDR SDRAM DIMM
Memory size (MB): 256

eeprom-i2c-0-50
Adapter: SMBus AMD756 adapter at 50e0
Memory type: SDR SDRAM DIMM
Memory size (MB): 256



My setup in an Gigabit GA-71XE4 motherboard with an Athlon 1GHz processor.

Clearly there must be something wrong wth the temperatures being displayed, and I don't understand why the fans are not showing any rpm.

Has anyone got any pointers for me?

EDIT - I found that temp3 is not used for AMD processors. It does not appear in my BIOS and I have no sensor for this, hence the strange results. I have ignored this in my sensors.conf. I still have one question though, my BIOS reports fan speeds and yet lm_sensors does not, does anyone have any idea why I am not getting anything for the fans?

dudus
November 17th, 2005, 07:22 PM
After I install xsensors and then ran it, why this?

rjarrrpcgp@ubuntu:~$ sudo -s
root@ubuntu:~# xsensors
Sensor 'it8712' not supported by xsensors!


Is the hardware monitoring chip really rare? ](*,)

But, this is with Hoary! (I wished that they moved the lm-sensors topic to another forum)

It seems that the new versions supports it :

http://www.linuxhardware.org/xsensors/CHANGELOG

dudus
November 17th, 2005, 07:49 PM
I've got some odd results from the sensor thing. Some values seems out f range, I think I should tweek this in the conf file. The temp3 is disabled and I can't figure out how to enable it.

When I use xsensors, it says that my chip isn't supported (it8712). My verssion of xsensors is 0.46. In the developer website I read that xsensors 0.47 supports my chip. But this verssion hasn't made into the repos yet.

Not sure If I should install the package since I don't fell confartable installing something that isn't even in the backports.


$sensors
it8712-isa-0290
Adapter: ISA adapter
VCore 1: +1.76 V (min = +1.42 V, max = +1.57 V) ALARM
VCore 2: +0.00 V (min = +2.40 V, max = +2.61 V) ALARM
+3.3V: +6.72 V (min = +3.14 V, max = +3.46 V) ALARM
+5V: +4.95 V (min = +4.76 V, max = +5.24 V)
+12V: +12.48 V (min = +11.39 V, max = +12.61 V) ALARM
-12V: -27.36 V (min = -12.63 V, max = -11.41 V) ALARM
-5V: -13.64 V (min = -5.26 V, max = -4.77 V) ALARM
Stdby: +5.08 V (min = +4.76 V, max = +5.24 V)
VBat: +4.08 V
fan1: 3040 RPM (min = 0 RPM, div = 2)
fan2: 2689 RPM (min = 2657 RPM, div = 2)
fan3: 0 RPM (min = 2657 RPM, div = 2) ALARM
M/B Temp: +48C (low = +15C, high = +40C) sensor = thermistor
CPU Temp: +37C (low = +15C, high = +45C) sensor = thermistor
Temp3: -1C (low = +15C, high = +45C) sensor = disabled

crag277
November 22nd, 2005, 10:36 PM
First of all, great guide! Everything works, except the version of lm_sensors that installs through apt-get is 2.9.1, and the version that contains the driver for my sensors (SMSC 47M15x/192) is 2.9.2. Therefore, when I run sensors-detect it detects everything just fine, but simply says there is no driver for my hardware. I have tried manually installing version 2.9.2, but I get nothing but errors. Is there an easier way to maybe just install the module I need for this chip even though the rest of the package is version 2.9.1? Any ideas?

-Eric

crag277
November 22nd, 2005, 11:08 PM
nevermind. I checked more carefully this time, and the driver I need doesn't exist yet. Looks like I need to wait.

Cuppa-Chino
November 24th, 2005, 12:34 AM
hi thx for the guide, got mine to work nearly straight off the bat...

where can I mod the limits - my VCore show too high, my MOBO temp is always alarmed:

w83627thf-isa-0290
Adapter: ISA adapter
VCore: +1.60 V (min = +1.45 V, max = +1.60 V) ALARM
+12V: +12.10 V (min = +10.82 V, max = +13.19 V)
+3.3V: +3.31 V (min = +3.14 V, max = +3.47 V)
+5V: +4.99 V (min = +4.75 V, max = +5.25 V)
-12V: -14.91 V (min = -10.80 V, max = -13.18 V)
V5SB: +4.97 V (min = +4.76 V, max = +5.24 V)
VBat: +0.00 V (min = +2.40 V, max = +3.60 V)
fan1: 0 RPM (min = 135000 RPM, div = 2)
CPU Fan: 0 RPM (min = -1 RPM, div = 2)
fan3: 1599 RPM (min = 84375 RPM, div = 4)
M/B Temp: +38C (high = +33C, hyst = +0C) sensor = thermistor
CPU Temp: +30.5C (high = +80C, hyst = +75C) sensor = thermistor
temp3: -48.0C (high = +80C, hyst = +75C) sensor = thermistor
vid: +1.525 V (VRM Version 9.0)
alarms:
beep_enable:
Sound alarm enabled


but I am okay with for instance the MOBO temp.

also where is conf file for xsensors as my display a lot about the sensors that have 0 readings above?

thanks

Arandomcow5
November 29th, 2005, 05:46 AM
Excellant guide, thanks a lot

I needed this to test my processor temperatures (i over clocked my processor 30%, so now its running at 3.9GHz) I wanted to make sure that it was running acceptably, and it is, yay!

Cuppa-Chino
November 29th, 2005, 08:48 PM
hi just thought I would "bump" my question wrt to the configuration of

also where is conf file for xsensors as my display a lot about the sensors that have 0 readings above?

thanks

juantxorena
January 1st, 2006, 08:13 PM
Here's my sensors-detect result:
#----cut here----
# I2C adapter drivers
i2c-nforce2
# I2C chip drivers
# Warning: the required module smbus-arp is not currently installed on your system.
# For status of 2.6 kernel ports see http://secure.netroedge.com/~lm78/supported.html
# If driver is built-in to the kernel, or unavailable, comment out the following line.
smbus-arp
#----cut here---- I've just compiled a new kernel, and I can't found anything related to smbus-arp. My motherboard is an ASUS A7N8X-E Deluxe, with a nForce2 chipset.
Any help?

Trev0r269
February 11th, 2006, 02:56 AM
i got the daunting msg, "No Sensors Found!" , but everything seemed to work ok.

there was a prompt to add the needed lined to /etc/modules, and i chose yes. i didnt havent to add anything myself like the guide implied. maybe something went wrong here? also, i see /etc/modules but i cant cd into it. i get told it is not a directory.

lleberg
February 27th, 2006, 05:30 PM
well, i think it worked.. But i have a small... error i think.


lleberg@margit:~$ sensors
it8712-isa-0290
Adapter: ISA adapter
VCore 1: +1.09 V (min = +1.42 V, max = +1.57 V) ALARM
VCore 2: +2.58 V (min = +2.40 V, max = +2.61 V)
+3.3V: +6.78 V (min = +3.14 V, max = +3.46 V) ALARM
+5V: +4.27 V (min = +4.76 V, max = +5.24 V) ALARM
+12V: +12.29 V (min = +11.39 V, max = +12.61 V)
-12V: -1.83 V (min = -12.63 V, max = -11.41 V) ALARM
-5V: -5.26 V (min = -5.26 V, max = -4.77 V) ALARM
Stdby: +2.63 V (min = +4.76 V, max = +5.24 V) ALARM
VBat: +4.08 V
fan1: 3183 RPM (min = 0 RPM, div = 8)
fan2: 1371 RPM (min = 664 RPM, div = 8)
fan3: 0 RPM (min = 664 RPM, div = 8) ALARM
M/B Temp: +25C (low = +15C, high = +40C) sensor = thermistor
CPU Temp: +28C (low = +15C, high = +45C) sensor = thermistor
Temp3: +69C (low = +15C, high = +45C) sensor = thermistor ALARM

Sure, i'm running my amd64 at 28 degrees C! Right!
And where are temp3 measured? Shouldn't the cpu hotter than the others?

Edit: uh, is this a warty-howto?
Did i just do something.. stupid? :D

Trev0r269
March 6th, 2006, 07:22 PM
For step 2

Where is the lm-sensors source?

I'm very new, and I'm trying hard to get this right.

henriquemaia
March 7th, 2006, 03:22 AM
Worked flawlessly. Thanks a lot!

:KS

MaX
March 10th, 2006, 05:56 PM
For step 2

Where is the lm-sensors source?

I'm very new, and I'm trying hard to get this right.
You just copy the text begining with "#!/bin/bash" and ending with "#end of file"
Into it's own file mkdev.sh and you make that runnable (rightclick select properties and run).
Then run the file.

negatron
March 22nd, 2006, 11:48 AM
Just a few questions with the installation, because I haven't got lm-sensors (or any other sensor program) working.

1. #sudo mbmon -dA
gives me the following:
SMBus[IntelPIIX4(440BX/MX)] found, but No HWM available on it!!

Does that mean that there are no sensors on my motherboard or have I just made something wrong? It also tells that mbmon needs "setuid root", whatever that means (running as sudo gives the same).

2. #sudo sensors-detect
No chips detected... That makes me think that maybe there just isn't any sensors on my mobo. :-|

I've tried to run the script mentioned in the how to but still all I got is nothing. So is there a way to make things work or am I just wasting time here? Could really use some help, I can't sleep with this problem ;)
And I am somewhat a n00b with Linux, so please be gentle...

fackamato
March 22nd, 2006, 01:14 PM
Just a few questions with the installation, because I haven't got lm-sensors (or any other sensor program) working.

1. #sudo mbmon -dA
gives me the following:
SMBus[IntelPIIX4(440BX/MX)] found, but No HWM available on it!!

Does that mean that there are no sensors on my motherboard or have I just made something wrong? It also tells that mbmon needs "setuid root", whatever that means (running as sudo gives the same).

2. #sudo sensors-detect
No chips detected... That makes me think that maybe there just isn't any sensors on my mobo. :-|

I've tried to run the script mentioned in the how to but still all I got is nothing. So is there a way to make things work or am I just wasting time here? Could really use some help, I can't sleep with this problem ;)
And I am somewhat a n00b with Linux, so please be gentle...


Doesn't seem like your sensor chips is/are supported yet, or you don't have any. What motherboard/BIOS are you using?

jtp51
March 26th, 2006, 05:04 PM
So, stating the obvious:

# Generated by sensors-detect on Sat Mar 25 11:54:08 2006
# I2C adapter drivers
i2c-isa
# I2C chip drivers
# no driver for SMSC 47M15x/192 Super IO Fan Sensors yet

I guess my machine is too new to have lm-sensors work correctly?

MSI MS-7184 motherboard.
AMD Athlon 64 X2 3800+ processor.
Northbridge: ATI RS482 and Southbridge: ATI SB400 chipset.
1 GB Ramm

How often are drivers released?

Thanks,

mitjab
March 27th, 2006, 09:14 AM
how to enable sound alarm

alarms:
beep_enable:
Sound alarm disabled

WelterPelter
March 31st, 2006, 05:09 AM
I used this guide (for 64-bit Dapper) and it worked fine, until the reboot stage. Now sensors-detect can't find anything again!

henriquemaia
March 31st, 2006, 07:47 PM
On my new system, an AMD64 dapper, sensors are not detected, unfortunately. Does anyone on amd64 have any ideas how to get this working?

WelterPelter
April 6th, 2006, 08:53 AM
Tonight I downloaded the unofficial AMD-64 version of lm-sensors from debian here (http://packages.debian.org/stable/utils/lm-sensors).
After I installed it, Dapper's update thingy told me there was a new version available, which I installed.
Then I went back through the sensor setup shown at the top of this thread.
Voila! $sensors:

w83627ehf-isa-0290
Adapter: ISA adapter
Case Fan: 0 RPM (min = 1205 RPM, div = 32)
CPU Fan: 3183 RPM (min = 1704 RPM, div = 8)
fan3: 0 RPM (min = 0 RPM, div = 32)
fan4: 0 RPM (min = 0 RPM, div = 4)
Sys Temp: +27C (high = +45C, hyst = +40C)
CPU Temp: +33.0C (high = +45.0C, hyst = +40.0C)
temp3: -48.0C (high = +127.0C, hyst = +127.0C)
:cool::D

JackandJohn
May 7th, 2006, 07:16 AM
Ok, I have a fun one:

I installed all the good stuff; works like a charm:


it8712-isa-0290
Adapter: ISA adapter
VCore 1: +1.39 V (min = +1.42 V, max = +1.57 V) ALARM
VCore 2: +2.58 V (min = +2.40 V, max = +2.61 V)
+3.3V: +6.62 V (min = +3.14 V, max = +3.46 V) ALARM
+5V: +4.87 V (min = +4.76 V, max = +5.24 V)
+12V: +12.29 V (min = +11.39 V, max = +12.61 V)
-12V: -11.77 V (min = -12.63 V, max = -11.41 V) ALARM
-5V: -1.86 V (min = -5.26 V, max = -4.77 V) ALARM
Stdby: +2.10 V (min = +4.76 V, max = +5.24 V) ALARM
VBat: +4.08 V
fan1: 4560 RPM (min = 0 RPM, div = 8)
fan2: 0 RPM (min = 3013 RPM, div = 8)
fan3: 1638 RPM (min = 3013 RPM, div = 8) ALARM
M/B Temp: +25C (low = +15C, high = +40C) sensor = thermistor
CPU Temp: +35C (low = +15C, high = +45C) sensor = thermistor
Temp3: +3C (low = +15C, high = +45C) sensor = diode


NOW, problem is when the cpu modules load:


#----cut here for sensor probing----
# I2C adapter drivers
# modprobe unknown adapter bt878 #0 [sw]
it87
eeprom
i2c-isa
i2c-nforce2
# I2C chip drivers
#----cut here----
(reversed as per the howto)

I get my mobo speaker beeping at me CONSTANTLY.
Like, one continuous beep that starts when the module is loaded (not sure which one, but one of the above), and does not end until I power down.

Un-usable.


Any help is appreicated; possibly disabling the alarm? or even disable linux's access to that speaker altogether (less than optimal)

Thanks!

seanUSXIII
May 19th, 2006, 03:40 PM
I use lm_sensors on dapper beta 2, and it only detects my cpu and case fans. It won't detect the CPU temp or case temp or anything like that. Speedfan can detect them just fine under windows. Is there any other program that maybe can control fan speeds automatically like speedfan?

CameronCalver
May 20th, 2006, 05:34 AM
hey a noob question on the very first post oyou said mkdev.sh where is that script exactly?

Keith_Beef
May 31st, 2006, 05:33 AM
Here's my sensors-detect result:
#----cut here----
# I2C adapter drivers
i2c-nforce2
# I2C chip drivers
# Warning: the required module smbus-arp is not currently installed on your system.
# For status of 2.6 kernel ports see http://secure.netroedge.com/~lm78/supported.html
# If driver is built-in to the kernel, or unavailable, comment out the following line.
smbus-arp
#----cut here---- I've just compiled a new kernel, and I can't found anything related to smbus-arp. My motherboard is an ASUS A7N8X-E Deluxe, with a nForce2 chipset.
Any help?

I have the same mainboard, and I believe I had lm-sensors working on it with Mandrake 10.2, then Mandriva, both with 2.6 series kernels. I don't remember having any problems getting the sensors to work.

What is this smbus-arp module?

(A while ago, I had lm-sensors working with mandrake on an Abit BP6.)

Beef.

angrykeyboarder
May 31st, 2006, 07:47 AM
Am I the only one that thinks step 1 is almost useless since it doesn't include steps 2-8?

Why do they bother with an installation program that doesn't configure anything?

Is it really worth all this for some geeky stuff on your desktop?

I lost complete interest in any sensors desktop stuff after seeing what a PITA this required package is.

Well at least you won't ever find yourself entering "sudo dpkg-reconfigure lm-sensors"

keithjr
June 11th, 2006, 03:19 PM
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, 06:40 PM
I've upgraded from 5.10 to 6.06 this weekend, and now my fancontrol is stopped.
Sensors are OK:


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: +47C (high = +85C, hyst = +125C) sensor = thermistor
temp2: +58.0C (high = +90C, hyst = +85C) sensor = thermistor (beep)
temp3: -48.0C (high = +90C, hyst = +85C) sensor = thermistor
vid: +1.650 V (VRM Version 9.0)
alarms:
beep_enable:
Sound alarm enabled

But, when I run fancontrol:


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, 11:27 PM
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, 04:22 PM
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, 03:03 PM
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/SensorInstallHowto?highlight=%28sensors%29

and sensors-detect have found this sensors:

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

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

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

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

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

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

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

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


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, 03:41 PM
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:

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, 01:07 AM
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.



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, 02:12 AM
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:?:

Trev0r269
July 2nd, 2006, 12:07 AM
2. Run the mkdev.sh script in the lm-sensors source

Where is the lm-sensors source?

eldaria
July 5th, 2006, 11:02 PM
http://www.lm-sensors.org/

cblanquer
July 9th, 2006, 03:27 PM
Hi,

Regarding "smbus-arp" I think it is a bug or a bad explanation form "lm-sensors".
Unless I made a mistake, it is loaded under "i2c-core", i.e. execute "sudo modprobe i2c-core" to get it loaded.

I did so and then the message regarding smbus-arp did not figure anymore and additional data were available.

(If I am wrong pease post)

cblanquer
July 9th, 2006, 03:28 PM
Juantxorena,

Check my later on the thread - I guess it is a part of "i2c-core".

theturner
July 13th, 2006, 11:00 AM
A seemingly simple question: What does "SBr Temp" mean? I couldn't find anything about it on the lm-sensors home page...

ExMachina
August 12th, 2006, 10:31 PM
A few questions..

This is wokring for me.

exmachina@ExMachina:~$ sensors
No sensors found!
exmachina@ExMachina:~$ sudo sensors
Password:
No sensors found!
exmachina@ExMachina:~$

is there a gui for this?
my laptop temp is usally 130 but can get up to 155.. kinda worries me

atze76
August 13th, 2006, 07:50 PM
I have managed to install lm-sensors on my laptop (running kubuntu dapper). After I have followed the steps described in this how-to and rebooted my system, the cpu utilization increased to almost 100%. Most of the cpu time is consumed by kacpid. I didn't have this problem before.
Now I have uninstalled the whole lm-sensors package (using synaptic) but one of the how-to steps must have left a permanent modification, which causes kacpid to use 100% cpu time.
Even the whole boot process is slow now, it take 5-10 times longer. I had to disable acpi (kernel parameter: acpi=off) in order to be able to boot faster.
Can anyone imagine, which step has to be undone to avoid this freaky behaviour of kacpid.

mark_v_torres
August 16th, 2006, 03:31 AM
I had the same problem. And the strange thing is, it also happens when I boot to Windows. I tried resetting to the default BIOS settings and that seemed to fix the issue.

LKRaider
August 22nd, 2006, 10:10 PM
For everyone using lm-sensors on Gnome, install the sensors-applet package.
It will place the sensors info on your Gnome panel and allow you to configure alarm levels and so on.

Screenshot of sensors-applet here on my pc (http://lkraider.eipper.com.br/files/pub/sensors-applet.jpg)

Very handy :)

Cuppa-Chino
August 22nd, 2006, 11:22 PM
For everyone using lm-sensors on Gnome, install the sensors-applet package.
It will place the sensors info on your Gnome panel and allow you to configure alarm levels and so on.
Very handy :)


embarrassing... how do I start them????

Found it! http://www.ubuntuforums.org/archive/index.php/t-92504.html

mordox
August 25th, 2006, 09:24 AM
I have intel 845GVSR board and i have recently installed Ubuntu 6.06LTS

I tried to configure lm-sensors as explained above. I tried the following

rivo@Xcc:~$ sudo sensors-detect
Password:
No i2c device files found. Use prog/mkdev/mkdev.sh to create them.
rivo@Xcc:~$ cd Desktop/
rivo@Xcc:~/Desktop$ chmod 755 mkdev.sh
rivo@Xcc:~/Desktop$ 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
rivo@Xcc:~/Desktop$ 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 82801DB ICH4
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no): n
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 not loaded. Do you want to load it now? (YES/no): y
Module loaded succesfully.

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: I810/I815 DDC Adapter
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x37
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Probing for `DDC monitor'... Success!
(confidence 8, driver `eeprom'), other addresses: 0x51 0x52 0x53 0x54 0x55 0 x56 0x57
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x52
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x53
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x54
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x55
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x56
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Client found at address 0x57
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Probing for `Sony Vaio EEPROM'... Failed!

Next adapter: I810/I815 I2C Adapter
Do you want to scan it? (YES/no/selectively): y

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! (0x1404)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0x1404)
Probing for `ITE 8712F Super IO Sensors'
Failed! (0x1404)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
Failed! (0x14)
Probing for `Nat. Semi. PC87591 Super IO'
Failed! (0x14)
Probing for `Nat. Semi. PC87371 Super IO'
Failed! (0x14)
Probing for `Nat. Semi. PC97371 Super IO'
Failed! (0x14)
Probing for `Nat. Semi. PC8739x Super IO'
Failed! (0x14)
Probing for `Nat. Semi. PC8741x Super IO'
Failed! (0x14)
Probing for `Nat. Semi. PCPC87427 Super IO'
Failed! (0x14)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (0x14)
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
Failed! (0x14)
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed! (0x14)
Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
Failed! (0x14)
Probing for `SMSC 47S42x Super IO Fan Sensors'
Failed! (0x14)
Probing for `SMSC 47S45x Super IO Fan Sensors'
Failed! (0x14)
Probing for `SMSC 47M172 Super IO'
Success... (no hardware monitoring capabilities)
Probing for `SMSC LPC47B397-NC Super IO'
Failed! (0x14)
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)

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

Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `I810/I815 DDC Adapter'
Busdriver `i2c-i810', I2C address 0x50 (and 0x51 0x52 0x53 0x54 0x55 0x56 0x 57)
Chip `DDC monitor' (confidence: 8)


I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)? smbus

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

#----cut here----
# I2C adapter drivers
i2c-i810
# I2C chip drivers
eeprom
#----cut here----

Do you want to add these lines to /etc/modules automatically? (yes/NO)y
rivo@Xcc:~/Desktop$ sudo /etc/init.d/module-init-tools
* Loading manual drivers... [ ok ]
rivo@Xcc:~/Desktop$ sudo modprobe i2c-i810
rivo@Xcc:~/Desktop$ sudo modprobe eeprom
rivo@Xcc:~/Desktop$ sudo modprobe i2c-i810 eeprom
rivo@Xcc:~/Desktop$ sensors
No sensors found!
rivo@Xcc:~/Desktop$ sudo depmod -a i2c-i810 eeprom
rivo@Xcc:~/Desktop$ sudo update-modules






I even tried reversing the order in which sensors-detect adds the modules but to no avail.
My /etc/modules

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

lp
psmouse




# Generated by sensors-detect on Fri Aug 25 13:20:58 2006
# I2C chip drivers
eeprom
# I2C adapter drivers
i2c-i810



Can anyone help plz! :confused:

Sfac
September 3rd, 2006, 11:06 PM
Installed lmsensors..all fine. but i cant see my cpu temp or fan speed. These are the sensors found:

# I2C adapter drivers
i2c-viapro
i2c-isa
# I2C chip drivers
eeprom
w83627hf

and this is the sensors list:

w83627hf-isa-0290
Adapter: ISA adapter
VCore 1: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM (beep)
VCore 2: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM (beep)
+3.3V: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM (beep)
+5V: +6.85 V (min = +6.85 V, max = +6.85 V) ALARM (beep)
+12V: +15.50 V (min = +15.50 V, max = +15.50 V) ALARM (beep)
-12V: +6.06 V (min = +6.06 V, max = +6.06 V) ALARM (beep)
-5V: +5.10 V (min = +5.10 V, max = +5.10 V) ALARM (beep)
V5SB: +6.85 V (min = +6.85 V, max = +6.85 V) ALARM (beep)
VBat: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM (beep)
fan1: 0 RPM (min = 0 RPM, div = 128) ALARM (beep)
fan2: 0 RPM (min = 0 RPM, div = 128) ALARM (beep)
fan3: 0 RPM (min = 0 RPM, div = 128) ALARM (beep)
temp1: -1C (high = -1C, hyst = -1C) sensor = diode ALARM (beep)
temp2: +0.0C (high = +0C, hyst = +0C) sensor = diode ALARM (beep)
temp3: +0.0C (high = +0C, hyst = +0C) sensor = diode ALARM (beep)
vid: +0.000 V (VRM Version 2.4)
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm enabled

How can i turn on the temp sensors?

Sfac
September 3rd, 2006, 11:07 PM
Forgot to say..mobo is a ABIT KV8-MAX3 VIA K8T800.
Thanks

detectiveinspekta
September 7th, 2006, 12:20 PM
I have a nforce2 motherboard with a amd 2500+



jonathan@booya:~/Documents$ sensors
w83627hf-isa-0290
Adapter: ISA adapter
VCore 1: +1.63 V (min = +1.44 V, max = +1.86 V)
VCore 2: +4.08 V (min = +1.44 V, max = +1.86 V) ALARM
+3.3V: +3.23 V (min = +2.82 V, max = +3.79 V)
+5V: +4.87 V (min = +3.71 V, max = +0.13 V) ALARM
+12V: +11.86 V (min = +1.40 V, max = +0.97 V) ALARM
-12V: -11.95 V (min = -13.59 V, max = -4.22 V)
-5V: +3.49 V (min = +3.34 V, max = -7.56 V) ALARM
V5SB: +5.46 V (min = +0.27 V, max = +0.97 V) ALARM
VBat: +1.47 V (min = +0.05 V, max = +0.77 V) ALARM
fan1: 0 RPM (min = 803 RPM, div = 8) ALARM
fan2: 0 RPM (min = 2109 RPM, div = 8) ALARM
fan3: 0 RPM (min = 897 RPM, div = 8) ALARM
temp1: +26C (high = +2C, hyst = +0C) sensor = thermistor ALARM
temp2: +28.5C (high = +100C, hyst = +95C) sensor = thermistor
temp3: +22.0C (high = +100C, hyst = +95C) sensor = thermistor
vid: +1.650 V (VRM Version 9.0)
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm enabled

lm90-i2c-0-4c
Adapter: SMBus nForce2 adapter at 5000
M/B Temp: +28C (low = +0C, high = +70C)
CPU Temp: +29.0C (low = +0.0C, high = +70.0C)
M/B Crit: +85C (hyst = +75C)
CPU Crit: +75C (hyst = +65C)

which is the acual temperature measurment on the CPU? I am water cooled but according to bios the CPU temp core is ~45 deg

maddbaron
September 19th, 2006, 08:37 PM
I tried get this error after following the instructions on this page:
http://www.debian-administration.org/articles/327



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): Yes
Probing for PCI bus adapters...
Use driver `i2c-sis96x' for device 00:02.1: Silicon Integrated Systems SMBus Controller
Probe succesfully concluded.

As you are not root, we can't load adapter modules. We will only scan
already loaded adapters.
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 0x8100
Do you want to scan it? (YES/no/selectively): YES
Can't open /dev/i2c-0

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.

As you are not root, we shall skip this step.

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.

As you are not root, we shall skip this step.

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.


What do I do? Help Please.

ac4000
October 2nd, 2006, 02:44 AM
emperor: Amazing how-to; thanks!

maddbaron: You should probably run:
sudo sensors-detect

ant1060
October 9th, 2006, 05:48 PM
Hi!
Thanks for this HOWTO.... but I am struggling with one of the last steps. Everything goes fine until I try and modprobe the i2c sensor when I receive this message
FATAL : Module i2c_sensor not found.
Two things are strange : one is that I enter it as i2c-sensor (but it replies as i2c_sensor with an underscore).... and the second is that earlier on in the process I received confirmation that the i2c sensor was installed correctly :

To continue, we need module 'i2c-dev' to eb loaded. If it is built-in into your kernel, you can safely skip this. i2c-dev is not loaded. Do you want to load it now? (YES/NO) : YES Module loaded succesfully.

What am I doing wrong?
Thanks for

asmweb
October 18th, 2006, 11:02 AM
I have the same problem it seems not to find the i2c-sensor, how come?

JayTee
October 20th, 2006, 01:41 AM
Thanks for an excellent how-to. I've got this running although I'm not sure about two things. The two things I'm not sure about are 1.) the Vcore settings and why it's in alarm and 2.) my cpu temp reports 35 celsius but when I do a quick restart and check the hw monitor in BIOS it reports between 45 and 47 celsius while the motherboard temp and remote temp are within 1 degree celsius or match the temp reported by sensors.

Here's the output when I run the sensors command.


lm85-i2c-0-2e
Adapter: SMBus I801 adapter at 2000
V1.5: +1.55 V (min = +1.42 V, max = +1.58 V)
VCore: +1.20 V (min = +1.76 V, max = +1.95 V) ALARM
V3.3: +3.33 V (min = +3.13 V, max = +3.47 V)
V5: +5.16 V (min = +4.74 V, max = +5.26 V)
V12: +12.19 V (min = +11.38 V, max = +12.62 V)
CPU_Fan: 3827 RPM (min = 1400 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 2282 RPM (min = 0 RPM)
CPU: +35C (low = +10C, high = +50C)
Board: +28C (low = +10C, high = +35C)
Remote: +30C (low = +10C, high = +35C)
CPU_PWM: 255
Fan2_PWM: 76
Fan3_PWM: 76
vid: +1.850 V (VRM Version 9.1)


Here is the section of /etc/sensors.conf that pertains to my motherboard.



# Sample configuration for the Intel S845WD1-E
# courtesy of Marcus Schopen
#
chip "lm85c-*" "adm1027-*" "adt7463-*" "lm85-*" "lm85b-*"

set temp1_max 55

# Voltage inputs
label in0 "V1.5" # AGP on Intel S845WD1-E
label in1 "VCore"
label in2 "V3.3"
label in3 "V5"
label in4 "V12"

# Temperature inputs
label temp1 "CPU"
label temp2 "Board"
label temp3 "Remote"

# Fan inputs
label fan1 "CPU_Fan"
# label fan2 "Fan2"
# label fan3 "Fan3"
# label fan4 "Fan4"

# PWM Outputs
label pwm1 "CPU_PWM"
label pwm2 "Fan2_PWM"
label pwm3 "Fan3_PWM"

# Voltage scaling is done on-chip. No 'compute' directive
# should be necessary. If in0 has external scaling set
# it here.

# compute in0 @ * 2.5, @ / 2.5

# Adjust fans speeds for actual pulses per rev
# compute fan1 @ * 2, @ / 2 # 1 pulse per rev
# set fan1_ppr 1 # ADM1027 or ADT7463
# compute fan2 @ / 2, @ * 2 # 4 pulse per rev
# set fan2_ppr 4 # ADM1027 or ADT7463

# Ignore fans you (or your motherboard) don't have
# ignore fan2
# ignore fan3
# ignore fan4

# Set VRM version
set vrm 9.1 # Pentium 4

# Set voltage limits
set in0_min 1.5 * 0.95
set in0_max 1.5 * 1.05
set in1_min vid * 0.95
set in1_max vid * 1.05
set in2_min 3.3 * 0.95
set in2_max 3.3 * 1.05
set in3_min 5.0 * 0.95
set in3_max 5.0 * 1.05
set in4_min 12 * 0.95
set in4_max 12 * 1.05

# Set Fan limits
set fan1_min 1400
set fan4_min 1800
# Set Temp Limits
set temp1_min 10
set temp1_max 55
set temp2_min 10
set temp2_max 35
set temp3_min 10
set temp3_max 35

How can I adjust the temperature monitoring for the CPU to be more accurate and should I bother with adjusting the Vcore limits?
Any advice would be appreciated. I've also attached a full copy of my sensors.conf file to this post.

asmweb
October 20th, 2006, 09:00 AM
Well I've been looking a lot of forums and no one explain what is the i2c-sensor module and moreover where to find it! Any help, would appreciate it!

mmajk
October 21st, 2006, 11:26 AM
Ubuntu dapper has 'old' version of lm-sensors, 2.9.something. The latest release is 2.10.something. You can download it from http://lm-sensors.org/wiki/Download.

As stated on the lm-sensors.org, you don't need the i2c package, since it's allready in the kernel.

Just download the lm-sensors package, READ THE DOCUMENTATION (there are some issues one needs to understand, it's well explained), run the mkdev.sh (from the prog directory in the lm-sensors package), and go with the sensors-detect. Should work fine now.

Tamale
October 25th, 2006, 04:16 PM
I followed all the instructions, and after answering "y" to all of the questions I got "Sorry, no chips were detected" on my new core 2 duo nc8430 laptop..

any ideas?

Tamale
October 25th, 2006, 04:17 PM
after answering "yes" to all of the questions I too got "Sorry, no chips were found" on my new core 2 duo nc8430 laptop...

any ideas?

raven65az
October 27th, 2006, 08:20 AM
did all steps..and alas "No sensors detected"
I am on a Toshiba Satellite A-65 Notebook.
Giving up on the project, but some other Toshiba users might find the info useful.
Scott

maddbaron
October 27th, 2006, 08:16 PM
Does this work with Edgy? I didn't work for me in Dapper so I am going to retry it in Edgy...will this work maybe?

Peepsalot
November 1st, 2006, 04:00 AM
I have an Asus A7N8X-E motherboard and cannot figure out how to configure lm-sensors.

I tried following the tutorial and ended up putting this in my /etc/modules:


sensor modules
i2c-core
i2c-nforce2
asb100
eeprom
ds1621

But it won't boot when this is placed in there. I don't know how to troubleshoot from here. Any suggestions?

devilbush
November 10th, 2006, 07:02 AM
Excellent HOWTO, thank you!

Peepsalot
November 10th, 2006, 07:41 AM
I actually found the solution to my problems today. Removed eeprom from the list of modules and it all works.

Jongi
November 12th, 2006, 01:53 PM
What does temp3 measure?

raul_
November 20th, 2006, 07:55 PM
less than 10 minutes for the whole process. Congratulations :)

Prajna
November 25th, 2006, 11:57 PM
I've just set up Dapper for the first time and have managed to get everything working nicely. I must say, I'm very impressed with it all. I have even managed to set up VNC and XDMCP from a windows box without too much bother but I am struggling to get lm_sensors to work.

The problem seems to be that I have a Fintek f71805f chip, which is not supported by the lm_sensors package installed by Synaptic.

I downloaded the latest sensors-detect and ran it, which has identified the problem. The essential output is:

#----cut here----
# I2C adapter drivers
modprobe i2c-viapro
modprobe i2c-isa
# Chip drivers
modprobe eeprom
# Warning: the required module f71805f 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 f71805f
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----

If someone could help me with finding and installing the f71805f module then I think I could get it working. I am a complete n00b with ubuntu and pretty rusty on unix/linux in general.

Thanks

Prajna
November 29th, 2006, 09:30 AM
I got my sensors working great with the f71805f support in Edgy. Sadly, during the upgrade I somehow managed to wipe out a very fast and reliable Xvnc setup, meaning I have had to revert to a sluggish Xwindows setup using cygwin (whilst I figure out how to set up FreeNX on Edgy).](*,)

Oh well, you win some and you lose some. At least I have got some very pretty temps and fan speeds in my panel!

scotte
November 30th, 2006, 07:19 PM
I finally got my sensors working again in edgy, and hopefully this tip helps others who had sensors working fine in dapper, but are no longer working with edgy. This particular issue is not directly related to anything done in Ubuntu.

For the background, I've got an intel 801 based motherboard on this particular box, and everything was working just fine with my former Gentoo install. Likewise, all was good when I installed Ubuntu dapper. After the upgrade to edgy, sensors stopped working. I tried compiling the latest lm-sensors, but that didn't help either.

A key piece of information is that dapper was on kernel 2.6.15 and edgy uses 2.6.17. With some research and perusal of drivers/pci/quirks.c, there are a number of systems where the SMBus is hidden by default (see asus_hides_smbus in quirks.c).

At any rate, I discovered there was a patch applied to quirks.c in 2.6.16 which effectively disables unhiding the SMBus when ACPI_SLEEP is enabled.

My solution was to build a custom kernel without ACPI_SLEEP support. I'm now running 2.6.19, but this should work equally well for 2.6.17 or .18.

Here's the supporting documentation:
http://bugzilla.kernel.org/show_bug.cgi?id=6449
http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.16.y.git;a=blobdiff;h=0693c23831bb923c12866737 891e40863fab66b5;hp=dda6099903c18adc8636d89683ddc0 2a9a17b32a;hb=a9cacd682ed7c031fa05b1d1367a3b322181 3932;f=drivers/pci/quirks.c
http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.16.y.git;a=commit;h=a9cacd682ed7c031fa05b1d136 7a3b3221813932

Hope this helps!

Sonic Reducer
December 2nd, 2006, 10:43 AM
so i got an interesting error:

w83627ehf-isa-0290
Adapter: ISA adapter
Case Fan: 0 RPM (min = 1318 RPM, div = 128)
CPU Fan: 0 RPM (min = 76 RPM, div = 128)
fan3: 2393 RPM (min = 2636 RPM, div = 4)
fan4: 0 RPM (min = 7670 RPM, div = 8)
Sys Temp: +27C (high = -111C, hyst = -124C)
CPU Temp: +27.5C (high = +80.0C, hyst = +75.0C)
temp3: +27.5C (high = +80.0C, hyst = +75.0C)

and when i turn down the CPU fanspeed with the Zalman FanMate potentiometer thingy that came with the CNPS7700:


w83627ehf-isa-0290
Adapter: ISA adapter
Case Fan: 0 RPM (min = 1318 RPM, div = 128)
CPU Fan: 0 RPM (min = 76 RPM, div = 128)
fan3: 1339 RPM (min = 2636 RPM, div = 4)
fan4: 0 RPM (min = 7670 RPM, div = 16)
Sys Temp: +27C (high = -111C, hyst = -124C)
CPU Temp: +28.0C (high = +80.0C, hyst = +75.0C)
temp3: +28.0C (high = +80.0C, hyst = +75.0C)

my CPU fan comes up as "fan3" how can i fix this?

Peepsalot
December 3rd, 2006, 10:15 AM
my CPU fan comes up as "fan3" how can i fix this?
Your motherboard probably expects the CPU fan to be plugged into a different spot than the one you are using. Try another.

froped
December 3rd, 2006, 03:59 PM
I'm running edgy and followed the initial setup. I get the following error when I run sensors:


Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!


The sensors where discovered and the modules loaded. mount shows that sysfs is mounted and i have libsensors installed. Any ideas?

Corbelius
December 3rd, 2006, 04:31 PM
I'm running edgy and followed the initial setup. I get the following error when I run sensors:


Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!


The sensors where discovered and the modules loaded. mount shows that sysfs is mounted and i have libsensors installed. Any ideas?

What kernel linux you have?

bluevoodoo1
December 4th, 2006, 03:36 AM
I'm running edgy and followed the initial setup. I get the following error when I run sensors:


Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!


The sensors where discovered and the modules loaded. mount shows that sysfs is mounted and i have libsensors installed. Any ideas?

I have the same problem.

three_sixteen
December 11th, 2006, 12:55 PM
What kernel linux you have?

I'm having the same problem - kernel version 2.6.17-10-386

Trying to run it on a Dell XPS m1210

#----cut here----
# I2C adapter drivers
# modprobe unknown adapter NVIDIA I2C Device
# modprobe unknown adapter NVIDIA I2C Device
# modprobe unknown adapter NVIDIA I2C Device
# I2C chip drivers
eeprom
#----cut here----

maschnitz
December 16th, 2006, 06:59 PM
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!

I am also receiving this error. I did a little research. Here's what I learned.

In my case, this is caused by my current kernel not supporting my I/O chip. For the record, I am running an Asus M2NPV-VM, which has an NForce 430 chipset (MCP 50). Apparently the I/O chip in question is the IT8716F. I'm running under a 2.6.18 kernel I compiled.

This comprehensive list (http://www.lm-sensors.org/wiki/Devices) shows what is and isn't supported in lm_sensors. But it is mapped by specific I/O chip name, not chipset name nor motherboard name. (In my case, it's the IT8716F). So you'll need to know that, too. Googling around is your best bet. It helps to do Google searches for your particular motherboard, or, better, your particular chipset, and "lm_sensors". Check your motherboard manual or motherboard box for the chipset. It lead me to this very relevant kernel developers' discussion (http://lists.lm-sensors.org/pipermail/lm-sensors/2006-August/017352.html) on my motherboard's chipset. I imagine it's possible to learn this by reading the labels on the chips on your motherboard.

It's likely you'll have to do a kernel patch or reinstallation. I haven't done this yet, but I've done one in the past. This HOW TO (http://ubuntuforums.org/showthread.php?t=217657) was very helpful.

And, finally, I learned that sometimes, your chips simply aren't supported yet. Especially if your chipset is brand new.

satandole666
December 17th, 2006, 03:40 AM
I have the same problem.

Add me to the list too.

Just made the cold-turkey switch from Windows to Ubuntu. Wiped my entire HD clean and installed last night.

Being an avid overclocker I'd kill for monitoring software right now.

Hardware is:

Opty165
DFI Lanparty nForce4 UT

After about 45 minutes of googling, reading guides, and tr ying solutions nothing has worked.

I did, however, discover that if I did modprobe on the other detected sensors I got these results:


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

#----cut here----
# I2C adapter drivers
i2c-nforce2
i2c-isa
# I2C chip drivers
eeprom
it87
#----cut here----

Do you want to add these lines to /etc/modules automatically? (yes/NO)y

sudo modprobe i2c-sensor
FATAL: Module i2c_sensor not found.
sudo modprobe i2c-nforce2
sudo modprobe i2c-isa
sudo modprobe eeprom
sudo modprobe it87
sudo depmod -a
sudo update-modules
sensors
it8712-isa-0290
Adapter: ISA adapter
VCore 1: +1.49 V (min = +0.00 V, max = +4.08 V)
VCore 2: +1.47 V (min = +1.28 V, max = +1.68 V)
+3.3V: +3.33 V (min = +2.78 V, max = +3.78 V)
+5V: +4.97 V (min = +4.49 V, max = +5.48 V)
+12V: +11.84 V (min = +9.98 V, max = +13.95 V)
-12V: -13.62 V (min = -22.94 V, max = -17.05 V) ALARM
-5V: -1.38 V (min = -9.14 V, max = -7.75 V) ALARM
Stdby: +5.05 V (min = +4.49 V, max = +5.48 V)
VBat: +3.09 V
fan1: 0 RPM (min = 811 RPM, div = 8)
fan2: 0 RPM (min = 811 RPM, div = 8)
fan3: 6490 RPM (min = 811 RPM, div = 8)
M/B Temp: +20C (low = +127C, high = +63C) sensor = diode
CPU Temp: +25C (low = +127C, high = +63C) sensor = thermistor
Temp3: +36C (low = +127C, high = +63C) sensor = thermistor


Seems to be a success. All I did was ignore the error. :-k I'm going to install a gui for this and see how it works. Anyway, I hope this helps someone.

P.S. And yes, I'm going to look into my -12V and -5V readings...if that's true it "might" be the reason I am limited to 2700mhz on my Opty165.

SuperMike
December 17th, 2006, 03:45 AM
I had to look up what 'lm-sensors' did. For the uninformed like me, it's to look at fan, temperature, and things like that on your PC or server.

satandole666
December 18th, 2006, 04:19 AM
Just as a follow up to my above post, GkrellM works perfect. My advice to anyone who gets that error is to continue modprobing and finish the install per this guide. Everything works and there are no problems. I'm still curious but it doesn't bother me that much.

Andyreas
December 22nd, 2006, 06:35 PM
Argh. A lot of people get the same problem: ((Sorry, no chips were detected. )) when u run sensors detect (even with sudo). The fun thing is that i've got an HP NX8220 and in another post in this thread a guy got another answer. Why? Really there must be someone that has an answer to this problem. What i can understand there is alot of people having this problem. Is it just that simple that our laptops isn't supported yet even thou i've had mine for a long time, 8 months...

jczucco
January 12th, 2007, 07:27 PM
I finally got my sensors working again in edgy, and hopefully this tip helps others who had sensors working fine in dapper, but are no longer working with edgy. This particular issue is not directly related to anything done in Ubuntu.

For the background, I've got an intel 801 based motherboard on this particular box, and everything was working just fine with my former Gentoo install. Likewise, all was good when I installed Ubuntu dapper. After the upgrade to edgy, sensors stopped working. I tried compiling the latest lm-sensors, but that didn't help either.

A key piece of information is that dapper was on kernel 2.6.15 and edgy uses 2.6.17. With some research and perusal of drivers/pci/quirks.c, there are a number of systems where the SMBus is hidden by default (see asus_hides_smbus in quirks.c).

At any rate, I discovered there was a patch applied to quirks.c in 2.6.16 which effectively disables unhiding the SMBus when ACPI_SLEEP is enabled.

My solution was to build a custom kernel without ACPI_SLEEP support. I'm now running 2.6.19, but this should work equally well for 2.6.17 or .18.

Here's the supporting documentation:
http://bugzilla.kernel.org/show_bug.cgi?id=6449
http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.16.y.git;a=blobdiff;h=0693c23831bb923c12866737 891e40863fab66b5;hp=dda6099903c18adc8636d89683ddc0 2a9a17b32a;hb=a9cacd682ed7c031fa05b1d1367a3b322181 3932;f=drivers/pci/quirks.c
http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.16.y.git;a=commit;h=a9cacd682ed7c031fa05b1d136 7a3b3221813932

Hope this helps!

Thanks for the tip! I will try this. Can you post your kernel .config ?

jczucco
January 12th, 2007, 07:30 PM
.

sputnik2012
February 4th, 2007, 04:00 PM
I'm using the 2.6.19.2 kernel, which doesn't have i2c-sensors as a module.

loaded modules are as follows


# Generated by sensors-detect on Fri Feb 2 22:36:27 2007
it87
# I2C adapter drivers
i2c-nforce2
i2c-isa
# I2C chip drivers
eeprom
# Warning: the required module it87 is not currently installed on your system.
# For status of 2.6 kernel ports see http://secure.netroedge.com/~lm78/supported
.html
# If driver is built-in to the kernel, or unavailable, comment out the following
line.


When I run sensors -s I get the following output:

root@rob-desktop:/home/rob# sensors -s
it8712-isa-0d00: Can't access procfs/sysfs file for writing;
Run as root?


I had a feeling sysfs was deprecated in favour of udev, but my /sys folder is there. I have built and rub mkdev.sh.

When I run sensors and I get the following output:

it8712-isa-0d00
Adapter: ISA adapter
VCore 1: +1.65 V (min = +1.42 V, max = +1.57 V) ALARM
VCore 2: +1.57 V (min = +2.40 V, max = +2.61 V) ALARM
+3.3V: +2.58 V (min = +3.14 V, max = +3.47 V) ALARM
+5V: +2.47 V (min = +4.76 V, max = +5.24 V) ALARM
+12V: +13.12 V (min = +11.39 V, max = +12.61 V) ALARM
-12V: -5.02 V (min = -12.63 V, max = -11.41 V) ALARM
-5V: -1.24 V (min = -5.26 V, max = -4.77 V) ALARM
Stdby: +5.05 V (min = +4.76 V, max = +5.24 V)
VBat: +4.08 V
fan1: 4299 RPM (min = 0 RPM, div = 2)
fan2: 2109 RPM (min = 2986 RPM, div = 4) ALARM
ERROR: Can't get FAN3 data!
M/B Temp: +51C (low = +15C, high = +40C) sensor = diode
CPU Temp: -1C (low = +15C, high = +45C) sensor = disabled
Temp3: -1C (low = +15C, high = +45C) sensor = disabled


How do I enable the CPU and Temp3 sensors?

Thanks,
Rob.

scotte
February 9th, 2007, 08:50 PM
Thanks for the tip! I will try this. Can you post your kernel .config ?

All I did was copy /boot/config-2.6.17-10-generic to the new kernel .config, did a "make oldconfig", disabled ACPI_SLEEP, then proceeded normally from there...

SebMKd
February 22nd, 2007, 04:17 AM
Great HowTo! =D>
Even simpler than expected as the Sensor detect install the modules automatically!

morganGDFP
February 25th, 2007, 09:29 PM
i can't quite get it to work..
I followed the howto and running sensors works after I have loaded the modules manually using sudo modprobe..

but I can't get them to load automatically during boot.
I think I need to be root to load some of the modules, and that's why they don't load properly..

these are the modules I need to load in order to get lm-sensors to work.


#----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-sis96x
i2c-isa
# I2C chip drivers
eeprom
w83627hf
#----cut here----

they are also added to my /etc/modules file.
but after boot up sensors does not work and I get this error message:


morgan@morgan-desktop:~$ sensors
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!

if I then run sudo modprobe on all the modules listed above it works..
if I run modprobe without sudo one of them tells me that I am not allowed to do that..(sorry, I don't remember which one it is)

So, my guess is that I need to load those modules during boot but I need to have sudo rights in order to do that..
Is there a way to do that or is there a completely different way to get lm-sensors to work
thank you in advance.

emperor
February 27th, 2007, 04:29 PM
Since Dapper, I have found that sensors-detect can automaticly make all the changes required to your system. For example, on Ubuntu 6.06.1 you can see below where sensors-detect did the following:

#/etc/modules:
# Generated by sensors-detect on Fri Feb 3 11:24:54 2006
# I2C adapter drivers
i2c-i801
i2c-isa
# I2C chip drivers
eeprom
w83627hf

e.p.

morganGDFP
February 27th, 2007, 07:45 PM
yes it does make the changes and adds the modules in /etc/modules but I still have to run them "manually" after each reboot in order for the "sensors" command to work..
Anyone know why this is?

emperor
February 28th, 2007, 03:52 AM
yes it does make the changes and adds the modules in /etc/modules but I still have to run them "manually" after each reboot in order for the "sensors" command to work..
Anyone know why this is?

Run "dmesg" and see if there are any messages related to the modprobe attempts related to "/etc/modules" during boot.

dmesg |less

Use page-down to examine the messages.

I would try running the following commands after manually inserting the modules using modprobe:

sudo depmod -a
sudo update-modules

rookieone
March 1st, 2007, 11:53 AM
i can't quite get it to work..


morgan@morgan-desktop:~$ sensors
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!



I have the same problem on Kubuntu 6.10 on an Nvida Nforce 430MCP board (Asus M2NPV-VM with an Athlon 64 X2 3800+).
I installed lm-sensors with apt, ran the .sh, then sensors detect which added the modules to my /etc/modules.
I get the same error when I try to run "sudo sensors -s" or just "sensors"

bravemosquito
March 1st, 2007, 05:03 PM
This is my case:



root@xxxx:/xxx/x# modprobe i2c-sensor
FATAL: Module i2c_sensor not found.


Did I miss something? My mobo is ASRock NForce4 MCP 410/430 with on-board vcard

Edit: Nevermind, after reboot measuring works now, but not at full - no hdd temp, constant cpu-fan speed (3183rpm)

Icarosaurus
March 1st, 2007, 07:22 PM
I finally made it work with my ABIT AN7 Motherboard.
Just go to the thread: http://www.ubuntuforums.org/showthread.php?p=2231651#post2231651

xfile087
March 5th, 2007, 02:18 PM
Hi guys - I don't know if this has been posted anywhere in this thread but here it anyway. I tried the tutorial many times and it just wouldn't detect sensors for my Asus M2NPV-MX so I downloaded the latest version of lm-sensors and followed the rest of the tutorial and it works perfectly!!

So download and install the latest version:-


sudo apt-get install flex bison libsysfs-dev

wget http://dl.lm-sensors.org/lm-sensors/releases/lm_sensors-2.10.2.tar.gz

tar -zxf lm_sensors-2.10.2.tar.gz

cd lm_sensors-2.10.2

make user

su

make user_install



and then follow the rest of the tutorial and it works perfectly.

captin_moor
March 6th, 2007, 10:27 AM
Hi there guys and girls, first time user long time listener here :). I user Redhat at work and have previously been an avide Xp user. Well I am glad that phase is over. Die MS die. Anyway what I require is someone to hold my hand to get this lm_sensor working. I would really love to get this to work if possible.

I have followed the HOWTO: pretty much to the letter but I still get:

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 i2c-i801
# Chip drivers
modprobe eeprom
# 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):

ubuntu>/home/captin/backup>cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

lp
psmouse

# Generated by sensors-detect on Tue Apr 3 13:21:47 2007

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

#For lm-sensors, i2c modules
i2c-i801
eeprom
/usr/local/bin/sensors -s

ubuntu>/home/captin/backup>sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
ubuntu>/home/captin/backup>

I have gone through and run the sensor-detect and it has located items, I have placed these in what I believe to be the correct dirs but still get the same message.

Can you let me know what you need to help me out and i will re post.

Thanks for all your help guys and if there is anything that you can help with, I will be eternally in your debit.

scotte
March 7th, 2007, 01:09 AM
captin_moor, since it looks like you have an i801 based system, you may be interested in my comments regarding ACPI_SLEEP on one of the previous pages of this thread...

captin_moor
March 7th, 2007, 08:37 AM
Hey Scotte, thank man I appreciate the help. But I think that this is a bit out of my league at this moment in time. I will need to do some serious google research to catch up to this stage my man. I appreciate the lead though. If I have any question I will let you know. Thanks, Tim :)

bravemosquito
March 9th, 2007, 10:42 PM
In my Gnome panel there isn't Hard Drive Temperature. When I want to check it I must type hddtemp /dev/hda

How can I put it back? There are only CPU temp, SYS temp and other unknown value: temp3 28'C. I haven't another pc component with built in temp sensor. Only CPU, NorthBridge and HDD :confused:

wikki
March 16th, 2007, 07:11 PM
I believe that I've followed the instructions correctly. Seems pretty simple. However when I run sensors I get the following message.

Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!

Pugwash
March 16th, 2007, 07:36 PM
I just noticed that I get an error during boot that goes something like this : "setting sensor limits .. failed" . Is it related to this? I'm quite sure I've not seen such an error during boot before.

zipeppe
March 17th, 2007, 11:52 AM
Hi guys,

lm-sensors doesn't work for me :(

My Laptop is the ASUS A6JA-Q002 equipped with an Analog Device ADT7463 sensor.

Everything works using SpeedFan under Windows XP, but it seems there are no way to handle the ADT7463 with Ubuntu (feisty 7.04 herd 5, kernel 2.6.20-11-generic).

With SpeedFan I can set FAN#1 to a wanted speed (50-70% because of a new HDD 7200 rpm installed), I can monitor CPU and HDD TEMP, and I got the following informations:



14/02/2007 22.26.49 - START OF DMI HEADER
14/02/2007 22.26.49 - Anchor String=_SM_
14/02/2007 22.26.49 - Entry Point Length=31
14/02/2007 22.26.49 - SMBIOS Major Version=2
14/02/2007 22.26.49 - SMBIOS Minor Version=3
14/02/2007 22.26.49 - Maximum Structure Size=182
14/02/2007 22.26.49 - Entry Point Revision=0
14/02/2007 22.26.49 - Intermediate Anchor String=_DMI_
14/02/2007 22.26.49 - Intermediate Checksum=152
14/02/2007 22.26.49 - Structure Table Length=1474
14/02/2007 22.26.49 - Structure Table Address=$000FC4F0
14/02/2007 22.26.49 - Number of SMBIOS Structures=35
14/02/2007 22.26.49 - SMBIOS BCD Revision=$23
14/02/2007 14/02/2007 22.26.49 - DMI tables properly parsed
14/02/2007 22.26.49 - -> MB Manufacturer <ASUSTeK Computer Inc.>
14/02/2007 22.26.49 - -> MB Model <A6J>
14/02/2007 22.26.49 - -> MB Version <1.0>
14/02/2007 22.26.49 - -> MB Serial <BSN12345678901234567>

14/02/2007 22.26.49 - UGURU found ASUSTeK Computer Inc. A6J
14/02/2007 22.26.49 - End of UGURU detection

14/02/2007 22.26.49 - About to probe ACPI
14/02/2007 22.26.50 - FOUND ACPI at $0000

- About to read first samples from ADT7463@$2E(onSMBusIntel@$400)
14/02/2007 22.26.50 - ...temperatures
14/02/2007 22.26.50 - ...fans
14/02/2007 22.26.50 - ...pwms
14/02/2007 22.26.51 - ...volts

- About to read first samples from HTE721010G9AT00MPD0Q7Y0H0TW7L
14/02/2007 22.26.51 - ...temperatures
14/02/2007 22.26.51 - ...fans
14/02/2007 22.26.51 - ...pwms
14/02/2007 22.26.51 - ...volts

- About to read first samples from ACPI
14/02/2007 22.26.51 - ...temperatures
14/02/2007 22.26.51 - ...fans
14/02/2007 22.26.51 - ...pwms
14/02/2007 22.26.51 - ...volts

xxx version 2.01

xxx Link UniqueID=ISA@$290

Name=ISA

Address=$290

xxx end



xxx Link UniqueID=PCI@$0

Name=PCI

Address=$0

xxx end



xxx Link UniqueID=SMBusIntel@$400

Name=SMBus

Address=$400

xxx end



xxx Link UniqueID=SMART@$0

Name=SMART

Address=$0

xxx end



xxx Sensor UniqueID=ADT7463@$2E(onSMBusIntel@$400)

Name=ADT7463

UsedBUS=Intel SMBus

Address=$2E

Link=SMBus

StickyProps=1

Property=13 |PWM 1 mode| set to |Manually controlled|

xxx end



xxx Sensor UniqueID=HTE721010G9AT00MPD0Q7Y0H0TW7L

Name=HD0 (100,0GB)

UsedBUS=SMART

Address=$0

Link=SMART

StickyProps=0

xxx end



xxx Sensor UniqueID=ACPI

Name=ACPI

UsedBUS=ISA

Address=$0

Link=ISA

StickyProps=0

xxx end



xxx the end



xxx Pwm 1 from ADT7463@$2E(onSMBusIntel@$400)

name=Speed01

active=true

min=55

max=100

variate=false

xxx end



xxx Pwm 2 from ADT7463@$2E(onSMBusIntel@$400)

name=Speed02

active=true

min=0

max=100

variate=false

xxx end



xxx Pwm 3 from ADT7463@$2E(onSMBusIntel@$400)

name=Speed03

active=true

min=0

max=100

variate=false

xxx end



xxx Temp 1 from ADT7463@$2E(onSMBusIntel@$400)

name=CPU

active=true

wanted=40

warning=50

offset=0

intray=true

UsedPwms=3

pwm=1 from ADT7463@$2E(onSMBusIntel@$400)

pwm=2 from ADT7463@$2E(onSMBusIntel@$400)

pwm=3 from ADT7463@$2E(onSMBusIntel@$400)

logged=false

xxx end



xxx Temp 2 from ADT7463@$2E(onSMBusIntel@$400)

name=Local

active=true

wanted=40

warning=50

offset=0

intray=false

UsedPwms=3

pwm=1 from ADT7463@$2E(onSMBusIntel@$400)

pwm=2 from ADT7463@$2E(onSMBusIntel@$400)

pwm=3 from ADT7463@$2E(onSMBusIntel@$400)

logged=false

xxx end



xxx Temp 3 from ADT7463@$2E(onSMBusIntel@$400)

name=Remote 2

active=true

wanted=40

warning=50

offset=0

intray=false

UsedPwms=3

pwm=1 from ADT7463@$2E(onSMBusIntel@$400)

pwm=2 from ADT7463@$2E(onSMBusIntel@$400)

pwm=3 from ADT7463@$2E(onSMBusIntel@$400)

logged=false

xxx end



xxx Temp 1 from HTE721010G9AT00MPD0Q7Y0H0TW7L

name=HD0

active=true

wanted=40

warning=50

offset=0

intray=false

UsedPwms=3

pwm=1 from ADT7463@$2E(onSMBusIntel@$400)

pwm=2 from ADT7463@$2E(onSMBusIntel@$400)

pwm=3 from ADT7463@$2E(onSMBusIntel@$400)

logged=false

xxx end



xxx Temp 1 from ACPI

name=Temp1

active=true

wanted=40

warning=50

offset=0

intray=false

UsedPwms=3

pwm=1 from ADT7463@$2E(onSMBusIntel@$400)

pwm=2 from ADT7463@$2E(onSMBusIntel@$400)

pwm=3 from ADT7463@$2E(onSMBusIntel@$400)

logged=false

xxx end



xxx Fan 1 from ADT7463@$2E(onSMBusIntel@$400)

name=Fan1

active=true

logged=false

xxx end



xxx Fan 2 from ADT7463@$2E(onSMBusIntel@$400)

name=Fan2

active=true

logged=false

xxx end



xxx Fan 3 from ADT7463@$2E(onSMBusIntel@$400)

name=Fan3

active=true

logged=false

xxx end



xxx Fan 4 from ADT7463@$2E(onSMBusIntel@$400)

name=Fan4

active=true

logged=false

xxx end



xxx Volt 1 from ADT7463@$2E(onSMBusIntel@$400)

name=+2.5V

active=true

logged=false

xxx end



xxx Volt 2 from ADT7463@$2E(onSMBusIntel@$400)

name=Vcore

active=true

logged=false

xxx end



xxx Volt 3 from ADT7463@$2E(onSMBusIntel@$400)

name=+3.3V

active=true

logged=false

xxx end



xxx Volt 4 from ADT7463@$2E(onSMBusIntel@$400)

name=+5V

active=true

logged=false

xxx end



xxx Volt 5 from ADT7463@$2E(onSMBusIntel@$400)

name=+12V

active=true

logged=false

xxx end


The problem is the sensor NOT DETECTED by sensors-detect command:
> 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): Yes
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): Yes
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): Yes
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 town 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.



Another thing make me puzzled: i2c_dev , i2c_ec and i2c_core modules are correctly loaded; nevertheless there are no i2c bus populated as shown:

> ls /proc/bus
input pccard pci usb

:confused: :confused:

Could anyone help me on this? The temp is going hot and I cannot use the laptop under Linux for more than one hour...

Cheers,
ZpP

emperor
March 18th, 2007, 04:53 AM
The sensor chip, ADT7463, has been supported a long time by the lm85 driver. However the bus chipset should be checked.
http://lm-sensors.org/wiki/Devices

bazar
March 22nd, 2007, 04:40 AM
I believe that I've followed the instructions correctly. Seems pretty simple. However when I run sensors I get the following message.

Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!


I have the exact same error message happen to me.
Does anyone have a solution for this?

t341
March 22nd, 2007, 04:52 AM
I also came up with the "Can't access procfs/sysfs file Unable to
find i2c bus information; For 2.6 kernels, make sure you have mounted
sysfs and libsensors was compiled with sysfs support!" error after using
the instructions in this thread and the ones at ubuntuguide.org.

Would it be at all possible to revise the instructions to include such
steps?

greenfrog
March 29th, 2007, 02:22 PM
I have a laptop with the NVIDIA chipset for my AMD64 CPU.
Anyone had a luck getting the sensors working.
I can only get the CPU temp working.

Thanks :confused:

DerArzt
March 31st, 2007, 05:00 PM
I realize that i need to tweak some stuff in the conf file, but I don't know what are reasonable values. I get all sorts of alarms .


it8712-isa-0290
Adapter: ISA adapter
VCore 1: +1.41 V (min = +1.42 V, max = +1.57 V) ALARM
VCore 2: +2.58 V (min = +2.40 V, max = +2.61 V)
+3.3V: +3.25 V (min = +3.14 V, max = +3.47 V)
+5V: +4.19 V (min = +4.76 V, max = +5.24 V) ALARM
+12V: +12.10 V (min = +11.39 V, max = +12.61 V)
-12V: -16.07 V (min = -12.63 V, max = -11.41 V) ALARM
-5V: -8.10 V (min = -5.26 V, max = -4.77 V) ALARM
Stdby: +3.09 V (min = +4.76 V, max = +5.24 V) ALARM
VBat: +4.08 V
fan1: 2636 RPM (min = 0 RPM, div = 8)
fan2: 0 RPM (min = 3013 RPM, div = 8) ALARM
fan3: 2556 RPM (min = 3013 RPM, div = 8) ALARM
M/B Temp: +25C (low = +15C, high = +40C) sensor = thermistor
CPU Temp: +25C (low = +15C, high = +45C) sensor = thermistor
Temp3: +35C (low = +15C, high = +45C) sensor = diode



Any help will be greatly appreciated

counterpoint
April 3rd, 2007, 05:53 PM
In my case, this is caused by my current kernel not supporting my I/O chip. For the record, I am running an Asus M2NPV-VM, which has an NForce 430 chipset (MCP 50). Apparently the I/O chip in question is the IT8716F. I'm running under a 2.6.18 kernel I compiled.

My new Linux PC is also built on the Asus M2NPV-VM, Mostly seems to be going well so far. But as a Linux beginner, I'd be delighted if someone could post step by step instructions for getting CPU temperature monitoring going,

zipeppe
April 15th, 2007, 05:52 PM
The sensor chip, ADT7463, has been supported a long time by the lm85 driver. However the bus chipset should be checked.
http://lm-sensors.org/wiki/Devices

What do you mean, please?

Could you give to me some more information? I don't know how to do it..

Tnx

Tanker Bob
April 17th, 2007, 03:04 AM
Does anyone have a DEB of version 2.10.3 or know where I can get it? The repository version doesn't work with my MB (MSI P6N SLI Platinum) and the tar file won't compile for me. Thanks!

PhotoJoe
April 18th, 2007, 06:44 AM
Excellent tutorial! XSensor did not work at all for me using the Add/Remove programs GUI route. I got an icon in System Tools that did nothing! Now it works great!

Here's the question I still have - lmsensors was installed (verified by Synaptic) and the program appeared as 'sleeping' in System Monitor before I even attempted this....so what was missing? This utility always worked (and still does) in the BIOS.

My guess is the 2 drivers I needed were not in the GUI package(s).....

saltydog
April 18th, 2007, 11:53 AM
This is my output to the sensors command:



w83627ehf-isa-0290
Adapter: ISA adapter
Case Fan: 0 RPM (min = 1240 RPM, div = 64)
CPU Fan: 1896 RPM (min = 1704 RPM, div = 8)
fan3: 0 RPM (min = 10546 RPM, div = 64)
fan4: 0 RPM (min = 1171 RPM, div = 128)
Sys Temp: +33C (high = +45C, hyst = +40C)
CPU Temp: +28.5C (high = +45.0C, hyst = +40.0C)
temp3: +33.0C (high = +80.0C, hyst = +75.0C)



What is temp3??

bravemosquito
April 18th, 2007, 01:12 PM
What is temp3??

Yeah, I'm asking the same question :-k

saltydog
April 18th, 2007, 06:11 PM
Running pwmconfig I got this message:

/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed

I have Dapper, so the patch on pwmconfig is applied. What should I do to have fan control? The fan is a 3-wire model.

Pkirkham
April 20th, 2007, 01:03 PM
Although the rest of this topic is quite antique it seems the most appropriate place to put this question.

I'm trying to use cacti to monitor sensors. I have installed net-snmp, lm-sensors etc.

If I type sensors at the CLI I get the correct sensor info back but using snmpwalk etc there are no sensor MIBs.

It would appear that I need to recompile net-snmp to include the MIBs but when I use the ./configure in the net-snmp install I get
configure: error: asked to use lm_sensors but I couldn't find sensors/sensors.h

I've looked in the Ubuntu Dapper headers but sensors.h isn't there.

Where is sensors.h?

I do hate having to recompile stuff to get it to work which for me is a bane of Linux but that's the way it is I suppose, like it or lump it!

Any advice would be appreciated, including a better plcae to post this.
Thanks,
Pete

nss0000
April 25th, 2007, 07:22 PM
CPT:

I'm running DAPPERx64 on an ASUS-M2N/AMD5400+ ... LM-Sensors has NEVER worked for me. Ultimately all I get is the error "no sensors found". Must be the NV430 chipset is still unsupported.

nss
*******

Chupa
May 2nd, 2007, 10:57 AM
Sensors don't work for me :( Don't know what the matter is. There is all I do:


root@chupa-desktop:/home/chupa# apt-get install lm-sensors
lm-sensors is already the newest version.

root@chupa-desktop:/home/chupa# ./mkdev.sh
/dev/i2c-0
mknod: `/dev/i2c-0': File exists

root@chupa-desktop:/home/chupa# 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.

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: SMBus I801 adapter at 0400
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x08
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 `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
i2c-i801
# Chip drivers
eeprom
w83627ehf
#----cut here----

Do you want to add these lines to /etc/modules automatically? (yes/NO)y

root@chupa-desktop:/home/chupa# /etc/init.d/module-init-tools
* Loading kernel modules... * Loading manual drivers... [ OK ]

root@chupa-desktop:/home/chupa# nano /etc/modprobe.d/local
root@chupa-desktop:/home/chupa# update-modules

root@chupa-desktop:/home/chupa# modprobe i2c-sensor
FATAL: Module i2c_sensor not found.

root@chupa-desktop:/home/chupa# modprobe i2c-viapro
FATAL: Module i2c_viapro not found.

root@chupa-desktop:/home/chupa# modprobe i2c-isa

root@chupa-desktop:/home/chupa# modprobe it87
FATAL: Error inserting it87 (/lib/modules/2.6.21-custom/kernel/drivers/hwmon/it8 7.ko): No such device

root@chupa-desktop:/home/chupa# depmod -a
root@chupa-desktop:/home/chupa# update-modules

root@chupa-desktop:/home/chupa# sensors
w83627dhg-isa-0290
Adapter: ISA adapter

ASUS P5B-E motherboard, Core 2 Duo E6300, ASUS Radeon X1650XT.

Tanker Bob
May 2nd, 2007, 11:47 AM
They don't work on my MSI P6N SLI Platinum motherboard with the NVIDIA nForce 850i chipset either.

Chupa
May 3rd, 2007, 12:57 PM
Hmm, GKrellm shows all the sensors correctly but sensons command gives only:
root@chupa-desktop:/home/chupa# sensors
w83627dhg-isa-0290
Adapter: ISA adapter
Why?

Reinhardt
May 4th, 2007, 02:10 AM
Sensors don't work for me :( Don't know what the matter is. There is all I do:



ASUS P5B-E motherboard, Core 2 Duo E6300, ASUS Radeon X1650XT.

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?

Chupa
May 4th, 2007, 09:44 AM
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
May 5th, 2007, 11:04 AM
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
May 9th, 2007, 03:01 PM
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
May 9th, 2007, 10:07 PM
Just did this on my DFI NF4 Ultra-D ...and it works flawlessly, modules load perfectly everytime on reboot.

Thnx...a bunch.

h0bbe
May 12th, 2007, 04:25 PM
I've followed both the HOW TO above an this one http://news.softpedia.com/news/How-to-Install-lm-sensors-on-Ubuntu-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
May 15th, 2007, 04:49 PM
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
May 20th, 2007, 10:07 PM
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
May 22nd, 2007, 09:13 PM
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 (http://ubuntuforums.org/showthread.php?t=447277).

zipeppe
May 31st, 2007, 10:24 PM
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
June 1st, 2007, 07:39 AM
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

belikralj
June 6th, 2007, 09:33 AM
I have also installed lm-sensors and got the mkdev.sh script as per the howto, but sensors-detect doesn't detect anything. Why? I have Ubuntu Dapper (32bit) installed on my athlon64. I also have both Feisty and Slackware (32bit) on this system and only Feisty (which is 64bit install) detects something and still it doesn't work. I'm guessing by what I see that it has something to do with the kernel (32bit of 64bit), I mean it still doesn't work on my 64bit Feisty but at least it detects something. So can anyone halp me with this? I'll make sure to look at what the problem is in Feisty cause I can't exactly remember of the top of my head what it was.

Thanx

libos
June 10th, 2007, 01:25 PM
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?

Not sure what went wrong to yours, but i got mine working :)
http://bsling.blogspot.com/2007/06/hardware-health-monitoring-on-asus-m2n.html

AmericanAqualung
June 22nd, 2007, 04:42 PM
Ok, so I got this up and running but have a few questions still. First, I get three sets of output (shown below) for my AMD opteron board with 4 dual core processors (its part of a linux cluster). Which do I use? The top two give reasonable values, but disagree and the third is nonsense (neg. temps). Also, shouldn't I be able to get either 4 or 8 temps for each cpu/core? And I understand that temp 1 is m/b, temp2 is cpu, but what is temp3? case? Thanks a lot.


adm1026-i2c-1-2d
Adapter: SMBus nForce2 adapter at 4c40
in0: +0.00 V (min = +0.00 V, max = +2.99 V) ALARM
in1: +0.00 V (min = +2.25 V, max = +2.75 V) ALARM
in2: +0.00 V (min = +2.25 V, max = +2.75 V) ALARM
in3: +0.00 V (min = +2.25 V, max = +2.75 V) ALARM
in4: +0.00 V (min = +0.00 V, max = +2.99 V) ALARM
in5: +0.00 V (min = +0.00 V, max = +2.99 V) ALARM
in6: +0.00 V (min = +0.00 V, max = +2.49 V) ALARM
in7: +1.36 V (min = +1.02 V, max = +1.68 V)
in8: +0.00 V (min = +0.00 V, max = +2.49 V)
in9: +0.35 V (min = +0.00 V, max = +0.76 V)
in10: +3.08 V (min = +2.97 V, max = +3.64 V)
in11: +3.42 V (min = +0.00 V, max = +4.42 V)
in12: +3.38 V (min = +2.97 V, max = +3.64 V)
in13: +3.36 V (min = +4.50 V, max = +5.49 V) ALARM
in14: +1.35 V (min = +1.02 V, max = +1.68 V)
in15: +0.00 V (min = +10.81 V, max = +13.19 V) ALARM
in16: +0.19 V (min = -13.18 V, max = -10.80 V) ALARM
ERROR: Can't get FAN0 data!
fan1: 0 RPM (min = 712 RPM, div = 8) ALARM
fan2: 0 RPM (min = 712 RPM, div = 8)
fan3: 6250 RPM (min = 712 RPM, div = 8)
fan4: 6250 RPM (min = 712 RPM, div = 8) ALARM
fan5: 0 RPM (min = 712 RPM, div = 8) ALARM
fan6: 0 RPM (min = 712 RPM, div = 8) ALARM
fan7: 0 RPM (min = 712 RPM, div = 8) ALARM
temp1: +51C (low = +0C, high = +80C)
temp2: +40C (low = +0C, high = +78C)
temp3: +36C (low = +0C, high = +78C)
vid: +0.975 V (VRM Version 2.4)

adm1026-i2c-1-2c
Adapter: SMBus nForce2 adapter at 4c40
in0: +2.62 V (min = +0.00 V, max = +2.99 V)
in1: +1.22 V (min = +2.25 V, max = +2.75 V) ALARM
in2: +2.65 V (min = +2.25 V, max = +2.75 V)
in3: +1.50 V (min = +2.25 V, max = +2.75 V) ALARM
in4: +0.00 V (min = +0.00 V, max = +2.99 V) ALARM
in5: +0.00 V (min = +0.00 V, max = +2.99 V) ALARM
in6: +0.00 V (min = +0.00 V, max = +2.49 V) ALARM
in7: +1.34 V (min = +1.02 V, max = +1.68 V)
in8: +0.00 V (min = +0.00 V, max = +2.49 V)
in9: +0.75 V (min = +0.00 V, max = +0.76 V)
in10: +3.12 V (min = +2.97 V, max = +3.64 V)
in11: +3.42 V (min = +2.97 V, max = +3.64 V)
in12: +3.38 V (min = +2.97 V, max = +3.64 V)
in13: +5.10 V (min = +4.50 V, max = +5.49 V)
in14: +1.34 V (min = +1.02 V, max = +1.68 V)
in15: +12.19 V (min = +10.81 V, max = +13.19 V)
in16: -12.03 V (min = -13.18 V, max = -10.80 V)
ERROR: Can't get FAN0 data!
fan1: 0 RPM (min = 712 RPM, div = 8) ALARM
fan2: 0 RPM (min = 712 RPM, div = 8) ALARM
fan3: 0 RPM (min = 712 RPM, div = 8)
fan4: 6250 RPM (min = 712 RPM, div = 8) ALARM
fan5: 0 RPM (min = 712 RPM, div = 8) ALARM
fan6: 0 RPM (min = 712 RPM, div = 8) ALARM
fan7: 0 RPM (min = 712 RPM, div = 8) ALARM
temp1: +45C (low = +0C, high = +80C)
temp2: +47C (low = +0C, high = +78C)
temp3: +77C (low = +0C, high = +78C)
vid: +0.975 V (VRM Version 2.4)

w83627hf-isa-0290
Adapter: ISA adapter
VCore 1: +3.14 V (min = +0.00 V, max = +0.00 V) ALARM
VCore 2: +3.10 V (min = +0.00 V, max = +0.00 V) ALARM
+3.3V: +3.12 V (min = +3.14 V, max = +3.47 V) ALARM
+5V: +5.30 V (min = +4.76 V, max = +5.24 V) ALARM
+12V: +11.86 V (min = +10.82 V, max = +13.19 V)
-12V: +0.72 V (min = -13.18 V, max = -10.80 V) ALARM
-5V: +2.09 V (min = -5.25 V, max = -4.75 V) ALARM
V5SB: +5.67 V (min = +4.76 V, max = +5.24 V) ALARM
VBat: +0.00 V (min = +2.40 V, max = +3.60 V) ALARM
fan1: 0 RPM (min = 0 RPM, div = 2)
fan2: 0 RPM (min = 0 RPM, div = 2)
fan3: 0 RPM (min = 5720 RPM, div = 2) ALARM
temp1: -15C (high = -1C, hyst = -1C) sensor = thermistor
temp2: -17.0C (high = +80C, hyst = +75C) sensor = thermistor
temp3: -16.5C (high = +80C, hyst = +75C) sensor = thermistor
vid: +0.000 V (VRM Version 2.4)
alarms:
beep_enable:
Sound alarm enabled

divdude
June 22nd, 2007, 06:08 PM
In my laptop I worked it like this.
First i ran sensors-detect
and ran
lsmod(list all loaded modules)

This is my list:
.
.
.
.
usbcore 134280 3 ehci_hcd,uhci_hcd
thermal 14856 0
processor 31048 1 thermal
fan 5636 0
fbcon 42656 0
tileblit 3584 1 fbcon
font 9216 1 fbcon
bitblit 6912 1 fbcon
softcursor 3200 1 bitblit

you can see thermal and processor modules are loaded

After that i ran
cat proc/acpi/thermal_zone/THRM/temperature
temperature: 47 C

which i think is cpu temperature.
you can run
cat /proc/acpi/thermal and TAB to get options

libos
June 23rd, 2007, 04:47 AM
Ok, so I got this up and running but have a few questions still. First, I get three sets of output (shown below) for my AMD opteron board with 4 dual core processors (its part of a linux cluster). Which do I use? The top two give reasonable values, but disagree and the third is nonsense (neg. temps). Also, shouldn't I be able to get either 4 or 8 temps for each cpu/core? And I understand that temp 1 is m/b, temp2 is cpu, but what is temp3? case? Thanks a lot.


adm1026-i2c-1-2d
Adapter: SMBus nForce2 adapter at 4c40
in0: +0.00 V (min = +0.00 V, max = +2.99 V) ALARM
in1: +0.00 V (min = +2.25 V, max = +2.75 V) ALARM
in2: +0.00 V (min = +2.25 V, max = +2.75 V) ALARM
in3: +0.00 V (min = +2.25 V, max = +2.75 V) ALARM
in4: +0.00 V (min = +0.00 V, max = +2.99 V) ALARM
in5: +0.00 V (min = +0.00 V, max = +2.99 V) ALARM
in6: +0.00 V (min = +0.00 V, max = +2.49 V) ALARM
in7: +1.36 V (min = +1.02 V, max = +1.68 V)
in8: +0.00 V (min = +0.00 V, max = +2.49 V)
in9: +0.35 V (min = +0.00 V, max = +0.76 V)
in10: +3.08 V (min = +2.97 V, max = +3.64 V)
in11: +3.42 V (min = +0.00 V, max = +4.42 V)
in12: +3.38 V (min = +2.97 V, max = +3.64 V)
in13: +3.36 V (min = +4.50 V, max = +5.49 V) ALARM
in14: +1.35 V (min = +1.02 V, max = +1.68 V)
in15: +0.00 V (min = +10.81 V, max = +13.19 V) ALARM
in16: +0.19 V (min = -13.18 V, max = -10.80 V) ALARM
ERROR: Can't get FAN0 data!
fan1: 0 RPM (min = 712 RPM, div = 8) ALARM
fan2: 0 RPM (min = 712 RPM, div = 8)
fan3: 6250 RPM (min = 712 RPM, div = 8)
fan4: 6250 RPM (min = 712 RPM, div = 8) ALARM
fan5: 0 RPM (min = 712 RPM, div = 8) ALARM
fan6: 0 RPM (min = 712 RPM, div = 8) ALARM
fan7: 0 RPM (min = 712 RPM, div = 8) ALARM
temp1: +51C (low = +0C, high = +80C)
temp2: +40C (low = +0C, high = +78C)
temp3: +36C (low = +0C, high = +78C)
vid: +0.975 V (VRM Version 2.4)

adm1026-i2c-1-2c
Adapter: SMBus nForce2 adapter at 4c40
in0: +2.62 V (min = +0.00 V, max = +2.99 V)
in1: +1.22 V (min = +2.25 V, max = +2.75 V) ALARM
in2: +2.65 V (min = +2.25 V, max = +2.75 V)
in3: +1.50 V (min = +2.25 V, max = +2.75 V) ALARM
in4: +0.00 V (min = +0.00 V, max = +2.99 V) ALARM
in5: +0.00 V (min = +0.00 V, max = +2.99 V) ALARM
in6: +0.00 V (min = +0.00 V, max = +2.49 V) ALARM
in7: +1.34 V (min = +1.02 V, max = +1.68 V)
in8: +0.00 V (min = +0.00 V, max = +2.49 V)
in9: +0.75 V (min = +0.00 V, max = +0.76 V)
in10: +3.12 V (min = +2.97 V, max = +3.64 V)
in11: +3.42 V (min = +2.97 V, max = +3.64 V)
in12: +3.38 V (min = +2.97 V, max = +3.64 V)
in13: +5.10 V (min = +4.50 V, max = +5.49 V)
in14: +1.34 V (min = +1.02 V, max = +1.68 V)
in15: +12.19 V (min = +10.81 V, max = +13.19 V)
in16: -12.03 V (min = -13.18 V, max = -10.80 V)
ERROR: Can't get FAN0 data!
fan1: 0 RPM (min = 712 RPM, div = 8) ALARM
fan2: 0 RPM (min = 712 RPM, div = 8) ALARM
fan3: 0 RPM (min = 712 RPM, div = 8)
fan4: 6250 RPM (min = 712 RPM, div = 8) ALARM
fan5: 0 RPM (min = 712 RPM, div = 8) ALARM
fan6: 0 RPM (min = 712 RPM, div = 8) ALARM
fan7: 0 RPM (min = 712 RPM, div = 8) ALARM
temp1: +45C (low = +0C, high = +80C)
temp2: +47C (low = +0C, high = +78C)
temp3: +77C (low = +0C, high = +78C)
vid: +0.975 V (VRM Version 2.4)

w83627hf-isa-0290
Adapter: ISA adapter
VCore 1: +3.14 V (min = +0.00 V, max = +0.00 V) ALARM
VCore 2: +3.10 V (min = +0.00 V, max = +0.00 V) ALARM
+3.3V: +3.12 V (min = +3.14 V, max = +3.47 V) ALARM
+5V: +5.30 V (min = +4.76 V, max = +5.24 V) ALARM
+12V: +11.86 V (min = +10.82 V, max = +13.19 V)
-12V: +0.72 V (min = -13.18 V, max = -10.80 V) ALARM
-5V: +2.09 V (min = -5.25 V, max = -4.75 V) ALARM
V5SB: +5.67 V (min = +4.76 V, max = +5.24 V) ALARM
VBat: +0.00 V (min = +2.40 V, max = +3.60 V) ALARM
fan1: 0 RPM (min = 0 RPM, div = 2)
fan2: 0 RPM (min = 0 RPM, div = 2)
fan3: 0 RPM (min = 5720 RPM, div = 2) ALARM
temp1: -15C (high = -1C, hyst = -1C) sensor = thermistor
temp2: -17.0C (high = +80C, hyst = +75C) sensor = thermistor
temp3: -16.5C (high = +80C, hyst = +75C) sensor = thermistor
vid: +0.000 V (VRM Version 2.4)
alarms:
beep_enable:
Sound alarm enabled


Aqualung,

My CPU core temps comes from k8temp module. Not sure you have the module loaded.
Mine looks like this:
----------------------------------
k8temp-pci-00c3
Adapter: PCI adapter
Algorithm: PCI algorithm
Core0 Temp:
+27C
Core1 Temp:
+33C
----------------------------------

As for the temp3, according to lm-sensors documentation, most of the time the temp3 sensor is disconnected but thats depend on your motherboard. If you dont need it, well just disable it from /etc/sensors.conf file.

http://www.lm-sensors.org/wiki/iwizard/WrongTemps
http://www.lm-sensors.org/browser/lm-sensors/trunk/doc/chips/SUMMARY

You can find lots more info from the site and also the sensors.conf file

I hope this helps.

Gossie
June 27th, 2007, 09:18 AM
Hi,

Would somebody please look at my temperatures?


My mobo is a Asus A8N-E, and I have the "Q-fan control" in the Bios enabled (called "Cool 'n' Quiet").
I use Feisty Fawn. My CPU is a AMD Athlon64 3800+ . There is one big noisy fan in the back, and according to the BIOS I have a CPU fan (going around 3000 rpm) and a thing called chip fan (going around 5000 rpm). So fan1 must be the CPU fan and I apparantly have a chip fan. But the BIOS also mentions a CHA1, chassis fan, going at 0 rpm - so even the bios doesn't 'hear' this propeller.

Also, is 127 something to worry about?

In de sensors.conf file, I tried putting the sensors in 'diode' (as suggested on http://www.lm-sensors.org/wiki/iwizard/WrongTemps). But that gave the same results. Furthermore, I didn't want to change the formulas in the sensors.conf, because I don't know much about hardware.

Here's my output from 'sensors' and also I give the contents of my /etc/modules

Thanks for helping!
Gossie




k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:
+37C

it8712-isa-0290
Adapter: ISA adapter
VCore 1: +1.33 V (min = +0.00 V, max = +3.82 V)
VCore 2: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
+3.3V: +3.30 V (min = +0.00 V, max = +4.08 V)
+5V: +4.84 V (min = +0.00 V, max = +6.85 V)
+12V: +11.84 V (min = +0.00 V, max = +16.32 V)
-12V: -5.15 V (min = -27.36 V, max = +3.93 V)
-5V: -13.64 V (min = -13.64 V, max = +4.03 V) ALARM
Stdby: +4.81 V (min = +0.00 V, max = +6.85 V)
VBat: +3.07 V
fan1: 1250 RPM (min = 811 RPM, div = 8)
fan2: 0 RPM (min = 0 RPM, div = 8)
fan3: 5443 RPM (min = 0 RPM, div = 8)
M/B Temp: +36C (low = -1C, high = +127C) sensor = thermistor
CPU Temp: +28C (low = -1C, high = +127C) sensor = thermistor
Temp3: +27C (low = -1C, high = +127C) sensor = thermistor
vid: +0.875 V




# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.


lp


# Generated by sensors-detect on Wed Jun 27 09:13:10 2007 (put them in reverse order as suggested in HOWTO on Ubuntuforums
# Chip drivers
it87
k8temp
eeprom
# I2C adapter drivers
i2c-nforce2


Finally, this might be something edgy


nijlpaard@haai:~$ sudo modprobe i2c-sensors
FATAL: Module i2c_sensors not found.


PS: With Q-fan control (from the mobo bios), the fan1 speed decreases to 900 - 1000 rpm, but I get a bios warning at boot.

libos
June 27th, 2007, 03:42 PM
Hi Gossie,

I guess your fan3 is probably your chasis fan. If you have enable the Q-fan control for chasis fans (there are 2 types of Q-fan control for my MOBO - M2N-E which is the CPU and the MOBO), there is 3 Q-fan control profiles to choose from. Silent,Optimum and Performance. Silent will give you the lowest fan speed possible; optimum will try to balance your temperature and fan speed; and at last the performance profile will give you highest fan speed possible. So check out your bios settings. I am just sharing base on my MOBO.

I got the same issue as your where your MOBO complains about your low CPU fan speed. There are 2 ways (at least what i have found, and any suggestions would be appreciated) to workaround this, first is to disable the alarm and second is to disable the quick boot setting.

Hope this helps.

Gossie
June 27th, 2007, 09:04 PM
Hi Libos,

Thanks for your advise! After I tried all the things I will mention next, my most important question is, off course, is anybody frightened by my 127? (See my post, two steps above.)
Would it be wise to uninstall lm-sensors, delete the modules in /etc/modules/ and reset the BIOS settings to default?

I had the idea that I was going to use fancontrol, and I found the HOWTO by 'remmelt': http://ubuntuforums.org/showthread.php?t=42737. But, allas, when I want to try the fans with pwmconfig, there is no complete result.

On http://www.almico.com/forumvotes.php?id=6608177 (as kindly suggested when running pwmconfig) I read that a lot of people with an Asus A8N-E Motherboard cannot control the fans exept the CPU fan. There is one post that says: "Got it to work on CPU fan by setting PWM1 mode to Software controlled under the Advanced tab." But that option is not in my BIOS (maybe it needs an upgrade...). I disabled "Cool 'n' Quiet". Still, pwmconfig is not working properly (same as with cool&quiet enabled).

Like you suggested, Libos, :popcorn:, I switched off the CHA1 (chassis fan) warning AND I disabled Quick boot. Then the CPU fan is sometimes going easier: 1100 rpm.
But the chassis fan is still constant at 5400 rpm. In the BIOS, it says CHA1 is 0 rpm but lm-sensors says fan3 is 5400. And I still had the pwmconfig problems...

When I disable "Q-fan control", I just get "There are no pwm-capable sensor modules installed".
"Cool 'n' Quiet" disabled or enabled had no effect on pwm-config, with "Q fan controller" on or off. With Q-fan control enabled, I get the results underneath.

Thanks,
Gossie



~$ sudo pwmconfig
Password:
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

Found the following PWM controls:
9191-0290/pwm1
9191-0290/pwm2
9191-0290/pwm3

Found the following fan sensors:
9191-0290/fan1_input current speed: 1562 RPM
9191-0290/fan2_input current speed: 0 ... skipping!
9191-0290/fan3_input current speed: 5443 RPM

Warning!!! This program will stop your fans, one at a time,
for approximately 5 seconds each!!!
This may cause your processor temperature to rise!!!
If you do not want to do this hit control-C now!!!
Hit return to continue:

Testing pwm control 9191-0290/pwm1 ...
9191-0290/fan1_input ... speed was 1562 now 0
It appears that fan 9191-0290/fan1_input
is controlled by pwm 9191-0290/pwm1
Would you like to generate a detailed correlation (y)? y
PWM 255 FAN 3183
PWM 240 FAN 3125
PWM 225 FAN 2860
PWM 210 FAN 2678
PWM 195 FAN 2481
PWM 180 FAN 2280
PWM 165 FAN 2057
PWM 150 FAN 1854
PWM 135 FAN 1622
PWM 120 FAN 1406
PWM 105 FAN 1155
PWM 90 FAN 942
PWM 75 FAN 680
PWM 60 FAN 0
Fan Stopped at PWM = 60

9191-0290/fan3_input ... speed was 5443 now 5273
no correlation

Testing pwm control 9191-0290/pwm2 ...
9191-0290/fan1_input ... speed was 1562 now 3245
no correlation
9191-0290/fan3_input ... speed was 5443 now 5443
no correlation

No correlations were detected.
There is either no fan connected to the output of 9191-0290/pwm2,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)

Did you see/hear a fan stopping during the above test (n)? y

Testing pwm control 9191-0290/pwm3 ...
9191-0290/fan1_input ... speed was 1562 now 3245
no correlation
9191-0290/fan3_input ... speed was 5443 now 5273
no correlation

No correlations were detected.
There is either no fan connected to the output of 9191-0290/pwm3,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php)

Did you see/hear a fan stopping during the above test (n)? n

Testing is complete.
Please verify that all fans have returned to their normal speed.

The fancontrol script can automatically respond to temperature changes
of your system by changing fanspeeds.
Do you want to set up its configuration file now (y)? y
What should be the path to your fancontrol config file (/etc/fancontrol)? y
Loading configuration from /etc/fancontrol ...

Select fan output to configure, or other action:
1) 9191-0290/pwm2 3) Change INTERVAL 5) Save and quit
2) 9191-0290/pwm1 4) Just quit 6) Show configuration
select (1-n): 6

Common Settings:
INTERVAL=10

Settings of 9191-0290/pwm2:
Depends on
Controls 9191-0290/fan1_input
MINTEMP=
MAXTEMP=
MINSTART=
MINSTOP=

Settings of 9191-0290/pwm1:
Depends on
Controls 9191-0290/fan1_input
MINTEMP=
MAXTEMP=
MINSTART=
MINSTOP=

select (1-n): 3

Current interval is 10 seconds.
Enter the interval at which fancontrol should update PWM values (in s):5
select (1-n): 2

Current temperature readings are as follows:
9191-0290/temp1_input 38
9191-0290/temp2_input 30
9191-0290/temp3_input 27

Select a temperature sensor as source for 9191-0290/pwm1:
1) 9191-0290/temp1_input
2) 9191-0290/temp2_input
3) 9191-0290/temp3_input
4) None (Do not affect this PWM output)
select (1-n): 4
select (1-n): 4

~$



This is what my BIOS says about the settings, rpm's and temparatures. These settings give the same output for the sensors as I posted earlier today.


Cool 'n' Quiet enabled
Q fan controller enabled
Quick boot disabled

CPU Temperature 38 C
M/B Temperature 30 C

CPU Fan Speed 3183 RPM
CHA1 Fan Speed 0 RPM
Chip Fan Speed 5192 RPM

CPU Target Temperature 72 C

CPU Fan Speed warning 800 RPM
CHA1 Fan Speed warning Disabled
CHIP Fan Speed warning Enabled

asmweb
June 29th, 2007, 11:51 AM
Hi there,

well i'm still suffering with the lm-sensors, I did followthis guide (https://help.ubuntu.com/community/SensorInstallHowto). It did go ahead all ok and here is what my /etc/module file is

# Generated by sensors-detect on Fri Jun 29 11:41:21 2007
# 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

after that I did
modprobe i2c-i801
modprobe eeprom

and my modprobe -L conferms that...

did the reboot too but still when I type sensors I get this:

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

How come?

I got an Dell Latitude D620 computer...

any help would be appreciated

Gossie
June 29th, 2007, 02:35 PM
(there are 2 types of Q-fan control for my MOBO - M2N-E which is the CPU and the MOBO), there is 3 Q-fan control profiles to choose from. Silent,Optimum and Performance.


Hi Libos,

There is only one choise in my BIOS: Q fan controller enabled or disabled. I cannot control the Chassis fan, and a lot of other people who have the same mobo, Asus A8N-E, have the same problem.

In your blog (http://bsling.blogspot.com/2007/06/hardware-health-monitoring-on-asus-m2n.html) I saw you have also 127 degrees Celcius as high temp, according to your 'sensors' (lm-sensors) ouput. And then you have read some specifications about your hardware and then you changed the min. and max. temperature. Cool.

Do you get your chassis fan under control with pwmconfig? Did you install fancontrol?

Bye,
Gossie

libos
July 1st, 2007, 10:50 AM
Hi Gossie,

The +127C is probably the high limit for the lm-sensors monitoring. Probably can be set in the sensors.conf but i am not so sure. I am using the sensors applet to monitor my temperatures.

I have just setup the pwmconfig and it works like charm :)
http://bsling.blogspot.com/2007/06/fancontrol.html

Rich1386
July 20th, 2007, 02:39 AM
I tried following the instructions, but on the reboot, grub selected ubuntu fine, but the screen went dead. I tried undoing as much of the stuff as I could, including uninstalling lm-sensors, but nothing. In recovery mode, I used to get some message about sensors failing while booting. Don't get it after I tried fixing it.

adub
July 25th, 2007, 05:45 PM
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.


I got to sensors-detect and answered yes to all the questions and i get the following output at the end.

i tried going to the websites but they require a password

adub
July 25th, 2007, 07:23 PM
I have the below motherboard

MSI P6N SLI Platinum motherboard with the NVIDIA nForce 850i chipset

I had seen mention that others were having difficulty with this particular board in getting lm-sensors to work

I am still working on this but i feel I am on the right path


I2C/SMBUS BUS DRIVERS - STATUS
nVidia MCP51, MCP55 yes i2c-nforce2 2.10.1 2.6.18

SENSOR CHIP DRIVERS - STATUS
Fintek F71882FG/F71883FG yes

according to the above the device list indicates for my motherboard lm-sensors has been working since 2.10.1 with kernel version 2.6.18. for the sensor chip drivers i heard that someone has this working with this motherboard, but they did not post a howto. I had seen browsing the web.

my problem is i can not find the driver to download to install anywhere. I also am thinking i need to update my kernel to have the i2c-nforce2 support.

# uname -a
Linux adub-desktop 2.6.17-12-generic #2 SMP Mon Jul 16 19:37:58 UTC 2007 i686 GNU/Linux

it appears i need to update kernel for i2c-nforce2 support for my particular bus drivers "i think"
although lspci list them but i think for them to work with lmsensors then maybe the update is needed

now on the fintek driver i have no clue rebuild kernel 100% clueless

gtstephenson
July 30th, 2007, 04:14 AM
I did just fine till I had to plug the sensors in.

Any suggestions?

Tom S.

root@Toms_Laptop:/etc# modprobe i2c-sensor
FATAL: Module i2c_sensor not found.

mr4thjuly
August 8th, 2007, 06:17 PM
This is an excellent How to. I just wanted to ask which one is the Harddrive temperature. I know that I have a hard drive temperature sensor but I don't see and output for it, or maybe one of them is the Hard drive temperature but I just don't know it yet.
Thanks in advance.

Pathfinder_
August 18th, 2007, 03:54 PM
lm-senors worked flawlessly on my desktop now when I try to get them working on my laptop(dell latitude c640) i get the following:


# 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...
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): 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 0x0e01
Trying family `National Semiconductor'... No
Trying family `SMSC'... Yes
Found unknown chip with ID 0x0e01
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.


Can anyone help me get this working on my laptop?

nauj27
August 29th, 2007, 11:24 PM
I have a dell inspiron 8600. All i get when i try to use lm sensors is it says no sensors detected. Can someone tell me what driver i am supposed to use so i can get this to work correctly?

Install i8kutils and sensors-applet. Make sure to load i8k kernel module and you are ready.

leona
August 30th, 2007, 12:51 AM
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?
nterestingly upgrading to 7.04 Fiesty Fixed this problem for me, I now have Temps and Fans, yippy! v-happy now.

Psykedelic
October 18th, 2007, 11:26 AM
Hi!
I have some problems with ls-sensors...
I have the P4B motherboard, so the SMBus is hidden and therefore lm-sensors-detect can't find anything...

I've read about the patch for 2.4-kernels, but i'm running 2.6.
I don't know if I understood this matter correctly, but is it so that I have to edit and recompile the kernel with the quirks.c part changed?
I'm an absolute beginner with linux, so I will not attempt to do this...

My second quesition is if anybody knows if there will be support for the P4B motherboard in upcoming kernels?

Yes
October 24th, 2007, 08:49 PM
They work fine for me, but how would I find the sensors for the CPU temp? So that it would just display the CPU temp, and nothing else?

Icarosaurus
October 27th, 2007, 01:32 AM
Try hardware sensors monitor applet in the desktop panel.
You can install it from synaptic if you don't find it in "add to panel" applets.

PurposeOfReason
October 27th, 2007, 09:20 PM
Which one is more accurate for my CPU? I have a core 0, core 1, and CPU Temp. I like that last because it is lowest. :)



shawn@Reasons:~$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +40C (high = +100C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +36C (high = +100C)

w83627dhg-isa-0290
Adapter: ISA adapter
VCore: +1.16 V (min = +0.00 V, max = +1.74 V)
in1: +12.46 V (min = +1.69 V, max = +0.53 V) ALARM
AVCC: +3.22 V (min = +1.58 V, max = +0.26 V) ALARM
3VCC: +3.20 V (min = +0.64 V, max = +2.05 V) ALARM
in4: +0.74 V (min = +0.26 V, max = +0.89 V)
in5: +1.62 V (min = +0.59 V, max = +0.51 V) ALARM
in6: +2.20 V (min = +2.05 V, max = +4.22 V)
VSB: +3.22 V (min = +2.72 V, max = +2.19 V) ALARM
VBAT: +2.05 V (min = +1.54 V, max = +0.51 V) ALARM
Case Fan: 2445 RPM (min = 3879 RPM, div = 4) ALARM
CPU Fan: 0 RPM (min = 458 RPM, div = 128) ALARM
Aux Fan: 0 RPM (min = 3515 RPM, div = 128) ALARM
fan4: 0 RPM (min = 10546 RPM, div = 128) ALARM
fan5: 0 RPM (min = 10546 RPM, div = 128) ALARM
Sys Temp: +31C (high = +33C, hyst = +0C) ALARM
CPU Temp: +33.0C (high = +80.0C, hyst = +75.0C)
AUX Temp: +124.5C (high = +80.0C, hyst = +75.0C) ALARM

shawn@Reasons:~$


All that fans (minus one) are at 0 because I use a fan controller.

Sonic Reducer
October 28th, 2007, 05:34 AM
$acpitemp always says 32F in conky, what is the name of my CPU sensor?

heres my output of sensors

ryan@ryan-desktop:~$ sensors
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:
+31C

w83627ehf-isa-0290
Adapter: ISA adapter
VCore: +1.17 V (min = +0.00 V, max = +1.74 V)
in1: +12.20 V (min = +4.49 V, max = +1.69 V) ALARM
AVCC: +3.22 V (min = +0.02 V, max = +2.66 V) ALARM
3VCC: +3.22 V (min = +2.51 V, max = +0.46 V) ALARM
in4: +2.04 V (min = +1.13 V, max = +1.90 V) ALARM
in5: +1.61 V (min = +0.02 V, max = +0.16 V) ALARM
in6: +5.17 V (min = +1.00 V, max = +0.18 V) ALARM
VSB: +3.22 V (min = +2.83 V, max = +0.26 V) ALARM
VBAT: +0.66 V (min = +3.78 V, max = +0.18 V) ALARM
in9: +1.54 V (min = +0.14 V, max = +0.06 V) ALARM
Case Fan: 0 RPM (min = 263 RPM, div = 128) ALARM
CPU Fan: 0 RPM (min = 76 RPM, div = 128) ALARM
Aux Fan: 2327 RPM (min = 2636 RPM, div = 4) ALARM
fan5: 0 RPM (min = 24107 RPM, div = 8) ALARM
Sys Temp: +30C (high = -111C, hyst = -124C) ALARM
CPU Temp: +25.5C (high = +80.0C, hyst = +75.0C)
AUX Temp: +25.5C (high = +80.0C, hyst = +75.0C)

i thought it would be k8temp but that does not work, what am i doing wrong here?

ahunor
November 7th, 2007, 11:59 AM
Hi there

Getting lm-sensors to work has never meant tourble, but now, as I'm on my Toshiba A200-14D laptop, it's driving me crazy...I can get readings only from the CPU.

sensors-detect says that I only need two modules, one for the cpu ( which is ok ), and 'smartbatt'...which would take care of the battery ( and, as sensors-detect says my nvidia GPU too ? ).

In the nvidia control panel I can see the temp of my card...nowhere else.

The Question : Where, in the kernel source could I find the smartbatt hw sensor support setting ?

thanks.

moving fusion
November 21st, 2007, 09:54 PM
Hi,

This is a post about w83627dhg (w83627ehf).

I have got it working on 7.10 kernel 2.6.23 (no support in kubuntu stock kernel so i thought might as well get the latest) http://www.howtoforge.com/kernel_compilation_ubuntu.

I was also using the version of lm-sensors via apt-get this didn't work even though sensors-detect etc was detecting the hardware.

I have just installed lm_sensors-3.0.0-rc3 with some issues with deps but sorted out easily enough.

I have a ASUS Maximus Formula mobo with Q6600:

~$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +37.0C (crit = +100.0C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +36.0C (crit = +100.0C)

coretemp-isa-0002
Adapter: ISA adapter
Core 2: +34.0C (crit = +100.0C)

coretemp-isa-0003
Adapter: ISA adapter
Core 3: +34.0C (crit = +100.0C)

w83627dhg-isa-0290
Adapter: ISA adapter
VCore: +1.32 V (min = +0.00 V, max = +1.74 V)
in1: +11.35 V (min = +0.84 V, max = +4.70 V) ALARM
AVCC: +3.18 V (min = +0.34 V, max = +2.21 V) ALARM
3VCC: +3.18 V (min = +1.23 V, max = +1.04 V) ALARM
in4: +1.53 V (min = +1.02 V, max = +0.29 V) ALARM
in5: +1.76 V (min = +0.02 V, max = +0.38 V) ALARM
in6: +5.02 V (min = +5.15 V, max = +1.66 V) ALARM
VSB: +3.18 V (min = +2.05 V, max = +2.30 V) ALARM
VBAT: +3.18 V (min = +2.34 V, max = +2.05 V) ALARM
Case Fan: 0 RPM (min = 319 RPM, div = 128) ALARM
CPU Fan: 2789 RPM (min = 2986 RPM, div = 2) ALARM
Aux Fan: 1917 RPM (min = 216 RPM, div = 32)
fan5: 2109 RPM (min = 180 RPM, div = 32)
Sys Temp: +30.0C (high = +97.0C, hyst = +0.0C) sensor = thermistor
CPU Temp: +28.0C (high = +80.0C, hyst = +75.0C) sensor = diode
AUX Temp: +7.5C (high = +80.0C, hyst = +75.0C) sensor = thermistor

if anyone needs more info i will be happy to help.

jludeman
December 2nd, 2007, 12:54 AM
Thanks for the how to. Worked great on my system.

A little off topic but how do I get this info onto the destop. I searched the forums and this thread for how to show this in conky. No luck. The conky man page does not help either.

Is there another desktop app that will show the cpu temp?

Or do I just have to type sensors in a terminal once in a while?

jludeman
December 2nd, 2007, 06:15 PM
Never mind. I gave up on conky altogether. I'm now using Gkrellm which works fine with lm sensors and is easy to set up.

thealmightyone
December 4th, 2007, 02:00 PM
A slight problem with lm-sensors.

When I run sensors-detect, I am told no sensors were detected. I am hoping that I did not install lm-sensors correctly, or this script didn't run correctly, rather than my motherboard is not supported.

Should I get this output when I run the script:


andy@andy-laptop:~$ sudo ./mkdev.sh
/dev/i2c-0
mknod: `/dev/i2c-0': File exists

MortenE
December 6th, 2007, 01:44 PM
I only get this output:


coretemp-isa-0000
Adapter: ISA adapter
Core 0: +32C (high = +100C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +35C (high = +100C)

In windows I get readings of fan, gpu temp, chip temp and hard drive temp aswell.. What could be the problem? I have a Dell XPS M1330.

glsli
December 7th, 2007, 11:02 PM
that first post of November 2004 is still updated and valid?

I don't want to engage myself in something outdated, just to discover after endelssly errors that that howto was quite old!

I'm on Ubuntu 7.10...

thank you!

Rafa.Supr
December 10th, 2007, 01:36 PM
I only had to install lm-sensors with synaptic, after that run the command sensors-detect and a reboot. It worked like a charm!

Gourgi
December 11th, 2007, 11:16 AM
I only had to install lm-sensors with synaptic, after that run the command sensors-detect and a reboot. It worked like a charm!
i tried that and k8temp loaded but the other module it didnl't
so i followed the guide and everthing seems ok now (w83627hf module loaded fine :) )
so the guide is valid for me
time to reboot know!

OffHand
December 12th, 2007, 12:03 PM
that first post of November 2004 is still updated and valid?

I don't want to engage myself in something outdated, just to discover after endelssly errors that that howto was quite old!

I'm on Ubuntu 7.10...

thank you!

Still works...

tmcmulli
December 13th, 2007, 10:49 PM
Not sure if anyone answered you... try the i2c variable... (${i2c tempf 2})

That should get you your CPU...


$acpitemp always says 32F in conky, what is the name of my CPU sensor?

heres my output of sensors

ryan@ryan-desktop:~$ sensors
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:
+31C

w83627ehf-isa-0290
Adapter: ISA adapter
VCore: +1.17 V (min = +0.00 V, max = +1.74 V)
in1: +12.20 V (min = +4.49 V, max = +1.69 V) ALARM
AVCC: +3.22 V (min = +0.02 V, max = +2.66 V) ALARM
3VCC: +3.22 V (min = +2.51 V, max = +0.46 V) ALARM
in4: +2.04 V (min = +1.13 V, max = +1.90 V) ALARM
in5: +1.61 V (min = +0.02 V, max = +0.16 V) ALARM
in6: +5.17 V (min = +1.00 V, max = +0.18 V) ALARM
VSB: +3.22 V (min = +2.83 V, max = +0.26 V) ALARM
VBAT: +0.66 V (min = +3.78 V, max = +0.18 V) ALARM
in9: +1.54 V (min = +0.14 V, max = +0.06 V) ALARM
Case Fan: 0 RPM (min = 263 RPM, div = 128) ALARM
CPU Fan: 0 RPM (min = 76 RPM, div = 128) ALARM
Aux Fan: 2327 RPM (min = 2636 RPM, div = 4) ALARM
fan5: 0 RPM (min = 24107 RPM, div = 8) ALARM
Sys Temp: +30C (high = -111C, hyst = -124C) ALARM
CPU Temp: +25.5C (high = +80.0C, hyst = +75.0C)
AUX Temp: +25.5C (high = +80.0C, hyst = +75.0C)

i thought it would be k8temp but that does not work, what am i doing wrong here?

DirtDart
December 30th, 2007, 03:24 PM
Guide still works like a charm!

To be honest, I didn't realize that the 1st post was 3+ years old until AFTER I followed it (nice attention to detail, huh?), but it worked without any problems.


Thanks again for posting this guide.

mysticmatrix
January 1st, 2008, 08:20 PM
Worked for me in Gutsy...
But my Intel DG965RY reported sensors only for the CPU temp... Hmnn that's odd :confused:

mackid
January 5th, 2008, 08:52 AM
Hi,

The guide worked for me, but I don't know which temperatures are my CPU! I have an Athlon 64 X2 4000, socket AM2, and an MSI motherboard.

I'm running Ubuntu 7.10:

$ uname -a
Linux hostname 2.6.22-14-generic #1 SMP Tue Dec 18 05:28:27 UTC 2007 x86_64 GNU/Linux

Here's the output from sensors:


$ sensors
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:
+34C
Core0 Temp:
+23C
Core1 Temp:
+28C
Core1 Temp:
+25C

w83627ehf-isa-0290
Adapter: ISA adapter
VCore: +1.30 V (min = +0.00 V, max = +1.74 V)
in1: +12.51 V (min = +13.46 V, max = +11.77 V) ALARM
AVCC: +3.30 V (min = +3.12 V, max = +2.61 V) ALARM
3VCC: +3.30 V (min = +4.08 V, max = +4.03 V) ALARM
in4: +2.04 V (min = +0.98 V, max = +1.98 V) ALARM
in5: +1.61 V (min = +1.53 V, max = +1.35 V) ALARM
in6: +5.09 V (min = +6.07 V, max = +4.48 V) ALARM
VSB: +3.30 V (min = +3.82 V, max = +3.04 V) ALARM
VBAT: +3.22 V (min = +1.57 V, max = +1.92 V) ALARM
in9: +1.61 V (min = +1.94 V, max = +1.34 V) ALARM
Case Fan: 0 RPM (min = 0 RPM, div = 128)
CPU Fan: 1730 RPM (min = 5532 RPM, div = 4) ALARM
Aux Fan: 0 RPM (min = 3515 RPM, div = 128) ALARM
fan5: 0 RPM (min = 0 RPM, div = 128)
Sys Temp: +33C (high = -71C, hyst = +122C)
CPU Temp: +49.0C (high = +100.0C, hyst = +95.0C)
AUX Temp: +51.0C (high = +100.0C, hyst = +95.0C)

The core temps seem a lot lower than the CPU Temp, and the temps for the same core differ by a lot as well (34C and 23C, same core!?) Which is correct? Could someone inform me? Thanks a lot.

dcstar
January 6th, 2008, 03:30 AM
Hi,

The guide worked for me, but I don't know which temperatures are my CPU! I have an Athlon 64 X2 4000, socket AM2, and an MSI motherboard.
........
Here's the output from sensors:


$ sensors
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:
+34C
Core0 Temp:
+23C
Core1 Temp:
+28C
Core1 Temp:
+25C
.........

The core temps seem a lot lower than the CPU Temp, and the temps for the same core differ by a lot as well (34C and 23C, same core!?) Which is correct? Could someone inform me? Thanks a lot.

I have just installed the same CPU on an Asus MB (replacing a Sempron 3400 which seemed to report temps ok) and have similar weird core temps.

Doing a web search seems to show this as a known problem, and it may be fixed in the new lm-sensors 3.0 package - we will just have to wait for the Ubuntu/Debian developers to start using this new package.

Epic Plecostomus
January 9th, 2008, 02:18 PM
Got my sensors up and running... what choices do i have as far as graphical output for Im-sensors? Xsensor is nice but I would prefer somthing I can minimze to a bar and set my own alarm bands for.

dcstar
January 10th, 2008, 09:27 AM
I have just installed the same CPU on an Asus MB (replacing a Sempron 3400 which seemed to report temps ok) and have similar weird core temps.

Doing a web search seems to show this as a known problem, and it may be fixed in the new lm-sensors 3.0 package - we will just have to wait for the Ubuntu/Debian developers to start using this new package.

I have just done some more research and found that the "Brisbane" core AMD X2 CPUs have a known problem with the accuracy of the temperature diodes (as reported by k8temp). These are the later 65W CPUs, the earlier 89W versions apparently report ok.

It looks like those of us with the Brisbane core CPUs will have to disregard the k8temp data, and find alternative reporting (from the motherboard).

SanskritFritz
January 29th, 2008, 10:16 PM
Howto Install and Configure lm-sensors
Thank you emperor it worked out of the box! Great how-to!

a-converted-sparky
January 30th, 2008, 09:15 PM
Hi peeps (i am a newbie)

I have got to stage 3. and ran
sudo sensors-detect

i have copied the output:

# Chip drivers
coretemp

but i do not have a directory/file for
/etc/modules

the insturction says to "To make the sensors modules behave correctly, add these lines to /etc/modules" ...

any ideas?

I can do the next part:Then, run /etc/init.d/module-init-tools - thats fine

Nikos.Alexandris
January 31st, 2008, 07:27 PM
I have a Samsung R20, Intel dual core duo 2 GHz.. but no luck with fancontrol. I get information only about temperature... which is really high always and the "coolers" run like crazy non-stop!

Anything I miss?

$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +69C (high = +100C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +69C (high = +100C)

Vadi
January 31st, 2008, 07:28 PM
I found the Hardinfo (http://getdeb.net/search.php?keywords=hardinfo) program to be a lot more useful. Provides the sensors data plus a ton of more things about your comp, all in one nice program.

Bruce M.
March 1st, 2008, 06:13 PM
Howto Install and Configure lm-sensors

Since there is no "Thank You" button here:


Thank You
for this post/thread

DasCrushinator
March 1st, 2008, 07:08 PM
Since there is no "Thank You" button here:


Thank You
for this post/thread

Button next to Quote button.

Bruce M.
March 1st, 2008, 07:22 PM
Button next to Quote button.

I know, but it doesn't show up until Post #227 on Page 23 in this thread.

There isn't one on Post #1 to thank emperor for the original HowTo.

So: :guitar: "I diiiiid iiiiiT .... myyyyyy wayyyyyy" :guitar:

DasCrushinator
March 1st, 2008, 07:44 PM
I know, but it doesn't show up until Post #227 on Page 23 in this thread.

There isn't one on Post #1 to thank emperor for the original HowTo.

So: :guitar: "I diiiiid iiiiiT .... myyyyyy wayyyyyy" :guitar:

lol

Didn't even check until just now, sorry :)

Bruce M.
March 1st, 2008, 08:22 PM
lol

Didn't even check until just now, sorry :)

No need to be.
Besides a "personal" Thank You is always nicer. It means that someone took the time to type it in.

Miroku
March 2nd, 2008, 12:51 AM
so i got to this stage after sensors-detect:


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

#----cut here----
# I2C adapter drivers
# modprobe unknown adapter NVIDIA i2c adapter
# modprobe unknown adapter NVIDIA i2c adapter
# modprobe unknown adapter NVIDIA i2c adapter
# Chip drivers
# 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
it87
coretemp
#----cut here----


Do you want to add these lines to /etc/modules automatically? (yes/NO)

i chose NO and now i need some further clarification please. thx.

bulldog
March 2nd, 2008, 05:36 PM
Better choose Yes instead,or add the lines manually.

andymadonna
March 16th, 2008, 09:29 PM
Hi I have a Sony Vaio and the fans used to be controlled in windows so that they would slow down after startup. I was able to get the sensors and fans detected, but how do I slow down the fans? Or get them controlled depending on temperature. This is just a kitchen computer for internet surfing, so it probably doesn't need the fans to ever run this high. But right now its just so loud.



michelle@michelle-desktop:~$ sensors
w83627hf-isa-0290
Adapter: ISA adapter
VCore 1: +1.71 V (min = +1.65 V, max = +2.05 V)
VCore 2: +0.00 V (min = +1.65 V, max = +2.05 V) ALARM
+3.3V: +3.26 V (min = +2.82 V, max = +3.79 V)
+5V: +5.11 V (min = +5.83 V, max = +6.32 V) ALARM
+12V: +11.73 V (min = +10.64 V, max = +7.54 V) ALARM
-12V: -12.03 V (min = +0.72 V, max = -4.88 V) ALARM
-5V: +3.54 V (min = +4.90 V, max = +4.50 V) ALARM
V5SB: +5.54 V (min = +5.56 V, max = +5.97 V) ALARM
VBat: +3.87 V (min = +3.01 V, max = +4.03 V)
fan1: 3835 RPM (min = 2947 RPM, div = 2)
fan2: 1985 RPM (min = 3708 RPM, div = 4) ALARM
fan3: 0 RPM (min = 0 RPM, div = 2)
temp1: -48C (high = -69C, hyst = -11C) sensor = thermistor
temp2: +46.5C (high = +80C, hyst = +75C) sensor = diode
temp3: +41.0C (high = +80C, hyst = +75C) sensor = thermistor
vid: +1.750 V (VRM Version 9.0)
alarms:
beep_enable:
Sound alarm enabled



Any help thanks!

libos
March 17th, 2008, 02:51 AM
Hi andymadonna,

I wrote these in my blog to remind me of how i configure my fancontrol with the lmsensors. I hope this could help you with it.

http://bsling.blogspot.com/search?q=fan+control

Kiri
March 27th, 2008, 09:15 AM
Only a couple of sensors seems to have got detected:

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

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +67.0C (crit = +100.0C)



Shouldnt I have more?

Jugix
April 9th, 2008, 09:34 AM
Nice HOWTO! Now I can seriously overclock my CPU with linux because I know core temps now. TY! :popcorn:

w83627dhg-isa-0290
Adapter: ISA adapter
VCore: +1.34 V (min = +0.00 V, max = +1.74 V)
in1: +6.07 V (min = +8.98 V, max = +8.40 V) ALARM
AVCC: +3.25 V (min = +3.55 V, max = +1.10 V) ALARM
3VCC: +3.25 V (min = +2.86 V, max = +0.27 V) ALARM
in4: +1.24 V (min = +1.87 V, max = +0.58 V) ALARM
in5: +1.34 V (min = +1.38 V, max = +1.54 V) ALARM
in6: +5.02 V (min = +2.87 V, max = +0.15 V) ALARM
VSB: +3.22 V (min = +2.59 V, max = +2.13 V) ALARM
VBAT: +3.18 V (min = +2.32 V, max = +2.40 V) ALARM
Case Fan: 0 RPM (min = 340 RPM, div = 128) ALARM
CPU Fan: 2721 RPM (min = 332 RPM, div = 16)
Aux Fan: 0 RPM (min = 340 RPM, div = 128) ALARM
fan4: 0 RPM (min = 340 RPM, div = 128) ALARM
fan5: 0 RPM (min = 1318 RPM, div = 128) ALARM
Sys Temp: +38.0C (high = +13.0C, hyst = +38.0C) ALARM sensor = thermistor
CPU Temp: +67.0C (high = +80.0C, hyst = +75.0C) sensor = diode
AUX Temp: +54.0C (high = +80.0C, hyst = +75.0C) sensor = thermistor

coretemp-isa-0000
Adapter: ISA adapter
Core 0: +66.0C (crit = +85.0C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +68.0C (crit = +85.0C)
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz
stepping : 13
cpu MHz : 3560.000
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm
bogomips : 7125.21
clflush size : 64

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz
stepping : 13
cpu MHz : 3560.000
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm
bogomips : 7120.44
clflush size : 64
:guitar:

abetterlie
April 13th, 2008, 07:11 AM
great writeup, thanks a million.
up and running and temperature sensoring in minutes.

SR_ELPIRATA
April 20th, 2008, 10:40 PM
WOW, I was wondering why x-sensors wasnt working. Installed lm-sensors easily though steps 3 to 5 were done by the system automatically, which was pretty nice. I did all this because I wanted to get GKrellM working that specific area and it did, but after doing it noticed that I could add these sensors to my panels easily and it looks 'clean', so I dont know, I think Im going to stick with these instead of GKrellM (but Im not going to uninstall them neither).

ELP

slick_nick
May 1st, 2008, 04:38 AM
Seems like it's gotten a lot easier to get sensors up and running since this thread was started; I don't think anyone has given a new how-to so I will. Thanks to the folks in this thread [ http://ubuntuforums.org/showthread.php?t=671015 ] I got it working quickly taking the following steps:

1. Open a terminal and do the ol' sudo apt-get install and install lm-sensors and sensors-applet.
2. After the install, run sudo sensors-detect and say Yes to everything.
3. Restart your computer.
4. Right-click the bar at the top of the screen and select Add to Panel. Find Hardware Sensors Monitor and click Add.


You can also type "sensors" into the terminal and get a readout like this:
slick@maritimus:~$ sensors
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp: +9.0C
Core0 Temp: +0.0C
Core1 Temp: +12.0C
Core1 Temp: +10.0C

it8718-isa-0228
Adapter: ISA adapter
in0: +1.31 V (min = +0.00 V, max = +4.08 V)
in1: +2.10 V (min = +0.00 V, max = +4.08 V)
in2: +3.31 V (min = +0.00 V, max = +4.08 V)
in3: +2.94 V (min = +0.00 V, max = +4.08 V)
in4: +3.02 V (min = +0.00 V, max = +4.08 V)
in5: +3.18 V (min = +0.00 V, max = +4.08 V)
in6: +4.08 V (min = +0.00 V, max = +4.08 V)
in7: +0.00 V (min = +0.00 V, max = +4.08 V)
in8: +3.07 V
fan1: 2710 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan5: 0 RPM (min = 0 RPM)
temp1: +32.0C (low = +127.0C, high = +127.0C) sensor = transistor
temp2: +36.0C (low = +127.0C, high = +70.0C) sensor = thermal diode
temp3: +80.0C (low = +127.0C, high = +127.0C) sensor = transistor
cpu0_vid: +1.550 V


A couple people asked this a while ago in this thread, and didn't get an answer as far as I saw, so I'll ask again: Anyone know what temp3 is?!?

wnelson
May 1st, 2008, 05:09 AM
If you look in /etc/sensors.conf you will find all of the chip set definitions. Most temp3 are ignored. Just browse that file and find out.


k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp: +9.0C
Core0 Temp: +0.0C
Core1 Temp: +12.0C
Core1 Temp: +10.0C

it8718-isa-0228 --------> it8718 is the chip set for you computer
Adapter: ISA adapter
in0: +1.31 V (min = +0.00 V, max = +4.08 V)
in1: +2.10 V (min = +0.00 V, max = +4.08 V)
in2: +3.31 V (min = +0.00 V, max = +4.08 V)
in3: +2.94 V (min = +0.00 V, max = +4.08 V)
in4: +3.02 V (min = +0.00 V, max = +4.08 V)
in5: +3.18 V (min = +0.00 V, max = +4.08 V)
in6: +4.08 V (min = +0.00 V, max = +4.08 V)
in7: +0.00 V (min = +0.00 V, max = +4.08 V)
in8: +3.07 V
fan1: 2710 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan5: 0 RPM (min = 0 RPM)
temp1: +32.0C (low = +127.0C, high = +127.0C) sensor = transistor
temp2: +36.0C (low = +127.0C, high = +70.0C) sensor = thermal diode
temp3: +80.0C (low = +127.0C, high = +127.0C) sensor = transistor
cpu0_vid: +1.550 V

Walt
Tacoma, WA