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