Eddi De Pieri
2011-08-16 07:26:06 UTC
Hi Jean...
The bios show fan rpm and temperature. Since my own proliant
microserver lacks of ipmi card, I doubt the bios give me the results
using ipmi call.
The HP Proliant Microserver chipset (SB820M) have a multiplexed smbus like your.
http://support.amd.com/it/Embedded_TechDocs/47283_sb820m_ds_pub_2.00.pdf
Here is technical document from amd...
at p52/53 they say:
(1) The SDA1 and SCL1 SMBus interface is dedicated for ASF devices
only. It should not be used to
connect to any other devices.
(2) There are only two SMBus controllers. The SCL1/SDA1 pair is
controlled by SMBus controller 1.
SCL0/SDA0, SCL2/SDA2, SCL3/SDA3 and SCL4/SDA4 are multiplexed pins
that are all controlled by
SMBus controller 0, and only 1 pair of those pins can be active at any time.
I can't understand how to enable 2, 3 and 4 muxed bus..
If you consolidate a solution for i2c-i801.c I hope we can be
replicated for i2c-piix4.c too..
Hi Karsten,
On Fri, 22 Oct 2010 16:04:10 +0200, karsten at maxi-dsl.de
*>* > sensors-detect. So if sensors-detect doesn't see your chip, I am not
*>* > surprised that the driver didn't either.
*>*
*>* > The full output of sensors-detect is needed to diagnose your problem
*>* > further. It could be that your SMBus controller isn't supported, or
*>* > maybe you are supposed to access the chip through IPMI.
*>*
*>* IPMI is probably the key..
*>*
*>* From the sensors-detect output:
*>* "Warning: the required module ipmisensors is not currently installed
*>* on your system. If it is built into the kernel then it's OK.
*>* Otherwise, check http://www.lm-sensors.org/wiki/Devices for
*>* driver availability" (full ouput attached)
*>*
*>* I did see the output before, but didn't really understand the
*>* implications (IPMI seems to be an alternative way of accessing the
*>* monitoring chips?)
*
Yes. The strength of IPMI access is that it can be used remotely too,
for example from a BMC plugged into your system.
*>* 2.6 in progress by Yani Ioannou")
*
That project is essentially dead. At the time being, the best way to
retrieve IPMI-based sensor values is using "ipmitool sensor". The
drawback is that this isn't integrated with libsensors, so the usually
monitoring applications won't work.
If you have a BMC or are otherwise already using IPMI on your machine,
just use ipmitool and you're done.
If not, then it might be worth trying ipmitool once, and then try
sensors-detect again. There is a small chance that, once ipmitool
managed to access the monitoring device, sensors-detect will see it. My
own mainboard which has a W83795ADG chip has a multiplexed SMBus, and I
can only see the W83795ADG in sensors-detect when the multiplexer is
set properly. Otherwise I would see the memory modules, which _do_
appear in your sensors-detect output. So maybe your board has a
multiplexed SMBus too.
If the trick doesn't work, you may want to try the new jc42 driver
which can monitor the temperature of some DDR3 memory modules. I
suspect your memory modules have such sensors. A more recent version of
sensors-detect would confirm that:
http://dl.lm-sensors.org/lm-sensors/files/sensors-detect
I also see that sensors-detect suggested to use the k10temp driver,
which your kernel doesn't have. You can try the standalone flavor of
the drivers which I maintain at:
http://khali.linux-fr.org/devel/misc/k10temp/
The accuracy of the CPU internal sensors is limited, but that's still
better than nothing.
The bios show fan rpm and temperature. Since my own proliant
microserver lacks of ipmi card, I doubt the bios give me the results
using ipmi call.
The HP Proliant Microserver chipset (SB820M) have a multiplexed smbus like your.
http://support.amd.com/it/Embedded_TechDocs/47283_sb820m_ds_pub_2.00.pdf
Here is technical document from amd...
at p52/53 they say:
(1) The SDA1 and SCL1 SMBus interface is dedicated for ASF devices
only. It should not be used to
connect to any other devices.
(2) There are only two SMBus controllers. The SCL1/SDA1 pair is
controlled by SMBus controller 1.
SCL0/SDA0, SCL2/SDA2, SCL3/SDA3 and SCL4/SDA4 are multiplexed pins
that are all controlled by
SMBus controller 0, and only 1 pair of those pins can be active at any time.
I can't understand how to enable 2, 3 and 4 muxed bus..
If you consolidate a solution for i2c-i801.c I hope we can be
replicated for i2c-piix4.c too..
Hi Karsten,
On Fri, 22 Oct 2010 16:04:10 +0200, karsten at maxi-dsl.de
* hi Jean,
*>* > The w83795 driver uses the same detection mechanism used in*>* > sensors-detect. So if sensors-detect doesn't see your chip, I am not
*>* > surprised that the driver didn't either.
*>*
*>* > The full output of sensors-detect is needed to diagnose your problem
*>* > further. It could be that your SMBus controller isn't supported, or
*>* > maybe you are supposed to access the chip through IPMI.
*>*
*>* IPMI is probably the key..
*>*
*>* From the sensors-detect output:
*>* "Warning: the required module ipmisensors is not currently installed
*>* on your system. If it is built into the kernel then it's OK.
*>* Otherwise, check http://www.lm-sensors.org/wiki/Devices for
*>* driver availability" (full ouput attached)
*>*
*>* I did see the output before, but didn't really understand the
*>* implications (IPMI seems to be an alternative way of accessing the
*>* monitoring chips?)
*
Yes. The strength of IPMI access is that it can be used remotely too,
for example from a BMC plugged into your system.
* The suggested ipmisensors driver however does not seem to be available, right?
*>* (http://lm-sensors.org/wiki/Devices says "(2004-12-12) Port to Linux*>* 2.6 in progress by Yani Ioannou")
*
That project is essentially dead. At the time being, the best way to
retrieve IPMI-based sensor values is using "ipmitool sensor". The
drawback is that this isn't integrated with libsensors, so the usually
monitoring applications won't work.
If you have a BMC or are otherwise already using IPMI on your machine,
just use ipmitool and you're done.
If not, then it might be worth trying ipmitool once, and then try
sensors-detect again. There is a small chance that, once ipmitool
managed to access the monitoring device, sensors-detect will see it. My
own mainboard which has a W83795ADG chip has a multiplexed SMBus, and I
can only see the W83795ADG in sensors-detect when the multiplexer is
set properly. Otherwise I would see the memory modules, which _do_
appear in your sensors-detect output. So maybe your board has a
multiplexed SMBus too.
If the trick doesn't work, you may want to try the new jc42 driver
which can monitor the temperature of some DDR3 memory modules. I
suspect your memory modules have such sensors. A more recent version of
sensors-detect would confirm that:
http://dl.lm-sensors.org/lm-sensors/files/sensors-detect
I also see that sensors-detect suggested to use the k10temp driver,
which your kernel doesn't have. You can try the standalone flavor of
the drivers which I maintain at:
http://khali.linux-fr.org/devel/misc/k10temp/
The accuracy of the CPU internal sensors is limited, but that's still
better than nothing.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20110816/d33e0d88/attachment.html>
Jean Delvare
http://khali.linux-fr.org/wishlist.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20110816/d33e0d88/attachment.html>