MEPIS Community Forum

I have an Acer travelmate 5740G, running M11 64 bit, it constantly overheats, I recently discovered this problem does not occur in W7 much to my dismay. I have tried playing with the perfomance parameters and had no luck with it constantly running at 70 degrees, it should be around 50 degrees.
### Edit ###
I suspect it is a CPU frequency scaling issue and am looking at this possibility, any alternate views or experience with these issues is appreciated, this artical looks promising http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html

The standard 2.6.36 M11 kernel may also be too old for this hardware, so I'd experiment with a newer one from squeeze-backports to see if that fixes the problem, as well as the newer xorg drivers there.

I have been looking at how to tinker with cpufreq scaling governors http://www.thinkwiki.org/wiki/How_to_make_use_of_Dynamic_Frequency_Scaling what do you think is it a good move or a dead end

The KDE in M11 does support CPU scaling, but it seems to be stuck on dynamic--that is, it varies depending on the load. whether you choose performance or powersave. This is OK, but your Travelmate may be stuck on High Speed, and maybe only a new kernel will let cpu scaling work. I did write a little guide in Tips and Tricks here on how to manually control the CPU speed:

viewtopic.php?f=23&t=29018

your right no matter what setting I use the frequency is 2266000
I will have a look at your guide

I have succesfully reduced the speed to 933M using your guide but the temp is still stubbornly sitting on 65 - 67 degrees

### edit ### 23 April 2012
it seems to be a major problem with a number of current linux kernels at the moment, I am also wondering about the acpi setting as a GRUB option

### edit 2 ### 24 April 2012
from what I have read online setting acpi in GRUB doesn't fix it, the problem is fixed in kernel 3.3 so I might be looking at the backports as you suggested Stevo

### edit 3 ### 25 April 2012
the backports only have 3.2 currently available, and from all I have read it is not fixed until 3.3, anyways I have set up an experimental install so I will backport 3.2 for the practice