I am not able to run the script!
Is it the smcfancontrol or the (shell script) smcfancontrol.sh that has to be ran? Running the shell script does not output anything. Running the smcfancontrol like:I getCode:sudo ./smcfancontrolUPDATE: I just had a look. This is checking for battery which is not in its place on my system. I use AC always while at home. I'll comment it out and see whether it works or not.Code:./smcfancontrol: line 109: *online=true: command not found
UPDATE 2: Nothing happens. The error message is away but it just waits and waits...
(shrug!) So I break it with Ctrl+C. Any help?
Last edited by Nikos.Alexandris; September 10th, 2009 at 03:15 AM.
Try running as
sudo /etc/init.d/smcfancontrol.sh start
Before you do so, you should change sensorsUsed=2 to sensorsUsed=25 or so. You basically need to monitor GPU temperature, and it is way down the list of sensors. The default is to monitor the CPU temperature which is not as high as the GPU.
To uninstall, I think deleting the two files /etc/init.d/smcfancontrol and /usr/local/sbin/smcfancontrol.sh and deleting the links under all the run levels rc0.d, rc1.d, etc, should do it.
Joushou, you did a very good job with this script, thanks.
Last edited by amd-64; September 10th, 2009 at 02:19 PM.
linux, linux, linux
All and all the sensors reported on the MBP51 are 20 (that's what the command [b]sensors[/s] gives).
Comparing the output of the command sensors and the Thermal Monitor of Nvidia X Server Settings application, the sensor # 8 corresponds to the GPU (using the "default" Nvidia 9600 graphics chip).
I guess the value of sensorsUsed should be set to 20 (?).
Yes, use 20. It should not affect the results. The number should be high enough to include all sensors. For me, on a MBP 5,3 the GPU is always the governing sensor.
linux, linux, linux
Using it since yesterday (sensorsUsed=20 and fanMinSpeed=2999). The result is that the GPU is kept at 69~70 deg. while the CPU's at 57~60 deg. The difference is not too much but it is something. I might need to modify something (more).
I want to note that the same level of temperature is achieved by using the mfc-daemon.
Anyhow, thanks to the author(s) for the(ir) script(s).
Nikos,
Here is the output from sensors, the machine is not doing anything intensive at this time and has been up for 2 hrs.
Code:#sensors coretemp-isa-0000 Adapter: ISA adapter Core 0: +41.0°C (high = +100.0°C, crit = +100.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +41.0°C (high = +100.0°C, crit = +100.0°C) applesmc-isa-0300 Adapter: ISA adapter Left side :2739 RPM (min = 2739 RPM) Right side :2742 RPM (min = 2739 RPM) temp1: +30.0°C temp2: +30.0°C temp3: +30.0°C temp4: +0.0°C temp5: +46.8°C temp6: +40.0°C temp7: +42.8°C temp8: +53.5°C temp9: +42.5°C temp10: +38.8°C temp11: +44.8°C temp12: +45.8°C ERROR: Can't get value of subfeature temp13_input: I/O error temp13: +0.0°C temp14: +47.0°C temp15: +45.2°C temp16: +49.0°C temp17: +40.5°C temp18: +45.8°C temp19: +28.2°C temp20: +35.2°C
As you can see it is significantly cooler. BTW the cpu is a P8800 not a T9xxx and I am running Nvidia-185 driver. I removed cpufreq, powersave, cpudyn. I use powernowd and both CPU and GPU scale down properly.
My GPU temps would only get above 60 when Firefox and Flash hog the CPU, which happens occasionally with firefox 3.5 on certain sites.
I use ksensors to dock CPU and GPU temps and fan speeds so I keep an eye on these.
On occasion, smcfancontrol quits, I think because of failing to read one of the sensors, this is why I created a cron job to restart it every few minutes until someone writes a cleaner fix. Since then, it has been maintenance-free and the fans are not noisy.
linux, linux, linux
I have been using these fan scripts for the past three days now and I notice a big difference.
However, a colleague of mine mentioned that fan control scripts could potentially not regulate the fans correctly and fry everything or some spots may be cool and others may be hot.
With the nature of applesmc and these scripts, does this have the potential of bricking your computer? Does this truely override the built in fan control?
Bookmarks