HOW TO: Install and configure lm-sensors

[deh1963]

Has anyone tried installing the latest version of lm-sensors (3.0.1) from the lm-sensors.org website? I checked in Package Manager and I have version 1:3.0.0-4ubuntu installed.

I ran through sensors-detect and had few signals detected. Makes me wonder if I'm missing something.

[slick_nick]

deh1963, good job noticing that...my sensors seem to be working fine/detecting with the older ubuntu version , but I might go head and try the latest version tomorrow if I get the time :)

[Nameless_one]

Hello. I installed lm-sensors following this howto (actually the updated info from page 24). I am trying to read my graphics card's temperature. My sensors output is this:

$ sensors
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:
+40°C
Core1 Temp:
+40°C

w83627ehf-isa-0290
Adapter: ISA adapter
VCore: +1.42 V (min = +0.00 V, max = +1.74 V)
in1: +9.40 V (min = +10.08 V, max = +6.71 V) ALARM
AVCC: +3.36 V (min = +1.97 V, max = +4.05 V)
3VCC: +3.39 V (min = +0.45 V, max = +4.02 V)
in4: +1.71 V (min = +1.90 V, max = +0.68 V) ALARM
in5: +1.72 V (min = +1.78 V, max = +0.57 V) ALARM
in6: +5.68 V (min = +3.23 V, max = +4.84 V) ALARM
VSB: +3.36 V (min = +3.82 V, max = +2.90 V) ALARM
VBAT: +0.00 V (min = +3.98 V, max = +3.50 V) ALARM
in9: +1.54 V (min = +2.04 V, max = +2.04 V) ALARM
Case Fan: 2250 RPM (min = 2909 RPM, div = 8) ALARM
CPU Fan: 3013 RPM (min = 975 RPM, div = 8)
Aux Fan: 0 RPM (min = 1506 RPM, div = 128) ALARM
fan5: 0 RPM (min = 0 RPM, div = 128)
Sys Temp: +31°C (high = +47°C, hyst = -1°C)
CPU Temp: +39.0°C (high = +80.0°C, hyst = +75.0°C)
AUX Temp: +39.0°C (high = +80.0°C, hyst = +75.0°C)


Does anyone know whether any of these metrics corresponds to my GPU?

[dtrapp]

This is also a noob question
Can you tell me where the mkdev.sh file is - I installed lm-sensors but cannot find the file.

[Nameless_one]

If you are running gutsy or later, I believe you don't need to run the mkdev.sh script. Check here (https://help.ubuntu.com/community/SensorInstallHowto).

If are running edgy or earlier, I think th idea is to create the mkdev.sh and run it yourself.

[carpman]

Does this guide still apply to Kubuntu Hardy?

If so where is this lm-sources it talks of running script in?

cheers

[Nameless_one]

There is no package lm-sources, if that's what you mean. The original poster means that you should run the mkdev.sh script from the source code of the package lm-sensors, but as of gutsy, that isn't necessary.

Also, if you need to run the script, create it yourself (cut and paste the script from this guide).

[DasCrushinator]

So what is the way to do it for Gutsy/Hardy?

[Nameless_one]

https://help.ubuntu.com/community/SensorInstallHowto

[DasCrushinator]

https://help.ubuntu.com/community/SensorInstallHowto

That still shows using the mkdev.sh script?

[Nameless_one]

I am sorry, I should have probably quoted directly from the bottom of the page:

In Gutsy the process to configure lm-sensors is much simpler. I installed lm-sensors and sensors-applet, ran sudo sensors-detect (and said yes to everything). It asks if I want it to automatically add the modules to /etc/modules, I said yes. Then restart to get the modules (one could do some modprobing, but just restarting is easier) . Then I added the sensor applet to my panel. -- SamTygier

[DasCrushinator]

I am sorry, I should have probably quoted directly from the bottom of the page:

Err, sorry about that. I just saw all the instructions from this post and didn't realize I could get away with just doing that.

Thanks!

[carpman]

I have done this but sensors-detect finds no sensors, which is odd as hardinfo finds two temps plus hard drive temp?

[DasCrushinator]

I have done this but sensors-detect finds no sensors, which is odd as hardinfo finds two temps plus hard drive temp?

What release are you using?

[carpman]

I am using Kubuntu hardy KDE4 remix

[markbuntu]

Hi, I got lm-sensors and it is working fine and found all my sensors and can be seen in my syslog and when I run sensors in the terminal I just have this one small problem:

May 22 17:02:26 mark-desktop sensord: Sensor alarm: Chip dme1737-i2c-0-2e: V5stby: +0.00 V (min = +0.00 V, max = +6.64 V) [ALARM]

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

dme1737-i2c-0-2e
Adapter: SMBus PIIX4 adapter at 0b00
V5stby: +0.00 V (min = +0.00 V, max = +6.64 V) ALARM
Vccp: +1.12 V (min = +0.00 V, max = +2.99 V)
V3.3: +3.34 V (min = +0.00 V, max = +4.38 V)
V5: +5.15 V (min = +0.00 V, max = +6.64 V)
V12: +12.18 V (min = +0.00 V, max = +15.94 V)
V3.3stby: +3.34 V (min = +0.00 V, max = +4.38 V)
Vbat: +3.25 V (min = +0.00 V, max = +4.38 V)
CPU_Fan: 1781 RPM (min = 0 RPM)
Fan2: 1324 RPM (min = 0 RPM)
Fan4: 0 RPM (min = 0 RPM)
RD1 Temp: +38.7°C (low = -127.0°C, high = +85.0°C)
Int Temp: +38.8°C (low = -127.0°C, high = +85.0°C)
CPU Temp: +47.2°C (low = -127.0°C, high = +85.0°C)
cpu0_vid: +1.550 V

Is there anyway to disable this V5stby sensor so I stop getting this message every minute?

Update: OK, I made a change in sensors3.conf according to the instructions and added

ignore in0


which is identified in sensors3.conf as V5stby like this

label in0 "V5stby"


I added it after the chip "dme 1737-*" statement.

sensors3.conf has a very good information and instruction section at the top.
I wish more .conf files were written like that.

I then ran sensors -s as suggested but sensord still reports an alarm on soft boot (ctrl-alt-Backspace) and the syslog reports this every minute.

The sensors applet no longer lists this sensor so the change seems to have worked for that but how can I change the sensord configuration since it appears that my motherboard does not seem to be using this particular sensor. It is an ASUS A8AE-LE motherboard (OEM) used in the HP Pavillion an1330 and others.

OK, fixed that. Hard reboot necessary. Duhhh... it is a hardware type thingy...

RTFM as they say...

I just hope this provides some help for someone.


I have tried this on both amd64 and 386i Hardy on this machine and can confirm that it works for both. No changes are necessary.

[dbn79]

Hello,

I am new to Ubuntu and have been having issues with my Sony PCV-RX550. When running xsensors my fan1 is running at ~4200 RPM - so it is a little loud. I've been working through directions on this page and others and seem to be making some progress, but I can't get the fan to slow down (expect when running pwmconfig correlation).

I've been able to change some of my settings as follows (not sure how useful they are, but at least I've been able to change them):

Settings of hwmon0/device/pwm2:
Depends on
Controls hwmon0/device/fan2_input
MINTEMP=37
MAXTEMP=41
MINSTART=90
MINSTOP=75
MINPWM=75
MAXPWM=80

Settings of hwmon0/device/pwm1:
Depends on hwmon0/device/temp1_input
Controls hwmon0/device/fan1_input
MINTEMP=37
MAXTEMP=41
MINSTART=150
MINSTOP=135
MINPWM=135
MAXPWM=140

When I run 'fancontrol start' I get the following message:
Enabling PWM on fans...
Starting automatic fan control...
/usr/sbin/fancontrol: line 265: ${tsens}: ambiguous redirect
Error reading temperature from /sys/class/hwmon/
Aborting, restoring fans...
Verify fans have returned to full speed

Not sure if this is useful, but when running sensors I get:
w83627hf-isa-0290
Adapter: ISA adapter
VCore 1: +1.71 V (min = +1.65 V, max = +2.05 V)
VCore 2: +0.05 V (min = +1.65 V, max = +2.05 V)
+3.3V: +3.33 V (min = +2.82 V, max = +3.79 V)
+5V: +5.13 V (min = +2.61 V, max = +3.09 V)
+12V: +11.80 V (min = +14.47 V, max = +11.61 V)
-12V: -12.11 V (min = +1.95 V, max = -1.83 V)
-5V: +3.54 V (min = +5.10 V, max = +0.93 V)
V5SB: +5.56 V (min = +5.91 V, max = +5.03 V)
VBat: +1.55 V (min = +1.76 V, max = +0.29 V)
fan1: 4218 RPM (min = 3534 RPM, div = 2)
fan2: 2177 RPM (min = 1584 RPM, div = 4)
fan3: 0 RPM (min = 3082 RPM, div = 2)
temp1: -48.0°C (high = +123.0°C, hyst = -18.0°C) sensor = thermistor
temp2: +38.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
temp3: +37.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
cpu0_vid: +1.750 V
beep_enable:enabled

Any suggestions? Thanks for any help...I'd like to actually run Ubuntu and move away from Windows a bit, but this fan speed is too much!

[rshel]

I really appreciate the ubuntu community for all of its kind efforts to help people. But it is really ridiculous that it takes such canoodling to get something as simple as temp sensors to work. And the only reason I need them to work is because Ubunut 8 is running so hot--despite the pre-release hype about running cooler than ever--that I fear I will fry my computer.

But thanks, again. Anybody recommend a good alternative to Ubuntu?

[wilberfan]

Anybody recommend a good alternative to Ubuntu?

Boy, you're in for it now! ;)

I'm pretty sure there are lot's of threads that discuss alternatives...but..since you asked...

I REALLY like Sidux. It's Debian based, takes less than 6 minutes to install (YMMV), and it's phenomenally easy to keep state-of-the-art (something I really enjoy) with it's "smxi" script. (It's KDE by default, though..if that's an issue for you.)

I don't know if configuring lm-sensors will be any easier (it's been awhile since I did that), but their IRC room is extremely helpful.

I tried a dozen or so distros before I landed on Sidux, and I literally stopped distroshopping when I found it.

But that's the cool thing about *nix--there's' something perfect (or nearly so) for everyone!

:guitar:

[jspiers]

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.0°C
Core0 Temp: +0.0°C
Core1 Temp: +12.0°C
Core1 Temp: +10.0°C

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.0°C (low = +127.0°C, high = +127.0°C) sensor = transistor
temp2: +36.0°C (low = +127.0°C, high = +70.0°C) sensor = thermal diode
temp3: +80.0°C (low = +127.0°C, high = +127.0°C) 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?!?


I asked Gigabyte about the temp readings from my it8718 on my Gigabyte GA-MA78GM-S2H (rev 1.0) and they said temp3 is the reading from the Northbridge. But they gave no details as to how it is wired so as to get a useful calculation of the actual temperature. I'm getting 87 degrees which seems rather crazy. Does anyone have more details about the proper calculation for this sensor?

[Nullack]

On intrepid all I did was:

sudo apt-get install
sudo sensors-detect
Yes to everything
Reboot or load modules
sensors all work

This guide needs updating

[MaPeD]

Hmm... Heres my output and for some reason im getting negative readings on temp1 and sys temp.. and it cant be true unless my box has turned into a freezer

lm78-i2c-1-28
Adapter: SMBus nForce2 adapter at f000
VCore 1: +2.85 V (min = +0.00 V, max = +3.49 V)
VCore 2: +2.98 V (min = +0.26 V, max = +0.51 V) ALARM
+3.3V: +3.25 V (min = +0.00 V, max = +1.02 V) ALARM
+5V: +5.46 V (min = +0.03 V, max = +0.32 V) ALARM
+12V: +10.52 V (min = +0.00 V, max = +0.36 V) ALARM
-12V: -10.63 V (min = -0.78 V, max = -2.23 V) ALARM
-5V: -5.44 V (min = -3.18 V, max = -2.02 V) ALARM
fan1: 5152 RPM (min = 42187 RPM, div = 2) ALARM
fan2: 2721 RPM (min = -1 RPM, div = 8) ALARM
fan3: 0 RPM (min = 5192 RPM, div = 2) ALARM
temp1: -65.0°C (high = +0.0°C, hyst = +127.0°C) ALARM
cpu0_vid: +3.100 V

