Bug#372955: libsensors3: Can't access procfs/sysfs file

2006-06-14 Thread Niccolo Rigacci
On Tue, Jun 13, 2006 at 07:46:12PM +0200, Aurelien Jarno wrote:

 When I run sensors I get the error:
 
 Can't access procfs/sysfs file
 Unable to find i2c bus information;
 For 2.6 kernels, make sure you have mounted sysfs and libsensors
 was compiled with sysfs support!
 For older kernels, make sure you have done 'modprobe i2c-proc'!
 
 Could you please send me the output of 'lsmod', and also from 'strace 
 sensors'. With that I will be able to better understand the problem.

In the attachment there is the output of lsmod, lspci and strace 
sensors.

Many thanks for your interest!

-- 
Niccolo Rigacci
Firenze - Italy

Iraq, missione di pace: 38355 morti - www.iraqbodycount.net


report.txt.gz
Description: Binary data


Bug#372955: libsensors3: Can't access procfs/sysfs file

2006-06-13 Thread Aurelien Jarno

Niccolo wrote:

Package: libsensors3
Version: 1:2.10.0-7
Severity: normal


When I run sensors I get the error:

Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!


From strace I see that sensors tries to open /sys/class/hwmon/ which

exists, but it is empty on my system.

I have instead /sys/bus/i2c/devices and /sys/bus/i2c/drivers,
which are populated because I inserted the modules suggested
by sensors-detect:

# Generated by sensors-detect on Sat Jun 10 16:20:04 2006
# I2C adapter drivers
i2c-i801
i2c-isa
# I2C chip drivers
# no driver for SMSC LPC47M15x, LPC47M192 or LPC47M997 yet
eeprom
smsc47m1

I don't know who is responsible for creating entries under /sys,
and I don't know if libsensors is searching in the right or wrong
place. Sorry.



Could you please send me the output of 'lsmod', and also from 'strace 
sensors'. With that I will be able to better understand the problem.


Thanks,
Aurelien

--
  .''`.  Aurelien Jarno | GPG: 1024D/F1BCDB73
 : :' :  Debian GNU/Linux developer | Electrical Engineer
 `. `'   [EMAIL PROTECTED] | [EMAIL PROTECTED]
   `-people.debian.org/~aurel32 | www.aurel32.net


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#372955: libsensors3: Can't access procfs/sysfs file

2006-06-12 Thread Niccolo
Package: libsensors3
Version: 1:2.10.0-7
Severity: normal


When I run sensors I get the error:

Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and libsensors
was compiled with sysfs support!
For older kernels, make sure you have done 'modprobe i2c-proc'!

From strace I see that sensors tries to open /sys/class/hwmon/ which
exists, but it is empty on my system.

I have instead /sys/bus/i2c/devices and /sys/bus/i2c/drivers,
which are populated because I inserted the modules suggested
by sensors-detect:

# Generated by sensors-detect on Sat Jun 10 16:20:04 2006
# I2C adapter drivers
i2c-i801
i2c-isa
# I2C chip drivers
# no driver for SMSC LPC47M15x, LPC47M192 or LPC47M997 yet
eeprom
smsc47m1

I don't know who is responsible for creating entries under /sys,
and I don't know if libsensors is searching in the right or wrong
place. Sorry.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages libsensors3 depends on:
ii  debconf [debconf-2.0] 1.5.1  Debian configuration management sy
ii  libc6 2.3.6-13   GNU C Library: Shared libraries
ii  libsysfs2 2.0.0-6interface library to sysfs
ii  makedev   2.3.1-81   creates device files in /dev
ii  udev  0.093-1/dev/ and hotplug management daemo

libsensors3 recommends no packages.

-- debconf information:
  libsensors3/nosensors_2.4:
  libsensors3/old2.6kernel:
  libsensors3/nosensors_2.6:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]