From: Luca Tettamanti <kronos.it@gmail.com>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [lm-sensors] it87 sensors need an ACPI driver (2.6.31)
Date: Mon, 21 Sep 2009 17:07:23 +0200 [thread overview]
Message-ID: <68676e00909210807h71171ae6l59eb4e8eb972c161@mail.gmail.com> (raw)
In-Reply-To: <200909211102.25354.gene.heskett@verizon.net>
On Mon, Sep 21, 2009 at 5:02 PM, Gene Heskett <gene.heskett@verizon.net> wrote:
> On Monday 21 September 2009, Luca Tettamanti wrote:
>>On Mon, Sep 21, 2009 at 2:35 AM, Gene Heskett <gene.heskett@verizon.net>
> wrote:
>>> On Sunday 20 September 2009, Luca Tettamanti wrote:
>>>>On Sun, Sep 20, 2009 at 10:37 PM, Gene Heskett <gene.heskett@verizon.net>
>>>
>>> wrote:
>>>>> Jumping in the middle of this, I am another that it87 doesn't work very
>>>>> well for, ASUS M2N SLI Deluxe board.
>>>>
>>>>Please define "doesn't work well". asus_atk0110 should handle that
>>>>board. In case of troubles enable CONFIG_HWMON_DEBUG_CHIP, load
>>>>asus_atk0110 and post the content of the kernel log.
>>>
>>> With that CONFIG_HWMON_DEBUG_CHIP enabled, dmesg (attached) looks semi-
>>> kosher, but neither gkrellm nor sensors can show me data until it87 is
>>> loaded. I unloaded it87 and reloaded it several times just now.
>>> Something funkity someplace... Is there a new application I need to dl
>>> and install?
>>
>>You probably need to upgrade the lm-sensors package. Version 3.1.1 has
>>support for ACPI devices.
>>
> Its the latest in the F10 repos, Luca. I have these:
>
> lm_sensors-3.0.2-1.fc10.i386
> lm_sensors-sensord-3.0.2-1.fc10.i386
Too old.
> I also note that while asus_atk0110 is loaded, it has no link count in an
> lsmod output. This has little or nothing to do with the lm_sensors version,
> when the kernel itself (2.6.31 final) doesn't get any real data. Or can it?
Usage count is zero because nothing is using the driver ;-) As the
dmesg shows the driver is loaded and has correctly identified the
sensors.
> I've stumbled around is the /sys/fs tree looking for data, but wasn't able to
> do anything but get stuck in a re-entrant loop, that is a bowl of spaghetti,
> well stirred.
You'll find the relevant sysfs entries under /sys/class/hwmon/
Luca
next prev parent reply other threads:[~2009-09-21 15:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 8:20 wixor
2009-09-20 9:10 ` Holger Hoffstaette
2009-09-20 9:17 ` Alan Jenkins
2009-09-20 12:20 ` [lm-sensors] " Luca Tettamanti
2009-09-20 12:46 ` wixor
2009-09-20 20:37 ` Gene Heskett
2009-09-20 21:31 ` Luca Tettamanti
2009-09-21 0:35 ` Gene Heskett
2009-09-21 9:43 ` Luca Tettamanti
2009-09-21 15:02 ` Gene Heskett
2009-09-21 15:07 ` Luca Tettamanti [this message]
2009-10-05 0:11 ` Brad Campbell
2009-10-05 9:12 ` Michael Tokarev
2009-10-05 13:48 ` Brad Campbell
2009-10-05 15:37 ` Luca Tettamanti
2009-10-05 16:40 ` Jean Delvare
2009-10-05 16:42 ` Michael Tokarev
2009-10-06 15:00 ` Luca Tettamanti
2009-10-06 15:22 ` Michael Tokarev
2009-10-06 15:34 ` Luca Tettamanti
2009-10-06 15:41 ` Michael Tokarev
2009-10-06 16:00 ` Jean Delvare
2009-10-06 16:10 ` Luca Tettamanti
2009-10-06 16:04 ` Alan Jenkins
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=68676e00909210807h71171ae6l59eb4e8eb972c161@mail.gmail.com \
--to=kronos.it@gmail.com \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®