ticket 1415

ticket 1415

[T Nuro]

Hello,

Here's the output from sensors -u as requested......not much output I'm 
afraid - ie. zero.....

fw:~# sensors -u
w83627thf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm


-- so -- I started tinkering again (i've been sick for a week, so 
haven't had a chance to experiment some more since my posting)
I've always noticed that when I run sensors-detect, it seems to almost 
always give me a different result each time I try it. Usually it bounces 
between saying that it detects the ITE, winbond w83627thf and lm75 in 
one case, and the next case would be only the winbond w83627thf and 
lm75. I've always ignored the ITE chip module since every info page I 
find on the net says that its got a winbond w83627thf......

Anyway, here's the output from the ITE. It make no sense, but it 
believes its getting valid data even though the results are not true.


it87-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore 1:   +2.89 V  (min =  +1.53 V, max =  +1.87 V)   ALARM
VCore 2:   +3.15 V  (min =  +2.25 V, max =  +2.75 V)
+3.3V:     +6.46 V  (min =  +2.96 V, max =  +3.60 V)
+5V:       +5.02 V  (min =  +4.50 V, max =  +5.48 V)
+12V:     +12.48 V  (min = +11.36 V, max = +13.80 V)
-12V:     -13.40 V  (min = -15.86 V, max = -13.40 V)
-5V:      -13.64 V  (min = -10.13 V, max =  -9.44 V)
Stdby:     +0.69 V  (min =  +0.00 V, max =  +0.00 V)
VBat:      +4.08 V
fan1:     11250 RPM  (min = 3000 RPM, div = 2)          ALARM
fan2:     135000 RPM  (min = 6000 RPM, div = 1)          ALARM
fan3:     67500 RPM  (min = 3000 RPM, div = 2)          ALARM
Temp1/MB:    -18?C  (low =   +0?C, high =  +44?C)         ALARM
Temp2/CPU:    -1?C  (low =  +20?C, high =   +0?C)         ALARM
Temp3:        +0?C  (low =  +20?C, high =  +60?C)         ALARM




Here's the output from sensors-detect from one instance (an instance 
that it doesn't suggest it87)




fw:/lib/modules/2.4.18-20030923-2/kernel/drivers/i2c# 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.

 BIOS vendor (ACPI): ACPIAM
 System vendor (DMI): To Be Filled By O.E.M.
 BIOS version (DMI): 1010.004
 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):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801EB ICH5
Probe succesfully concluded.

 We will now try to load each adapter module in turn.
Load `i2c-i801' (say NO if built into your kernel)? (YES/no):
Module loaded succesfully.
 Do you now want to be prompted for non-detectable adapters? (yes/NO):
 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 not loaded. Do you want to load it now? (YES/no):
 Module loaded succesfully.

 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: SMBus I801 adapter at 0400 (Non-I2C SMBus adapter)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x08
Client found at address 0x0d
Client found at address 0x2f
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1022'... Failed!
Probing for `Texas Instruments THMC50'... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'... Failed!
Client found at address 0x30
Client found at address 0x32
Client found at address 0x44
Client found at address 0x48
Probing for `National Semiconductor LM75'... Success!
    (confidence 4, driver `lm75')
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Maxim MAX6650/MAX6651'... Failed!
Probing for `Philips Semiconductors PCF8591'... Success!
    (confidence 1, driver `pcf8591')
