kernel >= 3.2.2 refuses to load w83627ehf because w83627ehf conflicts with ACPI region HWRE (verified on an AMD Phenom platform as well as on an Intel Xeon platform). Reproducible: Always Steps to Reproduce: 1. build 3.2.2 with CONFIG_SENSORS_W83627EHF=y 2. < re-boot > 3. grep -i w83627ehf /var/log/messages Actual Results: w83627ehf: Found NCT6776F chip at 0x290 resource w83627ehf [io 0x0295-0x0296] conflicts with ACPI region HWRE [io 0x290-0x299] Expected Results: w83627ehf: Found [...] chip at 0x290 Opened this bug for others to find (and follow) upstream bug cited above more easily.
detected because lm_sensors seemed not to display fan readings any more ;)
There lspci would be more helpful, but try asus_atk0110 module instead (CONFIG_SENSORS_ATK0110).
(In reply to comment #2) > ... instead ... Details: "Old Box" = AMD Phenom(tm) 9950 Quad-Core on ASUS M2N-SLI Deluxe featuring it87 sensor chip (ISA bus, address 0x290), formerly driven by "CONFIG_SENSORS_IT87"; now sensors being read by "CONFIG_SENSORS_ATK0110" _instead_ successfully in 3.2.2 - no conflicts. "New Box" = Intel(R) Xeon(R) CPU E31275 on ASUS P8B WS (new C206 B3 version) featuring Nuvoton NVT6776F (ISA bus, address 0x290), formerly driven by "CONFIG_SENSORS_W83627EHF"; now sensors being read by "CONFIG_SENSORS_ATK0110" in 3.2.2 - no conflicts; cpu-temp readings working; no (fan-)sensor readings available. Similar findings with 3.0.18. I presume, IFF these drivers can be configured "=y" simultaneously, they should be expected not to be mutually exclusive or conflict at boot / load time ?
Please c.f. https://bugzilla.kernel.org/show_bug.cgi?id=42682#c3 A well written explanation: http://www.lm-sensors.org/wiki/FAQ/Chapter3 #Mysensorshavestoppedworkinginkernel2.6.31
With "acpi_enforce_resources=lax" enabling the load of W83627EHF, Nuvoton NVT6776F readings are available. asus_atk0110 is not capable of providing the NVT6776F readings yet. So perhaps this bug should be modified to become a beg for enhancement of asus_atk0110 so that loading of W83627EHF becomes obsolete again ?
Will watch the upstream bug and backport and fixes identified.