[résolu]surveiller temp MB et CPU

[juddix]

salut a tous, je cherche un logiciel pour surveiller la températue de ma Cate mère ( ASUS P4S8X-X ) et mon CPU

 

j' ai installé lm-sensors qui sait aussitot mit dans /etc/init.d

 

il me fesait biper la carte mère a tout va

allé je vire de /etc/init.d/

 

sinon, j' ai installé Ksensors, et lui apparament détecte mal mon matos et confond la Carte mère et le CPU

j' ai lancé 2 glxgears pour faire monter le CPU, et il se trouve c' est la jauge M/B qui monte a 44°C

donc, il confond belle et bien le CPU et la MB

 

sinon, quand je lance sansors tout cour, voila

 # sensors
MT20xx universal-i2c-1-60
Adapter: bt878 #0 [sw]

tda9887-i2c-1-4b
Adapter: bt878 #0 [sw]

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

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

asb100-i2c-0-2d
Adapter: SiS96x SMBus adapter at 0xe600
VCore 1:   +1.60 V  (min =  +1.20 V, max =  +1.81 V)
+3.3V:	 +3.23 V  (min =  +2.96 V, max =  +3.63 V)
+5V:	   +5.03 V  (min =  +4.49 V, max =  +5.51 V)
+12V:	 +11.49 V  (min =  +9.55 V, max = +14.41 V)
-12V (reserved):
	  -12.01 V  (min =  -0.00 V, max =  -0.00 V)
-5V (reserved):
	   -5.04 V  (min =  -0.00 V, max =  -0.00 V)
CPU Fan:	 0 RPM  (min = 3994 RPM, div = 2)
Chassis Fan:
		 0 RPM  (min = 3994 RPM, div = 2)
Power Fan:   0 RPM  (min = 3994 RPM, div = 2)
M/B Temp:	+35°C  (high =   +80°C, hyst =   +75°C)
CPU Temp (Intel):
		 +29°C  (high =  +100°C, hyst =	+3°C)
Power Temp:
		 +30°C  (high =   +60°C, hyst =	+3°C)
CPU Temp (AMD):
		 +25°C  (high =   +80°C, hyst =   +75°C)
vid:	  +1.525 V  (VRM Version 9.0)
alarms:

vous avez des idéés ?

 

où un autre logiciel...

Modifié le 23 juillet 2006 par tourangeaux

[Invité tesgaz]

Salut,

 

tu as configurer les sensors ?

 

sensors-detect

 

 

sinon gkrellm qui marche pas mal

[juddix]

voila ce que dit sensors-detect:

 # sensors-detect 

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

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

We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): yes
Probing for PCI bus adapters...
Use driver `i2c-sis96x' for device 00:02.1: Silicon Integrated Systems SMBus Con troller
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-sis96x' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is already loaded.

We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).

Next adapter: bt878 #0 [sw]
Do you want to scan it? (YES/no/selectively): no

Next adapter: SiS96x SMBus adapter at 0xe600
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x08
Client found at address 0x10
Client at address 0x2d can not be probed - unload all client drivers first!
Client at address 0x48 can not be probed - unload all client drivers first!
Client at address 0x49 can not be probed - unload all client drivers first!
Client at address 0x50 can not be probed - unload all client drivers first!

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no): no

Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for `ITE 8702F Super IO Sensors'
 Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
 Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
 Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
 Failed! (0x68)
Probing for `Winbond W83627HF Super IO Sensors'
 Failed! (0x68)
Probing for `Winbond W83627THF Super IO Sensors'
 Failed! (0x68)
Probing for `Winbond W83637HF Super IO Sensors'
 Failed! (0x68)
Probing for `Winbond W83697HF Super IO Sensors'
 Failed! (0x68)
Probing for `Winbond W83697SF/UF Super IO PWM'
 Success... but not activated
Probing for `Winbond W83L517D Super IO'
 Failed! (0x68)

