Hi Casper, Le 29/12/2007, Casper Gripenberg a ?crit: >Rudolf Marek wrote: >> Perhaps you have still some kind of automatic mode maybe. What does >> cat pwm?_enable print? > >If I enable Asus Q-Fan (automatic fan control) from the >BIOS then pwm?_enable prints 2. If I disable it then it >prints 1. As expected... >> echo 1 > pwm1_enable will switch it to manual mode. > >Ok. I tried this both with automatic control enabled in >the BIOS and disabled. And then I tried again to echo >0 into pwm[1-4] with either mode. Nothing :( That's strange. >> You need to set there manual mode first. Imho you can try first with >> pwmconfig script which is doing that for you. Addtitionally you may >> check documentation for the chip in kernel >> Documentation/hwmon/w83627ehf >> >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/hwmon/w83627ehf;h=ccc2bcb610686aaf44a0d38c5f67db44e8985e82;hb=HEAD > >Thanks for the link. Seems the one that comes with my distro >(Ubuntu 7.10) was a bit outdated. > >I also have files called pwm?_mode, which are not explained >in the docs. I'm guessing these set either DC or pulse control >of the fan output. I tried modifying the values here too (either >0 or 1 was accepted). Didn't help either :-/ These are standard sysfs files, they are described in Documentation/hwmon/sysfs-interface. The external circuitry needed by each mode is different, so you shouldn't change the mode. The only reason why these files are writable is in case the BIOS did not properly setup the control mode, but that's not the case for you. >Anything else I could try? >(...) >Btw. with ASUS Q-Fan enabled the fans do spin down, so at >least the Q-Fan thing is working. But manual control not.. If the automatic mode (Q-Fan as Asus names it) works, it means that the chip is properly setup and the hardware is OK (both the board and the fans.) I have to admit that I have no idea why manual mode doesn't work then. But OTOH it seems that you are using a relatively old version of the driver, maybe that's an old bug causing the problem. If you have the opportunity to test with a recent live distribution (i.e. kernel >= 2.6.23), please give it a try. -- Jean Delvare
