From: Greg KH <greg@kroah.com>
To: Flameeyes <daps_mls@libero.it>
Cc: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test2, sensors and sysfs
Date: Thu, 31 Jul 2003 09:50:56 -0700 [thread overview]
Message-ID: <20030731165056.GA3622@kroah.com> (raw)
In-Reply-To: <1059669362.23100.12.camel@laurelin>
On Thu, Jul 31, 2003 at 06:36:02PM +0200, Flameeyes wrote:
> Hi,
> I need to know the system temperature for check some stability problems,
> under 2.4 I was using lm_sensors patches, using i2c-viapro as i2c bus
> and via686a as chip driver (I'm using a via 686 southbridge, see the
> lspci output attached), and I was able to use sensors for see the
> temperatures.
> With the 2.6.0-test2 (and all earlier kernels since 2.5.69), I'm not
> able anymore to see the temperature, nor with sensor (or libsensor
> library) nor with sysfs (that, AFAIK, should be the new method to access
> sensors data).
> The only i2c device that I can see in the sysfs is the tuner of my
> bt-based tv card.
> I tried either with i2c-viapro and via686a as modules, and built-in in
> kernel. Nothing changes. Also dmesg doesn't output anything.
> I have missed something?
What sensor drivers are you using in 2.4? Are these drivers even
present in 2.6? Remember, a lot of them have not been ported yet.
And yes, libsensors does not work right now for 2.6, you should be able
to get the sensor info yourself out of sysfs.
thanks,
greg k-h
next prev parent reply other threads:[~2003-07-31 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 16:36 2.6.0-test2, sensors and sysfs Flameeyes
2003-07-31 16:50 ` Greg KH [this message]
2003-07-31 17:01 ` Flameeyes
2003-07-31 17:36 ` Greg KH
2003-07-31 16:52 ` Sergey Vlasov
[not found] ` <20030731211732.5591495d.vsu@altlinux.ru>
2003-07-31 18:02 ` Flameeyes
-- strict thread matches above, loose matches on Subject: below --
2003-07-31 17:21 Tomasz Torcz
2003-07-31 17:34 ` Greg KH
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=20030731165056.GA3622@kroah.com \
--to=greg@kroah.com \
--cc=daps_mls@libero.it \
--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