Hi Patrick, On Sun, 11 Jan 2015 11:56:02 -0500, Patrik Dufresne wrote: > I've attach a tar.gz, I guess the mailing list doesn't accept attachments. > Thanks for your help. It's really appreciated. As Guenter already pointed out, the right way to solve this is most certainly by enabling IPMI and using ipmi tools. That being said, there's one strange thing with native drivers that I do not understand: > # sensors-detect > # sensors-detect revision 6260 (2014-12-12 15:25:20 +0100) > # System: Supermicro X10SLM-F [0123456789] > # Kernel: 3.16.0-0.bpo.4-amd64 x86_64 > # Processor: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz (6/60/3) > (...) > Next adapter: SMBus I801 adapter at 0580 (i2c-0) > Do you want to scan it? (YES/no/selectively): yes > Client found at address 0x1b > Handled by driver `jc42' (already loaded), chip type `jc42' Here it is said that the jc42 driver is bound to this device. However... > # sensors > acpitz-virtual-0 > Adapter: Virtual device > temp1: +27.8°C (crit = +105.0°C) > temp2: +29.8°C (crit = +105.0°C) > > coretemp-isa-0000 > Adapter: ISA adapter > Physical id 0: +29.0°C (high = +80.0°C, crit = +100.0°C) > Core 0: +29.0°C (high = +80.0°C, crit = +100.0°C) > Core 1: +26.0°C (high = +80.0°C, crit = +100.0°C) > Core 2: +27.0°C (high = +80.0°C, crit = +100.0°C) > Core 3: +25.0°C (high = +80.0°C, crit = +100.0°C) It does not show up here. Was the jc42 driver still loaded at that point? Did you force the driver to bind to the device? To investigate this further, I would need a word dump of the chip: # i2cdump 0 0x1b w Thanks, -- Jean Delvare SUSE L3 Support _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