w83627dhg-isa-0290
Adapter: ISA adapter
VCore: +1.42 V (min = +0.00 V, max = +1.74 V)
in1: +9.82 V (min = +0.84 V, max = +1.69 V) ALARM
AVCC: +3.25 V (min = +0.00 V, max = +1.02 V) ALARM
3VCC: +3.25 V (min = +0.02 V, max = +0.19 V) ALARM
in4: +1.38 V (min = +0.00 V, max = +0.05 V) ALARM
in5: +1.53 V (min = +0.11 V, max = +0.32 V) ALARM
in6: +5.79 V (min = +3.38 V, max = +2.15 V) ALARM
VSB: +3.25 V (min = +2.90 V, max = +0.06 V) ALARM
VBAT: +3.09 V (min = +2.11 V, max = +2.66 V) ALARM
Case Fan: 5113 RPM (min = 42187 RPM, div = 2) ALARM
CPU Fan: 2721 RPM (min = 0 RPM, div = 8) ALARM
Aux Fan: 0 RPM (min = 5192 RPM, div = 4) ALARM
fan4: 0 RPM (min = 84375 RPM, div = 16) ALARM
fan5: 0 RPM (min = 7670 RPM, div = 2) ALARM
Sys Temp: -65.0°C (high = +0.0°C, hyst = +127.0°C) sensor = diode
CPU Temp: +33.5°C (high = +127.0°C, hyst = +0.0°C) ALARM sensor = diode
AUX Temp: +34.0°C (high = +127.0°C, hyst = +0.0°C) sensor = thermistor

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

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +13.0°C (crit = +85.0°C)

[jabertolin]

Sorry for the question, I have been following all the steps of this HOWTO and just got, from *sensors-detect the following:

coretemp

I installed it into /etc/modules and with *sensors I only can see core 0 and 1 however nothing else, I am not able to get so much information as all of you showed here. Am I missing something else?

I installed sensors-applets and I can monitor core 0 and 1, hddtemp and acpi TZ01 and TZ00 (btw which is the difference between core 0 and acpi TZ00?)

I am looking for to monitor also nvidia GPU but unable to do it

Thanks

KJAB

[adredz]

when i try to edit /etc/modules i get this error:

adred@adred-desktop:~/Desktop$ sudo kate /etc/modules
Error: "/var/tmp/kdecache-adred" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-adred" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-adred" is owned by uid 1000 instead of uid 0.

same things happens when editing alises:

adred@adred-desktop:~/Desktop$ sudo kate /etc/modprobe.d/aliases
Error: "/var/tmp/kdecache-adred" is owned by uid 1000 instead of uid 0.
Error: "/tmp/kde-adred" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-adred" is owned by uid 1000 instead of uid 0.

what should i do?:(

[patoy]

i'm struggling lm-sensors to work with nagios. whew..

[Meserias]

It's this lm-sensors stuff loaded from Synaptics work trough SNMP ??????!?! With scripts are working with no problem.
Please see this page down>>> http://82.78.165.3:8081/

Promlem: using SNMPwalk I simply get no data
root@NecServ:~# snmpwalk -v1 -c public localhost LM-SENSORS-MIB::lmTempSensorsTable
root@NecServ:~#
It's simply no answer to this list
I'm intending to use this with MRTG / RRDTool
Please help me...:confused:

[Lakjin]

lakjin@lakjin-laptop:~$ sudo sensors-detect
# sensors-detect revision 5016 (2007-11-11 22:20:16 +0100)

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 82801H ICH8

We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no): y
Module loaded successfully.
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: SMBus I801 adapter at 1c00 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Client found at address 0x4c
Probing for `National Semiconductor LM75'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `Analog Devices ADT7466'... No
Probing for `Andigilog aSC7511'... No
Probing for `Dallas Semiconductor DS1621'... No
Probing for `Analog Devices ADM1021'... No
Probing for `Analog Devices ADM1021A/ADM1023'... No
Probing for `Maxim MAX1617'... No
Probing for `Maxim MAX1617A'... No
Probing for `Maxim MAX1668'... No
Probing for `Maxim MAX1805'... No
Probing for `Maxim MAX1989'... No
Probing for `Maxim MAX6655/MAX6656'... No
Probing for `TI THMC10'... No
Probing for `National Semiconductor LM84'... No
Probing for `Genesys Logic GL523SM'... No
Probing for `Onsemi MC1066'... No
Probing for `Maxim MAX1619'... No
Probing for `National Semiconductor LM82/LM83'... No
Probing for `National Semiconductor LM90'... No
Probing for `National Semiconductor LM89/LM99'... No
Probing for `National Semiconductor LM86'... No
Probing for `Analog Devices ADM1032'... No
Probing for `Maxim MAX6657/MAX6658/MAX6659'... No
Probing for `Maxim MAX6648/MAX6692'... No
Probing for `Maxim MAX6680/MAX6681'... No
Probing for `Winbond W83L771W/G'... No
Probing for `Texas Instruments TMP401'... No
Probing for `National Semiconductor LM63'... No
Probing for `Fintek F75363SG'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `Analog Devices ADT7461'... No
Probing for `Fintek F75383S/M'... No
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No

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 `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No

Some CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no): y
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... No
Intel AMB FB-DIMM thermal sensor... 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.


=( i followed those direction. why is it not working?

[dvelev]

Hello,
i have some problems with lm-sensors - when try to probe module i2c-sensors:
modprobe i2c-sensor
FATAL: Module i2c_sensor not found.

Here is my sensors-detect:
sudo sensors-detect
# sensors-detect revision 5016 (2007-11-11 22:20:16 +0100)

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...
Use driver `i2c-i810' for device 0000:00:02.0: Intel 82815 GMCH

We will now try to load each adapter module in turn.
Module `i2c-i810' 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: I810/I815 I2C Adapter (i2c-0)
Do you want to scan it? (YES/no/selectively):

Next adapter: I810/I815 DDC Adapter (i2c-1)
Do you want to scan it? (YES/no/selectively):

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 `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):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... Yes
Found `SMSC LPC47B357/M967 Super IO'
(no hardware monitoring capabilities)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No

Some CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no):
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... No
Intel AMB FB-DIMM thermal sensor... 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.
And here is the lsmod output:
lsmod
Module Size Used by
i2c_dev 8836 0
iptable_filter 3840 0
ip_tables 14820 1 iptable_filter
x_tables 16132 1 ip_tables
ide_generic 2176 0 [permanent]
ide_disk 17536 0
ide_cd 32416 0
ide_core 114252 3 ide_generic,ide_disk,ide_cd
i810 19968 0
drm 82580 1 i810
eeprom 8208 0
i2c_i801 10640 0
lp 12324 0
loop 19076 0
ipv6 272804 28
serio_raw 7940 0
button 9232 0
snd_intel8x0 35356 0
snd_ac97_codec 100772 1 snd_intel8x0
ac97_bus 3072 1 snd_ac97_codec
snd_pcm 78596 2 snd_intel8x0,snd_ac97_codec
snd_timer 24836 1 snd_pcm
snd 56868 4 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore 8800 1 snd
i2c_i810 5636 0
evdev 12928 0
iTCO_wdt 13092 0
iTCO_vendor_support 4868 1 iTCO_wdt
snd_page_alloc 11528 2 snd_intel8x0,snd_pcm
i2c_algo_bit 7300 1 i2c_i810
i2c_core 24832 5 i2c_dev,eeprom,i2c_i801,i2c_i810,i2c_algo_bit
intel_agp 25620 1
shpchp 34452 0
pci_hotplug 30880 1 shpchp
parport_pc 36644 1
parport 37704 2 lp,parport_pc
agpgart 34760 2 drm,intel_agp
pcspkr 4224 0
psmouse 40208 0
ext3 136584 1
jbd 48404 1 ext3
mbcache 9600 1 ext3
sg 36496 0
sr_mod 17828 0
cdrom 37280 2 ide_cd,sr_mod
sd_mod 30720 3
ata_generic 8324 0
floppy 59332 0
uhci_hcd 27152 0
e100 37516 0
usbcore 146028 2 uhci_hcd
ata_piix 19588 2
pata_acpi 8320 0
mii 6400 1 e100
libata 159344 3 ata_generic,ata_piix,pata_acpi
scsi_mod 151180 4 sg,sr_mod,sd_mod,libata
thermal 16796 0
processor 37000 1 thermal
fan 5636 0
fbcon 42656 0
tileblit 3456 1 fbcon
font 9472 1 fbcon
bitblit 6784 1 fbcon
softcursor 3072 1 bitblit
fuse 50580 1

I use ubuntu 8.04.1 server with Compaq Deskpro EN SFF PIII-1000MHz
Any suggestion for this problem?

[detroit/zero]

I followed the tutorial step-by-step, and ran into problems. Most obvious is that when I try to run sudo update-modules, I get a notice saying that the "command is deprecated and should not be used". Here's my terminal history for each step, picking up after creating and running the mkdev.sh script:
zero@zero-laptop:~$ sensors-detect
You need to be root to run this script.
zero@zero-laptop:~$ sudo !!
sudo sensors-detect
# sensors-detect revision 5016 (2007-11-11 22:20:16 +0100)

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...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7

