All of lore.kernel.org
 help / color / mirror / Atom feed
From: jim.cromie@gmail.com (Jim Cromie)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] VT1211-ISA-6000 &  procfs/sysfs
Date: Sat, 09 Sep 2006 23:38:49 +0000	[thread overview]
Message-ID: <45035089.4040809@gmail.com> (raw)
In-Reply-To: <45034A2F.2020701@programmers.ch>

Marc Kalberer wrote:
> Hi,
> I dont know if my problem is related to lm-sensors or VT1211 I2C patch 
> but I have the following prob when executing sensors -s :
>
> vt1211-isa-6000: Can't access procfs/sysfs file for writing;
>
> Conclusion : pwmconfig  give me a : No sensors found!
>
> Sys is populated,  kernel is a pure vanilla 2.6.18-rc5 patched with the 
> one given at 
> http://khali.linux-fr.org/devel/i2c/linux-2.6/hwmon-vt1211-new-driver.patch.  
> With the latest lm_sensors-2.10.0 and gcc4.0.3-1
>
> I both compile the full set of the I2C drivers in modules or built-in.  
> It gave me the same result.
>
> Hardware is EPIA M10000.
>
> It is supposed to work, but it doesn't ? Any Idea of the prob ? 
>
> I joined :
> 1) strace sensors -s
> 2) lspci
> 3) dmesg
>
> ++
>
> Marc
>
> sensor:
> ------------------------------------------
> execve("/usr/local/bin/sensors", ["sensors", "-s"], [/* 18 vars */]) = 0
> uname({sys="Linux", node="mediabox", ...}) = 0
>   

this suggests that you didnt run as root.

> write(2, "vt1211-isa-6000: Can\'t access pr"..., 61vt1211-isa-6000: 
> Can't access procfs/sysfs file for writing;
> ) = 61
> write(2, "Run as root?\n", 13Run as root?
> )          = 13
> exit_group(1)                           = ?
>
>   



  reply	other threads:[~2006-09-09 23:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-09 23:11 [lm-sensors] VT1211-ISA-6000 & procfs/sysfs Marc Kalberer
2006-09-09 23:38 ` Jim Cromie [this message]
2006-09-10  9:30 ` Marc Kalberer
2006-09-10 16:34 ` Jean Delvare
2006-09-10 19:47 ` Marc Kalberer
2006-09-10 21:27 ` Marc Kalberer
  -- strict thread matches above, loose matches on Subject: below --
2006-09-10 23:40 Juerg Haefliger

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=45035089.4040809@gmail.com \
    --to=jim.cromie@gmail.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.