From: John Lash <jlash@speakeasy.net>
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 09:59:11 -0600 [thread overview]
Message-ID: <20040110095911.7b99d40c.jlash@speakeasy.net> (raw)
In-Reply-To: <200401100754.47752.gene.heskett@verizon.net>
In a 2.6.x kernel, the sensors information is kept in sysfs. I haven't actually
tried installing lmsensors on my 2.6 system, but if I look in:
/sys/bus/i2c/devices/0-002d/
I can see files for all of the sensors on my system.
Check below in your last mail where it is complaining about "Algorithm:
Unavailable from sysfs".
--john
On Sat, 10 Jan 2004 07:54:47 -0500
Gene Heskett <gene.heskett@verizon.net> wrote:
> On Friday 09 January 2004 20:47, J. Ryan Earl wrote:
> >Gene Heskett wrote:
> >>Greetings;
> >>
> >>I'm still trying to make sensors (and gkrellm) work when booted to
> >> a 2.6.x kernel.
> >>
> >>The lm_sensors people say it should "just work", but so far no one
> >> has acknowledged that it doesn't work here because I don't have an
> >> "i2c" in my /proc/bus directory. Browsing all the
> >> sensors-detection stuff, in particular the bus detection script,
> >> this thing is hard coded to look for /proc/bus/i2c by default, or
> >> you can pass it an argument.
> >>
> >>I don't have a "/proc/bus/i2c". Passing this script the
> >> /sys/bus/i2c argument only gets an error return complaining that
> >> its a directory.
> >
> >You've run the "sensors-detect" script and have all the proper
> > modules loaded for your hardware? You should be able to just run
> > "sensors" to see if everything is working.
> >
> 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:
>
> [root@coyote lm_sensors-2.8.2]# sensors
> eeprom-i2c-1-51
> Adapter: SMBus Via Pro adapter at 5000
> Algorithm: Unavailable from sysfs
> Memory type: Unavailable
>
> eeprom-i2c-1-50
> Adapter: SMBus Via Pro adapter at 5000
> Algorithm: Unavailable from sysfs
> Memory type: Unavailable
>
> eeprom-i2c-0-57
> Adapter: bt878 #0 [sw]
> Algorithm: Unavailable from sysfs
> Memory type: Unavailable
>
> eeprom-i2c-0-56
> Adapter: bt878 #0 [sw]
> Algorithm: Unavailable from sysfs
> Memory type: Unavailable
>
> eeprom-i2c-0-55
> Adapter: bt878 #0 [sw]
> Algorithm: Unavailable from sysfs
> Memory type: Unavailable
>
> eeprom-i2c-0-54
> Adapter: bt878 #0 [sw]
> Algorithm: Unavailable from sysfs
> Memory type: Unavailable
>
> eeprom-i2c-0-53
> Adapter: bt878 #0 [sw]
> Algorithm: Unavailable from sysfs
> Memory type: Unavailable
>
> eeprom-i2c-0-52
> Adapter: bt878 #0 [sw]
> Algorithm: Unavailable from sysfs
> Memory type: Unavailable
>
> eeprom-i2c-0-51
> Adapter: bt878 #0 [sw]
> Algorithm: Unavailable from sysfs
> Memory type: Unavailable
>
> eeprom-i2c-0-50
> Adapter: bt878 #0 [sw]
> Algorithm: Unavailable from sysfs
> Memory type: Unavailable
>
> Temic-i2c-0-61
> Adapter: bt878 #0 [sw]
> Algorithm: Unavailable from sysfs
>
> Does this give a clue I'm too clueless to see?
>
> >-ryan
>
> --
> 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.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2004-01-10 15:59 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
2004-01-10 15:59 ` John Lash [this message]
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=20040110095911.7b99d40c.jlash@speakeasy.net \
--to=jlash@speakeasy.net \
--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