We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no): yes
Module loaded successfully.
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): yes
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: SMBus I801 adapter at 18c0 (i2c-0)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Client found at address 0x50
Handled by driver `eeprom' (already loaded), chip type `eeprom'
(note: this is probably NOT a sensor chip!)
Client found at address 0x52
Handled by driver `eeprom' (already loaded), chip type `eeprom'
(note: this is probably NOT a sensor chip!)

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 `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): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No

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

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

Driver `coretemp' (should be inserted):
Detects correctly:
* Chip `Intel Core family thermal sensor' (confidence: 9)

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

To load everything that is needed, add this to /etc/modules:

#----cut here----
# Chip drivers
coretemp
#----cut here----

Do you want to add these lines automatically? (yes/NO)yes
zero@zero-laptop:~$ sudo gedit /etc/modules
zero@zero-laptop:~$ /etc/init.d/module-init-tools
open: Permission denied
* Loading kernel modules... open: Permission denied
* Loading manual drivers... open: Permission denied
[ OK ]
zero@zero-laptop:~$ sudo !!
sudo /etc/init.d/module-init-tools
* Loading kernel modules... * Loading manual drivers... [ OK ]
zero@zero-laptop:~$ sudo gedit /etc/modprobe.d/local
zero@zero-laptop:~$ sudo update-modules

************************************************** **********************
*
* The update-modules command is deprecated and should not be used!
*
************************************************** **********************

zero@zero-laptop:~$ update-modules --help

************************************************** **********************
*
* The update-modules command is deprecated and should not be used!
*
************************************************** **********************

zero@zero-laptop:~$ sudo gedit /etc/modules
zero@zero-laptop:~$ sudo modprobe i2c-sensor
FATAL: Module i2c_sensor not found.
zero@zero-laptop:~$ sudo modprobe i2c-viapro
zero@zero-laptop:~$ sudo modprobe i2c-isa
FATAL: Module i2c_isa not found.
zero@zero-laptop:~$ sudo modprobe it87
FATAL: Error inserting it87 (/lib/modules/2.6.24-20-generic/kernel/drivers/hwmon/it87.ko): No such device
zero@zero-laptop:~$ sudo depmod -a
zero@zero-laptop:~$ sudo update-modules

************************************************** **********************
*
* The update-modules command is deprecated and should not be used!
*
************************************************** **********************
And, of course, my horrendously short sensors output. It doesn't even show my HDD temp, even though there is a sensor feeding output to my panel applet and an AWN temp applet. I'm just trying to find a way to pipe these outputs into conky (http://ubuntuforums.org/showpost.php?p=5548586&postcount=3218) so I can ditch the panel and AWN applets.
zero@zero-laptop:~$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +48.0°C (crit = +100.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +47.0°C (crit = +100.0°C) Where did I go wrong?

[emperor]

lm-sensors apparently detected no sensors with the exception of the Intel coretemp. If your motherboard has sensor chips, they are apparently not supported by lm-sensors.
At least in the version of lm-sensors you have installed from Ubuntu's repo.

The hard drive temperature is read by "hddtemp" not lm-sensors so no detection here.

[Ripose]

When you installed lm-sensors using Synaptic did you also install the "recommended" packages? i2c, read-edid & sensord

I also installed hardinfo for a graphical interface, this will be installed as "System Profiler & Benchmark" under System-Preferences.

I then ran sensor-detect, answered y to everything, at the end it automatically wrote the changes to etc/modules: for me.

Reboot!

All info shows up in System Profiler & Benchmark (click on sensors), although I still need to change a file somewhere so cpu temp is displayed instead of Temp 3, MB instead of Temp 2, etc.

I did not follow any of the originally posted complicated code.

[rustamb]

do we really need lm-sensors on ubuntu 8.04? Doesn't powernowd do the work?

[amigaone_xe]

Anyone know if Intel Core2Quad (Q9550 - 45nm yorkfiled) is supported by lm-sensors?
I can't get it to work and the "supported device"-list on lm-sensors homepage says it supports Core/Core2, but maybe the Core2Quad isn't included there?

Is there any way to get it to work?
I'm running ubuntu 8.04.1 and lm-sensors 3.0.0

[Ripose]

do we really need lm-sensors on ubuntu 8.04? Doesn't powernowd do the work?
powernowd is used for things such as CPU speed (frequency). For example my PC runs at 1000 MHz, but if something needs a faster speed than it will go 1800 MHz or 2400 MHz. The way the speed is incremented is set with powernowd (voltages too).

lm-sensors displays current temperatures, voltages, etc.

[Ripose]

It does not appear that lm-sensors supports the Intel Quad. At least it is not the website list: http://www.lm-sensors.org/wiki/Devices

Note: The ALPHA version of lm-sensors Install Wizard is now available at above website.

[deepclutch]

coretemp module shows wrong temperatures with my 2.4Ghz C2D .:( yes ,this is a 2.6.26 kernel.reason:
http://lkml.org/lkml/2008/4/18/190
so ,it shows 56 degrees idle temp for cores.original temperature -you have to subtract 16 from the reading.that is , 56-16= 40 .

still no fix kya?:confused:

[ram zu]

System Ubuntu 8.04
I've installed lm-sensors
"sudo sensors-detect" with yes in all questions

Result of sensors:

pedro@Home-Server:~$ sensors
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp: +29.0°C

w83697hf-isa-0290
Adapter: ISA adapter
VCore: +1.10 V (min = +0.40 V, max = +0.03 V)
+3.3V: +3.30 V (min = +0.26 V, max = +0.00 V)
+5V: +5.03 V (min = +6.02 V, max = +4.41 V)
+12V: +11.31 V (min = +5.84 V, max = +0.06 V)
-12V: +0.72 V (min = -10.30 V, max = -9.56 V)
-5V: +5.10 V (min = -7.46 V, max = -4.49 V)
V5SB: +5.51 V (min = +5.19 V, max = +0.00 V)
VBat: +0.00 V (min = +0.29 V, max = +0.00 V)
fan1: 1454 RPM (min = 3375 RPM, div = 8)
fan2: 0 RPM (min = 33750 RPM, div = 4)
temp1: +37.0°C (high = +0.0°C, hyst = +100.0°C) sensor = thermistor
temp2: +33.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
beep_enable:enabled


I think that is everything correct but I dont know how to make use of this information.
I've installed "X-Sensors" but nothing happens when executed.
Tryng to use this in conky but dont know what parameter to use (conky is working fine).

Any help will be very apreciated.
Thanks to all.

[Tanker Bob]

I think that is everything correct but I know I cant make use of this information.
I'v installed "X-Sensors" but nothing happens when executed.
Tryng to use this in conky but dont know what parameter to use (conky is working fine).

I'm not sure what your issue is. Everything looks like it's working fine. What do you want to do?

[ram zu]

The problem was with x-sensors not working. I execute but no information displayed.
I've install the applet and is working now on the panel.
Only have two questions now. How can I know what temperature is temp1, temp2 and core0. The other question is how can I add this information to conky?

[Tanker Bob]

Got it. I use ksensors with KDE, so am not familiar with those programs. Did you install libsensors3 and libsensors4, plus whatever other support that x-sensors lists? That's the only thing that comes to mind.

[jjgomera]

The problem was with x-sensors not working. I execute but no information displayed.
I've install the applet and is working now on the panel.
Only have two questions now. How can I know what temperature is temp1, temp2 and core0. The other question is how can I add this information to conky?
look up in directory /sys/bus where are your sensors and write it here

to configure in conky it depends from that

[ram zu]

What was supposed to find in the dir /sys/bus?
There are a lot of dirs there but can't find anything related to lm-sensors.

[jjgomera]

For example, for me this is the output of sensors command:

jjgomera@ordenata:~$ sensors
it8718-isa-0290
Adapter: ISA adapter
in0: +1.20 V (min = +0.00 V, max = +4.08 V)
in1: +1.84 V (min = +0.00 V, max = +4.08 V)
in2: +3.23 V (min = +0.00 V, max = +4.08 V)
in3: +3.01 V (min = +0.00 V, max = +4.08 V)
in4: +2.96 V (min = +0.00 V, max = +4.08 V)
in5: +0.67 V (min = +0.00 V, max = +4.08 V)
in6: +0.70 V (min = +0.00 V, max = +4.08 V)
in7: +2.90 V (min = +0.00 V, max = +4.08 V)
in8: +3.07 V
fan1: 2777 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
temp1: +40.0°C (low = -1.0°C, high = +127.0°C) sensor = thermal diode
temp2: +39.0°C (low = -1.0°C, high = +127.0°C) sensor = transistor
temp3: +25.0°C (low = -1.0°C, high = +127.0°C) sensor = transistor
cpu0_vid: +0.913 V



and if i look same directory not empty for in /sys/bus, i found only useful sensors in /sys/bus/platform/drivers/it87/it87.656

And really is there where sensors are:

jjgomera@ordenata:~$ ls /sys/bus/platform/drivers/it87/it87.656
alarms in0_max in3_max in6_max subsystem temp3_input
cpu0_vid in0_min in3_min in6_min temp1_input temp3_max
driver in1_input in4_input in7_input temp1_max temp3_min
fan1_input in1_max in4_max in7_max temp1_min temp3_type
fan1_min in1_min in4_min in7_min temp1_type uevent
fan2_input in2_input in5_input in8_input temp2_input vrm
fan2_min in2_max in5_max modalias temp2_max
hwmon in2_min in5_min name temp2_min
in0_input in3_input in6_input power temp2_type
jjgomera@ordenata:~$


For example, for fan:

http://img364.imageshack.us/img364/5311/pantallazo2cc7.png

I'm lucky and conky support platform devices, so i can use conky platform variable, for fan i use:
${platform it87.656 fan 1}

Conky support other devices like i2c, hwmon, really i dont know if your sensors is supported by conky itself.

But no problem if conky dont support your sensors, in my system, if conky dont support platform, i could use:
${execi 5 cat /sys/bus/platform/drivers/it87/it87.656/fan1_input}
and work too, its heavier resources although

[ram zu]

Thanks a lot JJgomera.
I was melting my brain trying to discover how to put that sensor to work.

Now I just need to guess witch of the temp sensors is related to the CPU.

Once again... many Kudos to you.

Gracias neighbor

[Despot Despondency]

Hey, great how to. Everything seems to have installed correctly. A couple of questions though

1) When I got to the stage of doing the command

sudo depmod -a

I got a message saying it was depreciated. Do I need to run any other command?

2) When I type sensors I get the following output


k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp: +34.0°C
Core1 Temp: +34.0°C

dme1737-i2c-0-2e
Adapter: SMBus nForce2 adapter at 4c00
V5stby: +0.00 V (min = +0.00 V, max = +6.64 V) ALARM
Vccp: +1.12 V (min = +0.00 V, max = +2.99 V)
V3.3: +3.35 V (min = +0.00 V, max = +4.38 V)
V5: +5.08 V (min = +0.00 V, max = +6.64 V)
V12: +12.07 V (min = +0.00 V, max = +15.94 V)
V3.3stby: +3.31 V (min = +0.00 V, max = +4.38 V)
Vbat: +3.03 V (min = +0.00 V, max = +4.38 V)
CPU_Fan: 1365 RPM (min = 0 RPM)
Fan2: 0 RPM (min = 0 RPM)
Fan4: 0 RPM (min = 0 RPM)
RD1 Temp: +36.1°C (low = -127.0°C, high = +91.0°C)
Int Temp: +38.2°C (low = -127.0°C, high = +91.0°C)
CPU Temp: +32.2°C (low = -127.0°C, high = +91.0°C)
cpu0_vid: +1.550 V



How do I find out what things like V5stby actually correspond to? I've never used lm-sensors before so most of the readings are random to me.

3) In section 5) I tried

sudo modprobe i2c-sensor

but got FATAL:i2c_sensor not found. Do I need to worry about this?

Cheers in advance

[z00t]

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

I get this as well. Have a vanilla install of Ubuntu 8.04 LTS Desktop Edition on a Sony Vaio PCV-RX540. Installed fresh an hour ago with only openssh-server installed since.

[tnvkrishna]

The output of
command sudo sensors is just.

krishna@talupula:~$ sudo sensors
[sudo] password for krishna:
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +46.0°C (crit = +85.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +45.0°C (crit = +85.0°C)

I think something is wrong .....
Could you please help me.
I am using ubuntu 8.04 64bit
core 2 duo 1.83GHz.

[b0k]

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

The same thing happens to me when i try to install lm-sensors. :/

[Tanker Bob]

It's in the main repositories, so it should be available. If you cannot get it there, try downloading and installing it directly from the repository here (http://packages.ubuntu.com/hardy/utils/lm-sensors). You may have to ensure that you've installed all the required support packages.

[havok1977]

Hello everyone, i am having trouble setting up lm-sensors from 8.10 on my Sony Vaio VGN-S170F laptop...

The i2c modules are compiled and loaded into my running kernel; and the sensors-detect script does find my chipset:


Next adapter: SMBus I801 adapter at 1880 (i2c-0)


And yet not a single sensor is detected:


Do you want to scan it? (YES/no/selectively):

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 `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 `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No

Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No

Sorry, no sensors were detected.


I seriously doubt that the laptop does not have any sensors... i have also tried with the SVN version of lm-sensors and got the same results.

Any ideas?

[ubuser_7]

The output of
command sudo sensors is just.

krishna@talupula:~$ sudo sensors
[sudo] password for krishna:
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +46.0°C (crit = +85.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +45.0°C (crit = +85.0°C)



I have the exact same problem. Did you find a solution?

Sensors-detect only detects the coretemp module. I have a Intel(R) Core(TM)2 Duo CPU, E4600 @ 2.40GHz

I am running hardy.


Linux xml1 2.6.24-21-server #1 SMP Tue Oct 21 23:40:13 UTC 2008 x86_64 GNU/Linux

Description: Ubuntu 8.04.1
Release: 8.04
Codename: hardy

[Seba4.0]

Hi,

Im new to conky and I'm trying to have the temps from both cores (T7200) displayed.
Running sensors in the terminal gives me this output;

seba@ARP-8944:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +43.0°C (crit = +107.0°C)
temp2: +49.0°C (crit = +106.0°C)
temp3: +44.0°C (crit = +106.0°C)
temp4: +40.0°C (crit = +106.0°C)
temp5: +41.0°C (crit = +106.0°C)
temp6: +40.0°C (crit = +106.0°C)

I've tried using the folowing lines in conky;

${color b0e2ff}${exec sensors | grep 'coretemp'}
${execi 60 sensors |grep temp | cut -c15-16}

This gives me the temperature (just the 2 digits) for all thermal zones.
Can someone explain how to display only temp1 and temp6
I've tried using cut --help in the terminal but frankly I don't understand how to use the different parameters.
Thanks, Seba

Edit: Never mind, I've figured it out.
Cheers

[GepettoBR]

Thanks for the howto, it worked!

Hi,

Im new to conky and I'm trying to have the temps from both cores (T7200) displayed.
Running sensors in the terminal gives me this output;

seba@ARP-8944:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +43.0°C (crit = +107.0°C)
temp2: +49.0°C (crit = +106.0°C)
temp3: +44.0°C (crit = +106.0°C)
temp4: +40.0°C (crit = +106.0°C)
temp5: +41.0°C (crit = +106.0°C)
temp6: +40.0°C (crit = +106.0°C)

I've tried using the folowing lines in conky;

${color b0e2ff}${exec sensors | grep 'coretemp'}
${execi 60 sensors |grep temp | cut -c15-16}

This gives me the temperature (just the 2 digits) for all thermal zones.
Can someone explain how to display only temp1 and temp6
I've tried using cut --help in the terminal but frankly I don't understand how to use the different parameters.
Thanks, Seba

Edit: Never mind, I've figured it out.
Cheers

Try making two separate commands (one for temp1 and one for temp6). Instead of piping them both through "grep temp", use "grep temp1" on one and "grep temp6" on the other.

EDIT: It's worth mentioning that you can also pipe the command through grep more than once.

[jdorenbush]

I'm stuck at Steps 3 and 4. I got passed the part of getting the modules into my /etc/modules file and that's about it.

# Generated by sensors-detect on Mon Dec 1 19:16:56 2008
# I2C adapter drivers
i2c-nforce2
# Chip drivers
# no driver for Analog Devices ADT7475 yet
it87
k8temp

And I don't even have this file, /etc/modprobe.d/local

and Step 4 has lost me. Based off my sensors-detect above can someone help put Step 4 together for me please?

Any word on GUI tool for fan control?? =]

[Thameslink]

I'm a bit stuck.
I'm trying to get lm-sensors working right on my vaio vgn-n38z
I need to control the fan speed

I run the script
it says

/dev/i2c-0
/home/jake/Desktop/mkdev.sh: 25: +: not found
/dev/i2c-0
mknod: `/dev/i2c-0': File exists