Do you want to scan for secondary Super I/O sensors? (YES/no): yes
Probing for `ITE 8702F Super IO Sensors'
 Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
 Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
 Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
 Failed! (skipping family)

Sorry, no chips were detected.
Either your sensors are not supported, or they are
connected to an I2C bus adapter that we do not support.
See doc/FAQ, doc/lm_sensors-FAQ.html, or
http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/lm_sensors-FAQ.html
(FAQ #4.24.3) for further information.
If you find out what chips are on your board, see
http://secure.netroedge.com/~lm78/newdrivers.html for driver status.

 

gkrellm

lui aussi inverse MB et CPU ( où c' est lm-sensors )

 

i2cset

# i2cset
Syntax: i2cset [-y] I2CBUS CHIP-ADDRESS DATA-ADDRESS VALUE [MODE]
	i2cset -V
 MODE is 'b[yte]' or 'w[ord]' (default b)
 I2CBUS is an integer
 Installed I2C busses:
i2c-1	   unknown		 bt878 #0 [sw]						   Algorithm unavailable
i2c-0	   unknown		 SiS96x SMBus adapter at 0xe600		  Algorithm unavailable

 

# acpi -V
No support for device type: thermal

 

Ubuntu 5.10 réglerais tout ça par hasard ?

[KewlCat]

man sensors

FILES

/etc/sensors.conf

The system wide configuration file. See sen-

sors.conf(5) for further details.

C'est dans le fichier /etc/sensors.conf que tu fais le lien entre ton sensor et le(s) label(s) affiché(s) en face des valeurs mesurées.

Chez moi aussi j'avais une inversion des températures MB / CPU avec le fichier de config par défaut, mais ça se règle très facilement

[juddix]

essai sous Archlinux avec sans passer par Ksensors, mais par

/usr/local/bin/sensors -s

 

Si je comprend bien il faut modifier /etc/sensors.conf

#

# This example was tested vs. Asus P4S333

#

chip "asb100-*"

set vrm 9.0

 

label in0 "VCore 1" |

set in0_min vid * 0.95 | Ne pas éditer

set in0_max vid * 1.05 |

 

label in1 "VCore 2" |

ignore in1 |

set in1_min vid * 0.95 | Ne pas éditer

set in1_max vid * 1.05 |

 

label in2 "+3.3V" |

set in2_min 3.3 * 0.95 | Ne pas éditer

set in2_max 3.3 * 1.05 |

 

label in3 "+5V" |

compute in3 1.68 * @ , @ / 1.68 |

set in3_min 5.0 * 0.95 | Ne pas éditer

set in3_max 5.0 * 1.05 |

 

label in4 "+12V" |

compute in4 3.8 * @ , @ / 3.8 |

set in4_min 12 * 0.90 | Ne pas éditer

set in4_max 12 * 1.10 |

 

label in5 "-12V (reserved)"

#ignore in5 | a décommenter ?

compute in5 -@ * 3.97 , -@ / 3.97

set in5_max -12 * 0.90

set in5_min -12 * 1.10

 

label in6 "-5V (reserved)"

#ignore in6 | a décommenter ?

compute in6 -@ * 1.666 , -@ / 1.666

set in6_max -5 * 0.95

set in6_min -5 * 1.05

 

label temp1 "M/B Temp"

set temp1_over 45 | a augmenter mais jusqu' a combien sans que ça soit critique ?

set temp1_hyst 40 | idem , over pour température et hyst pour historique ?

 

label temp2 "CPU Temp (Intel)"

#ignore temp2

set temp2_over 60 | a augmenter mais jusqu' a combien sans que ça soit critique ? Celeron 2.4Ghz

set temp2_hyst 50

 

# PWRTMP connector on P4S333, for external sensor

label temp3 "Power Temp" |

#ignore temp3 |

set temp3_over 45 | Power Temp correspond a quoi ?

set temp3_hyst 40 |

 

 

# Used for Athlon diode, ignore for P4S333

label temp4 "CPU Temp (AMD)" |

set temp4_over 60 |

set temp4_hyst 50 | a effacer, pas d AMD chez moi

#ignore temp4

 

label fan1 "CPU Fan"

set fan1_div 4

set fan1_min 2000 | a mettre a 0 , le ventillo tourne pas toujours quand le Celeron n' est pas soliciter

 

label fan2 "Chassis Fan"

set fan2_div 2

set fan2_min 4000 | Chassis Fan débrancher, sinon ça fait trop de bruit, a effacer où a commenter

 

label fan3 "Power Fan"

set fan3_div 2 | Power Fan , c' est a dire ?

set fan3_min 4000

 

Je testerais pas ce soir, je voudrais pas réveiller mon petit par des BIP des ma carte mère, due a une configuration de sensors.conf

/etc/sensors.conf est le seul fichier a configurer ?

 

voila les fichiers qui ont été installé par lm_sensors

# pacman -Ql lm_sensors

lm_sensors /etc/

lm_sensors /etc/sensors.conf

lm_sensors /usr/

lm_sensors /usr/bin/

lm_sensors /usr/bin/ddcmon

lm_sensors /usr/bin/decode-dimms.pl

lm_sensors /usr/bin/decode-edid.pl

lm_sensors /usr/bin/decode-vaio.pl

lm_sensors /usr/bin/decode-xeon.pl

lm_sensors /usr/bin/sensors

lm_sensors /usr/include/

lm_sensors /usr/include/sensors/

lm_sensors /usr/include/sensors/chips.h

lm_sensors /usr/include/sensors/error.h

lm_sensors /usr/include/sensors/sensors.h

lm_sensors /usr/lib/

lm_sensors /usr/lib/libsensors.a

lm_sensors /usr/lib/libsensors.so

lm_sensors /usr/lib/libsensors.so.3

lm_sensors /usr/lib/libsensors.so.3.0.9

lm_sensors /usr/man/

lm_sensors /usr/man/man1/

lm_sensors /usr/man/man1/sensors.1.gz

lm_sensors /usr/man/man3/

lm_sensors /usr/man/man3/libsensors.3.gz

lm_sensors /usr/man/man5/

lm_sensors /usr/man/man5/sensors.conf.5.gz

lm_sensors /usr/man/man8/

lm_sensors /usr/man/man8/fancontrol.8.gz

lm_sensors /usr/man/man8/i2cdetect.8.gz

lm_sensors /usr/man/man8/i2cdump.8.gz

lm_sensors /usr/man/man8/i2cset.8.gz

lm_sensors /usr/man/man8/isadump.8.gz

lm_sensors /usr/man/man8/isaset.8.gz

lm_sensors /usr/man/man8/pwmconfig.8.gz

lm_sensors /usr/man/man8/sensors-detect.8.gz

lm_sensors /usr/sbin/

lm_sensors /usr/sbin/fancontrol

lm_sensors /usr/sbin/fancontrol.pl

lm_sensors /usr/sbin/i2cdetect

lm_sensors /usr/sbin/i2cdump

lm_sensors /usr/sbin/i2cset

lm_sensors /usr/sbin/isadump

lm_sensors /usr/sbin/isaset

lm_sensors /usr/sbin/pwmconfig

lm_sensors /usr/sbin/sensors-detect

 

et voici les commentaires que j' ai sauvé pendant l' installation sous Arch

will now generate the commands needed to load the I2C modules.

Sometimes, a chip is available both through the ISA bus and an I2C bus.

ISA bus access is faster, but you need to load an additional driver module

for it. If you have the choice, do you want to use the ISA bus or the

I2C/SMBus (ISA/smbus)? no

 

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

/etc/modules.conf:

 

#----cut here----

# I2C module options

alias char-major-89 i2c-dev

#----cut here----

 

To load everything that is needed, add this to some /etc/rc* file:

 

#----cut here----

# I2C adapter drivers

modprobe i2c-sis96x

# I2C chip drivers

modprobe asb100

modprobe eeprom

# sleep 2 # optional

/usr/local/bin/sensors -s # recommended

#----cut here----

 

WARNING! If you have some things built into your kernel, the list above

will contain too many modules. Skip the appropriate ones! You really should

try these commands right now to make sure everything is working properly.

Monitoring programs won't work until it's done.

 

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO):

yes

Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors

for initialization at boot time.

Donc, c' est bien a la ligne chip "asb100-*" que je dois configurer tout ça ?

[juddix]

Bon, j' ai réussi

 

J' ai collé dans /etc/rc.local

modprobe i2c-sis96x

modprobe asb100

modprobe eeprom

hddtemp -d /dev/hda &

sensors -s

 

 

Sinon, pour le BIP , l' alarme , c' était le Vcore

# sensors

asb100-i2c-0-2d

Adapter: SiS96x SMBus adapter at 0xe600

VCore 1: +1.60 V (min = +1.46 V, max = +1.60 V) ALARM

 

plus de bip après modification du Vcore 1

chip "asb100-*"

set vrm 9.0

 

label in0 "VCore 1"

set in0_min vid * 0.95

set in0_max vid * 1.70

 

En modifiant la ligne du Vcore 1 de 1.60 à 1.70 , après sensors me dit max = +2.59 V

La valeur n' est pas la même mais c' est un détail....

Machine non-overclocker

# sensors

asb100-i2c-0-2d

Adapter: SiS96x SMBus adapter at 0xe600

VCore 1: +1.60 V (min = +1.46 V, max = +2.59 V)