From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] sensord with rrd
Date: Wed, 14 Jan 2009 20:03:33 +0000 [thread overview]
Message-ID: <20090114210333.6d8d90ce@hyperion.delvare> (raw)
In-Reply-To: <gkimcg$46k$1@ger.gmane.org>
On Wed, 14 Jan 2009 11:01:22 -0800, Mark Nienberg wrote:
> Jean Delvare wrote:
> >> [root@gecko ~]# rpm -q lm_sensors sensord
> >> lm_sensors-2.10.6-55.el5
> >> sensord-2.10.6-55.el5
> >
> > This is somewhat old...
>
> Agreed, but it is the latest rpm I could find already built for centOS 5.2.
>
> > What hardware monitoring chip do you have? sensord in lm-sensors 2.10.x
> > lacks support for many recent chips. Could be that logging works
> > somewhat in generic mode but rrd supports need chip-specific support.
>
> See my post from Jan 5 with subject "Asus KFN4-DRE board".
>
> http://article.gmane.org/gmane.linux.drivers.sensors/18601
>
> You can see that I have tried specifically setting the chip in the sensord init file,
> but it didn't help.
I confirm that sensord in lm-sensors 2.10 has no support for the
w83792d. You need lm-sensors 3.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-01-14 20:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 18:26 [lm-sensors] sensord with rrd Mark Nienberg
2009-01-14 10:32 ` Jean Delvare
2009-01-14 17:57 ` Mark Nienberg
2009-01-14 18:44 ` Jean Delvare
2009-01-14 19:01 ` Mark Nienberg
2009-01-14 20:03 ` Jean Delvare [this message]
2009-01-14 20:26 ` Mark E. Hansen
2009-01-14 20:39 ` Jean Delvare
2009-01-14 20:54 ` Mark Nienberg
2009-01-14 21:08 ` Mark E. Hansen
2009-01-14 21:58 ` Jean Delvare
2009-01-14 22:12 ` Mark E. Hansen
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=20090114210333.6d8d90ce@hyperion.delvare \
--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.