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 11:04:27 +0000	[thread overview]
Message-ID: <20061203120427.c61e0cbe.khali@linux-fr.org> (raw)
In-Reply-To: <45728865.5020308@xs4all.nl>

On Sun, 03 Dec 2006 11:41:38 +0100, Udo van den Heuvel wrote:
> Jean Delvare wrote:
> > On Sun, 03 Dec 2006 09:18:45 +0100, Udo van den Heuvel wrote:
> > > Also the temperature sensors are not shown.
> > 
> > Please provide the complete output of "sensors".
> 
> # sensors
> vt1211-isa-6000
> Adapter: ISA adapter
> VCore1:    +1.04 V  (min =  +1.13 V, max =  +1.27 V)   ALARM
> +5V:       +4.93 V  (min =  +4.74 V, max =  +5.26 V)
> +12V:     +12.05 V  (min = +11.38 V, max = +12.61 V)
> +3.3V:     +5.28 V  (min =  +3.14 V, max =  +3.47 V)   ALARM
> System:   4070 RPM  (min = 2580 RPM, div = 2)
> vid:      +1.850 V  (VRM Version 9.1)

No errors for temperatures, they are simply missing, so I guess there
are ignore statements for them in your configuration file. Can we
please see the vt1211 section of your configuration file? BTW, I hope
you started from the default configuration file shipped with lm_sensors
2.10.1 and not an older version, as it was significantly updated to
properly support the new Linux 2.6 version of the driver.

Please also provide the output of "sensors -c /dev/null".

> > What does "sensors -v" return?
> 
> sensors version 2.10.1 with libsensors version 2.10.1

So it's all OK.

> > Please provide a detailed listing (ls -l) of the files present in this
> > directory.
> 
> # pwd
> /sys/class/hwmon/hwmon0/device
> [root at recorder device]# ls -l
> total 0
> -r--r--r-- 1 root root 4096 Dec  3 11:38 alarms
> lrwxrwxrwx 1 root root    0 Dec  3 11:38 bus -> ../../../bus/platform
> -r--r--r-- 1 root root 4096 Dec  3 11:38 cpu0_vid
> lrwxrwxrwx 1 root root    0 Dec  3 11:38 driver -> ../../../bus/platform/drivers/vt1211
> -r--r--r-- 1 root root 4096 Dec  3 11:39 fan1_alarm
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 fan1_div
> -r--r--r-- 1 root root 4096 Dec  3 11:39 fan1_input
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 fan1_min
> -r--r--r-- 1 root root 4096 Dec  3 11:39 fan2_alarm
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 fan2_div
> -r--r--r-- 1 root root 4096 Dec  3 11:38 fan2_input
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 fan2_min
> lrwxrwxrwx 1 root root    0 Dec  3 11:39 hwmon:hwmon0 -> ../../../class/hwmon/hwmon0
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in0_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in0_input
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 in0_max
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 in0_min
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in1_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in1_input
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 in1_max
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 in1_min
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in2_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:38 in2_input
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in2_max
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in2_min
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in3_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:38 in3_input
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in3_max
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in3_min
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in4_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:38 in4_input
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in4_max
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in4_min
> -r--r--r-- 1 root root 4096 Dec  3 11:39 in5_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:38 in5_input
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in5_max
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 in5_min
> -r--r--r-- 1 root root 4096 Dec  3 11:39 modalias
> -r--r--r-- 1 root root 4096 Dec  3 11:38 name
> drwxr-xr-x 2 root root    0 Dec  3 09:02 power
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm1
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_channels_temp
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point1_pwm
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point1_temp
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point2_pwm
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point2_temp
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point3_pwm
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point3_temp
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point4_pwm
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_auto_point4_temp
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_enable
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm1_freq
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_channels_temp
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point1_pwm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point1_temp
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point2_pwm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point2_temp
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point3_pwm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point3_temp
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point4_pwm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_auto_point4_temp
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 pwm2_enable
> -r--r--r-- 1 root root 4096 Dec  3 11:39 pwm2_freq
> lrwxrwxrwx 1 root root    0 Dec  3 11:39 subsystem -> ../../../bus/platform
> -r--r--r-- 1 root root 4096 Dec  3 11:39 temp1_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 temp1_input
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 temp1_max
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 temp1_max_hyst
> -r--r--r-- 1 root root 4096 Dec  3 11:39 temp2_alarm
> -r--r--r-- 1 root root 4096 Dec  3 11:39 temp2_input
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 temp2_max
> -rw-r--r-- 1 root root 4096 Dec  3 11:39 temp2_max_hyst
> --w------- 1 root root 4096 Dec  3 11:39 uevent
> -rw-r--r-- 1 root root 4096 Dec  3 09:10 vrm

This looks all OK to me. As you can see the temperature files are
there.

-- 
Jean Delvare


  parent reply	other threads:[~2006-12-03 11:04 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 ` [lm-sensors] new vt1211 driver: Can't access procfs/sysfs file Jean Delvare
2006-12-03 10:41 ` Udo van den Heuvel
2006-12-03 11:04 ` Jean Delvare [this message]
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=20061203120427.c61e0cbe.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.