Page 1 of 1
CPUFREQ -- how to disable?
Posted: 16. Dec 2015, 06:30
by chazbroam
I have this old Dell Latitude that I am working on for my mom. The only real glitch it has is: it does not allow the software to handle CPU scaling. So anything with CPUFREQ, it just does not compute due to a firmware bug on it. It has only one CPU -- a Celeron 2.4 GHz. It is only single core -- 32bit.
I don't even want "Userspace" to run. Really. I want to turn the the whole thing OFF. So how do I go about it? I've tried to turn it off in /etc/rc.d/rc.modules, but that doesn't work. After a reboot, it's right back on.
Re: CPUFREQ -- how to disable?
Posted: 16. Dec 2015, 12:23
by djemos
pass the intel_pstate=disable to the kernel at boot. e.g. in your lilo.conf file
Edit:
Code: Select all
append="vt.default_utf8=1 intel_pstate=disable'
Re: CPUFREQ -- how to disable?
Posted: 16. Dec 2015, 14:53
by chazbroam
Code: Select all
append="vt.default_utf8=0,intel_pstate=disable'
It worked for one reboot, then went back to reporting 12MHz CPU speed (Conky).
Next suggestion please?
Re: CPUFREQ -- how to disable?
Posted: 16. Dec 2015, 15:41
by djemos
edit /etc/rc.d/rc.modules
on line 886, #/sbin/modprobe cpufreq_performance remove the # from the beginning of line
or at
line 823, line 830 CPUFREQ=on ( turn it to off)
and bellow
Play with this file settings to disable it.
Re: CPUFREQ -- how to disable?
Posted: 16. Dec 2015, 16:40
by westms
djemos wrote:pass the intel_pstate=disable to the kernel at boot. e.g. in your lilo.conf file
Code: Select all
append="vt.default_utf8=0,intel_pstate=disable'
Hello djemos,
I would like to make a correction. In the append= string, the comma must be replaced by a space. Commas have different meaning.
If originally vt.default_utf8=1 was present, and now vt.default_utf8=0 is valid, then it might be necessary to run unicode_start.
Re: CPUFREQ -- how to disable?
Posted: 16. Dec 2015, 17:08
by djemos
it was just an example. User can have whatever he likes in append=""
intel_pstate=disable is the needed parameter. As for the space, yes you're right.