Client found at address 0x49
Probing for `National Semiconductor LM75'... Success!
    (confidence 4, driver `lm75')
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Philips Semiconductors PCF8591'... Success!
    (confidence 1, driver `pcf8591')
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Client found at address 0x52
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Client found at address 0x61
Probing for `SMBus 2.0 ARP-Capable Device'... Success!
    (confidence 1, driver `smbus-arp')
Client found at address 0x69

 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.  Do you want to scan the ISA bus? (YES/no):
Probing for `National Semiconductor LM78'
  Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
  Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
  Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
  Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
  Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
  Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
  Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
  Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
  Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
  Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'
  Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
  Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
  Trying address 0x0ca8... Failed!

 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.  Do you want to scan for Super I/O sensors? (YES/no):
Probing for `SMSC 47M10x Super IO Fan Sensors'
  Failed!
Probing for `SMSC 47M14x Super IO Fan Sensors'
  Failed!
Probing for `VT1211 Super IO Sensors'
  Failed! (0x82)
Probing for `Winbond W83627HF Super IO Sensors'
  Failed! (0x82)
Probing for `Winbond W83627THF Super IO Sensors'
  Success... found at address 0x0290
Probing for `Winbond W83697HF Super IO Sensors'
  Failed! (0x82)

 Now follows a summary of the probes I have just done.
 Just press ENTER to continue:

Driver `lm75' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0400' (Non-I2C SMBus adapter)
    Busdriver `i2c-i801', I2C address 0x48
    Chip `National Semiconductor LM75' (confidence: 4)
  * Bus `SMBus I801 adapter at 0400' (Non-I2C SMBus adapter)
    Busdriver `i2c-i801', I2C address 0x49
    Chip `National Semiconductor LM75' (confidence: 4)

Driver `pcf8591' (may not be inserted):
  Misdetects:
  * Bus `SMBus I801 adapter at 0400' (Non-I2C SMBus adapter)
    Busdriver `i2c-i801', I2C address 0x48
    Chip `Philips Semiconductors PCF8591' (confidence: 1)
  * Bus `SMBus I801 adapter at 0400' (Non-I2C SMBus adapter)
    Busdriver `i2c-i801', I2C address 0x49
    Chip `Philips Semiconductors PCF8591' (confidence: 1)

Driver `eeprom' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0400' (Non-I2C SMBus adapter)
    Busdriver `i2c-i801', I2C address 0x50
    Chip `SPD EEPROM' (confidence: 8)
  * Bus `SMBus I801 adapter at 0400' (Non-I2C SMBus adapter)
    Busdriver `i2c-i801', I2C address 0x52
    Chip `SPD EEPROM' (confidence: 8)

Driver `smbus-arp' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0400' (Non-I2C SMBus adapter)
    Busdriver `i2c-i801', I2C address 0x61
    Chip `SMBus 2.0 ARP-Capable Device' (confidence: 1)

Driver `w83627hf' (should be inserted):
  Detects correctly:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `Winbond W83627THF Super IO Sensors' (confidence: 8)


 I 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)?

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-i801
modprobe i2c-isa
# I2C chip drivers
modprobe lm75
modprobe eeprom
modprobe smbus-arp
modprobe w83627hf
# 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):

I've successfully install lm sensors on several other machines, but this 
one is the newest mobo by a long way out of the ones I've setup. 
Unfortunately its also the most physically inaccessible for me too :)  
(ie. its in a foreign country but I need to monitor it)

thanks!

-Trevor

ticket 1415

[Mark M. Hoffman]

* T Nuro <tnuro@yahoo.com.au> [2003-10-21 21:20:43 +1000]:
> -- so -- I started tinkering again (i've been sick for a week, so 
> haven't had a chance to experiment some more since my posting)
> I've always noticed that when I run sensors-detect, it seems to almost 
> always give me a different result each time I try it. Usually it bounces 
> between saying that it detects the ITE, winbond w83627thf and lm75 in 
> one case, and the next case would be only the winbond w83627thf and 
> lm75. I've always ignored the ITE chip module since every info page I 
> find on the net says that its got a winbond w83627thf......

Funny...

I tried to install lm_sensors on the very same board (Asus P4C800) last
night.  I didn't see sensors-detect recommend ITE.  Your board almost
certainly has the w83627thf - I can see by inspection that mine does.

(You wrote in the ticket):
> The error I get is:
> w83627thf-isa-0290
> Adapter: ISA adapter
> Algorithm: ISA algorithm
> ERROR: Can??t get alarm data!
> ERROR: Can??t get beep data!
> ERROR: Can??t get IN0 data!
> ERROR: Can??t get IN2 data!
> ERROR: Can??t get IN3 data!
> ERROR: Can??t get IN4 data!
> ERROR: Can??t get IN7 data!
> ERROR: Can??t get IN8 data!
> ERROR: Can??t get FAN1 data!
> ERROR: Can??t get FAN2 data!
> ERROR: Can??t get TEMP1 data!
> ERROR: Can??t get TEMP2 data!

Well, libsensors is indeed missing some code to support it - but that's as
far as I got.  I'll try to commit something to CVS tonight.

Regards,

-- 
Mark M. Hoffman
mhoffman@lightlink.com

ticket 1415

[Mark M. Hoffman]

* Mark M. Hoffman <mhoffman@lightlink.com> [2003-10-21 12:53:35 -0400]:
> Well, libsensors is indeed missing some code to support it - but that's as
> far as I got.  I'll try to commit something to CVS tonight.

"It" is w83627thf...

OK, I committed a partial fix - go ahead and try it.  I already see that
sensors doesn't report fan3 (which corresponds to "Power Fan" in P4C800
BIOS.)  I will start another thread on the mailing list about that...

