From: "J. Ryan Earl" <heretic@clanhk.org>
To: Martin Schlemmer <azarah@nosferatu.za.org>
Cc: gene.heskett@verizon.net,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Q re /proc/bus/i2c
Date: Sat, 10 Jan 2004 17:32:08 +0000 [thread overview]
Message-ID: <40003718.2010007@clanhk.org> (raw)
In-Reply-To: <1073760037.9096.16.camel@nosferatu.lan>
Martin Schlemmer wrote:
>On Sat, 2004-01-10 at 13:58, J. Ryan Earl wrote:
>
>
>>>A couple questions:
>>>
>>>1) Have you installed the lm-sensors package?
>>>2) What kernel version?
>>>
>>>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.
>>>
>>>
>>>
>
>Uhm, AFIAK, you should _NOT_ install the drivers from the lm-sensors
>package, but use those in the kernel. Check the docs, they explicitly
>say that you should only do:
>
> # make user user_install
>
>if you have 2.6 kernel. Further, you do not _need_ lm-sensors package,
>as if you only want to check/monitor one setting, you can get it from
>/sys, and if you use gkrellm, it do not even use libsensors anymore
>(and thus works without, as it have since 2.6 support, before even
>libsensors was ported to understand sysfs) ...
>
>
It still uses devfs I think. Or you can just run the mkdev.sh command
to create the proper devices.
This is from installing lm-sensors:
* *****************************************************************
*
* This ebuild assumes your /usr/src/linux kernel is the one you
* used to build i2c-2.8.2.
*
* For 2.5+ series kernels, use the support already in the kernel
* under 'Character devices' -> 'I2C support' and then merge this
* ebuild.
*
* To cross-compile, 'export LINUX="/lib/modules/<version>/build"'
* or symlink /usr/src/linux to another kernel.
*
* *****************************************************************
You always need the lm-sensors package, period--it has all the user land
utilities plus drivers for most of the chips/sensors. You only need the
i2c package on earlier kernels, use built in for 2.6. On my Asus
boards, I use the asb100 module which is not in the kernel. `find
/usr/src/linux -name asb100* -print` Not there. Remember, you'll have
to recompile the lm-sensors package everytime you upgrade you change
your kernel.
-ryan
next prev parent reply other threads:[~2004-01-10 23:37 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 [this message]
2004-01-10 20:35 ` Gene Heskett
2004-01-10 20:56 ` Gene Heskett
2004-01-10 17:51 ` J. Ryan Earl
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=40003718.2010007@clanhk.org \
--to=heretic@clanhk.org \
--cc=azarah@nosferatu.za.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