From: ymu@winbond.com (Yuan Mu)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Linux 2.6.16 kernel and "Can't access
Date: Fri, 14 Jul 2006 05:08:03 +0000 [thread overview]
Message-ID: <44B726B3.9030704@winbond.com> (raw)
Hi Keith,
> I've installed lm_sensors v2.10.0 on a Linux system running a 2.16.6
> kernel. That's a Debian kernel, but I've also tried with a 2.6.17.4
> vanilla kernel.
>
> lm_sensors builds and installs fine, and sensors-detect runs and detects
> i2c-i801. The 'sensors' command gives 'Can't access procfs/sysfs file'.
> The FAQ suggests ensuring that /sys is mounted and populated (it is),
> and that i2c-proc is loaded. That module is not loaded, but it doesn't
> seem to be in the 2.16.6 kernels.
>
> Should I have an i2c-proc module? If not, any further suggestions would
> be welcome - thanks.
Can you give the output of sensors-detect and output of `ls /sys/bus/i2c/drivers/*`.
I think it may because it has not find any hwmon chips OR library linked to "sensors"
is not the right one.
--
Best Regards
Yuan Mu
=============================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.
next reply other threads:[~2006-07-14 5:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 5:08 Yuan Mu [this message]
2006-07-14 11:35 ` [lm-sensors] Linux 2.6.16 kernel and "Can't access com.ea
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=44B726B3.9030704@winbond.com \
--to=ymu@winbond.com \
--cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.