From: linux-kernel@ton.iguana.be (Ton Hospel)
To: linux-kernel@vger.kernel.org
Subject: Re: Sensors and linux 2.6.0-test4-bk8 question
Date: Sun, 7 Sep 2003 15:09:58 +0000 (UTC) [thread overview]
Message-ID: <bjfho6$k3j$1@post.home.lunix> (raw)
In-Reply-To: 1062934034.7923.2.camel@rousalka.dyndns.org
In article <1062934034.7923.2.camel@rousalka.dyndns.org>,
Nicolas Mailhot <Nicolas.Mailhot@laPoste.net> writes:
> --=-scQmpSv1XJXK2Qdu4l48
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
>
> Hi,
>
> Please bear with me and enlighten me a bit. I've been fiddling with
> 2.5/2.6 for some time, and got most of my hardware working (including
> acpi...) better than in 2.4. (in fact now I'm using only 2.6). So now I
> got to the point where I'm looking at nice-to-have stuff like sensors.
>
> I know libsensors is not yet 2.6 aware, but I thought sensed values
> where available in sysfs if one wanted to manually read them. Since I
> have via hardware:
If there is any interest, I have a perl program that does a configurable
display for 2.6
>
> Now there is no sensor-related message as far as I can see in my dmesg,
> and I do not seem to find any temperature/fan related info in /sys:
>
You still need the bus and chip drivers before anything appears.
Which ones is basically the same as with the old lmsensors stuff, so
look in their docs.
next prev parent reply other threads:[~2003-09-07 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-07 11:27 Sensors and linux 2.6.0-test4-bk8 question Nicolas Mailhot
2003-09-07 15:09 ` Ton Hospel [this message]
2003-09-07 17:35 ` Josh McKinney
[not found] ` <20030907173515.GA15338@_orming>
2003-09-07 20:17 ` Ton Hospel
2003-09-09 17:06 ` Ton Hospel
2003-09-07 16:38 Nicolas Mailhot
2003-09-08 6:20 "Andrey Borzenkov"
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='bjfho6$k3j$1@post.home.lunix' \
--to=linux-kernel@ton.iguana.be \
--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).