Hi Jean, 2014-07-25 17:45 GMT+02:00 Jean Delvare <jdelvare@xxxxxxx>: > Hi Eric, > > Please leave the list Cc'd. > > On Fri, 25 Jul 2014 15:55:06 +0200, Éric Le Bras wrote: > > 2014-07-25 9:31 GMT+02:00 Jean Delvare <jdelvare@xxxxxxx>: > > > On Wed, 23 Jul 2014 11:08:14 +0200, Éric Le Bras wrote: > > > > label temp1 "Sys temp" > > > > label temp2 "unknown" > > > > label temp3 "unknown" > > > > > > If you don't know, just don't put labels, "unknown" doesn't add much > > > value. One of these is most certainly the CPU temperature, I'm > > > surprised it's not obvious. What does the output of "sensors > > > -c /dev/null" say? > > > > temp2 sensor is labeled as CPU diode, so it is somewhat related to CPU > > temp. However there is another measure reported by "coretemp" circuit, > > which reports the exact temperature displayed by the BIOS. So what is > > exactly temp2? > > Coretemp is a digital reading straight from the CPU. Reacts very fast, > good accuracy at high temperatures, but very poor accuracy at low > temperatures. The readings from the W83627DHG chip, OTOH, are analog > temperature measurements using diodes or thermistors. So both coretemp > and temp2 are the CPU temperature, just measured differently. > Ok, I keep temp2 and label it "CPU temp" > > > Temp3 has a weird behaviour. It lowers when the CPU load increases. I > > enclosed a graph generated with sensord. The curve for temp3 has an > > "inversed" profile, compared to other temps. > > That does not mean it's wrong. You should draw the fan speed together > with the temperatures. Higher CPU temperature will typically result in > a faster spinning fan, which in turn can lower the temperature of > other parts of the system. This is even more likely for a system > without a CPU fan where the CPU cooling is achieved by the case fan. > > 20.5°C could well be the ambient temperature inside the case, if case > cooling is very good and the room temperature is cool too. > Not sure. First the fan is not regulated, so it spins at constant speed. Next, I live in southern France, and the room has no AC, so the room temperature is approx. 25°C today. > > > eric@tangha /etc/sensors.d % sensors -c /dev/null > > coretemp-isa-0000 > > Adapter: ISA adapter > > Core 0: +55.0°C (high = +100.0°C, crit = +100.0°C) > > > > w83627dhg-isa-0290 > > Adapter: ISA adapter > > in0: +1.34 V (min = +0.00 V, max = +1.74 V) > > in1: +1.74 V (min = +1.66 V, max = +1.83 V) > > in2: +3.25 V (min = +2.98 V, max = +3.63 V) > > in3: +3.25 V (min = +2.98 V, max = +3.63 V) > > in4: +1.81 V (min = +2.04 V, max = +2.04 V) ALARM > > in5: +0.10 V (min = +1.41 V, max = +1.72 V) ALARM > > in6: +1.57 V (min = +1.35 V, max = +1.65 V) > > in7: +3.25 V (min = +2.98 V, max = +3.63 V) > > in8: +3.09 V (min = +2.70 V, max = +3.63 V) > > in5 is way too low to be a scaled +5V. This strongly suggests that in4 > is +5V (assuming in1 is really +12V - how do you know that?) If > anything, in5 could only be a negative voltage, but even then it is way > too close to 0V to be plausible. So I think it's not connected, and is > reporting noise. > > If we assume that in4 is 5V then the scaling factor would be around > 2.76. I used to have an Intel board with a similar monitoring chip > where +5V was on in4 and the scaling factor was: > > compute in4 @*(1+18/10), @/(1+18/10) > > That might work for you. If you have a good multimeter, you can check > on a molex connector if the resulting +5V reading is realistic (keep in > mind that the monitoring chip value is typically not more accurate than > +/- 2%.) > I will try to verify for in4. For the +12V, I had only one value found on the web (12.084), and I observed 2 differents values on the BIOS on my own PC (11.935 and 11.990). The 12V was alterning between the 2 values 11.935 and 11.990, and only one of the 3 possibles sensors (in1, in4 and in5) was alterning at the same time : in1 (1.736 and 1.744). The site says the atomic measure for the W83627DHG is 8mv. So I tried with a divisor of 8, and found that the ratio 55/8 was ok. It gave exactly the temperatures displayed by the BIOS when applied to in1. > > > fan1: 3013 RPM (min = 1607 RPM, div = 8) > > fan2: 0 RPM (min = 10546 RPM, div = 128) ALARM > > fan3: 0 RPM (min = 10546 RPM, div = 128) ALARM > > fan4: 0 RPM (min = 10546 RPM, div = 128) ALARM > > temp1: +43.0°C (high = +95.0°C, hyst = +60.0°C) sensor = > thermistor > > temp2: +49.5°C (high = +110.0°C, hyst = +75.0°C) sensor = CPU > diode > > temp3: +20.5°C (high = +80.0°C, hyst = +75.0°C) sensor = > thermistor > > cpu0_vid: +0.000 V > > intrusion0: ALARM > > You can add an ignore statement for cpu0_vid too, as it is apparently > not connected. > > -- > Jean Delvare > SUSE L3 Support > _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
