Tag Archives: cpu volt
Température du CPU sous Linux Ubuntu
Aujourd'hui, ma carte SAS (une rocketraid 2680) c'est mise à biper. Immédiatement alerter, j'ai donc cherché à savoir pourquoi.
Ma piste s'est tout de suite diriger vers une surchauffe de la carte SAS mais également un surchauffe du processeur.
Pour savoir la température de mon processeur j'ai utilisé "lm_sensors" qui est disponible via le gestionnaire de paquets.
Installation de lm_sensors
Pour installer "lm_sensors", il suffit d'utiliser le gestionnaire de paquets:
apt-get install lm-sensors
Configuration de lm_sensors
Pour configurer "lm_sensors", il suffit de taper la commande suivante:
sensors-detect
Ce qui retourne:
# sensors-detect revision 5946 (2011-03-23 11:54:44 +0100)
# System: ASUSTeK Computer INC. M3N WS
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): yes
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... Success!
(driver `k8temp')
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
Intel digital 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): yes
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 IT8716F 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/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): yes
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-nforce2' for device 0000:00:01.1: nVidia Corporation nForce SMBus (MCP78S)
Module i2c-dev loaded successfully.
Next adapter: SMBus nForce2 adapter at 1c00 (i2c-0)
Do you want to scan it? (YES/no/selectively): yes
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 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD 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): yes
Client found at address 0x49
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Analog Devices ADT7410'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `National Semiconductor LM73'... No
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `SMSC EMC1023'... No
Probing for `SMSC EMC1043'... No
Probing for `SMSC EMC1053'... No
Probing for `SMSC EMC1063'... 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-2)
Do you want to scan it? (YES/no/selectively): yes
Next adapter: NVIDIA i2c adapter (i2c-3)
Do you want to scan it? (YES/no/selectively): yes
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `it87':
* ISA bus, address 0x290
Chip `ITE IT8716F Super IO Sensors' (confidence: 9)
Driver `k8temp' (autoloaded):
* Chip `AMD K8 thermal 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 'service module-init-tools start'
to load them.
Unloading i2c-dev... OK
Unloading cpuid... OK
Veuillez noter qu'à la question "Do you want to add these lines automatically to /etc/modules?" il faudra répondre "Yes". Celle-ci permet de mettre à jour certains modules et drivers afin de pouvoir récupérer les informations liées aux sondes spécifiques de votre hardware.
Pour les activer, vous pouvez tapez:
modprobe coretemp
modprobe it87
Récupération de la température du processeur
Une fois "lm_sensors" installé et configuré, il ne reste plus qu'à lancer la commande suivante pour récupérer les informations (voltage, température, …) de votre matériel:
sensors
Ce qui retournera:
acpitz-virtual-0
Adapter: Virtual device
temp1: +40.0°C (crit = +75.0°C)
atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage: +1.23 V (min = +0.85 V, max = +1.60 V)
+12V Voltage: +12.22 V (min = +10.20 V, max = +13.80 V)
+5V Voltage: +4.92 V (min = +4.50 V, max = +5.50 V)
+3.3V Voltage: +3.34 V (min = +2.97 V, max = +3.63 V)
CPU_FAN FAN Speed: 0 RPM (min = 800 RPM)
CHA_FAN1 FAN Speed: 1167 RPM (min = 800 RPM)
PWR_FAN FAN Speed: 3534 RPM (min = 800 RPM)
CHA_FAN2 FAN Speed: 1192 RPM (min = 800 RPM)
CPU Temperature: +25.0°C (high = +60.0°C, crit = +95.0°C)
MB Temperature: +30.0°C (high = +45.0°C, crit = +95.0°C)
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp: +24.0°C
Core1 Temp: +25.0°C
ZeM.fr est un blog que j'ai lancé afin de stocker les informations qui me semblent importantes.