I’m attempting to read the CPU temperature sensors on a Tyan Thunder K8SE S2892. The system I’m working on has a front-panel LED board which includes a ‘fan fail’ and an ‘overheat’ LED. I need to make my code toggle these LEDs when the appropriate conditions occur.
I’ve run Tyan’s system monitor, so I know all the sensors are working.
As far as I can tell from poking around in WMI there isn’t any useful data being exported by any driver in the system, not even when Tyan’s system monitor is running.
I’ve had success in reading the Winbond chip (a W83627HF) via IO port calls. Sadly, on this motherboard, the CPU fans are on the Winbond chip, while the CPU temp sensors are attached to an ADT7463 (which is functionally similiar to a National LM85).
My problem is: How do I talk to the ADT chip? The Winbond chip is mapped via I/O ports, so I can use a simple driver that does inp/outp instructions and be fine and dandy. The ADT, however, is an SMBus device, and I don’t know what driver (if any on my system) that I should be trying to use to talk to it. I’ve found very little by googling on-line. I’ve found some old references (Win2K era) to a Microsoft SMBus driver and several more to other solutions that supplant the MS version. I can’t seem to find anything further than that, however.
I’ve e-mailed Tyan’s support address, but I’ve gotten nothing from them. I found an lm_sensors config on Tyan’s web site, so I know that the temp sensors on the winbond chip are not connected to the CPU temperatures, and I know which sensors on the ADT are connected to which CPU.
I’d appreciate anyone who could point me in the direction of the right documentation. I’m sure there’s a sensible way to do this, and I’m just missing the point.
Thanks.
Michael Kohne
xxxxx@kohne.org
“You must be smarter than the equipment you are trying to operate.”
Sounds to me like you’re an end user trying to do this… Is this the case? If so, please stop.
The OEM/IHV/ODM is responsible for the drivers that talk to their SMBUS and SIO devices. If they want folks to play with them, they provide a documented interface or a program that uses some undocumented and/or unsupported interfaces.
You haven’t found much via googling, because the register layouts of the various support chips are typically confidential.
If you’re the OEM/IHV/ODM, you work with colleagues at Tyan/ADT/Winbond and they’ll tell you what device you talk to, or what device you need to instantiate a driver over to access the devices in question… and they get you the docs you need under NDA. Many of the registers in question are typically used by the BIOS, in any case.
Peter
OSR
Sadly, I’m not exactly an end user, but we don’t buy enough to have a close relationship with the motherboard manufacturer. We sell equipment to the video production industry (I work for the Harris Broadcast Communications Divison). The product I’m working on is based on a windows server, in a chassis designed for another one of our company’s products. We’re using a Tyan motherboard instead of the one used by another division for reasons I don’t know. The other division got their vendor to give them the info they needed, I’m not presently so lucky (my queries to Tyan have so far been met with silence).
Sadly, the manufacturers don’t seem to be taking the presence of the WMI Win32_TemperatureProbe and Win32_Fan classes as a big enough hint that they should be providing this information through WMI where it might do some good.
Ahh well, I guess I’ll muddle through somehow.
Thanks.
Michael Kohne
xxxxx@kohne.org
“You must be smarter than the equipment you are trying to operate.”
-------Original Message-------
From: xxxxx@osr.com
Subject: RE:[ntdev] Motherboard temperature sensors (Tyan Thunder K8SE S2892 mobo, ADT7463 sensor)
Sent: Oct 02 '06 22:04
Sounds to me like you’re an end user trying to do this… Is this the case? If so, please stop.
The OEM/IHV/ODM is responsible for the drivers that talk to their SMBUS and SIO devices. If they want folks to play with them, they provide a documented interface or a program that uses some undocumented and/or unsupported interfaces.
You haven’t found much via googling, because the register layouts of the various support chips are typically confidential.
If you’re the OEM/IHV/ODM, you work with colleagues at Tyan/ADT/Winbond and they’ll tell you what device you talk to, or what device you need to instantiate a driver over to access the devices in question… and they get you the docs you need under NDA. Many of the registers in question are typically used by the BIOS, in any case.
Peter
OSR
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer