lm_sensors doesn't detect voltage measurements on HP Proliant DL320 G2 machine

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jean,

Thank you very much for your help.

The attached file contains the results by using i2cdump. Hope this help.


I have contacted HP. They recommended me to use their "System Inside
Manager" utility which can show all the measurements. That sounds like
they must have a sensor or sensors on the board. But they might not
provide the interface for the user to integrate. Is there anything we
can do about this that we can get the measurements out?

Kindly regards,

Jim

-----Original Message-----
From: Jean Delvare [mailto:khali at linux-fr.org] 
Sent: 14 September 2004 17:30
To: Jim Chen
Cc: sensors at Stimpy.netroedge.com
Subject: Re: lm_sensors doesn't detect voltage measurements on HP
Proliant DL320 G2 machine

> Please see attached file for details done by sensors-detectprogram. I
am
> using Linux Enterprise 3 (Red Hat 2.4.21).

Actually Red Hat Enterprise 3 (Linux 2.4.21), I presume.

> I have downloaded the lm_sensors2.8.7 and installed on my mahcine and
it
> works fine with the detecting the eepromand AMBus adaptor but couldn't
list
> the voltages, fan speeds and temperatures.It sounds like it couldn't
detect
> the sensors chip. Could you help to have lookwhat exactly happened and
any
> possible solution for this? I have also raised aticket in the forum
with No.
> of 1774.

The output from sensors-detect reveals that you have no known ISA chip,
one
Super-I/O chipset but known not to have integrated sensors, and a few
I2C/SMBus chips (including your memory module EEPROM at 0x53 and
presumably a
clock chip at 0x69). There are two more (unknown) I2C chips at 0x33 and
0x60.
The former is probably the same EEPROM as 0x53 but maybe not.

Both addresses are not typical addresses for hardware monitoring
devices, but
who knows... Please provide the output of "i2cdump 0 0x33" and "i2cdump
0
0x60" (assuming that this is I2C bus 0; if not, pick the correct number
from
/proc/bus/i2c).

Note that i2cdump is potentially dangerous to use especially on unknown
chips,
so run it at your own risk and only if rebooting the machine afterwards
is an
option.

-- 
Jean Delvare 
http://khali.linux-fr.org/

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: i2cdump-result.txt
Url: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20040915/9c8c0bb9/attachment.txt 


[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux