All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] CPU Temp on ECS NFORCE3-A939
Date: Mon, 19 Jun 2006 09:54:45 +0000	[thread overview]
Message-ID: <20060619115445.55524ba3.khali@linux-fr.org> (raw)
In-Reply-To: <000f01c69295$f481af80$7001a8c0@parisi02>

Lou,

> Regarding the kernel version - I have a fresh install of CentOS 4 and have
> updated all packages using yum.  Lm_sensors is actually the first thing I am
> trying to get running on this new box before I put it off into a closet.
> The output from uname -r is below:
> # uname -r
> 2.6.9-34.0.1.EL
> 
> The only other thing that is possible is I first had lm_sensors 2.8
> installed from yum and then when I was having the problem with the cpu temps
> removed using yum and then downloaded the source and compiled and installed.
> 
> Do you think there could be something left over from this? The version from
> sensors shows 2.10
> # sensors -v
> sensors version 2.10.0 with libsensors version 2.10.0

No, for Linux 2.6 kernels, the lm_sensors package only brings the user
space support, so it can't explain the observed inconsistencies on the
kernel front. It seems that you have an older version of the it87
driver than your kernel version suggests. I can't explain it, we would
need to know how exactly CentOS built their kernel.

Anyway, it doesn't matter that much, you can live without vid readings
- we aren't even sure if your boards support that.

> The only other thing I can think of is I am running amd64 version of linux
> which can sometimes cause some strange behaviors in applications.

It can't explain the observed inconsistencies either, and I doubt it
will cause any kind of problem on the lm_sensors side in general.

-- 
Jean Delvare


  parent reply	other threads:[~2006-06-19  9:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-18  5:13 [lm-sensors] CPU Temp on ECS NFORCE3-A939 Lou Parisi
2006-06-18 10:11 ` Jean Delvare
2006-06-18 14:22 ` Brian Beardall
2006-06-18 14:51 ` Jean Delvare
2006-06-18 15:10 ` Brian Beardall
2006-06-18 15:54 ` Lou Parisi
2006-06-18 16:55 ` Jean Delvare
2006-06-18 17:16 ` Brian Beardall
2006-06-18 18:12 ` Jean Delvare
2006-06-18 19:58 ` Jean Delvare
2006-06-18 22:18 ` Brian Beardall
2006-06-19  3:12 ` Lou Parisi
2006-06-19  4:49 ` Lou Parisi
2006-06-19  9:54 ` Jean Delvare [this message]
2006-06-19 10:01 ` Jean Delvare
2006-06-20  0:13 ` Lou Parisi
2006-06-20 12:52 ` Jean Delvare
2006-06-25  2:26 ` Brian Beardall
2006-06-26 20:39 ` Jean Delvare
2006-06-27  0:08 ` Brian Beardall
2006-07-03  7:07 ` Lou Parisi

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=20060619115445.55524ba3.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --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.