From: Sergey Vlasov <vsu@altlinux.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2, sensors and sysfs
Date: Thu, 31 Jul 2003 20:52:22 +0400 [thread overview]
Message-ID: <20030731205222.0f1521f1.vsu@altlinux.ru> (raw)
In-Reply-To: 1059669362.23100.12.camel@laurelin
On 31 Jul 2003 18:36:02 +0200
Flameeyes <daps_mls@libero.it> wrote:
> 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?
Currently (2.6.0-test2) i2c-viapro and via686a don't work together -
you can use only one of them. This is because they want to work with
the same PCI device - and having multiple drivers for one device is
not allowed for obvious reasons.
This issue is already known to the lm_sensors developers.
So you will need to remove i2c-viapro for now (but leave i2c-isa);
then you will see the via686a sensors again.
next prev parent reply other threads:[~2003-08-04 13:24 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
2003-07-31 17:01 ` Flameeyes
2003-07-31 17:36 ` Greg KH
2003-07-31 16:52 ` Sergey Vlasov [this message]
[not found] ` <20030731211732.5591495d.vsu@altlinux.ru>
2003-07-31 18:02 ` Flameeyes
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=20030731205222.0f1521f1.vsu@altlinux.ru \
--to=vsu@altlinux.ru \
--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;
as well as URLs for NNTP newsgroup(s).