LinuxQuestions.org - How to access CPU, Harddrive and GPU temperature sensors ?

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - How to access CPU, Harddrive and GPU temperature sensors ? (https://www.linuxquestions.org/questions/linux-hardware-18/how-to-access-cpu-harddrive-and-gpu-temperature-sensors-4175446630/)

How to access CPU, Harddrive and GPU temperature sensors ?

Hello all,
Recently i have been using ubuntu 11.04 and using psensors and jupiter to mainyain and monitor my hardware temperatures.

But yesterday i install Debain 6.0.6 Squeeze.

I installed lm-sensors in debian but sensors are not able to fetch correct temperatues.

here's the output of "sensors-detect"

Code:

# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)

# System: Dell Inc. XPS L501X

# Board: Dell Inc. 0NYTH5



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 Family 10h thermal sensors...                          No

AMD Family 11h thermal sensors...                          No

Intel Core family thermal sensor...                        No

Intel Atom thermal sensor...                                No

Intel AMB FB-DIMM thermal sensor...                        No

VIA C7 thermal sensor...                                    No

VIA Nano thermal sensor...                                  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/Nuvoton/Fintek'...              No

Trying family `ITE'...                                      No

Probing for Super-I/O at 0x4e/0x4f

Trying family `National Semiconductor'...                  Yes

Found unknown chip with ID 0x8502



Some systems (mainly servers) implement IPMI, a set of common interfaces

through which system health data may be retrieved, amongst other things.

We first try to get the information from SMBIOS. If we don't find it

there, 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): 

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

Found unknown SMBus adapter 8086:3b30 at 0000:00:1f.3.

Sorry, no supported PCI bus adapters found.



Next adapter: intel drm CRTDDC_A (i2c-0)

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



Next adapter: intel drm LVDSDDC_C (i2c-1)

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

Client found at address 0x28

Probing for `National Semiconductor LM78'...                No

Probing for `National Semiconductor LM79'...                No

Probing for `National Semiconductor LM80'...                No

Probing for `Winbond W83781D'...                            No

Probing for `Winbond W83782D'...                            No

Probing for `Winbond W83627HF'...                          No

Probing for `Winbond W83627EHF'...                          No

Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No

Probing for `Asus AS99127F (rev.1)'...                      No

Probing for `Asus AS99127F (rev.2)'...                      No

Probing for `Asus ASB100 Bach'...                          No

Probing for `Analog Devices ADM1029'...                    No

Probing for `ITE IT8712F'...                                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: intel drm HDMIC (i2c-2)

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



Next adapter: DPDDC-C (i2c-3)

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



Sorry, no sensors were detected.

Either your system has no sensors, or they are not supported, or

they are connected to an I2C or SMBus adapter that is not

supported. If you find out what chips are on your board, check

http://www.lm-sensors.org/wiki/Devices for driver status.

I tried searching internet for solution but none of them works!
Can anyone help me?

Output of "uname -a" is

Code:

Linux unkn0wn-XPS 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64 GNU/Linux

I haven't tried this yet, http://forums.gentoo.org/viewtopic-t-894334.html Because i didn't understand it.

Thanks.

Try running as root

Quote:

#sensors

Hi

I don't know about lm-sensors but I'm I've got an information that "could" help you.
Dell has changed some things in the 12G generation of their servers (Rx20) that notably disable the access to BIOS parameters. The only way to get these data is to install openmanage... Maybe that's the same for the temperatures ?
Maybe you should ask them about that ?

Fyi, here is the link to my thread about that:
http://en.community.dell.com/support....aspx#20223201

hope it helps...
Bests
Julien

Quote:

Originally Posted by EDDY1 (Post 4875371)

Try running as root

Thanks for replying,

I already ran this many times, it continues to give me false values,

Code:

acpitz-virtual-0

Adapter: Virtual device

temp1:        +26.8°C  (crit = +100.0°C)

temp2:        +0.0°C  (crit = +100.0°C)

Some one told me to install lm-sensors from Debian wheezy. I did.
here's the output of "sudo sensors-detect"

Code:

sizil@unkn0wn-XPS:~$ sudo sensors-detect

# sensors-detect revision 6031 (2012-03-07 17:14:01 +0100)

# System: Dell Inc. XPS L501X [A08] (laptop)

# Board: Dell Inc. 0NYTH5



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

WARNING: All config files need .conf: /etc/modprobe.d/alsa-base, it will be ignored in a future release.

Module cpuid loaded successfully.

Silicon Integrated Systems SIS5595...                      No

VIA VT82C686 Integrated Sensors...                          No

VIA VT8231 Integrated Sensors...                            No

AMD K8 thermal sensors...                                  No

AMD Family 10h thermal sensors...                          No

AMD Family 11h thermal sensors...                          No

AMD Family 12h and 14h thermal sensors...                  No

AMD Family 15h thermal sensors...                          No

AMD Family 15h power sensors...                            No

