All of lore.kernel.org
 help / color / mirror / Atom feed
From: a@gaydenko.com (Andrew Gaydenko)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] W83627DHG, steps to use
Date: Fri, 29 Dec 2006 03:01:04 +0000	[thread overview]
Message-ID: <200612290601.04303@goldspace.net> (raw)
In-Reply-To: <200612271943.00165@goldspace.net>

==== On Friday 29 December 2006 05:32, you wrote: ===>Hi Andrew,
>
>> I have applied the W83627DHG patch, all sensors works (THANKS!) except for +5V
>> (it shows something about 0.384V). So, I can stay with CPU temp from
>>  W83627DHG. But what does this sensor show? First CPU temp?
>> Second one? I mean Core 2 Duo.
>
>The w83627dhg has three temperature input pins. (SYSTIN, CPUTIN,
>AUXTIN) However, the motherboard manufacturer can wire the pins any
>way they want. When you discover what each pin is wired to, you can
>update your sensors.conf and send an email to us letting us know what
>your motherboard is and what customizations you did. The Core 2 Duo
>should have four sensors, if it's like my Athlon 64 X2. That is, there
>are two digital sensors (one per core) which the coretemp driver will
>read. And there are two analog sensors (one per core) which the
>motherboard might connect to the w83627dhg. Use cpuburn or something
>you prefer and see which temperatures increase.

AUX Temp doesn't change at all when both CPU are under heavy loading.
The sensor value is 119C always (it is for ASUS P5B-VM motherboard).

>
>> Another problem is, when I try pwmconfig, I get such error:
>>
>> Testing pwm control 9191-0290/pwm2 ...
>>   9191-0290/fan2_input ... speed was 1721 now 1713
>> /usr/sbin/pwmconfig: line 102: echo: write error: Invalid argument
>>
>> It is for current SVN tree. So, I don't know a reason why pwm doesn't work - is
>> this disabled by BIOS, or is this the script error? I'm not shell guru :-)
>
>I'm going to pass on this one. Rudolf?
>
>David

I think script is correct. I have tried 'echo 0' > blablabla and got the same
error. Given pwm2_enable has content "1". 'echo 1' doesn't lead to error.

P.S. Must I use multiple "To:" in accordance with msg header, or must I answer
     to the mailing list only? (I use last variant now)


Andrew


  parent reply	other threads:[~2006-12-29  3:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-27 16:42 [lm-sensors] W83627DHG, steps to use Andrew Gaydenko
2006-12-27 22:49 ` Andrew Gaydenko
2006-12-28  6:59 ` David Hubbard
2006-12-28 21:22 ` Andrew Gaydenko
2006-12-29  2:32 ` David Hubbard
2006-12-29  3:01 ` Andrew Gaydenko [this message]
2006-12-29  3:09 ` David Hubbard
2006-12-29  3:24 ` Andrew Gaydenko
2006-12-29 14:32 ` Luca
2006-12-30  2:50 ` David Hubbard
2006-12-30 18:11 ` Luca Tettamanti
2007-01-02 18:49 ` Rudolf Marek
2007-01-03  1:55 ` * *
2007-01-03 14:25 ` Jean Delvare
2007-01-03 14:36 ` Jean Delvare
2007-01-04  2:37 ` Andrew Gaydenko
2007-01-04  3:34 ` richardvoigt at gmail.com
2007-01-04  3:54 ` Andrew Gaydenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200612290601.04303@goldspace.net \
    --to=a@gaydenko.com \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.