All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boleslaw Ciesielski <bolek-sensors@curl.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Backporting coretemp and w83793 to 2.6.18
Date: Wed, 22 Aug 2007 02:38:36 +0000	[thread overview]
Message-ID: <46CBA1AC.5070400@curl.com> (raw)
In-Reply-To: <46CB9161.5090408@curl.com>

Boleslaw Ciesielski wrote:
> I have this new server based on the Asus DSBF-DE/SAS motherboard and a
> pair of Xeons 5355. I want to run CentOS 5.0 (RHEL 5 clone) on it.
> CentOS 5.0 is based on the 2.6.18 kernel and as such has drivers for
> everything *except* for the sensors. The motherboard uses 83793 chip.
> 
> So, I wanted to backport the w83793 and coretemp drivers to 2.6.18
> kernel. I took the source from 2.6.22.3 for these two and tried to
> compile them for 2.6.18.
> 
> The w83793 compiles and loads as is, without any changes.
> 
> coretemp required some changes related to msr so I just restored the
> code that was in there when coretemp was floating around as a patch
> before it made it to the kernel. See the attached patch for detail.
> 
> Anyway, with those changes both coretemp and w83793 compile and load. I
> also copied sensors.conf from 2.10.4 and ran "sensors -s". However,
> neither is providing any data. Output looks like this:

Just a quick update. I got reply off-list that I am missing the new 
versions of the user tools. I installed 2.10.4 rpm from Fedora 7 and I 
get the readings now.

Thank you

Bolek

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  reply	other threads:[~2007-08-22  2:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22  1:29 [lm-sensors] Backporting coretemp and w83793 to 2.6.18 Boleslaw Ciesielski
2007-08-22  2:38 ` Boleslaw Ciesielski [this message]
2008-05-05 17:05 ` Darth Tumi
2008-05-05 17:16 ` Darth Tumi
2008-05-12 12:37 ` Jean Delvare
2008-05-12 13:22 ` Darth Tumi

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=46CBA1AC.5070400@curl.com \
    --to=bolek-sensors@curl.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.