Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#28121 - [linux] 3.2 - 3.3.x w83627ehf fails to load
Attached to Project:
Arch Linux
Opened by Pierre Schmitz (Pierre) - Thursday, 26 January 2012, 19:23 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 13 June 2012, 13:18 GMT
Opened by Pierre Schmitz (Pierre) - Thursday, 26 January 2012, 19:23 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 13 June 2012, 13:18 GMT
|
DetailsSince version 3.2.2 the module w83627ehf can no longer be loaded. Relevant dmesg output:
[ 169.279442] w83627ehf: Found NCT6776F chip at 0x290 [ 169.279506] ACPI: resource w83627ehf [io 0x0295-0x0296] conflicts with ACPI region HWRE [io 0x290-0x299] [ 169.279511] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver (I'll try to figure out later and add more information; for now just wanted to let you know that there might be a problem) |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Wednesday, 13 June 2012, 13:18 GMT
Reason for closing: Not a bug
Wednesday, 13 June 2012, 13:18 GMT
Reason for closing: Not a bug
I reported the problem (not knowing what caused it) and got the following explanation from Jean Delvare:
"That was indeed a bug... in 3.2. Kernels between 2.6.39 and 3.2
(inclusive) lack the ACPI resource conflict check, it was accidentally
disabled. And this is fixed in 3.3.
See
http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
for details."