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] HT1000 support (see lm_sensors ticket 2031,
Date: Wed, 01 Mar 2006 19:19:18 +0000	[thread overview]
Message-ID: <20060301201918.ab898494.khali@linux-fr.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0603010955280.24174@trinity.phys.uwm.edu>

Hi Bruce,

> I'd like to get lm_sensors support for a system with an HT1000 chip.
> References are on http://www2.lm-sensors.nu/~lm78/newdrivers.html
> 
> -- I've rebuilt a stock 2.6.15.4 kernel using the HT1000 patch referenced
>     on the newdrivers page:
>     http://khali.linux-fr.org/devel/i2c/linux-2.6/i2c-piix4-add-ht1000-support.patch
> 
> -- I then built and installed sysfsutils-2.0.0
> 
> -- I then built and installed lm_sensors-2.10.0.
> 
> -- I loaded the i2c_piix4 module using modprobe.
> 
> -- I mounted sysfs on /sysfs
> 
> However sensors-detect does not find ANYTHING.  Not even eeprom!  Am I 
> doing something stupid?

The HT-1000 is (from our simplified point of view) an SMBus master. It
may give you access to I2C/SMBus hardware monitoring chips, but isn't
itself a hardware monitoring chip.

> (Note: for kicks I also went into the lm_sensors source and 'hacked' the 
> SERVERWORKS CSB6 0x0203 PCI-id to be 0x0205 both the sensors-detect script 
> and in the i2c_piix4 code contained there. It didn't help.)

The i2c-piix4 driver found in the lm_sensors is a Linux 2.4 driver, so
it is of no use to you.

Adding the ID to sensors-detect will let it autoload the i2c-piix4
driver, but given that you had manually loaded it beforehand anyway, it
did not change anything for you.

Please check your logs after loading the i2c-piix4 driver. Did it
complain of anything?

Second, please provide the full output of sensors-detect. There are
many possible reasons why no chips were found on your HT-1000, and this
output should help us sort through them. You may also provide the
output of "i2cdetect 0" (assuming that the HT-1000 is the only i2c
adapter on the system; if not try "i2cdetect -l" first.)

> One other possibility is that because I have a BMC card plugged in to the 
> motherboard (SuperMicro H8SSL-i) the BMC card is not allowing access to 
> the devices from lm_sensors.

BMC are handled by a different set of drivers which were not yet merged
into Linux 2.6. See http://bmcsensors-26.sourceforge.net/ if you think
this is what you need. I can not help much on this myself.

-- 
Jean Delvare


  reply	other threads:[~2006-03-01 19:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-01 16:14 [lm-sensors] HT1000 support (see lm_sensors ticket 2031, Bruce Allen
2006-03-01 19:19 ` Jean Delvare [this message]
2006-03-01 20:23 ` Martin Devera
2006-03-01 20:53 ` Bruce Allen
2006-03-01 20:57 ` Martin Devera
2006-03-01 21:03 ` Bruce Allen
2006-03-01 22:07 ` Bruce Allen
2006-03-01 22:10 ` Martin Devera
2006-03-02  2:12 ` Bruce Allen
2006-03-02  4:45 ` Mark M. Hoffman

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=20060301201918.ab898494.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.