public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 11:58:28 +0000	[thread overview]
Message-ID: <3FFFE8E4.8080004@clanhk.org> (raw)
In-Reply-To: <200401100754.47752.gene.heskett@verizon.net>

Gene Heskett wrote:

>On Friday 09 January 2004 20:47, J. Ryan Earl wrote:
>  
>
>I've also got a bttv card, whose init seems to be done quite early in 
>the bootup, and that requires I have i2c-dev in the kernel.  So I 
>might as well put it all in, the current situation.  All in, or all 
>out, it doesn't work.  A run of sensors right now, returns this:
>  
>

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.

-ryan


  reply	other threads:[~2004-01-10 18:04 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 [this message]
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
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=3FFFE8E4.8080004@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