[Bug 544867] New: pwmconfig broken: unable to recognize fan chip
http://bugzilla.novell.com/show_bug.cgi?id=544867 Summary: pwmconfig broken: unable to recognize fan chip Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 8 Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: frankebay99@gmail.com QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.16) Gecko/20080716 SUSE/2.0.0.16-0.1 Firefox/2.0.0.16 I have run pwmconfig in 10.3 64-bits no problem. It detected the chip and tested the fans. I set up a FANCONTROL file which works for 2 years without a flaw. I copied that file to /etc in 11.2 M8 but it does not load. I see an error during boot sequence, but I don't remember in which log file to grep it. If I manually start fancontrol with 'sudo fancontrol' it tells the following: --- m8@oskde64:~> fancontrol Loading configuration from /etc/fancontrol ... Common settings: INTERVAL=5 Settings for hwmon0/device/pwm1: Depends on hwmon0/device/temp1_input Controls hwmon0/device/fan1_input MINTEMP=30 MAXTEMP=38 MINSTART=115 MINSTOP=115 MINPWM=115 MAXPWM=255 Settings for hwmon0/device/pwm2: Depends on hwmon0/device/temp2_input Controls hwmon0/device/fan2_input MINTEMP=28 MAXTEMP=40 MINSTART=110 MINSTOP=110 MINPWM=100 MAXPWM=255 Configuration is too old, please run pwmconfig again --- So I run pwmconfig, but it's broken and cannot detect correctly my fan chip It gives me the following error: --- /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed --- Fine, so let's run 'sensors' and see what I get: --- m8@oskde64:~> sensors atk0110-acpi-0 Adapter: ACPI interface Vcore Voltage: +1.22 V (min = +0.85 V, max = +1.60 V) +3.3 Voltage: +3.30 V (min = +2.97 V, max = +3.63 V) +5 Voltage: +4.87 V (min = +4.50 V, max = +5.50 V) +12 Voltage: +11.98 V (min = +10.20 V, max = +13.80 V) CPU FAN Speed: 856 RPM (min = 600 RPM) CHASSIS1 FAN Speed:1081 RPM (min = 600 RPM) CHASSIS2 FAN Speed:1081 RPM (min = 600 RPM) CHASSIS3 FAN Speed:1110 RPM (min = 800 RPM) CPU Temperature: +27.0°C (high = +60.0°C, crit = +95.0°C) MB Temperature: +33.0°C (high = +45.0°C, crit = +95.0°C) coretemp-isa-0000 Adapter: ISA adapter Core 0: +42.0°C (high = +82.0°C, crit = +100.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +43.0°C (high = +82.0°C, crit = +100.0°C) coretemp-isa-0002 Adapter: ISA adapter Core 2: +34.0°C (high = +82.0°C, crit = +100.0°C) coretemp-isa-0003 Adapter: ISA adapter Core 3: +39.0°C (high = +82.0°C, crit = +100.0°C) --- Ok, so what's the problem then? Reproducible: Always Steps to Reproduce: 1. Run pwmconfig 2. 3. Actual Results: No pwm-capable sensors installed. Expected Results: Sensors seem to be installed and loaded, pwmconfig should detect them. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=544867 User frankebay99@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=544867#c1 --- Comment #1 from Francis Lamonde <frankebay99@gmail.com> 2009-10-07 06:38:56 MDT --- I am also missing the bridge temperature (AUX Temp) and 4 or 5 Voltages. As a comparison, here is what I get in 10.3 (exact same hardware, it's the same machine that I use): frank@oskde64:~> sensors coretemp-isa-0003 Adapter: ISA adapter Core 3: +39.0°C (crit = +100.0°C) coretemp-isa-0002 Adapter: ISA adapter Core 2: +33.0°C (crit = +100.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +39.0°C (crit = +100.0°C) coretemp-isa-0000 Adapter: ISA adapter Core 0: +40.0°C (crit = +100.0°C) w83627dhg-isa-0290 Adapter: ISA adapter VCore: +1.22 V (min = +0.00 V, max = +1.74 V) in1: +11.30 V (min = +0.00 V, max = +6.76 V) ALARM AVCC: +3.30 V (min = +1.02 V, max = +0.54 V) ALARM 3VCC: +3.30 V (min = +2.06 V, max = +1.15 V) ALARM in4: +1.43 V (min = +0.51 V, max = +0.05 V) ALARM in5: +1.62 V (min = +0.01 V, max = +1.03 V) ALARM in6: +4.61 V (min = +0.82 V, max = +0.00 V) ALARM VSB: +3.30 V (min = +0.00 V, max = +0.29 V) ALARM VBAT: +2.82 V (min = +2.06 V, max = +2.08 V) ALARM Case Fan: 843 RPM (min = 2636 RPM, div = 32) ALARM CPU Fan: 942 RPM (min = 1298 RPM, div = 8) ALARM Aux Fan: 843 RPM (min = 2343 RPM, div = 32) ALARM fan5: 878 RPM (min = 82 RPM, div = 128) Sys Temp: +32.0°C (high = +9.0°C, hyst = +80.0°C) CPU Temp: +26.0°C (high = +80.0°C, hyst = +75.0°C) AUX Temp: +121.5°C (high = +80.0°C, hyst = +75.0°C) ALARM -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=544867 User frankebay99@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=544867#c2 --- Comment #2 from Francis Lamonde <frankebay99@gmail.com> 2009-10-07 08:20:22 MDT --- Ok I am progressing. There's been a change in 2.6.31 so lm-sensors works differently now. This cuts the hwmon monitoring. There is explanation and potential fix here: http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginker... I will try that, though I don't know how to enable a driver in the kernel, but if the bypass method in grub.conf works, then it's not a bug for sure. I would like to have that confirmed somehow, ideally by someone who did the fix from that website, if anyone is reading this and has tried, plz let me know. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=544867 User frankebay99@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=544867#c3 Francis Lamonde <frankebay99@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |UPSTREAM --- Comment #3 from Francis Lamonde <frankebay99@gmail.com> 2009-10-07 20:20:06 MDT --- Ok got it. So yes, since 2.6.31 (2.6.30, but there was a bug so it hit only in 2.6.31 (and 2.6.29 for Fedora)) there is a new way to talk with sensors which does not conflict with acpi on the ports. This is mostly for recent MB models to prevent 2 processes to talk to the ports and potentially freeze the machine.. Mine is 2yo, so it's older and I should not have that problem. I ran 2 years without issues so I take the risk to continue the legacy way. For those people (legacy), or for the risky ones, you can edit your 'menu.lst' (grub.conf for some other distros) in /boot/grub and make sure you have the option 'acpi_enforce_resources=lax'. Something like this: --- kernel /boot/vmlinuz-2.6.31-10-desktop root=/dev/sdb1 resume=/dev/disk/by-id/ata-ST3500320AS_5QM0PP7M-part5 splash=silent quiet showopts acpi_enforce_resources=lax vga=0x317 initrd /boot/initrd-2.6.31-10-desktop --- Of course, reboot. If you run 'sensors', you'll notice it show a lot more sensors than before. Good news. Then run pwmconfig. It will not display the error anymore, but it might still fail to control/test the fans. Continue the test up to the point it creates the FANCONTROL file. Then quit and either run 'sudo fancontrol' to see if it works, or edit the file to ensure driver 'atk01100' is associated with 'hwmon0' and that the sensors are associated with another number. In my case it was 'hwmon5'. Not superclean, but for older MB it's risk free and it works. Closing. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com