From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] new abituguru driver in mm kernel
Date: Wed, 05 Jul 2006 17:37:33 +0000 [thread overview]
Message-ID: <20060705193733.cf1c71c9.khali@linux-fr.org> (raw)
In-Reply-To: <ce9ef0d90607041146t6837a584x68d1ab7e528139ea@mail.gmail.com>
Hi Sunil,
> A related question: gkrellm2 (2.2.9) refuses to see my sensors as reported
> by abit driver, but its able to see bogus sensors reported by w83627hf if I
> modprobe it. sensors and ksensors, both see the values correctly.
>
> Why would gkrellm not see them? Is there a configuration setting that
> gkrellm reads which works for w83627hf but not for abituguru.
gkrellm accesses /sys directly instead of using libsensors. The
consequence of this unfortunate choice is that the results you get with
gkrellm can differ from what all other hardware monitoring frontends
report, and when support for new chips is added gkrellm doesn't benefit
from the libsensors update and must implement support on its own.
So you better complain to the gkrellm folks, there's nothing we can do
about it.
--
Jean Delvare
next prev parent reply other threads:[~2006-07-05 17:37 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 18:46 [lm-sensors] new abituguru driver in mm kernel Sunil Kumar
2006-07-04 20:10 ` Stephen Cormier
2006-07-05 6:38 ` Hans de Goede
2006-07-05 16:35 ` Sunil Kumar
2006-07-05 17:37 ` Jean Delvare [this message]
2006-07-05 17:41 ` Hans de Goede
2006-07-05 17:44 ` Hans de Goede
2006-07-05 20:11 ` Hans de Goede
2006-07-05 20:16 ` Sunil Kumar
2006-07-06 1:09 ` Sunil Kumar
2006-07-06 1:24 ` Stephen Cormier
2006-07-08 23:03 ` Sunil Kumar
2006-07-09 8:16 ` Hans de Goede
2006-07-09 14:44 ` Sunil Kumar
2006-07-09 16:41 ` Sunil Kumar
2006-07-09 17:11 ` Hans de Goede
2006-07-09 17:30 ` Sunil Kumar
2006-07-09 20:32 ` Hans de Goede
2006-07-09 20:54 ` Sunil Kumar
2006-07-10 4:33 ` Hans de Goede
2006-07-11 4:43 ` Sunil Kumar
2006-07-14 19:15 ` Hans de Goede
2006-07-14 19:33 ` Sunil Kumar
2006-07-14 19:43 ` Hans de Goede
2006-07-14 19:50 ` Sunil Kumar
2006-07-15 0:52 ` Sunil Kumar
2006-07-19 4:35 ` Hans de Goede
2006-07-19 20:34 ` Sunil Kumar
2006-07-19 22:42 ` Sunil Kumar
2006-07-19 23:02 ` Sunil Kumar
2006-07-20 5:23 ` Sunil Kumar
2006-07-20 7:54 ` Hans de Goede
2006-07-20 14:37 ` Sunil Kumar
2006-07-20 17:13 ` Sunil Kumar
2006-07-20 17:14 ` Sunil Kumar
2006-07-21 6:10 ` Hans de Goede
2006-07-21 16:15 ` Sunil Kumar
2006-07-25 3:27 ` Sunil Kumar
2006-07-26 14:30 ` Hans de Goede
2006-07-26 18:32 ` Sunil Kumar
2006-07-26 20:43 ` Hans de Goede
2006-07-27 0:48 ` Sunil Kumar
2006-07-27 8:19 ` Hans de Goede
2006-07-27 14:31 ` Sunil Kumar
2006-07-27 14:44 ` Hans de Goede
2006-07-27 16:07 ` Sunil Kumar
2006-08-01 4:01 ` Hans de Goede
2006-08-25 23:13 ` Sunil Kumar
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=20060705193733.cf1c71c9.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.