From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] CPU fan with full speed
Date: Sun, 01 Jul 2012 04:53:45 +0000 [thread overview]
Message-ID: <20120701045345.GA22909@roeck-us.net> (raw)
In-Reply-To: <jsm40t$qk8$1@dough.gmane.org>
On Sun, Jul 01, 2012 at 04:46:11AM +0100, Michael Zintakis wrote:
>
> >No ... those are separate drivers, and different sensors. Also, the coretemp
> >reading is not really that exact. Especially at low temperatures it can be quite
> >a bit off, as far as I remember by 10 degrees C or more. It is more accurate at
> >very high temperatures.
> I see, interesting - for some reason I always thought the Intel
> censors are more accurate (judging by their measurements, because
> when I place a load on that machine, both Intel CPU readings jump,
> but the f71882fg driver barely moves a degree or two and stays in
> line with the rest of the sensors, which doesn't really makes sense
> - when the CPU is under load its temperature should rise rapidly).
>
> >Also, keep in mind that you have a different chip. pwm3_auto_channels_pwm
> >means something completely different on the f71882fg. For that chip, it is
> >not a bit map, but the temperature sensor index. 1..4 in pwmX_auto_channels_pwm
> >reflects temp[1..4]_input.
> I am totally confused now! :-\
>
> The driver has only 3 temperature readings: temp[1..3]_input,
> corresponding to CPU (single censor, even though I've got 2 cores)
> and 2 motherboard readings (one on the PC board extension card and
> another one on the main board itself).
>
> So, I have the following values by default:
>
> pwm1_auto_channels_pwm = 1 (1 binary - fan1)
> pwm2_auto_channels_pwm = 2 (10 binary - fan2)
> pwm3_auto_channels_pwm = 4 (100 binary - fan3)
>
Guess you mean pwm[1-3]_auto_channels_temp.
> Makes perfect sense since I do not have a 4th temperature reading
> anywhere on the system, unless you take into account the coretemp
> driver, which is in a different subdirectory: hwmon0 and not hwmon1
> as the f71882fg driver is.
>
You are right - sorry for that. I looked into the driver. The chip
understands [1, 2, 3], but the driver maps those values into a bit map,
where only one bit can be true at any given time.
Guenter
_______________________________________________
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-07-01 4:53 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
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 [this message]
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=20120701045345.GA22909@roeck-us.net \
--to=linux@roeck-us.net \
--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.