Been scanning the recent activity around how 2.6.31 has broken fan control on many m/boards, and am hoping to make a contribution so this problem can be fixed. Given that my coding skills are limited to Fortran 77, best I can do is help with data and test. I've not (yet) enabled the "lax" workaround, so I don't know if it works. Happy to follow instructions from here to provide H/W input.
Regards
Matt
- i7-920 + ASUS P6T.
What worked:
- Under Ubuntu 9.0.4 with 2.6.14 through 2.6.16 (canonical distributions).
- Manual modprobe w83627ehf added to rc script
- lm-sensors 3.1.1 (tarball from sensors web-site). Fan control found 3 fans (1 CPU + 2 x chassis), with 2 x PWM devices (1 CPU + 1 chassis). The two m/b connected fans were sucessfully controlled using:
Settings for hwmon8/device/pwm2:
Depends on hwmon8/device/temp2_input
Controls hwmon8/device/fan4_input
What doesn't work:
- Under Ubuntu 9.10 with 2.6.31 (Canonical distribution, online upgrade from 9.0.4)
- sensors version 3.1.1 with libsensors version 3.1.1 (canonical distributions)
- sensors sees CPU and core temps + 3 fans.
- There are no pwm-capable sensor modules installed devices found (hence no fan-control)
# sensors
atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage: +1.05 V (min = +0.80 V, max = +1.60 V)
+3.3 Voltage: +3.30 V (min = +2.97 V, max = +3.63 V)
+5 Voltage: +4.97 V (min = +4.50 V, max = +5.50 V)
+12 Voltage: +11.97 V (min = +10.20 V, max = +13.80 V)
CPU FAN Speed: 2481 RPM (min = 600 RPM)
CHASSIS1 FAN Speed:3590 RPM (min = 600 RPM)
CHASSIS2 FAN Speed:3245 RPM (min = 600 RPM)
POWER FAN Speed: 0 RPM (min = 0 RPM)
CPU Temperature: +45.0°C (high = +60.0°C, crit = +75.0°C)
MB Temperature: +40.0°C (high = +45.0°C, crit = +75.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +46.0°C (high = +80.0°C, crit = +100.0°C)
...
coretemp-isa-0007
Adapter: ISA adapter
Core 7: +43.0°C (high = +80.0°C, crit = +100.0°C)
dmesg:
[ 13.045551] Adding 19044984k swap on /dev/md2. Priority:-1 extents:1 across:19044984k
[ 13.178591] nvidia: module license 'NVIDIA' taints kernel.
[ 13.178594] Disabling lock debugging due to kernel taint
[ 13.203853] Bluetooth: Generic Bluetooth USB driver ver 0.5
[ 13.203949] usbcore: registered new interface driver btusb
[ 13.222574] lp: driver loaded but no devices found
[ 13.431026] alloc irq_desc for 24 on node 0
[ 13.431028] alloc kstat_irqs on node 0
[ 13.431035] nvidia 0000:02:00.0: PCI INT A -> GSI 24 (level, low) -> IRQ 24
[ 13.431040] nvidia 0000:02:00.0: setting latency timer to 64
[ 13.431147] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 173.14.20 Thu Jun 25 18:15:32 PDT 2009
[ 13.511995] coretemp coretemp.0: Using relative temperature scale!
[ 13.512023] coretemp coretemp.1: Using relative temperature scale!
[ 13.512044] coretemp coretemp.2: Using relative temperature scale!
[ 13.512065] coretemp coretemp.3: Using relative temperature scale!
[ 13.512089] coretemp coretemp.4: Using relative temperature scale!
[ 13.512111] coretemp coretemp.5: Using relative temperature scale!
[ 13.512136] coretemp coretemp.6: Using relative temperature scale!
[ 13.512161] coretemp coretemp.7: Using relative temperature scale!
[ 13.570109] cfg80211: Calling CRDA to update world regulatory domain
[ 13.797234] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 14.204574] w83627ehf: Found W83627EHG chip at 0x290
[ 14.204594] ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region HWRE [0x290-0x299]
[ 14.204596] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
--
Matt Sheumack
_______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