Regards,

-- 
Mark M. Hoffman
mhoffman@lightlink.com

ticket 1415

[TN]

An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20031022/df42112f/attachment.html

ticket 1415

[TN]

Mark M. Hoffman wrote:

>* Mark M. Hoffman <mhoffman@lightlink.com> [2003-10-21 12:53:35 -0400]:
>  
>
>>Well, libsensors is indeed missing some code to support it - but that's as
>>far as I got.  I'll try to commit something to CVS tonight.
>>    
>>
>
>"It" is w83627thf...
>
>OK, I committed a partial fix - go ahead and try it.  I already see that
>sensors doesn't report fan3 (which corresponds to "Power Fan" in P4C800
>BIOS.)  I will start another thread on the mailing list about that...
>
>Regards,
>
>  
>

Hi Mark,

success.......I got the latest from cvs and sure enough, numbers! I'm 
not sure about a couple of these (ie. the voltage sensors seem to have 1 
or 2 weirdnesses about them), but it appears to be working. The fan 
speed & temperatures seem to make sense and change in a sensible manner 
(speed increases as temperature increases)

One thing I've noticed is that on my physically accessible servers, the 
temp readings seldom agree with the bios readings.....is there a 
calivration process I need to go through ?

Anyway, thanks again for listening.
-Trevor.



fw:~# sensors
w83627thf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
in0:       +2.89 V  (min =  +0.00 V, max =  +0.00 V)
in2:       +3.23 V  (min =  +2.97 V, max =  +3.63 V)
in3:       +2.97 V  (min =  +2.68 V, max =  +3.26 V)
in4:       +0.00 V  (min =  +0.08 V, max =  +1.34 V)
in7:       +2.94 V  (min =  +2.68 V, max =  +3.26 V)
in8:       +3.23 V  (min =  +2.70 V, max =  +3.29 V)
fan1:        0 RPM  (min =  187 RPM, div = 32)
fan2:     3214 RPM  (min = 3000 RPM, div = 2)
temp1:       +32?C  (limit =  +60?C)                       sensor = 
thermistor
temp2:     +37.5?C  (limit =  +60?C, hysteresis =  +50?C) sensor = 
PII/Celeron diode
alarms:
beep_enable:
          Sound alarm disabled

ticket 1415

[Mark Studebaker]

mark h,
thanks for adding the glue to libsensors.
Obviously I forgot to do it when I added THF support.
I'll close the ticket.
mds

TN wrote:
> 
> Mark M. Hoffman wrote:
> 
> >* Mark M. Hoffman <mhoffman@lightlink.com> [2003-10-21 12:53:35 -0400]:
> >
> >
> >>Well, libsensors is indeed missing some code to support it - but that's as
> >>far as I got.  I'll try to commit something to CVS tonight.
> >>
> >>
> >
> >"It" is w83627thf...
> >
> >OK, I committed a partial fix - go ahead and try it.  I already see that
> >sensors doesn't report fan3 (which corresponds to "Power Fan" in P4C800
> >BIOS.)  I will start another thread on the mailing list about that...
> >
> >Regards,
> >
> >
> >
> 
> Hi Mark,
> 
> success.......I got the latest from cvs and sure enough, numbers! I'm
> not sure about a couple of these (ie. the voltage sensors seem to have 1
> or 2 weirdnesses about them), but it appears to be working. The fan
> speed & temperatures seem to make sense and change in a sensible manner
> (speed increases as temperature increases)
> 
> One thing I've noticed is that on my physically accessible servers, the
> temp readings seldom agree with the bios readings.....is there a
> calivration process I need to go through ?
> 
> Anyway, thanks again for listening.
> -Trevor.
> 
> fw:~# sensors
> w83627thf-isa-0290
> Adapter: ISA adapter
> Algorithm: ISA algorithm
> in0:       +2.89 V  (min =  +0.00 V, max =  +0.00 V)
> in2:       +3.23 V  (min =  +2.97 V, max =  +3.63 V)
> in3:       +2.97 V  (min =  +2.68 V, max =  +3.26 V)
> in4:       +0.00 V  (min =  +0.08 V, max =  +1.34 V)
> in7:       +2.94 V  (min =  +2.68 V, max =  +3.26 V)
> in8:       +3.23 V  (min =  +2.70 V, max =  +3.29 V)
> fan1:        0 RPM  (min =  187 RPM, div = 32)
> fan2:     3214 RPM  (min = 3000 RPM, div = 2)
> temp1:       +32?C  (limit =  +60?C)                       sensor > thermistor
> temp2:     +37.5?C  (limit =  +60?C, hysteresis =  +50?C) sensor > PII/Celeron diode
> alarms:
> beep_enable:
>           Sound alarm disabled

