Re: temperature
On Sunday 26 of February 2012 19:40:16 Camaleón wrote:
> On Tue, 21 Feb 2012 19:56:20 +0100, Zbigniew Komarnicki wrote:
> > which package to use to see the hardware temperature on AMD FX(tm)-6100
> > Six-Core Processor and GPU using Debian Squeeze, Linux 2.6.32-5-amd64
>
> "lm-sensors"? :-)
I have installed it, but it cannot detect the sensors of CPU (I was thinking
that) and GPU.
> I don't know if lm-sensors can read the temps for nvidia cards when using
> the closed source driver. Are you using nuvó or nvidia's own driver for
> your VGA card?
>
> (btw, nvidia driver provides an utility -nvidia-settings- to read the
> card temps)
I have the nouveau driver.
> > I have a water cooling system.
> >
> > I got:
> > # sensors
> > it8720-isa-0228
>
> It seems that you have only loaded one kernel module (it87). Did
> "sensors-detect" suggest any additional modules to load?
>
> (...)
Here is my output:
---------------------------
# sensors-detect
# sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
# System: Gigabyte Technology Co., Ltd. GA-990FXA-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 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'... Yes
Found `ITE IT8720F Super IO Sensors' Success!
(address 0x228, driver `it87')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/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 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): 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-piix4' for device 0000:00:14.0: ATI Technologies Inc
SB600/SB700/SB800 SMBus
Next adapter: NVIDIA i2c adapter 0 at 1:00.0 (i2c-0)
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 6 at 1:00.0 (i2c-1)
Do you want to scan it? (YES/no/selectively):
Next adapter: NVIDIA i2c adapter 8 at 1:00.0 (i2c-2)
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 `it87':
* ISA bus, address 0x228
Chip `ITE IT8720F Super IO Sensors' (confidence: 9)
To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
it87
#----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/module-init-tools start'
to load them.
>
> > fan1: 0 RPM (min = 0 RPM)
> > fan2: 0 RPM (min = 0 RPM)
> > fan3: 587 RPM (min = 0 RPM)
> > fan4: 0 RPM (min = 0 RPM)
>
> These are the detected fan sensors. As you're using a water cooling system,
> having only one fan enabled can be right but does this match with your
> current chassis configuration?
I do not know nothing about sensors before, because I started using it one
week ago to test my water cooling system.
I'm install also the Debian wheezy/sid and there no problem with the
temperatures of CPU and GPU. I had there 5 sensors of temperatures:
tepm1, temp2, ..., temp5, but after upgrade one day from linux-image-3.1 ...
to linux-image-3.2... my system cannot boot. It boot to some point and then
frozen and I'm waiting forever (system probably hang, I could not write the
details, because I remove the Debian testing). The new kernel in Debian
wheeze/sid cannot boot my system, so I install the stable version, but here no
sensors for GPU temperature.
> > temp1: +31.0°C (low = +127.0°C, high = +127.0°C) sensor =
> > thermistor temp2: +27.0°C (low = +127.0°C, high = +127.0°C)
> > sensor = thermal diode temp3: +27.0°C (low = +127.0°C, high =
> > +60.0°C) sensor = thermal diode
>
> And here are the detected temps. I'm not familiar with AMD micros but temp1
> can be for CPU, temp2 for the chipset and temp3 for the cabinet though they
> seem to be very low... Are these temps matching the BIOS values?
I checked these temperatures in BIOS and the first one is for 'Current System
Temperature', the second one is for 'Current CPU Temperature', and the third
sensor I don't know what for is, because in BIOS only above two temperatures
are showed.
I install today also the proprietary driver form www.nvidia.com, and as you
told me the utility -nvidia-settings, show me the temperature.
Thank you very much for your help. I do not correctly understand the sensors
temp1, temp2 temp3 in Debian stable version, because the name temp1, temp2 and
temp3 do say nothing for my on the first look. It will by better if the name
were more descriptive e.g. CPU_temp, SYS_temp or something like that.
Thank you very much for your time and help.
>
> Greetings,
Greetings,
Zbigniew
Reply to: