* ticket 1415
2005-05-19 6:24 ticket 1415 T Nuro
@ 2005-05-19 6:24 ` TN
2005-05-19 6:24 ` TN
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: TN @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
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
^ permalink raw reply [flat|nested] 10+ messages in thread* ticket 1415
2005-05-19 6:24 ticket 1415 T Nuro
2005-05-19 6:24 ` TN
@ 2005-05-19 6:24 ` TN
2005-05-19 6:24 ` Mark Studebaker
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: TN @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20031022/df42112f/attachment.html
^ permalink raw reply [flat|nested] 10+ messages in thread* ticket 1415
2005-05-19 6:24 ticket 1415 T Nuro
2005-05-19 6:24 ` TN
2005-05-19 6:24 ` TN
@ 2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark M. Hoffman
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Mark Studebaker @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
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
^ permalink raw reply [flat|nested] 10+ messages in thread* ticket 1415
2005-05-19 6:24 ticket 1415 T Nuro
` (2 preceding siblings ...)
2005-05-19 6:24 ` Mark Studebaker
@ 2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` Mark M. Hoffman
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Mark M. Hoffman @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
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
^ permalink raw reply [flat|nested] 10+ messages in thread* ticket 1415
2005-05-19 6:24 ticket 1415 T Nuro
` (3 preceding siblings ...)
2005-05-19 6:24 ` Mark M. Hoffman
@ 2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` Mark M. Hoffman
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Mark M. Hoffman @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
* 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
^ permalink raw reply [flat|nested] 10+ messages in thread* ticket 1415
2005-05-19 6:24 ticket 1415 T Nuro
` (4 preceding siblings ...)
2005-05-19 6:24 ` Mark M. Hoffman
@ 2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` Mark M. Hoffman
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Mark M. Hoffman @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
* 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
^ permalink raw reply [flat|nested] 10+ messages in thread* ticket 1415
2005-05-19 6:24 ticket 1415 T Nuro
` (5 preceding siblings ...)
2005-05-19 6:24 ` Mark M. Hoffman
@ 2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` TN
2005-05-19 6:24 ` TN
8 siblings, 0 replies; 10+ messages in thread
From: Mark M. Hoffman @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
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
^ permalink raw reply [flat|nested] 10+ messages in thread* ticket 1415
2005-05-19 6:24 ticket 1415 T Nuro
` (6 preceding siblings ...)
2005-05-19 6:24 ` Mark M. Hoffman
@ 2005-05-19 6:24 ` TN
2005-05-19 6:24 ` TN
8 siblings, 0 replies; 10+ messages in thread
From: TN @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
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.
^ permalink raw reply [flat|nested] 10+ messages in thread* ticket 1415
2005-05-19 6:24 ticket 1415 T Nuro
` (7 preceding siblings ...)
2005-05-19 6:24 ` TN
@ 2005-05-19 6:24 ` TN
8 siblings, 0 replies; 10+ messages in thread
From: TN @ 2005-05-19 6:24 UTC (permalink / raw)
To: lm-sensors
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20031031/df0f5515/attachment.html
^ permalink raw reply [flat|nested] 10+ messages in thread