RHEL+Celeron-M - CPUfreq possible?
 

Hi,

I am currently running Scientific Linux 4.4 ( a RHEL clone) on Acer Travelmate 2312 ( Celeron M) and the kernel is 2.6.9-42.0.3.EL. Earlier I ran Mandriva 2006.0 and SUSE-10.1 on the same machine and could perform frequency scaling.

Somehow I cannot do the same for this RHEL clone ( I think this should the same for RHEL and its clones).

Has anyone managed to do this on Celeron-M with RHEL4? I think the kernel fails to detect even the basic speedstep capabilities of the CPU. In the earlier distros used ( MdV and SUSE) I needed to insert the module p4-clockmods and that did the job. I can't do this now as it seems there is no "/sys/devices/system/cpu/cpu0/cpufreq" present.

Any ideas?

Thanks in advance,

AM

Does the kernel have cpufreq support built in? And are all of the modules for cpufreq enabled in the kernel? Second, do you have cpufreqd or powernowd installed and running? You need to have both the driver and the program to get cpufreq working.

Dear Titetanium,

How can I tell that the kernel has cpufreq support built in ? For RHEL kernels - they have they have cpuspeed instead of powernowd which is present in other vendors kernels (SUSE/Ubuntu..).

On Mandriva, the frequency scaling is controlled by cpufreqd -it is also available from dag's repo for EL4 but is not part of the standard EL4.

I have posted the similar question in the centos forum but I was surprised that not too many people are running centos/EL4 on laptops!!

Thanks anyway. I will post my findings on this thread.

- AM

Tweaking/ recompiling the kernel got me nowhere. Following a suggestion by Lenard ( who regularly posts here as well as in the Centos forums) - I intend to use the RHEL beta 2 kernel. I tried FC6 on the machine and for it cpufreq works flawlessly.

A.

I didn't take into account the differences between distros as I use debian. I compile all of my kernels every time to work with my laptop. Perhaps when you are compiling your kernel, you could copy the .config file in /usr/src/<kernel version> from the previous kernel that successfully worked. That way you could tailor it to your laptop from that config.