All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] new vt1211 driver: Can't access procfs/sysfs file
Date: Sun, 03 Dec 2006 10:36:05 +0000	[thread overview]
Message-ID: <20061203113605.a00f8766.khali@linux-fr.org> (raw)
In-Reply-To: <45728865.5020308@xs4all.nl>

Hi Udo,

On Sun, 03 Dec 2006 09:18:45 +0100, Udo van den Heuvel wrote:
> Since booting into 2.6.19 on my VIA SP8000 I have a small problem with
> the vt1211 sensors driver:
> 
> sensors -s gives:
> 
> vt1211-isa-6000: Can't access procfs/sysfs file for writing;

Are you root when running this command?

> 
> Also the temperature sensors are not shown.

Please provide the complete output of "sensors".

> 
> sysfs is of course mounted and accessible.
> lm_sensors 2.10.1 we have installed before rebooting.

What does "sensors -v" return?

> 
> The vt1211 sensors stuff has moved to
> /sys/bus/platform/drivers/vt1211/vt1211.24576. In that directory the
> files with sensors info for rpm, voltage etc can be found.

Yes, this is OK. You should also have a link in /sys/class/hwmon
pointing to it.

> 
> Of course the sensor's location on the bus was not changed so I am
> wondering what is wrong, why can't the sensors command find the files in
> /sys/bus/platform/drivers/vt1211/vt1211.24576?

Please provide a detailed listing (ls -l) of the files present in this
directory.

-- 
Jean Delvare


  reply	other threads:[~2006-12-03 10:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-03  8:18 [lm-sensors] new vt1211 driver: Can't access procfs/sysfs file for Udo van den Heuvel
2006-12-03 10:36 ` Jean Delvare [this message]
2006-12-03 10:41 ` [lm-sensors] new vt1211 driver: Can't access procfs/sysfs file Udo van den Heuvel
2006-12-03 11:04 ` Jean Delvare
2006-12-03 11:13 ` Udo van den Heuvel
2006-12-03 12:26 ` Jean Delvare
2006-12-03 12:33 ` Udo van den Heuvel
2006-12-03 13:42 ` Jean Delvare
2006-12-03 14:34 ` Udo van den Heuvel

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=20061203113605.a00f8766.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --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.