Reading the P5GD1-VM sensors
I have been using lmsensors for quite a while now but recently stumbled
across an ASUS P5GD1-VM MotherBoard at work.
I installed the i2c and lmsensors, read the quick installation
documentation, ran the suggested utilities and was able to identify the
sensor chip as a Winbound w83627ehf.
I then applied all the recommendations, updated the files as specified,
restarted my machine and came out empty handed. No sensors detected.
Spent quite a bit of time googling to get further information about the
w83627ehf Super IO Chip, but results were unsuccessful.
Came back to the lmsensors site, further read the lmsensors
documentation and tried to use alternate quasi equivalent chip. Again
came out empty handed.
Because I have a multi-OS system I ran SiSoftware Sandra in Windows 2K
(this is at work, I can not avoid using this OS for the time being) and
reading through the output report I came across the following bit of
information:
Environment Monitor 1
Model: Winbound W83782D ISA
Of course Asus Probe reads all parameters correctly, so why was it that
I could not do it in Slackware 10.2 using a 2.4.31 kernel.
Went back to the lmsensors documentation again and found advice at the
end of the new drivers page which gave a clear example of how to force a
chip driver.
*FORCING A CHIP DRIVER:*
If we do not support a chip, you may often get partial support by
'forcing' the driver for a similar chip to load. Follow these
instructions (running as root) to force an i2c driver:
1.
Run 'prog/detect/i2cdetect' with no arguments to determine the i2c
bus number the chip is on (often 0).
2.
Run 'prog/detect/i2cdetect /n/' where /n/ is the bus number (often
0) to locate the i2c address of the chip (often 0x2d).
3.
Get the name of the similar chip and associated driver (module)
from the table above (for example lm78 chip and driver).
4.
Load the driver as follows: 'modprobe /driver/
force_/chip/=/bus/,/address/' (for example 'modprobe lm78
force_lm78=0,0x2d'). For an ISA-bus device, use magic bus number
'9191'.
5.
Run 'lsmod' and check the syslog or dmesg to verify the driver
loaded.
6.
Run 'sensors -s' and then 'sensors' to verify the driver is
reporting results and see if some of the results make sense.
7.
Adjust settings in /etc/sensors.conf as necessary; rerun 'sensors
-s' and 'sensors'.
8.
Contact us with the results.
Steps 3 to 7 proved very useful indeed
Based on this info I did a forced chip driver installation as follows
I used the w83781d module which is essentially (I think) fully
compatible with the w83782d identified by SySoftware Sandra in Windows.
Notice tha Sandra saw it as an ISA bus chip, so I opted for the ISA
magic number in the force command parameters.
During the lmsensors installation, the utility had identified the
address of the Super IO chip as being 0x0290, so this is what I used for
the address parameter in the command. This is how I proceeded
I opened a terminal and typed
/sbin/modprobe w83781d force_w83781d=9191,0x0290
then I ran
sensors -s
and then
sensors
which yielded the following output
root at JeanPC:~# sensors
eeprom-i2c-0-50
Adapter: SMBus I801 adapter at 0400
Memory type: DDR SDRAM DIMM
Memory size (MB): 512
eeprom-i2c-0-52
Adapter: SMBus I801 adapter at 0400
Memory type: DDR SDRAM DIMM
Memory size (MB): 512
arp-i2c-0-61
Adapter: SMBus I801 adapter at 0400
w83781d-isa-0290
Adapter: ISA adapter
VCore 1: +2.90 V (min = +1.74 V, max = +1.94 V)
VCore 2: +3.68 V (min = +1.74 V, max = +1.94 V)
+3.3V: +3.34 V (min = +3.14 V, max = +3.46 V)
+5V: +5.61 V (min = +4.74 V, max = +5.24 V)
+12V: +15.50 V (min = +11.36 V, max = +12.58 V)
-12V: -11.06 V (min = -12.59 V, max = -11.33 V)
-5V: -0.05 V (min = -5.25 V, max = -4.74 V)
fan1: 2191 RPM (min = 10227 RPM, div = 4)
fan2: 2393 RPM (min = -1 RPM, div = 4)
fan3: 0 RPM (min = 8333 RPM, div = 2)
temp1: +39?C (high = +4?C, hyst = +64?C) ALARM
temp2: +42.0?C (high = +80?C, hyst = +75?C)
temp3: +38.0?C (high = +80?C, hyst = +75?C)
vid: +1.850 V (VRM Version 8.2)
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm disabled
Finally and to my amazement, after a good week of frustrations and
intense googling I could actually read my sensors.
I modified my rc.modules file (this is a Slackware Distro) to include
the force driver command //sbin/modprobe w83781d
force_w83781d=9191,0x0290 /and my //etc/sysconfig/lm_sensors/ file to
adjust my MODULE_4 name to w83781d/ (I am not sure editing the
lm_sensors file is very important but I did not take any chances)./
Rebooted my system, checked my dmesg output, checked lsmod, ran sensors
and got a valid sensors output. Reconfigured my Gkrellm and voila, my
sensors reading were displayed and results were coherent with the ASUS
Probe readings in my other OS.
If this is not an already known quick fix to the problems associated
with reading the ASUS P5GD1-VM MotherBoard sensors, I hope this bit of
text can help other people which might be attempting to correctly read
the Winbound w83627ehf chip on a 2.4.31kernel. Otherwise I still wanted
to share this knowledge with your community.
I would like to thank the lmsensors team for providing the Linux/Unix
community with these very useful drivers and software.
--
Jean Dumas
email : mcinc1993 at gmail.com
mcinc1993 at hotmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mcinc1993.vcf
Type: text/x-vcard
Size: 203 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060406/8a5284c1/attachment.vcf
