On 21 Mar, Harry Putnam wrote: > Harry Putnam <rea...@newsguy.com> writes: > > Forgot to give kernel version: > uname -r > 2.6.33-gentoo > >> I see lots of bug reports about this in several linux OSs but not able >> to see a solution. >> >> I've make the propers kernel settings and the w83627hf modules is >> built and available in /lib/modules/* >> I tried rebuilding the kernel with that stuff built-in. but then >> lm_sensors couldn't even find tools to work with when running >> sensors-detect >> >> So calling `sensors' just in case it would work: >> # sensors >> No sensors found! >> Make sure you loaded all the kernel drivers you need. >> Try sensors-detect to find out which these are. >> >> Back to a modular kernel: >> lm_sensors tells me that w83627hf is the one to load in >> /etc/conf.d/lm_sensors. >> >> But any attempt to load it meets with this result (wrapped for mail): >> modprobe w83627hf >> FATAL: Error inserting w83627hf >> (/lib/modules/2.6.33-gentoo/kernel/drivers/hwmon/w83627hf.ko): >> Device or resource busy >> >> Looking at dmesg after running the above command, I find lines like >> these (repeated several times): >> [ 1321.715673] w83627hf: Found W83627THF chip at 0x290 >> >> [ 1321.715712] ACPI: I/O resource w83627hf [0x295-0x296] conflicts >> with ACPI region HWMT [0x295-0x296] >> >> [ 1321.715716] ACPI: If an ACPI driver is available for this device, >> you should use it instead of the native driver >> >> ------- --------- ---=--- --------- -------- >> >> So anyone know what is wrong here?
I can only report that I've built a 2.6.33-gentoo kernel with the device (sensors) Winbond W83627EHF/EF/EHG/EG built in (not just a module), then ran sensors-detect and now, xsensor works just fine (on a Phenom-II) Helmut. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany
