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] Reading ASUS P5GD1-VM sensors
Date: Thu, 06 Apr 2006 19:44:49 +0000	[thread overview]
Message-ID: <20060406214449.4556ca21.khali@linux-fr.org> (raw)
In-Reply-To: <44354E63.5090703@gmail.com>

Hi Jean,

> Reading the P5GD1-VM sensors
> 
> I have been using lmsensors for quite a while now but recently stumbled 
> across an ASUS P5GD1-VM MotherBoard at work.
> 
> I installed the i2c and lmsensors, read the quick installation 
> documentation, ran the suggested utilities and was able to identify the 
> sensor chip as a Winbound w83627ehf.
> 
> I then applied all the recommendations, updated the files as specified, 
> restarted my machine and came out empty handed. No sensors detected. 
> Spent quite a bit of time googling to get further information about the 
> w83627ehf Super IO Chip, but results were unsuccessful.
> (...)
> Of course Asus Probe reads all parameters correctly, so why was it that 
> I could not do it in Slackware 10.2 using a 2.4.31 kernel.

Because the w83627ehf driver only exists for Linux 2.6 at the moment.
Nobody ported it back to lm_sensors CVS (which is where drivers for
Linux 2.4 are maintained), most probably due to a lack of resources and
interest.

I just modified our "new drivers" web page to mention your interest in
a backport.

Your trick of forcing the w83781d driver is interesting, although a bit
complex for the regular users, and there are also some new features of
the W83627EHF chip which you will miss. But I agree that it's better
than nothing.

-- 
Jean Delvare


      reply	other threads:[~2006-04-06 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-06 17:22 [lm-sensors] Reading ASUS P5GD1-VM sensors Jean Dumas
2006-04-06 19:44 ` Jean Delvare [this message]

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=20060406214449.4556ca21.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.