Don't worry, your machine is OK. I've got this behavior on a few of my machines. I'd expect it's a result of the overall crappiness of the x86 platform rather than a bug in the driver. Seeing how it(4) was added in 3.4, said crappiness probably involves cheap design and hardware as well as a HUGE diversity in how various vendors implement these sensors. Figuring out that they are even there on the i2c bus let alone WHO they are has got to be some tricky work.
Looks like there's some new stuff in -current related to sensors, a "two-level api." I don't know what this does for sensors, but it has to be good! =) Travers Buda On Sat, 23 Dec 2006 21:18:54 -0600 "Matthew R. Dempsky" <[EMAIL PROTECTED]> wrote: > When I run ``sysctl hw.sensors'' on one of my machines, I get the > following output: > > $ sysctl hw.sensors > hw.sensors.0=it0, Fan1, 5113 RPM > hw.sensors.3=it0, VCORE_A, 1.25 V DC > hw.sensors.4=it0, VCORE_B, 2.56 V DC > hw.sensors.5=it0, +3.3V, 2.38 V DC > hw.sensors.6=it0, +5V, 3.52 V DC > hw.sensors.7=it0, +12V, 10.69 V DC > hw.sensors.8=it0, Unused, -2.75 V DC > hw.sensors.9=it0, -12V, -11.40 V DC > hw.sensors.10=it0, +5VSB, 4.87 V DC > hw.sensors.11=it0, VBAT, 4.08 V DC > hw.sensors.12=it0, Temp 1, 33.00 degC > hw.sensors.13=it0, Temp 2, 35.00 degC > hw.sensors.14=it0, Temp 3, 36.00 degC
