* [lm-sensors] HT1000 support (see lm_sensors ticket 2031,
2006-03-01 16:14 [lm-sensors] HT1000 support (see lm_sensors ticket 2031, Bruce Allen
@ 2006-03-01 19:19 ` Jean Delvare
2006-03-01 20:23 ` Martin Devera
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Jean Delvare @ 2006-03-01 19:19 UTC (permalink / raw)
To: lm-sensors
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
^ permalink raw reply [flat|nested] 10+ messages in thread* [lm-sensors] HT1000 support (see lm_sensors ticket 2031,
2006-03-01 16:14 [lm-sensors] HT1000 support (see lm_sensors ticket 2031, Bruce Allen
2006-03-01 19:19 ` Jean Delvare
@ 2006-03-01 20:23 ` Martin Devera
2006-03-01 20:53 ` Bruce Allen
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Martin Devera @ 2006-03-01 20:23 UTC (permalink / raw)
To: lm-sensors
> 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.
it works well for me for the same MB, only loaded patched piix4 and then
adm1026 module. Then even supermicro's superodoctor started to work on
the bow :) But I can imagine that it may become unavailable after BMC is
plugged in. I havn't bought BMC yet but I want to.
By the way, Jean, is it possible to have two masters on one i2c bus ?
How are priorities handled then ?
devik
^ permalink raw reply [flat|nested] 10+ messages in thread* [lm-sensors] HT1000 support (see lm_sensors ticket 2031,
2006-03-01 16:14 [lm-sensors] HT1000 support (see lm_sensors ticket 2031, Bruce Allen
2006-03-01 19:19 ` Jean Delvare
2006-03-01 20:23 ` Martin Devera
@ 2006-03-01 20:53 ` Bruce Allen
2006-03-01 20:57 ` Martin Devera
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Bruce Allen @ 2006-03-01 20:53 UTC (permalink / raw)
To: lm-sensors
>> 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.
>
> it works well for me for the same MB, only loaded patched piix4 and then
> adm1026 module. Then even supermicro's superodoctor started to work on the
> bow :) But I can imagine that it may become unavailable after BMC is plugged
> in. I havn't bought BMC yet but I want to.
I loaded the adm1026 module by hand:
[root at nemo-slave0017 ~]# lsmod | egrep '(i2c|adm)'
adm1026 46736 0
i2c_piix4 14480 0
adm1025 27156 0
hwmon_vid 7040 2 adm1026,adm1025
i2c_isa 10624 0
i2c_dev 17408 0
i2c_core 30720 6 adm1026,i2c_piix4,adm1025,eeprom,i2c_isa,i2c_dev
I have:
[root at nemo-slave0017 ~]# ls /sysfs
block bus class devices firmware kernel module power
[root at nemo-slave0017 ~]# ls /sys
block bus class devices firmware kernel module power
sensors-detect reports: "Sorry, no chips were detected."
[root at nemo-slave0017 ~]# sensors
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'!
^ permalink raw reply [flat|nested] 10+ messages in thread* [lm-sensors] HT1000 support (see lm_sensors ticket 2031,
2006-03-01 16:14 [lm-sensors] HT1000 support (see lm_sensors ticket 2031, Bruce Allen
` (2 preceding siblings ...)
2006-03-01 20:53 ` Bruce Allen
@ 2006-03-01 20:57 ` Martin Devera
2006-03-01 21:03 ` Bruce Allen
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Martin Devera @ 2006-03-01 20:57 UTC (permalink / raw)
To: lm-sensors
> I loaded the adm1026 module by hand:
>
> [root at nemo-slave0017 ~]# lsmod | egrep '(i2c|adm)'
> adm1026 46736 0
> i2c_piix4 14480 0
> adm1025 27156 0
> hwmon_vid 7040 2 adm1026,adm1025
> i2c_isa 10624 0
> i2c_dev 17408 0
> i2c_core 30720 6
> adm1026,i2c_piix4,adm1025,eeprom,i2c_isa,i2c_dev
>
> I have:
> [root at nemo-slave0017 ~]# ls /sysfs
> block bus class devices firmware kernel module power
> [root at nemo-slave0017 ~]# ls /sys
> block bus class devices firmware kernel module power
>
send
dmesg|tail -n 30
and try
ls /sys/class
(there is typicaly hwmon class, if yes, list it too)
^ permalink raw reply [flat|nested] 10+ messages in thread* [lm-sensors] HT1000 support (see lm_sensors ticket 2031,
2006-03-01 16:14 [lm-sensors] HT1000 support (see lm_sensors ticket 2031, Bruce Allen
` (3 preceding siblings ...)
2006-03-01 20:57 ` Martin Devera
@ 2006-03-01 21:03 ` Bruce Allen
2006-03-01 22:07 ` Bruce Allen
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Bruce Allen @ 2006-03-01 21:03 UTC (permalink / raw)
To: lm-sensors
>> -- 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.
OK. I tried loading the adm1026 module that Martin uses -- no go.
>
>> (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.
OK. In any case I am loading the i2c-piix4 modules from the (modified)
2.6.15 tree.
> 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?
I just did:
rmmod i2c_piix4
modprobe i2c_piix4
lsmod shows the module loaded, but there was NO output in
/var/log/messages.
> 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.
It's attached to this email.
> 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.)
[root at nemo-slave0017 lm_sensors-2.10.0]# i2cdetect 0
Error: Could not open file `/dev/i2c-0': No such device
[root at nemo-slave0017 lm_sensors-2.10.0]# i2cdetect 1
Error: Could not open file `/dev/i2c-1': No such device
[root at nemo-slave0017 lm_sensors-2.10.0]# ls /dev/i2c*
/dev/i2c0 /dev/i2c1 /dev/i2c2 /dev/i2c3 /dev/i2c4 /dev/i2c5
/dev/i2c6 /dev/i2c7
/dev/i2c-0 /dev/i2c-1 /dev/i2c-2 /dev/i2c-3 /dev/i2c-4 /dev/i2c-5
/dev/i2c-6 /dev/i2c-7
>> 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.
I actually have access to the BMC directly, via ipmitool. And perhaps
this is the problem. I am loading these modules:
modprobe ipmi_msghandler
modprobe ipmi_si type=kcs ports=0xca8 regspacings=4
modprobe ipmi_devintf
Perhaps they interfere with the i2c functionality needed by lm_sensors.
Thanks very much for your help with this!
Cheers,
Bruce
-------------- next part --------------
# sensors-detect revision 1.413 (2006/01/19 20:28:00)
This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.
It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.
We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): Probing for PCI bus adapters...
Use driver `i2c-piix4' for device 00:02.0: ServerWorks CSB6 South Bridge
Probe succesfully concluded.
We will now try to load each adapter module in turn.
Module `i2c-piix4' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.
To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is already loaded.
We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).
Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan the ISA bus? (YES/no): Probing for `National Semiconductor LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8712F'
Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!
Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.
Do you want to scan for Super I/O sensors? (YES/no): Probing for `ITE 8702F Super IO Sensors'
Failed! (0xf219)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0xf219)
Probing for `ITE 8712F Super IO Sensors'
Failed! (0xf219)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (0xf2)
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
Failed! (0xf2)
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
Failed! (0xf2)
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
Failed! (0xf2)
Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
Failed! (0xf2)
Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
Failed! (0xf2)
Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
Failed! (0xf2)
Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
Failed! (0xf2)
Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
Failed! (0xf2)
Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
Failed! (0xf2)
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
Failed! (0xf2)
Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
Failed! (0xf2)
Probing for `Nat. Semi. PC87591 Super IO'
Failed! (0xf2)
Probing for `Nat. Semi. PC87371 Super IO'
Failed! (0xf2)
Probing for `Nat. Semi. PC97371 Super IO'
Failed! (0xf2)
Probing for `Nat. Semi. PC8739x Super IO'
Failed! (0xf2)
Probing for `Nat. Semi. PC8741x Super IO'
Failed! (0xf2)
Probing for `Nat. Semi. PCPC87427 Super IO'
Success... (no hardware monitoring capabilities)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (0xf2)
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
Failed! (0xf2)
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed! (0xf2)
Probing for `SMSC 47M15x/192/997 Super IO Fan Sensors'
Failed! (0xf2)
Probing for `SMSC 47S42x Super IO Fan Sensors'
Failed! (0xf2)
Probing for `SMSC 47S45x Super IO Fan Sensors'
Failed! (0xf2)
Probing for `SMSC 47M172 Super IO'
Failed! (0xf2)
Probing for `SMSC LPC47B397-NC Super IO'
Failed! (0xf2)
Probing for `SMSC SCH5307-NS Super IO'
Failed! (0xf2)
Probing for `VT1211 Super IO Sensors'
Failed! (0xf2)
Probing for `Winbond W83627HF Super IO Sensors'
Failed! (0xf2)
Probing for `Winbond W83627THF Super IO Sensors'
Failed! (0xf2)
Probing for `Winbond W83637HF Super IO Sensors'
Failed! (0xf2)
Probing for `Winbond W83687THF Super IO Sensors'
Failed! (0xf2)
Probing for `Winbond W83697HF Super IO Sensors'
Failed! (0xf2)
Probing for `Winbond W83697SF/UF Super IO PWM'
Failed! (0xf2)
Probing for `Winbond W83L517D Super IO'
Failed! (0xf2)
Probing for `Fintek F71805F/FG Super IO Sensors'
Failed! (0xf219)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
Failed! (0xf219)
Do you want to scan for secondary Super I/O sensors? (YES/no): Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Probing for `Winbond W83627EHF/EHG Super IO Sensors'
Failed! (skipping family)
Sorry, no chips were detected.
Either your sensors are not supported, or they are
connected to an I2C bus adapter that we do not support.
See doc/FAQ, doc/lm_sensors-FAQ.html, or
http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/lm_sensors-FAQ.html
(FAQ #4.24.3) for further information.
If you find out what chips are on your board, see
http://secure.netroedge.com/~lm78/newdrivers.html for driver status.
^ permalink raw reply [flat|nested] 10+ messages in thread* [lm-sensors] HT1000 support (see lm_sensors ticket 2031,
2006-03-01 16:14 [lm-sensors] HT1000 support (see lm_sensors ticket 2031, Bruce Allen
` (4 preceding siblings ...)
2006-03-01 21:03 ` Bruce Allen
@ 2006-03-01 22:07 ` Bruce Allen
2006-03-01 22:10 ` Martin Devera
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: Bruce Allen @ 2006-03-01 22:07 UTC (permalink / raw)
To: lm-sensors
>> I loaded the adm1026 module by hand:
>>
>> [root at nemo-slave0017 ~]# lsmod | egrep '(i2c|adm)'
>> adm1026 46736 0
>> i2c_piix4 14480 0
>> adm1025 27156 0
>> hwmon_vid 7040 2 adm1026,adm1025
>> i2c_isa 10624 0
>> i2c_dev 17408 0
>> i2c_core 30720 6
>> adm1026,i2c_piix4,adm1025,eeprom,i2c_isa,i2c_dev
>>
>> I have:
>> [root at nemo-slave0017 ~]# ls /sysfs
>> block bus class devices firmware kernel module power
>> [root at nemo-slave0017 ~]# ls /sys
>> block bus class devices firmware kernel module power
>>
>
> send
> dmesg|tail -n 30
[root at nemo-slave0017 ~]# modprobe i2c_piix4
[root at nemo-slave0017 ~]# modprobe adm1026
[root at nemo-slave0017 ~]# dmesg | tail -n 30
md: ... autorun DONE.
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel at redhat.com
cdrom: open failed.
cdrom: open failed.
EXT3 FS on sda3, internal journal
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 5116692k swap on /dev/sda2. Priority:-1 extents:1 across:5116692k
tg3: eth0: Link is up at 1000 Mbps, full duplex.
tg3: eth0: Flow control is off for TX and off for RX.
i2c /dev entries driver
lp: driver loaded but no devices found
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
Installing knfsd (copyright (C) 1996 okir at monad.swb.de).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: recovery directory /var/lib/nfs/v4recovery doesn't exist
NFSD: starting 90-second grace period
ipmi message handler version 38.0
IPMI System Interface driver.
ipmi_si: Trying "kcs" at I/O port 0xca8
IPMI kcs interface initialized
ipmi device interface
eth0: no IPv6 routers present
> and try
> ls /sys/class
> (there is typicaly hwmon class, if yes, list it too)
[root at nemo-slave0017 ~]# ls /sys/class/
cpuid firmware graphics hwmon i2c-adapter i2c-dev input ipmi mem
misc msr net pci_bus printer scsi_device scsi_host tty usb
usb_device usb_host vc
[root at nemo-slave0017 ~]# ls /sys/class/hwmon/
[root at nemo-slave0017 ~]# ls /sys/class/i2c-adapter/
i2c-9191
[root at nemo-slave0017 ~]# ls /sys/class/i2c-dev/
[root at nemo-slave0017 ~]#
^ permalink raw reply [flat|nested] 10+ messages in thread* [lm-sensors] HT1000 support (see lm_sensors ticket 2031,
2006-03-01 16:14 [lm-sensors] HT1000 support (see lm_sensors ticket 2031, Bruce Allen
` (5 preceding siblings ...)
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
8 siblings, 0 replies; 10+ messages in thread
From: Martin Devera @ 2006-03-01 22:10 UTC (permalink / raw)
To: lm-sensors
> IPMI kcs interface initialized
> ipmi device interface
> eth0: no IPv6 routers present
interestingly there is no info from piix4 module...
>> and try
>> ls /sys/class
>> (there is typicaly hwmon class, if yes, list it too)
>
> [root at nemo-slave0017 ~]# ls /sys/class/
> cpuid firmware graphics hwmon i2c-adapter i2c-dev input ipmi mem
> misc msr net pci_bus printer scsi_device scsi_host tty usb
> usb_device usb_host vc
> [root at nemo-slave0017 ~]# ls /sys/class/hwmon/
> [root at nemo-slave0017 ~]# ls /sys/class/i2c-adapter/
> i2c-9191
> [root at nemo-slave0017 ~]# ls /sys/class/i2c-dev/
> [root at nemo-slave0017 ~]#
>
Hmm, it really seems as if BMC "disconnected" i2c bus from HT1000 bus.
It would be interesting to try with BMC withdrawn. I'll test once I get
the BMC.
devik
^ permalink raw reply [flat|nested] 10+ messages in thread* [lm-sensors] HT1000 support (see lm_sensors ticket 2031,
2006-03-01 16:14 [lm-sensors] HT1000 support (see lm_sensors ticket 2031, Bruce Allen
` (6 preceding siblings ...)
2006-03-01 22:10 ` Martin Devera
@ 2006-03-02 2:12 ` Bruce Allen
2006-03-02 4:45 ` Mark M. Hoffman
8 siblings, 0 replies; 10+ messages in thread
From: Bruce Allen @ 2006-03-02 2:12 UTC (permalink / raw)
To: lm-sensors
>> IPMI kcs interface initialized
>> ipmi device interface
>> eth0: no IPv6 routers present
>
> interestingly there is no info from piix4 module...
>
>>> and try
>>> ls /sys/class
>>> (there is typicaly hwmon class, if yes, list it too)
>>
>> [root at nemo-slave0017 ~]# ls /sys/class/
>> cpuid firmware graphics hwmon i2c-adapter i2c-dev input ipmi mem
>> misc msr net pci_bus printer scsi_device scsi_host tty usb
>> usb_device usb_host vc
>> [root at nemo-slave0017 ~]# ls /sys/class/hwmon/
>> [root at nemo-slave0017 ~]# ls /sys/class/i2c-adapter/
>> i2c-9191
>> [root at nemo-slave0017 ~]# ls /sys/class/i2c-dev/
>> [root at nemo-slave0017 ~]#
>>
>
> Hmm, it really seems as if BMC "disconnected" i2c bus from HT1000 bus. It
> would be interesting to try with BMC withdrawn. I'll test once I get the BMC.
I'll give this a try tomorrow also. It's easy to yank out the BMC.
Cheers,
Bruce
^ permalink raw reply [flat|nested] 10+ messages in thread* [lm-sensors] HT1000 support (see lm_sensors ticket 2031,
2006-03-01 16:14 [lm-sensors] HT1000 support (see lm_sensors ticket 2031, Bruce Allen
` (7 preceding siblings ...)
2006-03-02 2:12 ` Bruce Allen
@ 2006-03-02 4:45 ` Mark M. Hoffman
8 siblings, 0 replies; 10+ messages in thread
From: Mark M. Hoffman @ 2006-03-02 4:45 UTC (permalink / raw)
To: lm-sensors
Hi Martin:
* Martin Devera <devik at cdi.cz> [2006-03-01 21:23:54 +0100]:
> > 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.
>
> it works well for me for the same MB, only loaded patched piix4 and then
> adm1026 module. Then even supermicro's superodoctor started to work on
> the bow :) But I can imagine that it may become unavailable after BMC is
> plugged in. I havn't bought BMC yet but I want to.
>
> By the way, Jean, is it possible to have two masters on one i2c bus ?
> How are priorities handled then ?
The i2c bus is multi-master capable. There is no defined priority scheme.
However, there is an arbitration protocol that determines the outcome in
case two or more masters begin a transfer at the same time. In a nutshell:
the transfer that is *not* corrupted wins. It's simple and (IMHO) elegant.
I refer you to the I2C bus specification for more details, esp section 8.2:
http://www.semiconductors.philips.com/acrobat/literature/9398/39340011.pdf
If a Linux host I2C master loses arbitration, the transfer fails and an
error status is returned to the slave device driver. Many (but not all)
hwmon drivers will retry the transfer several times before giving up.
Regards,
--
Mark M. Hoffman
mhoffman at lightlink.com
^ permalink raw reply [flat|nested] 10+ messages in thread