My CPU is stuck on the lowest speed. [Solved]

[Asimov]

It's probably caused by a power-manager daemon. But some desktops (Mate) are very slow.

[micia]

How can you tell that it's stuck at the lowest speed?
What's the output of:

Code: Select all

cpufreq-info


[Asimov]

cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 1.60 GHz - 2.80 GHz
available frequency steps: 2.80 GHz, 2.40 GHz, 2.14 GHz, 1.87 GHz, 1.60 GHz
available cpufreq governors: conservative, ondemand, powersave, userspace, performance
current policy: frequency should be within 1.60 GHz and 2.80 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
cpufreq stats: 2.80 GHz:10.23%, 2.40 GHz:0.28%, 2.14 GHz:0.33%, 1.87 GHz:0.49%, 1.60 GHz:88.68% (5451)
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 10.0 us.
hardware limits: 1.60 GHz - 2.80 GHz
available frequency steps: 2.80 GHz, 2.40 GHz, 2.14 GHz, 1.87 GHz, 1.60 GHz
available cpufreq governors: conservative, ondemand, powersave, userspace, performance
current policy: frequency should be within 1.60 GHz and 2.80 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.60 GHz.
cpufreq stats: 2.80 GHz:11.09%, 2.40 GHz:0.30%, 2.14 GHz:0.29%, 1.87 GHz:0.40%, 1.60 GHz:87.92% (5294)

[steffie]

CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1

[micia]

[...]
current CPU frequency is 1.60 GHz.
cpufreq stats: 2.80 GHz:10.23%, 2.40 GHz:0.28%, 2.14 GHz:0.33%, 1.87 GHz:0.49%, 1.60 GHz:88.68% (5451)
[...]
current CPU frequency is 1.60 GHz.
cpufreq stats: 2.80 GHz:11.09%, 2.40 GHz:0.30%, 2.14 GHz:0.29%, 1.87 GHz:0.40%, 1.60 GHz:87.92% (5294)

You should look at both lines, as you can see they are not stuck, there simply is an ondemand scheduler active that prevents the CPU to run fullspeed when it isn't necessary, to save power and prevent unnecessary overheating.
Your CPU ran 11% full power and 88% at low speed, which is perfectly normal for most systems.

If you wish to make it always run fullspeed, edit the:
/etc/conf.d/cpufrequtils
file to make it adopt the performance policy.
To make changes active avoiding a reboot you could run:
(as root)

Code: Select all

/etc/init.d/cpufrequtils restart


I would avoid doing it, the ondemand policy really affected my performance in only one (very old) processor this far.

[Asimov]

The stats are different on Enlitghtenment

current CPU frequency is 1.60 GHz.
cpufreq stats: 2.80 GHz:15.61%, 2.40 GHz:0.57%, 2.14 GHz:0.54%, 1.87 GHz:0.71%, 1.60 GHz:82.58% (3123)

| guess there is something wrong with the evaluation of demands on Mate. Because i had to wait, even for the drawing of the menu. Even Gnome was unresponsive.

Thank

[micia]

The stats aren't evaluated by MATE or E17, but by the kernel itself, so that cannot be the root of that issue.
The responsiveness issue could be caused by a number of other reasons, slow disk I/O (which is very unlikely since it would involve slowdowns on any environment) and, much more likely, bad graphics drivers setup.
Try to check for other possible reasons, I don't think this is due to a slow CPU.

[Asimov]

The stats aren't evaluated by MATE or E17, but by the kernel itself, so that cannot be the root of that issue.
The responsiveness issue could be caused by a number of other reasons, slow disk I/O (which is very unlikely since it would involve slowdowns on any environment) and, much more likely, bad graphics drivers setup.
Try to check for other possible reasons, I don't think this is due to a slow CPU.

KDE and Razor do not show any slowdown. E17 is not fast as usual but the response time remains acceptable. But Cinnamon, Gnome and Mate are slow like hell.

There is a bug with these application: When you launch nero or caja in enlightenment you have a the mate or cinnamon desktop opening in a window.

But you can't remove it.