On Tue, 22 Jan 2008, Jordan Crouse wrote: > Revamped driver is attached. I got it compiled, after changing I2C_DRIVERID_ADT74XX to I2C_DRIVERID_ADT7475 in i2c-id.h . Here are the results: --- ADT7475-i2c-5-2e Adapter: SMBus nForce2 adapter at 1c40 vccp: +0.00 V (min = +0.00 V, max = +2.99 V) ALARM vcc: +3.24 V (min = +0.00 V, max = +4.28 V) fan1: 0 RPM (min = 0 RPM) fan2: 0 RPM (min = 0 RPM) fan3: 0 RPM (min = 0 RPM) fan4: 0 RPM (min = 0 RPM) remote1: FAULT (low = -63.0?C, high = +191.0?C) ALARM local: +40.2?C (low = -63.0?C, high = +191.0?C) remote2: FAULT (low = -63.0?C, high = +191.0?C) ALARM --- For reference, here is the output from Hans de Goede's work-in-progress driver: --- adt7475-i2c-5-2e Adapter: SMBus nForce2 adapter at 1c40 in0: +0.03 V (min = +0.00 V, max = +7.47 V) in1: +32.42 V (min = +0.00 V, max = +10.71 V) fan1: 0 RPM (min = 0 RPM) fan2: 0 RPM (min = 0 RPM) fan3: 0 RPM (min = 0 RPM) fan4: 0 RPM (min = 0 RPM) temp1: -64.0?C (low = +1.0?C, high = +127.0?C) temp2: +39.5?C (low = +1.0?C, high = +127.0?C) temp3: -64.0?C (low = +1.0?C, high = +127.0?C) --- At first glance, Jordan's driver has probably more accurate names, a more sensible value for vcc, and recognizes that remote[12] probably aren't hooked up. I think my next move will be to hook up some fans to the "chassis fan" connectors on the motherboard and see if that makes the fan inputs report anything. I am guessing that the standard test for this is to 1) see if the driver reports any RPM at all when the fan is turning and then 2) with the fan turning, put your thumb on the hub and make sure the reported RPM goes down. (I do have a function generator, but what fun is that?) Thanks! Matt Roberds
