[elrepo] Fwd: [lm-sensors] Gigabyte GA-P35-DS3P - VID Zero value

[Simon Wilson]

Quoting Phil Perry <phil at elrepo.org>:

> Refresh my memory... what is vid?
>

from /usr/share/doc/lm_sensors-2.10.8/doc/:

"The VID (Voltage Identification) pins on sensor chips are used to  
read the CPU Core voltage setting."

lm_sensors then uses the VID value to calculate the Vcore (in0) in a  
range of +/- 5%.

in0 (Vcore) calculation on these boards should be:

    set in0_min vid * 0.95
    set in0_max vid * 1.05

According to that file:

"The following chip drivers support only VRM 8.2 and cannot be changed:

         adm1024, it87, mtp008, adm9240, gl520sm, lm78"

Attempting to "set vrm" fails.

And according to various info out there, such as at  
http://lists.lm-sensors.org/pipermail/lm-sensors/2008-October/024581.html  
it87.c should support the it8718's VID value:

#define GPIO	0x07	/* The device with the IT8718F VID value in it */

And:

The IT8718F and IT8720F also features VID inputs (up to 8 pins) but  
the value is stored in the Super-I/O configuration space. Due to  
technical limitations, this value can currently only be read once at  
initialization time, so the driver won't notice and report changes in  
the VID value. The two upper VID bits share their pins with voltage  
inputs (in5 and in6) so you can't have both on a given board.

***This thread is the same issue, albeit on a different motherboard***

http://lists.lm-sensors.org/pipermail/lm-sensors/2009-January/025018.html

He "fixed" it by changing /sys/class/hwmon/hwmon0/device/vrm to read  
100 instead of 110. Although reading through the rest of the thread it  
appears that this should have been resolved by hwmon-vid in kernel  
2.6.20+.

With it set to 100 it works for me, I get a VID of 1.088. +/- 5% gives  
me a Non-alarm range of 1.03 to 1.14 V.

So is it a hwmon-vid version issue in the CentOS kernel?

Simon
-- 
Simon Wilson
www.simonandkate.net