All of lore.kernel.org
 help / color / mirror / Atom feed
From: crotalus@superig.com.br (Paulo Roma Cavalcanti)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] asb100 not working in kernel 2.6.16
Date: Fri, 21 Apr 2006 23:06:17 +0000	[thread overview]
Message-ID: <44496569.6030100@superig.com.br> (raw)


I have been using lm_sensors for a long time
on an Asus P4S333 motherboard.
However, they are no longer working with the 2.6.16
kernel series. During the boot there is a message
saying it cannot find any i2c information.

Interesting is that the modules are loaded:

eeprom                  7249  0
asb100                 20437  0
hwmon_vid               2881  1 asb100
hwmon                   3269  1 asb100
i2c_sis96x              5829  0
i2c_core               21697  3 eeprom,asb100,i2c_sis96x
rfcomm                 36821  0
l2cap                  24641  5 rfcomm

But if I try to read the sensors, I get:

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'!

My system is a Fedora 4 with latest lm_sensors from ATrpms.

Linux version 2.6.16-1.2096_FC4 (bhcompile at hs20-bc1-4.build.redhat.com)

I am loading the modules below in /etc/sysconfig/lm_sensors:

MODULE_0=i2c-sis96x
MODULE_1=asb100
MODULE_2îprom

They work very well with kernel 2.6.15 and below, only.

I appreciate any suggestion.

Thank you.

/Paulo Roma


             reply	other threads:[~2006-04-21 23:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21 23:06 Paulo Roma Cavalcanti [this message]
2006-04-22 18:35 ` [lm-sensors] asb100 not working in kernel 2.6.16 Mark M. Hoffman
2006-04-23 22:16 ` Mark M. Hoffman
2006-04-23 22:59 ` Paulo Roma Cavalcanti
2006-04-24  6:26 ` Jean Delvare

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=44496569.6030100@superig.com.br \
    --to=crotalus@superig.com.br \
    --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.