ticket 1415

[Mark M. Hoffman]

Hi Trevor:

* TN <tnuro@yahoo.com.au> [2003-10-23 09:52:02 +1000]:
> success.......I got the latest from cvs and sure enough, numbers! I'm 
> not sure about a couple of these (ie. the voltage sensors seem to have 1 
> or 2 weirdnesses about them), but it appears to be working. The fan 
> speed & temperatures seem to make sense and change in a sensible manner 
> (speed increases as temperature increases)

OK, first of all... I've committed another change to CVS.  You should now
see in1, fan3, and temp3 which we didn't see before.

For my P4C800E, I know these things for sure:

chip "w83627thf-*"

	label fan1 "Chassis Fan"
	label fan2 "CPU Fan"
	label fan3 "Power Fan"

I'm also assuming these:

	label temp1 "MB Temp"
	label temp2 "CPU Temp"
	label temp3 "PWR Temp"
	# PWR Temp is the 2 pin connector on the mainboard
	# unless you've actually connected a sensor...
	ignore temp3

I can't say anything about inX yet.

> One thing I've noticed is that on my physically accessible servers, the 
> temp readings seldom agree with the bios readings.....is there a 
> calivration process I need to go through ?

Yes, if possible.  There is no way for us to automate this.  Check 
/etc/sensors.conf for examples.  OTOH, if you're patient you can just wait
for me to do it. ;)  I have the feeling that more source code changes are
necessary yet anyway.

BTW my temp1/MB actually looks pretty good; it's the temp2/CPU that's low
by ~6C compared to BIOS.  It's also possible that neither is lying - if the
BIOS sits in a tight loop it could cause the CPU to heat up as compared to
a mostly idle/halted CPU running Linux.

Regards,

-- 
Mark M. Hoffman
mhoffman@lightlink.com

ticket 1415

[TN]

An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20031031/df0f5515/attachment.html

ticket 1415

[Mark M. Hoffman]

Hi Trevor:

Please, send only plain text email!

* TN <tnuro@yahoo.com.au> [2003-10-31 10:20:49 +1100]:

>    The  temperature readings I am getting are definately too low, despite
>    variances  like  bios  loading  vs  linux  loading while observing the
>    readings, as I take the readings as soon as the OS or bios has booted,
>    and so I don't believe the CPU can change temperatures by such a large
>    gap in such a short time.

I have a power measuring device which tells me that one of my computers
uses ~55 watts at idle but ~80 watts when in the BIOS screen.  Cup your
hand over a 25 watt light bulb and turn it on, then you'll believe...

>    lm-sensors on my P4 2.8 says about 30c. Bios says about 40-42, which I
>    believe  is  more  like  it,  maybe even then a little low based on my
>    experience with all our other machines.
>    I've  had  a  quick rummage around in the w83627hf.c code, and I can't
>    see  anywhere  where  the CPUTIN offset register is added into the raw
>    reading  from CPUTIN, and neither can I see the other offset registers
>    for  SYSTIN & VTIN being added in to SYSIN, VTIN. Am I blind & haven't
>    read the code right ?

The way I read the datasheet, the value of the offset registers are added to
the raw temp readings by the sensor chip itself.  This is bizarre, I've never
seen another chip do that.  I haven't tested this theory yet though...

>    When I do a isadump on reg 0x55, bank 4, my CPUTIN offset is 0x11.
>    What  has  written  this  value  into this register, is it the bios or
>    somewhere in the lm-sensors modules ?

Just checking, but you did this?

# isadump 0x295 0x296 4 0x4e

