Hi Ian, On Wed, 19 Feb 2014 18:59:18 -0800 (PST), ianp wrote: > I wish to share some more configurations as I set them up. Now I'm trying to configure my sensors on a Gigabyte GA-945GCM-S2L, running Linux 3.2. > > > $ dmesg | grep it87 > it87: Found IT8718F chip at 0x290, revision 4 > it87: Beeping is supported > (...) > For +12V scaling, and seeing that in4 is the only unscaled input sensor that is not at 4.080V, which is the maximum range for this Super-I/O chip, I decided to go ahead with the computation even with just two sample voltages that I have personally observed in the BIOS: > > +12V BIOS samples: 12.302, 12.365 > > 12.365 - 12.302 = 0.063 > > 12.302 / (63/16) = 3.12431746 > > which is very close to in4 (3.120). At one time it read: > > in4: > in4_input: 3.140 There's something weird here: 3.140 isn't a integer multiple of 0.016, so it is not possible that the IT8718F sensed that voltage value. Are you sure this is the exact value reported by "sensors"? Or is it a copy and paste error? > in4_min: 2.896 > in4_max: 3.200 > in4_alarm: 0.000 > in4_beep: 0.000 > > 12.365 / (63/16) = 3.14031746 > > and still as close as it gets to in4 (3.140). So my compute statement for +12V scaling is: > > compute in4 @*(63/16), @/(63/16) I have found a BIOS screenshot on the web (was hard to find): http://img155.imageshack.us/img155/5831/dsc00004kz6.jpg Sample value there is 12.175 V. 12.302 - 12.175 = 0.127 12.365 - 12.175 = 0.190 The would suggests that the scaling factor isn't exactly 63/16 (3.9375) but closer to 190/48 (3.9583.) However 190/48 doesn't map raw values to BIOS values so that can't be it. Your original assumption was that 12.302 in the BIOS was 3.120 in "sensors". I think actually 12.365 in the BIOS was 3.120 in "sensors". If you put some load on the CPU, you may be able to collect another in4 value from "sensors" (presumably 3.104) that would match the 12.302 in the BIOS. If I'm right then a scaling factor that would work would be somewhere between 12.302/3.104 and 12.365/3.120, i.e. 3.9633. Note that this isn't the first time this strange scaling factors shows up for Gigabyte boards: http://jdelvare.nerim.net/devel/lm-sensors/config/sensors3-Gigabyte-7N400-Pro2.conf http://jdelvare.nerim.net/devel/lm-sensors/config/sensors3-Gigabyte-890GPA-UD3H.conf http://www.lm-sensors.org/wiki/Configurations/Gigabyte/EX38-DS4 So I would go with: compute in4 @*3.9633, @/3.9633 It maps the values seen in the BIOS with actual register values: 192 * 0.016 * 3.9633 = 12.175 194 * 0.016 * 3.9633 = 12.302 195 * 0.016 * 3.9633 = 12.365 > Here's the sensors output, using my configuration thus far: > > $ sensors > > it8718-isa-0290 > Adapter: ISA adapter > Vcore: +1.18 V (min = +0.85 V, max = +1.36 V) > Vram: +1.84 V (min = +1.71 V, max = +1.89 V) > +3.3V: +3.39 V (min = +3.14 V, max = +3.47 V) > in3: +4.08 V (min = +0.00 V, max = +4.08 V) ALARM > +12V: +12.29 V (min = +11.40 V, max = +12.60 V) > in5: +4.08 V (min = +0.00 V, max = +4.08 V) ALARM > in6: +4.08 V (min = +0.00 V, max = +4.08 V) ALARM > in7: +4.08 V (min = +0.00 V, max = +4.08 V) ALARM > Vbat: +3.06 V > CPU Fan: 1721 RPM (min = 900 RPM) > CHA Fan: 2096 RPM (min = 0 RPM) > temp1: -55.0°C (low = +20.0°C, high = +55.0°C) sensor = thermistor > temp2: -2.0°C (low = +20.0°C, high = +55.0°C) sensor = thermistor > temp3: +41.0°C (low = +127.0°C, high = +60.0°C) sensor = thermal diode > cpu0_vid: +3.500 V > intrusion0: ALARM > > > I'm now faced with the problem of determining +5V scaling, which is not even present in the BIOS monitoring section. Even if it were present, how could I determine which unscaled sensor input to match it up if in3, in5, in6, and in7 are all 4.080V? You can't. All evidence indicates that +5V is not monitored on this motherboard. > Regarding temperatures, temp1 and temp2 don't look right. How can this invalid reading be rectified if possible? The BIOS shows a single temperature, so I'm afraid temp3 is the CPU temperature and temp1 and temp2 aren't connected. -- Jean Delvare Suse L3 Support _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
