From: Gene Heskett <gene.heskett@verizon.net>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Q re /proc/bus/i2c
Date: Sat, 10 Jan 2004 01:17:42 -0500 [thread overview]
Message-ID: <200401100117.42252.gene.heskett@verizon.net> (raw)
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.
I can't see the forest for all the trees here, so where do I stand and
start swinging my chainsaw?
--
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.
next reply other threads:[~2004-01-10 6:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 6:17 Gene Heskett [this message]
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
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=200401100117.42252.gene.heskett@verizon.net \
--to=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
all inboxes | Powered by JetHome®