From: fabien.pourias@thales-is.com (fabien.pourias)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] RE: w83792d driver for the 2.6 kernel
Date: Tue, 21 Jun 2005 11:20:22 +0000 [thread overview]
Message-ID: <42AA952B@mailmlk.tisfr.thales> (raw)
In-Reply-To: <FF9D611BFCDB1E42B37FAA148096BECE5E7741@weshml03.winbond.com.tw>
>=== Original Message From "Jean Delvare" <khali@linux-fr.org> ==>Hi Fabien,
>
>> Thanks a lot for the patch. It works pretty well (i.e. we see meaningful
>> values when we run sensors -u) but the user tools are not up to date :
>> - sensors-detect fails to detect the w83792d
>> - the "sensors" output only includes the old w83627hf data
>
>Did you update the lm_sensors user-space tools as Rudolf Marek
>recommended? Support for the W83792D is in CVS only.
I used the daily snapshot as recommanded by Rudolf and had to :
- copy the etc/sensors.conf.eg to /etc/sensors.conf
- run the sensors-detect from the lm_sensors distribution (the make
user_install command did not install it)
- run /usr/local/bin/sensors to make sure I did not run the Fedora version of
sensors.
I also removed the Fedora version but the sensors-detect script still failed
to detect the 83792d. Could it be because it is not properly installed ? What
commands should I issue in addition to "make user; make user_install" ?
thanks for your help,
F. Pourias
next prev parent reply other threads:[~2005-06-21 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 3:42 [lm-sensors] RE: w83792d driver for the 2.6 kernel Huang0
2005-06-21 8:49 ` Rudolf Marek
2005-06-21 10:50 ` fabien.pourias
2005-06-21 11:00 ` Jean Delvare
2005-06-21 11:20 ` fabien.pourias [this message]
2005-06-21 11:43 ` Jean Delvare
2005-06-22 3:45 ` Huang0
2005-06-22 4:08 ` Huang0
2005-06-22 10:15 ` P.O. Gaillard
2005-06-22 10:34 ` Rudolf Marek
2005-06-22 12:07 ` fabien.pourias
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=42AA952B@mailmlk.tisfr.thales \
--to=fabien.pourias@thales-is.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.