mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: "J. Ryan Earl" <heretic@clanhk.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Q re /proc/bus/i2c
Date: Sat, 10 Jan 2004 15:56:01 -0500	[thread overview]
Message-ID: <200401101556.01736.gene.heskett@verizon.net> (raw)
In-Reply-To: <3FFFE8E4.8080004@clanhk.org>

On Saturday 10 January 2004 06:58, J. Ryan Earl wrote:
>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?

By hand, make user_install did not in fact overwrite any of the older 
sensors stuff, so I did it with mc.

>2) What kernel version?

2.6.1-mm1

>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?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty: soap,
ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.


  parent reply	other threads:[~2004-01-10 20:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10  6:17 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 [this message]
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=200401101556.01736.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.net \
    --cc=heretic@clanhk.org \
    --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

all inboxes | Powered by JetHome®