1 |
I see lots of bug reports about this in several linux OSs but not able |
2 |
to see a solution. |
3 |
|
4 |
I've make the propers kernel settings and the w83627hf modules is |
5 |
built and available in /lib/modules/* |
6 |
I tried rebuilding the kernel with that stuff built-in. but then |
7 |
lm_sensors couldn't even find tools to work with when running |
8 |
sensors-detect |
9 |
|
10 |
So calling `sensors' just in case it would work: |
11 |
# sensors |
12 |
No sensors found! |
13 |
Make sure you loaded all the kernel drivers you need. |
14 |
Try sensors-detect to find out which these are. |
15 |
|
16 |
Back to a modular kernel: |
17 |
lm_sensors tells me that w83627hf is the one to load in |
18 |
/etc/conf.d/lm_sensors. |
19 |
|
20 |
But any attempt to load it meets with this result (wrapped for mail): |
21 |
modprobe w83627hf |
22 |
FATAL: Error inserting w83627hf |
23 |
(/lib/modules/2.6.33-gentoo/kernel/drivers/hwmon/w83627hf.ko): |
24 |
Device or resource busy |
25 |
|
26 |
Looking at dmesg after running the above command, I find lines like |
27 |
these (repeated several times): |
28 |
[ 1321.715673] w83627hf: Found W83627THF chip at 0x290 |
29 |
|
30 |
[ 1321.715712] ACPI: I/O resource w83627hf [0x295-0x296] conflicts |
31 |
with ACPI region HWMT [0x295-0x296] |
32 |
|
33 |
[ 1321.715716] ACPI: If an ACPI driver is available for this device, |
34 |
you should use it instead of the native driver |
35 |
|
36 |
------- --------- ---=--- --------- -------- |
37 |
|
38 |
So anyone know what is wrong here? |