Intel digital thermal sensor...                            Success!

    (driver `coretemp')

Intel AMB FB-DIMM thermal sensor...                        No

VIA C7 thermal sensor...                                    No

VIA Nano thermal sensor...                                  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/ITE'...              No

Trying family `SMSC'...                                    No

Trying family `VIA/Winbond/Nuvoton/Fintek'...              No

Trying family `ITE'...                                      No

Probing for Super-I/O at 0x4e/0x4f

Trying family `National Semiconductor/ITE'...              Yes

Found unknown chip with ID 0x8502



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

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 3400/5 Series (PCH)

WARNING: All config files need .conf: /etc/modprobe.d/alsa-base, it will be ignored in a future release.

Module i2c-dev loaded successfully.



Next adapter: intel drm CRTDDC_A (i2c-0)

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



Next adapter: intel drm LVDSDDC_C (i2c-1)

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

Client found at address 0x28

Probing for `National Semiconductor LM78'...                No

Probing for `National Semiconductor LM79'...                No

Probing for `National Semiconductor LM80'...                No

Probing for `National Semiconductor LM96080'...            No

Probing for `Winbond W83781D'...                            No

Probing for `Winbond W83782D'...                            No

Probing for `Winbond W83627HF'...                          No

Probing for `Winbond W83627EHF'...                          No

Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No

Probing for `Asus AS99127F (rev.1)'...                      No

Probing for `Asus AS99127F (rev.2)'...                      No

Probing for `Asus ASB100 Bach'...                          No

Probing for `Analog Devices ADM1029'...                    No

Probing for `ITE IT8712F'...                                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: intel drm HDMIC (i2c-2)

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



Next adapter: DPDDC-C (i2c-3)

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



Now follows a summary of the probes I have just done.

Just press ENTER to continue: 



Driver `coretemp':

  * Chip `Intel digital thermal sensor' (confidence: 9)



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

#----cut here----

# Chip drivers

coretemp

#----cut here----

If you have some drivers built into your kernel, the list above will

contain too many modules. Skip the appropriate ones!



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

Successful!



Monitoring programs won't work until the needed modules are

loaded. You may want to run '/etc/init.d/kmod start'

to load them.



Unloading i2c-dev... OK

Unloading cpuid... OK

Few things changed there, but no real progress.

And akiuni, that could be true but then how come psensor was working in previous distribution and i am able to correctly monitor my HDD temp on debian now!

coretemp will tell you the temperatures of the CPU cores. Just modprobe it and runs 'sensors' to get the temperature.

For the GPU, with an nvidia card, the proprietary drivers can get the GPU temp.

For the HDD, you can get the temperature using 'smartctl -A /dev/sda'.

Quote:

Originally Posted by unkn(0)wn (Post 4875439)

And akiuni, that could be true but then how come psensor was working in previous distribution and i am able to correctly monitor my HDD temp on debian now!

"Previous distro" is newer than Debian Squeeze. Squeeze does not have psensor in its repos.
You have to install at least Debian Wheezy (now testing in freeze, soon the next stable) to install it from the repos.

Code:

$ apt-cache policy psensor

psensor:

  Installed: (none)

  Candidate: 0.6.2.17-2+b1

  Version table:

    0.7.0.3-1 0

          1 http://ftp.debian.org/debian/ unstable/main i386 Packages

    0.6.2.17-2+b1 0

        500 http://ftp.debian.org/debian/ testing/main i386 Packages

Although from its description:

Code:

It can monitor: 

 * the temperature of the motherboard and CPU sensors (using lm-sensors). 

 * the temperature of the NVidia GPUs (using XNVCtrl). 

 * the temperature of the Hard Disk Drives (using hddtemp). 

 * the rotation speed of the fans (using lm-sensors). 

 * the sensors of a remote computer (using psensor-server).

it too uses lm-sensors, hddtemp - all of these are available in squeeze.

Quote:

Originally Posted by H_TeXMeX_H (Post 4875454)

I tried running

Code:

root@unkn0wn-XPS:/home/sizil# modprobe coretemp

WARNING: All config files need .conf: /etc/modprobe.d/alsa-base, it will be ignored in a future release.

FATAL: Error inserting coretemp (/lib/modules/2.6.32-5-amd64/kernel/drivers/hwmon/coretemp.ko): No such device

Whereas,

Code:

root@unkn0wn-XPS:/home/sizil# modinfo coretemp

filename:      /lib/modules/2.6.32-5-amd64/kernel/drivers/hwmon/coretemp.ko

license:        GPL

description:    Intel Core temperature monitor

author:        Rudolf Marek <r.marek@assembler.cz>

depends:        

vermagic:      2.6.32-5-amd64 SMP mod_unload modversions

I added something which took me to,

Code:

root@unkn0wn-XPS:/home/sizil# sensors

acpitz-virtual-0

Adapter: Virtual device

temp1:        +26.8°C  (crit = +100.0°C)

temp2:        +0.0°C  (crit = +100.0°C)



w83627ehf-isa-fff8

Adapter: ISA adapter

Vcore:        +2.04 V  (min =  +2.04 V, max =  +2.04 V)  ALARM

in1:          +2.04 V  (min =  +2.04 V, max =  +2.04 V)  ALARM

AVCC:        +4.08 V  (min =  +4.08 V, max =  +4.08 V)  ALARM

VCC:          +4.08 V  (min =  +4.08 V, max =  +4.08 V)  ALARM

in4:          +2.04 V  (min =  +2.04 V, max =  +2.04 V)  ALARM

in5:          +2.04 V  (min =  +2.04 V, max =  +2.04 V)  ALARM

in6:          +2.04 V  (min =  +2.04 V, max =  +2.04 V)  ALARM

3VSB:        +4.08 V  (min =  +4.08 V, max =  +4.08 V)  ALARM

Vbat:        +4.08 V  (min =  +4.08 V, max =  +4.08 V)  ALARM

in9:          +2.04 V  (min =  +2.04 V, max =  +2.04 V)  ALARM

fan1:          0 RPM  (min =    0 RPM, div = 128)  ALARM

fan2:          0 RPM  (min =    0 RPM, div = 128)  ALARM

fan3:          0 RPM  (min =    0 RPM, div = 128)  ALARM

temp1:        -1.0°C  (high =  -1.0°C, hyst =  -1.0°C)  ALARM  sensor = CPU diode

temp2:        +0.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = CPU diode

temp3:        +0.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = CPU diode

cpu0_vid:    +0.000 V

No original CPU Temp