From: Joris Creyghton <jorisctn@gmail.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Erratic value of MCH temp. (0C),
Date: Mon, 17 Jan 2011 20:17:56 +0000 [thread overview]
Message-ID: <1295295476.2045.7.camel@Asus5> (raw)
In-Reply-To: <1294052867.1860.36.camel@Asus5>
[-- Attachment #1.1: Type: text/plain, Size: 1237 bytes --]
Hi Luca,
On Mon, 2011-01-17 at 13:49 +0100, Luca Tettamanti wrote:
> Sorry for the delay :)
No problem :-)
> I've updated the driver to automatically select the correct interface
> on your board.
> Compile and load it without any additional parameter.
It's working fine.
I have looked into your source and would like to suggest to change the
comment in line 33, which reads:
/* Old interface has broken fan monitoring */
The main problem with the old interface was that it didn't communicate
the MCH temperature. The MCH happens to be the hottest component on this
MB, so I want to keep an eye on it.
The confusion about the labeling of the different fans is rather
trivial.
There are 6 fan connectors on the MB, all properly labeled. One of them
has the label NB_fan, although there is no North Bridge fan on this
board. That's just careless of Asus. I think I connected one of the
chassis fans to this connector.
So I would suggest that you change the comment in line 33 to:
/* Old interface has broken MCH temperature monitoring */
When you think it is usefull I can verify whether the different fan
connector labels are properly displayed in the BIOS output and in the
output of the sensors command.
Joris
[-- Attachment #1.2: Type: text/html, Size: 1688 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2011-01-17 20:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 11:07 [lm-sensors] Erratic value of MCH temp. (0C), Joris Creyghton
2011-01-05 11:35 ` Luca Tettamanti
2011-01-05 13:45 ` Joris Creyghton
2011-01-05 14:08 ` Luca Tettamanti
2011-01-05 14:35 ` Joris Creyghton
2011-01-06 21:01 ` Jean Delvare
2011-01-07 13:14 ` Luca Tettamanti
2011-01-10 15:25 ` Luca Tettamanti
2011-01-10 18:48 ` Joris Creyghton
2011-01-10 18:56 ` Jean Delvare
2011-01-10 20:01 ` Joris Creyghton
2011-01-11 14:07 ` Joris Creyghton
2011-01-11 14:23 ` Luca Tettamanti
2011-01-12 14:03 ` Luca Tettamanti
2011-01-12 14:15 ` Jean Delvare
2011-01-12 14:30 ` Luca Tettamanti
2011-01-12 15:01 ` Joris Creyghton
2011-01-17 12:49 ` Luca Tettamanti
2011-01-17 20:17 ` Joris Creyghton [this message]
2011-01-18 14:40 ` Luca Tettamanti
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=1295295476.2045.7.camel@Asus5 \
--to=jorisctn@gmail.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.