which I don't understand, but I don't think it's right.

after going through the rest of the steps i run sensors and get

jake@jake-vaio:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +52.0°C (crit = +105.0°C)
temp2: +52.0°C (crit = +105.0°C)

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

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

jake@jake-vaio:~$ sudo modprobe it87
FATAL: Error inserting it87 (/lib/modules/2.6.27-9-generic/kernel/drivers/hwmon/it87.ko): No such device


I think the it87 thing is the vpm module i need, but I'm quite far out of my depth. I only installed ubuntu 1 week ago.

Can anyone help me please?

[quazar]

I'm trying to display lm_sensors data on my 2x16 LCD running LCDd/lcdproc.

For the script I'm trying to run (lcdsensors.pl (http://www.esat.kuleuven.ac.be/~nvanhell/LCDsensors.html)), I need a location for the k8temp sensor.
I found the it8718 chipset sensor under /sys/devices/platform/:
## variables regarding lm_sensors, update these conform to your system
my $chip='/sys/devices/platform/it87.552'; # directory where lm_sensors writes its data

But I cannot find the k8temp sensor in the directory /sys/devices/platform/

Is there a way to get the k8temp sensor files in that directory?

Edit: found the sensor under /sys/bus/pci/drivers/k8temp/0000:00:18.3

[alzekak]

Hey there, since I've been having issues installing lm-sensors properly for a while now on 8.10, (following any kinda guide i've found so far) I concluded on installing the sensors-applet for the gnome panel which works perfectly so far.

It may not be the ideal solution since you don't really get all the indications you could get with lm-sensors yet still it's an alternative.

Hope to have helped,
Alexander.

[jamesperterson]

I have now word to say that you solve my big problem.......

Awesome Nice forum Keep it up up Guys.....

[newbie2]

lm-sensors 3.0.3

This is a completely reworked package, for Linux 2.6.5+. It supports all the devices your kernel supports, as it no longer contains chip-specific code.
http://www.lm-sensors.org/wiki/Download

[newbie2]

isn't it possible to 'integrate' lm-sensors into Hardware-info (http://www.watchingthenet.com/ubuntu-guide-for-windows-users-display-system-hardware-information.html)?...all info about my CPU sensors i get in this 'hardware-info' is this :

http://img6.imageshack.us/img6/4175/screenshot01j.th.png (http://img6.imageshack.us/my.php?image=screenshot01j.png)

