http://bugzilla.novell.com/show_bug.cgi?id=580988 http://bugzilla.novell.com/show_bug.cgi?id=580988#c2 --- Comment #2 from Francis Lamonde <frankebay99@gmail.com> 2010-02-26 02:20:51 UTC --- You are right, it wasn't easy to explain. Let's do it step by step. I will answer to *1 now and *2 partly now and fully on next suspend-to-RAM. *1 When fancontrol runs and I suspend-to-RAM (hereby and forever called STR), everything's ok during the suspend process. When I come back from STR, my fancontrol does not run, I mean for real, the actions/results fancontrol is providing normally is not happening, the fans are running at BIOS's speed, based on BIOS's settings to control the fans. Then I go in konsole and type the usual 'sudo fancontrol' to start it up, cuz to my eyes it is not running since the fans are controlled at the BIOS's settings (I know those settings, they increase by 200rpm my fans, I have set it up this way). When I start fancontrol after STR, the following happens: === Loading configuration from /etc/fancontrol ... Common settings: INTERVAL=5 Settings for hwmon5/device/pwm1: Depends on hwmon5/device/temp1_input Controls hwmon5/device/fan1_input MINTEMP=27 MAXTEMP=33 MINSTART=110 MINSTOP=110 MINPWM=110 MAXPWM=255 Settings for hwmon5/device/pwm2: Depends on hwmon5/device/temp2_input Controls hwmon5/device/fan2_input MINTEMP=28 MAXTEMP=40 MINSTART=105 MINSTOP=105 MINPWM=85 MAXPWM=255 File /var/run/fancontrol.pid exists, is fancontrol already running? === The .pid is running to the eyes of the kernel or whichever god controls the processes. But for real it's not controlling anything and when fancontrol does not control the fans, the BIOS takes over. I think I was not clear when I said "it thinks the service is NOT running". We should remove that statement. I CAN stop it and restart it, though really not the usual way. What I need to do is a 'sudo top | egrep fancontrol' After about 4-5 secs it finds the pid and returns something like 11738 root 20 0 12564 1728 1312 S 0 0.0 0:04.63 fancontrol So that I can 'sudo kill 11738' (11738 is subject to change of course) And then to start it up 'sudo fancontrol' It's a little less complicated then I originally thought, but still, fancontrol remains a pid part of top, though the service is really not running since the fans speeds are then controlled by the BIOS. When I restart fancontrol, the fan speeds immediately drop 200rpm like they should. These above steps need to be performed after each STR. *2 (partly) I suspect 'sensors' will return the real temps and speeds. I use gkrellm for all my sensors, gkrellm gets sensors' values and the values correspond to what they should be when the BIOS is controlling the speeds, not fancontrol. I will give it a true 'sensors' and see if it matches what I expect. I also don't believe it's fancontrol itself either. It really seems to be how the deamon or don't know what is controlling the fancontrol service. -- 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.