mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: Martin Schlemmer <azarah@nosferatu.za.org>,
	John Lash <jlash@speakeasy.net>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Q re /proc/bus/i2c
Date: Sat, 10 Jan 2004 14:15:46 -0500	[thread overview]
Message-ID: <200401101415.46745.gene.heskett@verizon.net> (raw)
In-Reply-To: <1073758800.9096.12.camel@nosferatu.lan>

On Saturday 10 January 2004 13:20, Martin Schlemmer wrote:
>On Sat, 2004-01-10 at 17:59, John Lash wrote:
>> 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".
>
>Right, needs sysfs mounted.  You should (after creating /sys) add
>the following to /etc/fstab:
>
>--
>none	/sys	sysfs	defaults	0 0
>--

>From my fstab, and its been there for several months now:
---
none    /sys    sysfs   defaults        0 0
---
Also, from my mtab:
Well, I was gonna quote that too, but apparently my entry in 
rc.sysinit doesn't record it in mtab.  I've got a message in the log 
to the effect that its already mounted or is otherwise busy.  I'd put 
that line in rc.sysinit a few (2-3) weeks ago, thinking it needed to 
be done earlier than the fstab driven mount.  I'll remove it from 
rc.sysinit and reboot for effects.

Done.

I also moved the mount of /proc/bus/usb to fstab while I was at it, 
and they are all recorded in mtab now:
---
none /proc/bus/usb usbfs rw 0 0
none /sys sysfs rw 0 0
---
But the response from sensors is still as I posted before, "Algorithm: 
Unavailable from sysfs"

tvtime still works, so thats promising.  Sounds like they (the Feed 
Bag Information folks) got something/someone(s) trapped on a plane at 
Dulles according to FOX News, who are of course makeing the usual 
mountain out of whats probably a molehill.

Next thing to check?

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


  reply	other threads:[~2004-01-10 19:15 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
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 [this message]
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=200401101415.46745.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.net \
    --cc=azarah@nosferatu.za.org \
    --cc=jlash@speakeasy.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®