:rolleyes::-(

[narsaw]

Anyone knows why my output from sensors haves these weird characters? They look like ( Â ).

Also, is my cpu temp +22 or +30. I see Core0 and Cpu Temp reported below.


% sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +40.0°C (crit = +75.0°C)

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

it8712-isa-0290
Adapter: ISA adapter
VCore 1: +1.12 V (min = +0.00 V, max = +4.08 V)
VCore 2: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
+3.3V: +3.28 V (min = +0.00 V, max = +4.08 V)
+5V: +4.81 V (min = +0.00 V, max = +6.85 V)
+12V: +12.42 V (min = +0.00 V, max = +16.32 V)
-12V: -4.90 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.06 V
fan1: 1117 RPM (min = 811 RPM, div = 8)
fan2: 0 RPM (min = 0 RPM, div = 8)
fan3: 0 RPM (min = 0 RPM, div = 8)
M/B Temp: +23.0°C (low = -1.0°C, high = +127.0°C) sensor = transistor
CPU Temp: +30.0°C (low = -1.0°C, high = +127.0°C) sensor = transistor
Temp3: +25.0°C (low = -1.0°C, high = +127.0°C) sensor = transistor
cpu0_vid: +0.875 V

[deepclutch]

huh.it has to do with locale support("locale" command will list your default locale.mine is en_US.utf8).you add this sensors-applet(install first) and to Gnome-Panel.it works.

[afeasfaerw23231233]

It cannot detect the voltage scanner. I am sure it must has voltage sensors because I can see the voltage of CPU in Windows. What to do?

[Deathray]

This is all I get, how come? My motherboard is an Asus P5Q Pro and I really like Ubuntu too much too uninstall it just because of the fan being so loud! :(

deathray@deathray-desktop:~$ sudo sensors-detect
# sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)

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...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported I2C/SMBus 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 (i2c-0)
Do you want to scan it? (YES/no/selectively): YES
Client found at address 0x4f
Probing for `National Semiconductor LM75'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No

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 `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 `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... Yes
Found unknown chip with ID 0xa513
(logical device B has address 0x290, could be sensors)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No

Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no): YES
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No

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

Driver `coretemp' (should be inserted):
Detects correctly:
* Chip `Intel Core family thermal sensor' (confidence: 9)

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

To load everything that is needed, add this to /etc/modules:

#----cut here----
# Chip drivers
coretemp
#----cut here----

Do you want to add these lines automatically? (yes/NO)YES
deathray@deathray-desktop:~$
deathray@deathray-desktop:~$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +33.0°C (high = +82.0°C, crit = +100.0°C)

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

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

coretemp-isa-0003
Adapter: ISA adapter
Core 3: +30.0°C (high = +82.0°C, crit = +100.0°C)

deathray@deathray-desktop:~$

[miegiel]

Better late then never :)

All 4 of my k8temp-pci-00c3 outputs go up and down when I stress my GPU with the glxgears command, so I'm pretty sure it's my graphics card.

GPUs have cores too and that's probably what k8temp-pci-00c3 also senses in your case. I'm trying to figure out what exactly is being sensed here and if the the temps are accurate. It might be that they are (in my case) 4 GPU temp sensors, but it wouldn't surprise me if only 1 is and another senses my cards memory. And a 3rd might not be a temp sensor at all and actually be sensing the rpm of the cards fan.

Anyone knows why my output from sensors haves these weird characters? They look like ( Â ).

Also, is my cpu temp +22 or +30. I see Core0 and Cpu Temp reported below.


% sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +40.0°C (crit = +75.0°C)

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

it8712-isa-0290
Adapter: ISA adapter
VCore 1: +1.12 V (min = +0.00 V, max = +4.08 V)
VCore 2: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
+3.3V: +3.28 V (min = +0.00 V, max = +4.08 V)
+5V: +4.81 V (min = +0.00 V, max = +6.85 V)
+12V: +12.42 V (min = +0.00 V, max = +16.32 V)
-12V: -4.90 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.06 V
fan1: 1117 RPM (min = 811 RPM, div = 8)
fan2: 0 RPM (min = 0 RPM, div = 8)
fan3: 0 RPM (min = 0 RPM, div = 8)
M/B Temp: +23.0°C (low = -1.0°C, high = +127.0°C) sensor = transistor
CPU Temp: +30.0°C (low = -1.0°C, high = +127.0°C) sensor = transistor
Temp3: +25.0°C (low = -1.0°C, high = +127.0°C) sensor = transistor
cpu0_vid: +0.875 V


My sensors output :
:~$ sensors
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp: +34.0°C
Core0 Temp: +35.0°C
Core1 Temp: +28.0°C
Core1 Temp: +27.0°C

it8716-isa-0228
Adapter: ISA adapter
VCore: +1.18 V (min = +0.00 V, max = +4.08 V)
VDDR: +1.28 V (min = +0.00 V, max = +4.08 V)
+3.3V: +3.31 V (min = +0.00 V, max = +4.08 V)
+5V: +4.95 V (min = +0.00 V, max = +5.99 V)
+12V: +12.10 V (min = +0.00 V, max = +16.32 V)
in5: +1.18 V (min = +0.00 V, max = +4.08 V)
in6: +2.30 V (min = +0.00 V, max = +4.08 V)
5VSB: +4.87 V (min = +0.00 V, max = +6.85 V)
VBat: +3.33 V
fan1: 1358 RPM (min = 3245 RPM)
fan2: 1618 RPM (min = 3245 RPM)
fan3: 1704 RPM (min = 3245 RPM)
temp1: +47.0°C (low = +127.0°C, high = +84.0°C) sensor = thermal diode
temp2: +47.0°C (low = +127.0°C, high = +84.0°C) sensor = transistor
temp3: +53.0°C (low = +127.0°C, high = +84.0°C) sensor = transistor
cpu0_vid: +1.550 V

[alek66]

I hope I can get started this week, when Its done i´ll post my experiences and probably my issues!

Cheers

[vampire666eng]

I have an Asus P5Q-E, I followed the instructions on the first post but it looks like the program couldn't find any sensors?

alain@VAMPIRE666:~$ 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
./mkdev.sh: line 32: b.: comando non trovato
./mkdev.sh: line 36: c.: comando non trovato
/dev/i2c-0
mknod: "/dev/i2c-0": Il file esiste
alain@VAMPIRE666:~$ sudo sensors-detect
# sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)

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 ICH10

We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no): y
Module loaded successfully.
If you have undetectable or unsupported I2C/SMBus 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 (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x49
Probing for `National Semiconductor LM75'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
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'... Yes
(confidence 8, not a hardware monitoring chip)

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

Next adapter: NVIDIA i2c adapter (i2c-2)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x2e
Probing for `Myson MTP008'... No
Probing for `National Semiconductor LM78'... No
Probing for `National Semiconductor LM78-J'... No
Probing for `National Semiconductor LM79'... No
Probing for `National Semiconductor LM80'... No
Probing for `National Semiconductor LM85 or LM96000'... No
Probing for `Analog Devices ADM1027, ADT7460 or ADT7463'... No
Probing for `SMSC EMC6D100, EMC6D101 or EMC6D102'... No
Probing for `Analog Devices ADT7462'... No
Probing for `Analog Devices ADT7467 or ADT7468'... No
Probing for `Analog Devices ADT7470'... No
Probing for `Analog Devices ADT7473'... Success!
(confidence 5, driver `to-be-written')
Probing for `Analog Devices ADT7475'... No
Probing for `Analog Devices ADT7476'... No
Probing for `Andigilog aSC7611'... No
Probing for `Andigilog aSC7621'... No
Probing for `National Semiconductor LM87'... No
Probing for `National Semiconductor LM93'... No
Probing for `Winbond W83781D'... No
Probing for `Winbond W83782D'... No
Probing for `Winbond W83792D'... No
Probing for `Winbond W83793R/G'... No
Probing for `Winbond W83791SD'... No
Probing for `Winbond W83627HF'... No
Probing for `Winbond W83627EHF'... No
Probing for `Winbond W83627DHG'... No
Probing for `Asus AS99127F (rev.1)'... No
Probing for `Asus AS99127F (rev.2)'... No
Probing for `Asus ASB100 Bach'... No
Probing for `Winbond W83L786NR/NG/R/G'... No
Probing for `Winbond W83L785TS-S'... No
Probing for `Analog Devices ADM9240'... No
Probing for `Dallas Semiconductor DS1780'... No
Probing for `National Semiconductor LM81'... No
Probing for `Analog Devices ADM1026'... No
Probing for `Analog Devices ADM1025'... No
Probing for `Analog Devices ADM1029'... No
Probing for `Analog Devices ADM1030'... No
Probing for `Analog Devices ADM1031'... No
Probing for `Analog Devices ADM1022'... No
Probing for `Texas Instruments THMC50'... No
Probing for `Analog Devices ADM1028'... No
Probing for `ITE IT8712F'... No
Probing for `SMSC DME1737'... No
Probing for `SMSC SCH5027D-NW'... No
Probing for `Fintek F75373S/SG'... No
Probing for `Fintek F75375S/SP'... No
Probing for `Fintek F75387SG/RG'... No
Probing for `Analog Devices ADM1024'... No
Probing for `Winbond W83791D'... No

Next adapter: SMBus I801 adapter at 0400 (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'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No

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 `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 `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... Yes
Found unknown chip with ID 0xa513
(logical device B has address 0x290, could be sensors)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No

Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no): y
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No

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

Driver `to-be-written' (should be inserted):
Detects correctly:
* Bus `NVIDIA i2c adapter '
Busdriver `UNKNOWN', I2C address 0x2e
Chip `Analog Devices ADT7473' (confidence: 5)

Driver `coretemp' (should be inserted):
Detects correctly:
* Chip `Intel Core family thermal sensor' (confidence: 9)

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

To load everything that is needed, add this 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
# no driver for Analog Devices ADT7473 yet
coretemp
#----cut here----

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


Any help?

[abjt]

doesn't work with integrated intel. I have a DG45FC mobo and sensors cannot detect the temp or voltage

[cb_rex]

I have an Asus P5Q-E, I followed the instructions on the first post but it looks like the program couldn't find any sensors?
...
Any help?



This is all I get, how come? My motherboard is an Asus P5Q Pro and I really like Ubuntu too much too uninstall it just because of the fan being so loud! :(
...


I was getting a similar issue to you with my ASUS P5Q SE, with it only showing my core temperatures and nothing else. I found this thread (http://ubuntu-virginia.ubuntuforums.org/showthread.php?t=871001) that helped me out.

Essentially running "sudo modprobe w83627ehf force_id=0x8860" and then "sensors -s" and then "sensors" revealed all the sensor information that had been missing.

I also added the lines:

echo "$(modprobe w83627ehf force_id=0x8860)"
echo "$(sensors -s)"

into the "etc/rc.local" file to load the correct sensors information for my motherboard on boot up, so now my sensors applet displays everything properly.

I don't know how to control the fan speeds in ubuntu, I just use the quiet setting in the BIOS, which seems to take care of everything.

[EDIT 2nd November 2009]

I've just performed a clean install of Karmic 9.10 and encountered some slight issues as described >HERE< (http://ubuntu-virginia.ubuntuforums.org/showthread.php?t=871001&page=2).

I found that initially the sensors didn't work, so I decided to update my motherboard to the latest BIOS on the ASUS website. After doing this I could see temperatures, but not fan speeds.

To fix this I first tried the "acpi_enforce_resources=lax" into grub menu.lst file; as described in post 15 from the above link, however this didn't work. After a bit of reading round >HERE< (http://bugs.launchpad.net/ubuntu/+source/linux/+bug/418246) (post 11 was when it all made sense, thanks Stefan), I realised it was due to me having Grub 2 as I had done a clean install not an upgrade from 9.04. Essentially its the same fix but the file is in a different place...

/etc/default/grub

Here I inserted: GRUB_CMDLINE_LINUX="acpi_enforce_resources=lax"
Saved and closed then in the terminal ran: update-grub
Then rebooted.

After reboot I applied the modprobe fix exactly as I describe above for 9.04 and it seems to be working fine again.

[Wookiee]

edit: Nevermind, I've got it configured and set up. But it seems my sensors aren't supported by x sensor.

[iamboredr]

nice info men wow great to use thanks

[Shekibobo]

The only thing my sensors detected was the intel-chipset cpus:

josh@ubuntu:~$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +52.0°C (high = +85.0°C, crit = +85.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1: +54.0°C (high = +85.0°C, crit = +85.0°C)


And it automatically added the lines of code required:

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

Driver `coretemp' (should be inserted):
Detects correctly:
* Chip `Intel Core family thermal sensor' (confidence: 9)

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

To load everything that is needed, add this to /etc/modules:

#----cut here----
# Chip drivers
coretemp
#----cut here----

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

I apparently didn't need to do anything else because the sensors command seems to work just fine. I just don't get much info. Might be because I'm on a laptop, though.

[sharkcohen]

Is anyone using lm-sensors with the Intel Core i7 965 Extreme? I'm seeing temps of about 65C at idle with lm-sensors. Is this accurate, can I trust what lm-sensors and coretemp are reporting?

[cyberkost]

I'm not using i7 965, but I read that:
1) many temp sensors return not the temp, but delta to critical temp. So, the reading is a function of how correctly the critical temp is set in the BIOS
2) lm-sensors do a bit of math that is sensor specific. The formulas may be wrong, chances of that are higher for newer/rarer hardware.
Can you check temp in a Windows environment?

[o0Chris0o]

ok I installed lm-sensors and everything. I don't think its listing right. Please have a look.

chris@TuX:~$ sensors
it8712-isa-0290
Adapter: ISA adapter
VCore 1: +1.14 V (min = +0.00 V, max = +4.08 V)
VCore 2: +4.08 V (min = +0.00 V, max = +4.08 V) ALARM
+3.3V: +3.28 V (min = +0.00 V, max = +4.08 V)
+5V: +6.85 V (min = +0.00 V, max = +6.85 V) ALARM
+12V: +12.80 V (min = +0.00 V, max = +16.32 V)
-12V: -14.97 V (min = -27.36 V, max = +3.93 V)
-5V: +4.03 V (min = -13.64 V, max = +4.03 V) ALARM
Stdby: +6.85 V (min = +0.00 V, max = +6.85 V) ALARM
VBat: +3.17 V
fan1: 2509 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
M/B Temp: +45.0°C (low = -1.0°C, high = +127.0°C) sensor = thermistor
CPU Temp: +31.0°C (low = -1.0°C, high = +127.0°C) sensor = thermistor
Temp3: -128.0°C (low = -1.0°C, high = +127.0°C) sensor = disabled
cpu0_vid: +0.763 V


any ideas? I am trying to get the temperatures/fan speed for my Motherboard, Processor and 4 cores for conky. My computer information is in my sig.

[miegiel]

@o0Chris0o, the calculations of the sensor output are probably wrong. If you're worried that there might be something wrong with the PSU go to the BIOS and check the voltages there. In any case at 4V your CPU would have already died.

[Greyhound-]

I have an Intel Core i7 on a Gigabyte GA-EX58-UD5 motherboard and am running Ubuntu 9.04. I've been trying like crazy to get lm-sensors to work but seem to be failing miserably. Could someone please tell me what I'm doing wrong? I first installed lm-sensors through the repository, ran sensors-detect.. had not luck, then I installed it from source, same thing happened again. Here's the output I get from running sensors-detect:

# sensors-detect revision 5666 (2009-02-26 17:15:04 +0100)
# System: Gigabyte Technology Co., Ltd. EX58-UD5

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.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
Intel Core family thermal sensor... Success!
(driver `coretemp')
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal and voltage sensors... No

Some Super I/O chips contain embedded 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 `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... Yes
Found `ITE IT8720F Super IO Sensors' Success!
(address 0x290, driver `it87')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We have to read from arbitrary I/O ports to probe for such interfaces.
This is normally safe. Do you want to scan for IPMI interfaces?
(YES/no):
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No

Some hardware monitoring chips are 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 LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device 0000:00:1f.3: Intel ICH10
Module i2c-i801 loaded successfully.
Module i2c-dev loaded successfully.

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

Next adapter: NVIDIA i2c adapter (i2c-1)
Do you want to scan it? (YES/no/selectively):
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'... Yes
(confidence 8, not a hardware monitoring chip)

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

Next adapter: NVIDIA i2c adapter (i2c-3)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x2e
Probing for `Myson MTP008'... No
Probing for `National Semiconductor LM78'... No
Probing for `National Semiconductor LM79'... No
Probing for `National Semiconductor LM80'... No
Probing for `National Semiconductor LM85'... No
Probing for `National Semiconductor LM96000 or PC8374L'... No
Probing for `Analog Devices ADM1027'... No
Probing for `Analog Devices ADT7460 or ADT7463'... No
Probing for `SMSC EMC6D100 or EMC6D101'... No
Probing for `SMSC EMC6D102'... No
Probing for `SMSC EMC6D103'... No
Probing for `Winbond WPCD377I'... No
Probing for `Analog Devices ADT7467 or ADT7468'... No
Probing for `Analog Devices ADT7470'... No
Probing for `Analog Devices ADT7473'... Success!
(confidence 5, driver `adt7473')
Probing for `Analog Devices ADT7475'... No
Probing for `Analog Devices ADT7476'... No
Probing for `Andigilog aSC7611'... No
Probing for `Andigilog aSC7621'... No
Probing for `National Semiconductor LM87'... No
Probing for `Analog Devices ADM1024'... No
Probing for `National Semiconductor LM93'... No
Probing for `Winbond W83781D'... No
Probing for `Winbond W83782D'... No
Probing for `Winbond W83791D'... No
Probing for `Winbond W83792D'... No
Probing for `Winbond W83793R/G'... No
Probing for `Winbond W83627HF'... No
Probing for `Winbond W83627EHF'... No
Probing for `Winbond W83627DHG'... No
Probing for `Asus AS99127F (rev.1)'... No
Probing for `Asus AS99127F (rev.2)'... No
Probing for `Asus ASB100 Bach'... No
Probing for `Winbond W83L786NR/NG/R/G'... No
Probing for `Winbond W83L785TS-S'... No
Probing for `Analog Devices ADM9240'... No
Probing for `Dallas Semiconductor DS1780'... No
Probing for `National Semiconductor LM81'... No
Probing for `Analog Devices ADM1026'... No
Probing for `Analog Devices ADM1025'... No
Probing for `Analog Devices ADM1029'... No
Probing for `Analog Devices ADM1030'... No
Probing for `Analog Devices ADM1031'... No
Probing for `Analog Devices ADM1022'... No
Probing for `Texas Instruments THMC50'... No
Probing for `Analog Devices ADM1028'... No
Probing for `Texas Instruments THMC51'... No
Probing for `ITE IT8712F'... No
Probing for `SMSC DME1737'... No
Probing for `SMSC SCH5027D-NW'... No
Probing for `Fintek F75373S/SG'... No
Probing for `Fintek F75375S/SP'... No
Probing for `Fintek F75387SG/RG'... No
Probing for `Winbond W83791SD'... No

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

Next adapter: NVIDIA i2c adapter (i2c-5)
Do you want to scan it? (YES/no/selectively):
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'... No
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x53
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No

Next adapter: SMBus I801 adapter at 0500 (i2c-6)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x4e
Probing for `National Semiconductor LM75'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `Analog Devices ADM1021'... No
Probing for `Analog Devices ADM1021A/ADM1023'... No
Probing for `Maxim MAX1617'... No
Probing for `Maxim MAX1617A'... No
Probing for `Maxim MAX1668'... No
Probing for `Maxim MAX1805'... No
Probing for `Maxim MAX1989'... No
Probing for `Maxim MAX6655/MAX6656'... No
Probing for `TI THMC10'... No
Probing for `National Semiconductor LM84'... No
Probing for `Genesys Logic GL523SM'... No
Probing for `Onsemi MC1066'... No
Probing for `Maxim MAX1618'... No
Probing for `Maxim MAX1619'... No
Probing for `National Semiconductor LM82/LM83'... No
Probing for `Maxim MAX6654/MAX6690'... No
Probing for `Maxim MAX6659'... No
Probing for `Maxim MAX6647'... No
Probing for `Maxim MAX6680/MAX6681'... No
Probing for `Texas Instruments TMP411'... No
Probing for `National Semiconductor LM64'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `Fintek F75121R/F75122R/RG (VID+GPIO)'... No
Probing for `Fintek F75111R/RG/N (GPIO)'... No
Probing for `ITE IT8201R/IT8203R/IT8206R/IT8266R'... Yes
(confidence 6, not a hardware monitoring chip)
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)

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

Driver `it87':
* ISA bus, address 0x290
Chip `ITE IT8720F Super IO Sensors' (confidence: 9)

Driver `adt7473':
* Bus `NVIDIA i2c adapter '
Busdriver `nvidia', I2C address 0x2e
Chip `Analog Devices ADT7473' (confidence: 5)

Driver `coretemp':
* Chip `Intel Core family thermal sensor' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.

Unloading i2c-dev... OK
Unloading i2c-i801... OK

[miegiel]

I have an Intel Core i7 on a Gigabyte GA-EX58-UD5 motherboard and am running Ubuntu 9.04. I've been trying like crazy to get lm-sensors to work but seem to be failing miserably. Could someone please tell me what I'm doing wrong? I first installed lm-sensors through the repository, ran sensors-detect.. had not luck, then I installed it from source, same thing happened again. Here's the output I get from running sensors-detect:

In hardy I'd say add# lm-sensors for Gigabyte GA-EX58-UD5
it87
coretemp too the end of your /etc/modules file. But your sensors-detect out put is different from mine :( so possibly stuff has changed ? Do you have a /etc/modules file?

[Greenwidth]

Thanks for the HOW TO!
I seem to be getting conflicting results though from SMBus and ISA.. Not really important but how do I stop SMBus reporting? Remove it from etc/modules ?

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

w83791d-i2c-1-2d
Adapter: SMBus nForce2 adapter at 1c80
in0: +1.26 V (min = +0.00 V, max = +3.06 V)
in1: +1.54 V (min = +0.00 V, max = +3.06 V)
in2: +1.26 V (min = +2.82 V, max = +3.79 V) ALARM
in3: +3.06 V (min = +0.00 V, max = +0.00 V) ALARM
in4: +1.04 V (min = +0.26 V, max = +0.00 V) ALARM
in5: +1.12 V (min = +1.02 V, max = +0.00 V) ALARM
in6: +1.25 V (min = +0.03 V, max = +0.00 V) ALARM
in7: +2.98 V (min = +0.51 V, max = +1.02 V) ALARM
in8: +3.22 V (min = +1.02 V, max = +2.11 V) ALARM
in9: +2.10 V (min = +1.02 V, max = +0.51 V) ALARM
fan1: 0 RPM (min = 168750 RPM, div = 8) ALARM
fan2: 0 RPM (min = -1 RPM, div = 8) ALARM
fan3: 0 RPM (min = -1 RPM, div = 8) ALARM
fan4: 0 RPM (min = -1 RPM, div = 8) ALARM
fan5: 0 RPM (min = -1 RPM, div = 8) ALARM
temp1: -9.0°C (high = +0.0°C, hyst = +4.0°C)
temp2: -7.5°C (high = +80.0°C, hyst = +75.0°C)
temp3: -10.0°C (high = +80.0°C, hyst = +75.0°C)
cpu0_vid: +1.419 V
beep_enable:enabled

it8718-isa-0290
Adapter: ISA adapter
in0: +1.22 V (min = +0.00 V, max = +4.08 V)
in1: +3.30 V (min = +0.00 V, max = +4.08 V)
in2: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
in3: +2.99 V (min = +0.00 V, max = +4.08 V)
in4: +2.94 V (min = +0.00 V, max = +4.08 V)
in5: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
in6: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
in7: +2.93 V (min = +0.00 V, max = +4.08 V)
in8: +2.99 V
fan1: 1155 RPM (min = 3245 RPM) ALARM
fan2: 868 RPM (min = 3245 RPM) ALARM
fan3: 0 RPM (min = 0 RPM)
temp1: +23.0°C (low = -1.0°C, high = +127.0°C) sensor = thermal diode
temp2: +29.0°C (low = -1.0°C, high = +127.0°C) sensor = thermistor
temp3: -55.0°C (low = -1.0°C, high = +127.0°C) sensor = thermistor
cpu0_vid: +0.000 V

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

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

coretemp-isa-0002
Adapter: ISA adapter
Core 2: +36.0°C (high = +82.0°C, crit = +100.0°C)

coretemp-isa-0003
Adapter: ISA adapter
Core 3: +31.0°C (high = +82.0°C, crit = +100.0°C)

[miegiel]

Thanks for the HOW TO!
I seem to be getting conflicting results though from SMBus and ISA.. Not really important but how do I stop SMBus reporting? Remove it from etc/modules ?

In short yes, or put a # at the start of the line.

Running sensors-detect again and checking the "confidence" of the different sensors might be wise too.

[Greenwidth]

Running sensors-detect again and checking the "confidence" of the different sensors might be wise too.

Good plan - SMBus scores a 5 and ISA gets 9 so i'll go with that :)

[jetbelbes]

Hi guys!

I'm quite new to lm-sensors. Anyway, I tried sudo sensors-detect but after answering YES to all questions, here's the terminal output.

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
http://www.lm-sensors.org/wiki/FAQ/Chapter3 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 help me. I'm using ACER Travelmate 2420 and I badly need lm-sensors because this laptop heats up a lot and to a very high temp and, at times, even auto-shuts down because of the heat. Thanks!

-Jet

[Tanker Bob]

If sensors-detect didn't find any sensors, lmsensors probably doesn't support your motherboard. That's a lot more common on laptops that all have custom boards.

[jetbelbes]

Oh, If lmsensors does not support my motherboard, is there any other motherboard detection software/support that might be compatible with my board?:popcorn:

[edemkrimea]

The tutorial is great . However here is my sensors output . Could you point me what happened to M/B Temp and CPU Temp lines? Thanks in advance

[miegiel]

The tutorial is great . However here is my sensors output . Could you point me what happened to M/B Temp and CPU Temp lines? Thanks in advance

Open /etc/sensors3.conf (disclaimer: I'm using hardy (8.04)) and search it for "it8712-" to find the stuff on your sensor.

Quoting from the temperature section of the it8712 sensor:
# Important - if your temperature readings are completely whacky
# you probably need to change the sensor type.
# Adujst and uncomment the appropriate lines below.

I'm guessing Temp3 is your CPU temperature, since it's a thermal diode.

[Laysan_A]

@jetbelbes

I'm sorry you can't find a solution for your laptop.

I read your post and I wanted to offer you a warning (slightly off topic). I had (actually still do) an inspiron 8000 with a pIII that always ran hot (they were a very hot chip). I didn't have any monitoring software, didn't even know that I should have. Anyway, it started just dying unexpectedly, at first very rarely, but then more and more often until it finally wouldn't even stay on long enough to finish loading windows.

I didn't know what the problem was until I spent the money for a refirbished mb and a used processor to fix it with. When I opened the case I discovered that the heat sink was completely empty of coolant - it had all leaked out over time.

If you have a windows partition I'd use it to find out what temp you're operating at, and check your processor's temp. limits (google it at the manufacturer's site). I don't think your laptop should ever overheat if everything's working properly (you're not blocking the vents are you?). Check your fans for good speed and smooth operation.

If your operating temp. and the processor's specs don't align, ie. you're operating outside the safe operating zone, you need to fix it or you'll likely lose it. You might look at ebay for inexpensive parts (buyer beware, though [my refirbished mb went bad]).

Good luck.

[tonydunno]

I'm having trouble with my pwmconfig.

Found the following PWM controls:
hwmon2/device/pwm1
hwmon2/device/pwm2
hwmon2/device/pwm3
There are no usable PWM outputs.


Though my sensors cleary reads out the fans


nelis@nelis-desktop:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +41.0°C (crit = +70.0°C)
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp: +36.0°C
Core1 Temp: -49.0°C
f71862fg-isa-0220
Adapter: ISA adapter
in0: +1.70 V
in1: +2.04 V
in2: +1.20 V
in3: +2.04 V
in4: +1.34 V
in5: +1.18 V
in6: +1.18 V
in7: +1.68 V
in8: +1.66 V
fan1: 2538 RPM
fan2: 2222 RPM
fan3: 0 RPM ALARM
temp1: +41.0°C (high = +85.0°C, hyst = +81.0°C)
(crit = +70.0°C, hyst = +66.0°C) sensor = transistor
temp2: +89.0°C (high = +85.0°C, hyst = +81.0°C) ALARM
(crit = +100.0°C, hyst = +96.0°C) sensor = transistor
temp3: +44.0°C (high = +254.0°C, hyst = +252.0°C)
(crit = +254.0°C, hyst = +252.0°C) sensor = transistor




Anyone got an idea on how to deal with this ?

I did read through http://ubuntuforums.org/showthread.php?t=42737

[Laysan_A]

I'd be interested if there's a fix for this too. Pwmconfig finds my case fan okay, but doesn't know my processor fan exists.

[VastOne]

I have a new MSI 790FX-GD70 motherboard and have run into this with sensors-detect:

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

Driver `to-be-written':
* Chip `AMD K10 thermal sensors' (confidence: 9)
* Bus `SMBus PIIX4 adapter at 0b00'
Busdriver `i2c_piix4', I2C address 0x2e
Chip `Fintek F75387SG/RG' (confidence: 7)

Note: there is no driver for AMD K10 thermal sensors yet.
Check http://www.lm-sensors.org/wiki/Devices for updates.

No modules to load, skipping modules configuration.


I have checked everywhere on the web for the AMD K10, the Fintek and i2c_piix4 help and have been stuck in the mud for over a month now.

Has anyone gotten any of these to work with lm_sensors?

This is driving me nuts as one the unsolved mysteries affecting my sleep and even my work...:confused:

[eddski]

This is probably a dumb question, but how do set a minimum fan speed? I don't care about the noise (it's minimal), but I do want to cool down the CPU in my laptop.

[miegiel]

This is probably a dumb question, but how do set a minimum fan speed? I don't care about the noise (it's minimal), but I do want to cool down the CPU in my laptop.

No experience with that, but try: Search: Keyword(s): fan, control

[coller_girl]

hi i need help with this my fan speeds al over the shop, so i tried installing lm-sensors and got this output... what to do next?


sara@sara-desktop:~$ gksudo sama
sara@sara-desktop:~$ sudo apt-get install lm-sensors
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libsensors4
Suggested packages:
sensord read-edid i2c-tools
The following NEW packages will be installed
libsensors4 lm-sensors
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 188kB of archives.
After this operation, 782kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get: 1 http://gb.archive.ubuntu.com jaunty/main libsensors4 1:3.0.2-2ubuntu4 [63.0kB]
Get: 2 http://gb.archive.ubuntu.com jaunty/main lm-sensors 1:3.0.2-2ubuntu4 [125kB]
Fetched 188kB in 1s (183kB/s)
Selecting previously deselected package libsensors4.
(Reading database ... 134714 files and directories currently installed.)
Unpacking libsensors4 (from .../libsensors4_1%3a3.0.2-2ubuntu4_i386.deb) ...
Selecting previously deselected package lm-sensors.
Unpacking lm-sensors (from .../lm-sensors_1%3a3.0.2-2ubuntu4_i386.deb) ...
Processing triggers for man-db ...
Setting up libsensors4 (1:3.0.2-2ubuntu4) ...
.udevdb or .udev presence implies active udev. Aborting MAKEDEV invocation.

Creating config file /etc/sensors3.conf with new version

Setting up lm-sensors (1:3.0.2-2ubuntu4) ...

Processing triggers for libc6 ...
ldconfig deferred processing now taking place
sara@sara-desktop:~$ sudo nano
sara@sara-desktop:~$ chmod 755 mkdev.sh
chmod: changing permissions of `mkdev.sh': Operation not permitted
sara@sara-desktop:~$ sudo chmod 755 mkdev.sh
sara@sara-desktop:~$
sara@sara-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
sara@sara-desktop:~$ sudo sensors-detect
# sensors-detect revision 5249 (2008-05-11 22:56:25 +0200)

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...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7

We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no): yes
Module loaded successfully.
If you have undetectable or unsupported I2C/SMBus 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): yes
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: SMBus I801 adapter at 0500 (i2c-0)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x4e
Probing for `National Semiconductor LM75'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `Analog Devices ADM1021'... No
Probing for `Analog Devices ADM1021A/ADM1023'... No
Probing for `Maxim MAX1617'... No
Probing for `Maxim MAX1617A'... No
Probing for `Maxim MAX1668'... No
Probing for `Maxim MAX1805'... No
Probing for `Maxim MAX1989'... No
Probing for `Maxim MAX6655/MAX6656'... No
Probing for `TI THMC10'... No
Probing for `National Semiconductor LM84'... No
Probing for `Genesys Logic GL523SM'... No
Probing for `Onsemi MC1066'... No
Probing for `Maxim MAX1619'... No
Probing for `National Semiconductor LM82/LM83'... No
Probing for `Maxim MAX6659'... No
Probing for `Maxim MAX6680/MAX6681'... No
Probing for `National Semiconductor LM64'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `ITE IT8201R/IT8203R/IT8206R/IT8266R'... Yes
(confidence 6, not a hardware monitoring chip)
Probing for `Fintek F75111R/RG/N (GPIO)'... No
Probing for `Fintek F75121R/F75122R/RG (VID+GPIO)'... No
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No

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 `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 `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... Yes
Found `ITE IT8712F Super IO Sensors' Success!
(address 0x290, driver `it87')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No

Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no): yes
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD K10 thermal sensors... No
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: yes

Driver `it87' (should be inserted):
Detects correctly:
* ISA bus, address 0x290
Chip `ITE IT8712F Super IO Sensors' (confidence: 9)

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

To load everything that is needed, add this to /etc/modules:

#----cut here----
# Chip drivers
it87
#----cut here----

Do you want to add these lines automatically? (yes/NO)yes
sara@sara-desktop:~$

[miegiel]

hi i need help with this my fan speeds al over the shop, so i tried installing lm-sensors and got this output... what to do next?

1st of all, lm-sensors is only a monitoring program, it doesn't control your fan speed.

You can open /etc/modules in a text editor to make sure your it87 is there. If it isn't just add it (you'll need root rights to edit it). The modules file gets read during boot up, to read the sensor's values run sensors in a terminal.

[limejuice]

If you have Intel i7 chip and 1366 mobo, see this thread http://ubuntuforums.org/showthread.php?t=1056681


This said I needed to get lm-sensors 3.1.0 and build it from source. The current version in the Ubuntu repository for 09.04 release is 3.0.2.

However, you only need 3.1.0 to get sensors-detect to recognize the correct modules for you.
Here are the correct modules for i7. This works even with 3.0.2 lm-sensors.


#Chip drivers
coretemp
w83627ehf force_id=0x8860

[Feelin_froggy8877]

I cannot get past "sudo sensors-detect" 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
http://www.lm-sensors.org/wiki/FAQ/Chapter3 for further information.
If you find out what chips are on your board, check
http://www.lm-sensors.org/wiki/Devices for driver status.

k-dawg@k-dawg-desktop:~$ sudo lshw
k-dawg-desktop
description: Desktop Computer
product: OptiPlex GX270
vendor: Dell Computer Corporation
width: 32 bits
capabilities: smbios-2.3 dmi-2.3 smp-1.4 smp
configuration: administrator_password=enabled boot=normal chassis=desktop cpus=1 power-on_password=enabled uuid=44454C4C-0000-1020-8020-80C04F202020
*-core
description: Motherboard
product: 0CG566
vendor: Dell Computer Corp.
physical id: 0
serial: ..CN1374046O058I.
*-firmware
description: BIOS
vendor: Dell Computer Corporation
physical id: 0
version: A07 (06/26/2006)
size: 64KiB
capacity: 448KiB
capabilities: pci pnp apm upgrade shadowing escd cdboot bootselect edd int13floppytoshiba int5printscreen int9keyboard int14serial int17printer acpi usb agp ls120boot biosbootspecification netboot
*-cpu
description: CPU
product: Intel(R) Pentium(R) 4 CPU 2.40GHz
vendor: Intel Corp.
physical id: 400
bus info: cpu@0
version: 15.2.9
slot: Microprocessor
size: 2400MHz
capacity: 3600MHz
width: 32 bits
clock: 800MHz
capabilities: boot fpu fpu_exception wp 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 pebs bts cid xtpr
configuration: id=1
*-cache:0
description: L1 cache
physical id: 700
size: 8KiB
capacity: 16KiB
capabilities: internal write-back data
*-cache:1
description: L2 cache
physical id: 701
size: 512KiB
capacity: 512KiB
capabilities: internal varies unified
*-logicalcpu:0
description: Logical CPU
physical id: 1.1
width: 32 bits
capabilities: logical
*-logicalcpu:1
description: Logical CPU
physical id: 1.2
width: 32 bits
capabilities: logical
*-memory
description: System Memory
physical id: 1000
slot: System board or motherboard
size: 1536MiB
*-bank:0
description: DIMM SDRAM Synchronous 333 MHz (3.0 ns)
physical id: 0
slot: DIMM_1
size: 256MiB
width: 64 bits
clock: 333MHz (3.0ns)
*-bank:1
description: DIMM SDRAM Synchronous 333 MHz (3.0 ns)
physical id: 1
slot: DIMM_2
size: 512MiB
width: 64 bits
clock: 333MHz (3.0ns)
*-bank:2
description: DIMM SDRAM Synchronous 333 MHz (3.0 ns)
physical id: 2
slot: DIMM_3
size: 256MiB
width: 64 bits
clock: 333MHz (3.0ns)
*-bank:3
description: DIMM SDRAM Synchronous 333 MHz (3.0 ns)
physical id: 3
slot: DIMM_4
size: 512MiB
width: 64 bits
clock: 333MHz (3.0ns)
*-pci
description: Host bridge
product: 82865G/PE/P DRAM Controller/Host-Hub Interface
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 02
width: 32 bits
clock: 33MHz
configuration: driver=agpgart-intel module=intel_agp
*-pci:0
description: PCI bridge
product: 82865G/PE/P PCI to AGP Controller
vendor: Intel Corporation
physical id: 1
bus info: pci@0000:00:01.0
version: 02
width: 32 bits
clock: 66MHz
capabilities: pci bus_master
*-display
description: VGA compatible controller
product: NV18 [GeForce4 MX 440 AGP 8x]
vendor: nVidia Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a2
width: 32 bits
clock: 66MHz
capabilities: pm agp agp-3.0 bus_master cap_list
configuration: driver=nvidia latency=248 maxlatency=1 mingnt=5 module=nvidia
*-usb:0
description: USB Controller
product: 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1
vendor: Intel Corporation
physical id: 1d
bus info: pci@0000:00:1d.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: bus_master
configuration: driver=uhci_hcd latency=0 module=uhci_hcd
*-usb:1
description: USB Controller
product: 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2
vendor: Intel Corporation
physical id: 1d.1
bus info: pci@0000:00:1d.1
version: 02
width: 32 bits
clock: 33MHz
capabilities: bus_master
configuration: driver=uhci_hcd latency=0 module=uhci_hcd
*-usb:2
description: USB Controller
product: 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3
vendor: Intel Corporation
physical id: 1d.2
bus info: pci@0000:00:1d.2
version: 02
width: 32 bits
clock: 33MHz
capabilities: bus_master
configuration: driver=uhci_hcd latency=0 module=uhci_hcd
*-usb:3
description: USB Controller
product: 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4
vendor: Intel Corporation
physical id: 1d.3
bus info: pci@0000:00:1d.3
version: 02
width: 32 bits
clock: 33MHz
capabilities: bus_master
configuration: driver=uhci_hcd latency=0 module=uhci_hcd
*-usb:4
description: USB Controller
product: 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller
vendor: Intel Corporation
physical id: 1d.7
bus info: pci@0000:00:1d.7
version: 02
width: 32 bits
clock: 33MHz
capabilities: pm debug bus_master cap_list
configuration: driver=ehci_hcd latency=0 module=ehci_hcd
*-pci:1
description: PCI bridge
product: 82801 PCI Bridge
vendor: Intel Corporation
physical id: 1e
bus info: pci@0000:00:1e.0
version: c2
width: 32 bits
clock: 33MHz
capabilities: pci bus_master
*-multimedia
description: Multimedia audio controller
product: SB Audigy
vendor: Creative Labs
physical id: 8
bus info: pci@0000:02:08.0
version: 04
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: driver=EMU10K1_Audigy latency=64 maxlatency=20 mingnt=2 module=snd_emu10k1
*-firewire
description: FireWire (IEEE 1394)
product: SB Audigy FireWire Port
vendor: Creative Labs
physical id: 8.2
bus info: pci@0000:02:08.2
version: 04
width: 32 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: driver=ohci1394 latency=64 maxlatency=4 mingnt=2 module=ohci1394
*-network
description: Ethernet interface
product: 82540EM Gigabit Ethernet Controller
vendor: Intel Corporation
physical id: c
bus info: pci@0000:02:0c.0
logical name: eth0
version: 02
serial: 00:1a:a0:aa:03:0f
size: 100MB/s
capacity: 1GB/s
width: 32 bits
clock: 66MHz
capabilities: pm pcix msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000 driverversion=7.3.21-k3-NAPI duplex=full firmware=N/A ip=98.240.112.82 latency=64 link=yes mingnt=255 module=e1000 multicast=yes port=twisted pair speed=100MB/s
*-isa
description: ISA bridge
product: 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:00:1f.0
version: 02
width: 32 bits
clock: 33MHz
capabilities: isa bus_master
configuration: latency=0
*-ide:0
description: IDE interface
product: 82801EB/ER (ICH5/ICH5R) IDE Controller
vendor: Intel Corporation
physical id: 1f.1
bus info: pci@0000:00:1f.1
logical name: scsi0
logical name: scsi1
version: 02
width: 32 bits
clock: 33MHz
capabilities: ide bus_master emulated
configuration: driver=ata_piix latency=0
*-disk:0
description: ATA Disk
product: QUANTUM FIREBALL
vendor: Quantum
physical id: 0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: APL.
serial: 052123205633
size: 19GiB (20GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=81108110
*-volume:0
description: Windows NTFS volume
physical id: 1
bus info: scsi@0:0.0.0,1
logical name: /dev/sda1
version: 3.1
serial: 8074442b-808b-9d4a-94dd-c5dfffc703e5
size: 10001MiB
capacity: 10001MiB
capabilities: primary bootable ntfs initialized
configuration: clustersize=4096 created=2009-07-25 11:51:43 filesystem=ntfs label=Microshit state=clean
*-volume:1
description: Extended partition
physical id: 2
bus info: scsi@0:0.0.0,2
logical name: /dev/sda2
size: 9467MiB
capacity: 9467MiB
capabilities: primary extended partitioned partitioned:extended
*-logicalvolume
description: Linux filesystem partition
physical id: 5
logical name: /dev/sda5
logical name: /
capacity: 9467MiB
configuration: mount.fstype=ext3 mount.options=rw,relatime,errors=remount-ro,data=ordered state=mounted
*-disk:1
description: ATA Disk
product: Maxtor 6Y120P0
vendor: Maxtor
physical id: 1
bus info: scsi@0:0.1.0
logical name: /dev/sdb
version: YAR4
serial: Y33YD2BE
size: 114GiB (122GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=000784c4
*-volume:0
description: EXT3 volume
vendor: Linux
physical id: 1
bus info: scsi@0:0.1.0,1
logical name: /dev/sdb1
version: 1.0
serial: 63fc02f9-c191-4ec9-bd2c-0afd3eddd597
size: 4094MiB
capacity: 4094MiB
capabilities: primary bootable journaled extended_attributes large_files ext3 ext2 initialized
configuration: created=2009-07-25 17:56:26 filesystem=ext3 label=AntiX modified=2009-08-30 23:36:45 mounted=2009-08-30 23:36:45 state=clean
*-volume:1
description: Extended partition
physical id: 2
bus info: scsi@0:0.1.0,2
logical name: /dev/sdb2
size: 110GiB
capacity: 110GiB
capabilities: primary extended partitioned partitioned:extended
*-logicalvolume:0
description: W95 FAT32 partition
physical id: 5
logical name: /dev/sdb5
logical name: /media/myshit
capacity: 101GiB
configuration: mount.fstype=vfat mount.options=rw,fmask=0000,dmask=0000,allow_utime =0022,codepage=cp437,iocharset=utf8 state=mounted
*-logicalvolume:1
description: Linux filesystem partition
physical id: 6
logical name: /dev/sdb6
capacity: 2933MiB
*-logicalvolume:2
description: Linux swap / Solaris partition
physical id: 7
logical name: /dev/sdb7
capacity: 2557MiB
capabilities: nofs
*-logicalvolume:3
description: Linux filesystem partition
physical id: 8
logical name: /dev/sdb8
capacity: 3851MiB
*-cdrom
description: CD-R/CD-RW writer
physical id: 2
bus info: scsi@1:0.0.0
logical name: /dev/cdrom
logical name: /dev/cdrw
logical name: /dev/scd0
logical name: /dev/sr0
capabilities: audio cd-r cd-rw
configuration: status=nodisc
*-disk:2
description: ATA Disk
product: WDC WD100EB-00BH
vendor: Western Digital
physical id: 3
bus info: scsi@1:0.1.0
logical name: /dev/sdc
version: 15.1
serial: WD-WMA713523734
size: 9541MiB (10GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=00730072
*-volume
description: EXT3 volume
vendor: Linux
physical id: 1
bus info: scsi@1:0.1.0,1
logical name: /dev/sdc1
version: 1.0
serial: d498af98-c9af-411b-aeb4-4942469e8d9d
size: 9538MiB
capacity: 9538MiB
capabilities: primary bootable journaled large_files ext3 ext2 initialized
configuration: created=2009-07-26 19:03:58 filesystem=ext3 label=Sabayon modified=2009-08-30 23:36:56 mounted=2009-08-30 23:36:55 state=clean
*-ide:1
description: IDE interface
product: 82801EB (ICH5) SATA Controller
vendor: Intel Corporation
physical id: 1f.2
bus info: pci@0000:00:1f.2
version: 02
width: 32 bits
clock: 66MHz
capabilities: ide bus_master
configuration: driver=ata_piix latency=0
*-serial
description: SMBus
product: 82801EB/ER (ICH5/ICH5R) SMBus Controller
vendor: Intel Corporation
physical id: 1f.3
bus info: pci@0000:00:1f.3
version: 02
width: 32 bits
clock: 33MHz
configuration: driver=i801_smbus latency=0 module=i2c_i801
*-network DISABLED
description: Ethernet interface
physical id: 1
logical name: pan0
serial: 76:45:b1:89:5d:86
capabilities: ethernet physical
configuration: broadcast=yes driver=bridge driverversion=2.3 firmware=N/A link=yes multicast=yes

[jlh68]

On my Laptop, I can only get one temperature to show: ACPI THRM CPU and lmsensors temp1, actually they are both reporting the same thing. I do not get my HDD temp or any other data. I can get my HDD temp by using the following command "sudo hddtemp /dev/sda", so I know it is available. I do get the HDD temp on my desktop.

OK, please help me to get more data from lm-sensors.
thanks

[abdusamed]

can u recreate this thread.. because the thread is old..and mkdev isn't used now.. i REALLY want to slow my fan DOWN in xubuntu 9.04


sensors-detect doesn'[t detect anny sensors what so ever in my old ***** p4.

[miegiel]

can u recreate this thread.. because the thread is old..and mkdev isn't used now.. i REALLY want to slow my fan DOWN in xubuntu 9.04


sensors-detect doesn'[t detect anny sensors what so ever in my old ***** p4.

AFAIK you don't need to run that mkdev script anymore. Just install > detect > add detected sensor to /etc/modules > reboot.

sudo apt-get install lm-sensors
sudo sensors-detect
sudo nano /etc/modules

Also, lm-sensors is just a monitor. So it will only tell you your fan speed and not change the speed. I normally set the fan speed in the BIOS, but not every BIOS gives you the option to change it.

[whitethorn]

AFAIK you don't need to run that mkdev script anymore. Just install > detect > add detected sensor to /etc/modules > reboot.

sudo apt-get install lm-sensors
sudo sensors-detect
sudo nano /etc/modules

Also, lm-sensors is just a monitor. So it will only tell you your fan speed and not change the speed. I normally set the fan speed in the BIOS, but not every BIOS gives you the option to change it.

Once you have lm-sensors installed and after running sensors-detect. When you run sensors if it shows some fan speeds then running pwmconfig might be able to let you control your fan speeds. pwmconfig is pretty straightforward. Afterwards you only need a couple small steps to get fancontrol to start on boot and you can control your fanspeeds. Maybe I should write a howto about it :)

[abdusamed]

okay..thanks..ill give it a try... and yes.. the module did open.. now to remember what to do :D

[mr clark25]

this guide is great!

i should know this, but i dont.... how do you change a file when the owner is root? (need to do this to complete step 4 where you paste the modules to the modules file located in /ect/modules)
so, how do you do this? do you use sudo in the terminal?

im new to this kind of thing, but i really want to do this. i just cant save my changes in modules.

PLZ HELP!

[Penguin Guy]

this guide is great!

i should know this, but i dont.... how do you change a file when the owner is root? (need to do this to complete step 4 where you paste the modules to the modules file located in /ect/modules)
so, how do you do this? do you use sudo in the terminal?

im new to this kind of thing, but i really want to do this. i just cant save my changes in modules.

PLZ HELP!
Run gksu gedit /etc/modules, and just paste it in.

[mr clark25]

thanks so much for you help! i now now that my processor runs nice and cool with all stock settings and cooling.

output:

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

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

[swalker23]

Hopefully someone can help me. I've installed lm_sensors on intrepid and jaunty from source on my i7 setup and didn't have any problems. Lm-sensors detected all my cores,voltages, and etc. I just did a fresh install of Kubuntu 9.1 Koala and the first thing I did was install lm-sensors from source 3.1.1. Everything installed fine no hang ups on make or install and after running senors detect I ran sensors. This is what it gave me:
acpitz-virtual-0
Adapter: Virtual device
temp1: +25.0°C (crit = +6280.3°C)


How can I get my temps to show? I've been googling but didn't have any luck in solving my problem. My motherboard is a EVGA classified. I'm still a linux noob so bare with me.

Edit:
Please disregard my above question I got it working. I will put my solution down for anyone else experiencing difficulties.
Copy and paste the below into /etc/modules and reboot after you save. I pasted it hours ago and just didn't reboot.
#Chip drivers
coretemp
w83627ehf force_id=0x8860

[mr clark25]

someone might have said this already, but this works great with the command: "watch"
this makes it re-fresh every 2 seconds.

just enter:
watch sensors

[jsa13]

Running "sensors-detect" identified w83627hf, but modprobe wouldn't insert it. Checking dmesg was the key.

For 9.10, I had to add kernel option "acpi_enforce_resources=lax" to /etc/default/grub (2.x, or /boot/grub/menu.lst w/ grub 1.x).

Then w83627hf for my abit K8 loaded w/o issue. Setting up the fan speeds w/ "pwmconfig" afterward was easy.

[nishant.singh28]

ummm...a stupid question but what do the temp values stand for. I have a Dell Studio 1555 notebook with the GPU embedded onto the motherboard( all new laptops have them on the motherboard ). It would be appreciable if someone could tell me what the temp temperature signifies? :KS

[miegiel]

ummm...a stupid question but what do the temp values stand for. I have a Dell Studio 1555 notebook with the GPU embedded onto the motherboard( all new laptops have them on the motherboard ). It would be appreciable if someone could tell me what the temp temperature signifies? :KS

Can't tell really, without the output of
sensors
It could be the CPU temp or the chipset temp or both.

[nishant.singh28]

Can't tell really, without the output of
sensorsIt could be the CPU temp or the chipset temp or both.

acpitz-virtual-0
Adapter: Virtual device
temp1: +54.0°C (crit = +100.0°C)
temp2: +55.0°C (crit = +100.0°C)
temp3: +57.0°C (crit = +100.0°C)

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

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


Now??

[miegiel]

acpitz-virtual-0
Adapter: Virtual device
temp1: +54.0°C (crit = +100.0°C)
temp2: +55.0°C (crit = +100.0°C)
temp3: +57.0°C (crit = +100.0°C)

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

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


Now??
The coretemp-isa-000X sensors sense the temperatures of the cores of intel dual core CPUs (1 for each core). I think acpitz-virtual-0 is the sensor of your laptop's motherboard, probably northbridge (with the graphics core in it), southbridge and a external CPU sensor.

If you can see the temperatures in the BIOS (my laptop BIOS doesn't show them, but my desktop BIOS does) you can compare the values there with the values you get from lm-sensors. If you let your laptop run idle for a few min and then reboot into the BIOS the temperatures will be more or less the same.

You can also stress different parts and see which temperature increases. For example glxgears (terminal) will stress your CPU and graphics core. And you might be able to tell which temperature is the southbridge by stressing your network (is likely connected to your southbridge) or copying files on your disk.

[nishant.singh28]

The coretemp-isa-000X sensors sense the temperatures of the cores of intel dual core CPUs (1 for each core). I think acpitz-virtual-0 is the sensor of your laptop's motherboard, probably northbridge (with the graphics core in it), southbridge and a external CPU sensor.

If you can see the temperatures in the BIOS (my laptop BIOS doesn't show them, but my desktop BIOS does) you can compare the values there with the values you get from lm-sensors. If you let your laptop run idle for a few min and then reboot into the BIOS the temperatures will be more or less the same.

You can also stress different parts and see which temperature increases. For example glxgears (terminal) will stress your CPU and graphics core. And you might be able to tell which temperature is the southbridge by stressing your network (is likely connected to your southbridge) or copying files on your disk.


Well I figured it out....temp1 is GPU, temp2 is the Southbridge and temp3 the Northbridge...thanks!!!:)