From: Michael Zintakis <michael.zintakis@googlemail.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] CPU fan with full speed
Date: Sat, 30 Jun 2012 22:46:14 +0000 [thread overview]
Message-ID: <4FEF81B6.6010209@googlemail.com> (raw)
In-Reply-To: <jsm40t$qk8$1@dough.gmane.org>
> If I understand the code and the data sheet correectly, this attribute
> is a bit map used to map a temperature source to one or multiple fans.
>
I was just about to fire-up a question regarding that point! My
pwm3_auto_channels_pwm has a value of 4 and I was a bit baffled why 4
and not 3 - the above explains it very well.
Related to this query: as part of my censors setup, I have 3 different
temperature monitors which supply reading for my CPU. 2 of them are in
hwmon0/device/tempX_input (Intel's own coretemp module, X=2,3) and one
of them is part of my f71882fg chip-supported reading:
hwmon1/device/temp1_input. There are 2 Intel readings, because the CPU
is multi-core.
Now, the f71882fg CPU reading is a bit off. What I mean by that is that
it shows temperature which is between 3-7 degrees cooler than the
Intel's own (coretemp) readings. Is there a way (via
pwm1_auto_channels_pwm perhaps) to force f71882fg to take the coretemp
reading into account instead of using its own?
I tried to "cheat" by executing "ln -s
/sys/class/hwmon/hwmon0/device/temp2_input
/sysclass/hwmon/hwmon1/device/temp4_input" but that didn't work - I get
"No such file or directory" error. I cannot write anything to that
hwmon1/device directory. Is there any way of pointing my f71882fg driver
to read the 2 Intel temperatures temperatures instead of using its own,
not very accurate reading?
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2012-06-30 22:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 5:52 [lm-sensors] CPU fan with full speed Philipp Kraus
2012-06-30 13:41 ` Guenter Roeck
2012-06-30 14:06 ` Philipp Kraus
2012-06-30 14:21 ` Guenter Roeck
2012-06-30 14:37 ` Philipp Kraus
2012-06-30 15:33 ` Guenter Roeck
2012-06-30 16:04 ` Philipp Kraus
2012-06-30 17:03 ` Guenter Roeck
2012-06-30 17:27 ` Philipp Kraus
2012-06-30 19:24 ` Guenter Roeck
2012-06-30 22:46 ` Michael Zintakis [this message]
2012-07-01 0:06 ` Philipp Kraus
2012-07-01 0:24 ` Guenter Roeck
2012-07-01 0:31 ` Guenter Roeck
2012-07-01 3:46 ` Michael Zintakis
2012-07-01 4:53 ` Guenter Roeck
2012-07-01 10:03 ` Michael Zintakis
2012-07-02 1:14 ` Philipp Kraus
2012-07-02 1:28 ` Philipp Kraus
2012-07-02 2:09 ` Guenter Roeck
2012-07-02 2:09 ` Guenter Roeck
2012-07-02 3:25 ` Philipp Kraus
2012-07-02 15:02 ` Guenter Roeck
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=4FEF81B6.6010209@googlemail.com \
--to=michael.zintakis@googlemail.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.