Mine reads 0x11 too.  But, the reported value of 38C looks ok for me.  Also,
my VTIN offset is 0xfe, which is ridiculous unless it's interpreted as a 
signed value (two's complement)... in which case it's -2.  And furthermore,
what's the scaling?  Two of the temps report 9 bits for LSB of 0.5C.  So
are those offset regs 1C/bit or 0.5C/bit?

Who knows?  The datasheet is very ambiguous about all that.  Some time this
weekend I'll modify the driver to poke some values in there and see what
happens.

In any event, whatever programmed h/w offset is redundant anyway because
you can get the same result by modifying the compute lines of sensors.conf.

And BTW: here is my current sensors.conf with some comments about what
I'll be working on...

# P4C800E-Deluxe

chip "w83627thf-*"

# VOLTAGES
	label in0 "VCORE"
	#(TODO) the following compute line is b0rk...
	#compute in0 (0.488 * @ / 100) + 0.69 , (@ - 0.69) * 100 / 0.488

	label in1 "+12V"
	compute in1 3.8 * @ ,  @ / 3.8
	set in1_min 12.0 * 0.90
	set in1_max 12.0 * 1.10

	label in2 "+3.3V"
	set in2_min 3.3 * 0.95
	set in2_max 3.3 * 1.05

	label in3 "+5V"
	compute in3 1.68 * @ , @ / 1.68
	set in3_min 5.0 * 0.95
	set in3_max 5.0 * 1.05

	ignore in4
	ignore in5
	ignore in6

	label in7 "5VSB"
	compute in7 1.68 * @ , @ / 1.68
	set in7_min 5.0 * 0.95
	set in7_max 5.0 * 1.05

	# (TODO) driver needs to enable this one...
	label in8 "VBat"
	set in8_min 3.0 * 0.80
	set in8_max 3.0 * 1.20

# FANS
	label fan1 "Chassis Fan"
	ignore fan1
	set fan1_div 8
	set fan1_min 1500

	label fan2 "CPU Fan"
	set fan2_div 4
	set fan2_min 2000

	label fan3 "Power Fan"
	set fan3_div 8
	set fan3_min 1500

# TEMPS
	label temp1 "M/B Temp"
	set temp1_over 50
	set temp1_hyst 45

	label temp2 "CPU Temp"
	set temp2_over 60
	set temp2_hyst 55

	label temp3 "PWR Temp"
	ignore temp3
	set temp1_over 50
	set temp1_hyst 45

# OTHER
	# (TODO) vid technically not supported...
	ignore vid

Regards,

-- 
Mark M. Hoffman
mhoffman@lightlink.com

ticket 1415

[TN]

Hi Mark,

Mark M. Hoffman wrote:

>Hi Trevor:
>
>Please, send only plain text email!
>
>  
>

Sorry about that.


>* TN <tnuro@yahoo.com.au> [2003-10-31 10:20:49 +1100]:
>
>  
>
>>   The  temperature readings I am getting are definately too low, despite
>>   variances  like  bios  loading  vs  linux  loading while observing the
>>   readings, as I take the readings as soon as the OS or bios has booted,
>>   and so I don't believe the CPU can change temperatures by such a large
>>   gap in such a short time.
>>    
>>
>
>I have a power measuring device which tells me that one of my computers
>uses ~55 watts at idle but ~80 watts when in the BIOS screen.  Cup your
>hand over a 25 watt light bulb and turn it on, then you'll believe...
>
>  
>
well that 25 watts is dissipated over the entire machine of course, not 
just the cpu, gpus run damn hot too - BUT- I take your point. I have a 
12 watt soldering iron which gets reasonably warm ;) so I do know what 
10 watts can do.
I still think the readings are incorrect though, as my remote server is 
sitting in a tropical location with an ambient room temperature of about 
30celsius, so for the CPU to claim only a few C above that just isn't 
believable to me.

>>   lm-sensors on my P4 2.8 says about 30c. Bios says about 40-42, which I
>>   believe  is  more  like  it,  maybe even then a little low based on my
>>   experience with all our other machines.
>>   I've  had  a  quick rummage around in the w83627hf.c code, and I can't
>>   see  anywhere  where  the CPUTIN offset register is added into the raw
>>   reading  from CPUTIN, and neither can I see the other offset registers
>>   for  SYSTIN & VTIN being added in to SYSIN, VTIN. Am I blind & haven't
>>   read the code right ?
>>    
>>
>
>The way I read the datasheet, the value of the offset registers are added to
>the raw temp readings by the sensor chip itself.  This is bizarre, I've never
>seen another chip do that.  I haven't tested this theory yet though...
>
>  
>
Yep, I agree - it's vague - and I've not seen chips auto-add registers 
before either.

