From: "J. Ryan Earl" <heretic@clanhk.org>
To: gene.heskett@verizon.net
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Q re /proc/bus/i2c
Date: Sat, 10 Jan 2004 17:51:45 +0000 [thread overview]
Message-ID: <40003BB1.2010709@clanhk.org> (raw)
In-Reply-To: <200401101556.01736.gene.heskett@verizon.net>
Gene Heskett wrote:
>>Even with 2.6, you need to install the lm-sensors package, but not
>>the i2c package as the kernel already has everything needed in it.
>>The lm-sensors packages contains drivers for all the sensor chips.
>>After you get lm-sensors installed on your current kernel, run
>>sensors-detect to get the proper modules loaded for your hardware.
>>
>>-ryan
>>
>>
>
>Reread the README in lm_sensors-2.8.2. I've followed that, except
>that a make user_install apparently only goes thru the motions
>without reporting any errors.
>
>Been there, done that, a dozen times maybe?
>
>
OK, I'm going to try this on 2.6. The sensor I use isn't in the kernel:
asb100 (Asus's ASIC).
I know for a fact the 2.6 doesn't support nearly as many sensors as the
lm-sensors package, but I never tried getting it all setup on 2.6 since
2.6 hasn't been stable enough for what I needed it for. I thought that
lm-sensors merely used the in-kernel i2c interface but provided it's own
driver modules. I realize that the documentation says to build only the
user utilities, but I thought that was just an error. I let portage
take care of all the details.
-ryan
next prev parent reply other threads:[~2004-01-10 23:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 6:17 Q re /proc/bus/i2c Gene Heskett
2004-01-10 1:47 ` J. Ryan Earl
2004-01-10 12:54 ` Gene Heskett
2004-01-10 11:58 ` J. Ryan Earl
2004-01-10 18:40 ` Martin Schlemmer
2004-01-10 17:32 ` J. Ryan Earl
2004-01-10 20:35 ` Gene Heskett
2004-01-10 20:56 ` Gene Heskett
2004-01-10 17:51 ` J. Ryan Earl [this message]
2004-01-10 15:59 ` John Lash
2004-01-10 18:12 ` Gene Heskett
2004-01-10 18:20 ` Martin Schlemmer
2004-01-10 19:15 ` Gene Heskett
2004-01-10 19:40 ` Martin Schlemmer
2004-01-10 23:14 ` Gene Heskett
2004-01-10 20:57 ` Gene Heskett
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=40003BB1.2010709@clanhk.org \
--to=heretic@clanhk.org \
--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