"CPUTIN temperature offset value. The value in this register will be 
added to  the monitored value so that the reading value will be the sum 
of the monitored value and the offset value."

Having a flick through the rest of the doc, it reads to me a bit like 
chino-english in some minor parts, and so I think the translation is not 
accurate, although on the whole its good. I'm guessing the opposite case 
to you I suppose, I guess that they are instructing the reader to do the 
adding (as in "will be added" = "you shall add")

>>   When I do a isadump on reg 0x55, bank 4, my CPUTIN offset is 0x11.
>>   What  has  written  this  value  into this register, is it the bios or
>>   somewhere in the lm-sensors modules ?
>>    
>>
>
>Just checking, but you did this?
>
># isadump 0x295 0x296 4 0x4e
>
>  
>
yep, i did that.

>Mine reads 0x11 too.  But, the reported value of 38C looks ok for me.  Also,
>my VTIN offset is 0xfe, which is ridiculous unless it's interpreted as a 
>signed value (two's complement)... in which case it's -2.  And furthermore,
>what's the scaling?  Two of the temps report 9 bits for LSB of 0.5C.  So
>are those offset regs 1C/bit or 0.5C/bit?
>
>  
>
My VTIN offset is also 0xfe, and I interpreted it as 2's complement too, 
so its -2. I assume the setup is saying that the VTIN sensor is reading 
too high, so they pull it back by 2C.
I'm also guessing that the offset is 1C increments, since all other 8 
bit temp values are. Its still not exactly spelled out though in the docs.


>Who knows?  The datasheet is very ambiguous about all that.  Some time this
>weekend I'll modify the driver to poke some values in there and see what
>happens.
>  
>
yes, we are guessing and things are open to interpretation, so we'll 
have to dig some more. I'll attempt to contact winbond and get an answer 
to the vague parts.

>In any event, whatever programmed h/w offset is redundant anyway because
>you can get the same result by modifying the compute lines of sensors.conf.
>
>And BTW: here is my current sensors.conf with some comments about what
>I'll be working on...
>
># P4C800E-Deluxe
>
>chip "w83627thf-*"
>
># VOLTAGES
>	label in0 "VCORE"
>	#(TODO) the following compute line is b0rk...
>	#compute in0 (0.488 * @ / 100) + 0.69 , (@ - 0.69) * 100 / 0.488
>
>	label in1 "+12V"
>	compute in1 3.8 * @ ,  @ / 3.8
>	set in1_min 12.0 * 0.90
>	set in1_max 12.0 * 1.10
>
>	label in2 "+3.3V"
>	set in2_min 3.3 * 0.95
>	set in2_max 3.3 * 1.05
>
>	label in3 "+5V"
>	compute in3 1.68 * @ , @ / 1.68
>	set in3_min 5.0 * 0.95
>	set in3_max 5.0 * 1.05
>
>	ignore in4
>	ignore in5
>	ignore in6
>
>	label in7 "5VSB"
>	compute in7 1.68 * @ , @ / 1.68
>	set in7_min 5.0 * 0.95
>	set in7_max 5.0 * 1.05
>
>	# (TODO) driver needs to enable this one...
>	label in8 "VBat"
>	set in8_min 3.0 * 0.80
>	set in8_max 3.0 * 1.20
>
># FANS
>	label fan1 "Chassis Fan"
>	ignore fan1
>	set fan1_div 8
>	set fan1_min 1500
>
>	label fan2 "CPU Fan"
>	set fan2_div 4
>	set fan2_min 2000
>
>	label fan3 "Power Fan"
>	set fan3_div 8
>	set fan3_min 1500
>
># TEMPS
>	label temp1 "M/B Temp"
>	set temp1_over 50
>	set temp1_hyst 45
>
>	label temp2 "CPU Temp"
>	set temp2_over 60
>	set temp2_hyst 55
>
>	label temp3 "PWR Temp"
>	ignore temp3
>	set temp1_over 50
>	set temp1_hyst 45
>
># OTHER
>	# (TODO) vid technically not supported...
>	ignore vid
>
>Regards,
>  
>

OK, thanks for that!
Its certainly interesting comparing notes & interpretations on this, so 
I'll try to discover more too. I'd love to afford a reasonably accurate 
temperature probe to check all this out, I'll see if I can borrow one.


cheers
Trevor.