Second workaround:

In grub line to add intel_pstate=disable to activate module acpi-cpufreq instead intel_pstate. Then cpupower works as well.

Well,

intel_pstate is the driver designed for use with Sandy Bridge and newer hardware, 

acpi-cpufreq is obsolete and does not handle new hw efficiently

CC: (none) => tmb

Ah, I see you noticed in first "workaround" that it needs another performance or powersave.

Trouble is we dont have a way so far to set that config depending on hw.

I wonder if we should forcus on performance as default, and let people set other states if they want...

· Ok, so, who uses a driver intel_pstate (see example output from # cpupower frequency-info) then user must change from "ondemand" to "performance" or "powersave" in /etc/sysconfig/cpupower. Otherwise cpupower.service fails on start.

If some problems with apps (like Steam (choppy sound, ...), etc.) then in grub line to add intel_pstate=disable to activate older acpi-cpufreq.

· Sources:
https://wiki.archlinux.org/index.php/CPU_frequency_scaling
https://bbs.archlinux.org/viewtopic.php?pid=1294415#p1294415

· Q: Is not better to set in cpupower-3.12.18-x.mga4 to "powersave" for all processors?

· Q: Better to add some information to wiki about how to use/switch cpupower? Errata/New "cpupower" page


Thank you and for me can be this bugreport closed as solved/workaround.

I'm not sure if this is related. With this kernel the contents of /sys/devices/system/cpu/cpu0/cpufreq is:-

[derij@pip cpufreq]$ uname -a
Linux pip.chuzzlewit.co.uk 3.12.18-desktop-1.mga4 #1 SMP Thu Apr 24 13:10:59 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[derij@pip cpufreq]$ ll
total 0
-r--r--r-- 1 root root 4096 May 15 11:16 affected_cpus
-r-------- 1 root root 4096 May 15 11:16 cpuinfo_cur_freq
-r--r--r-- 1 root root 4096 May 15 11:16 cpuinfo_max_freq
-r--r--r-- 1 root root 4096 May 15 11:16 cpuinfo_min_freq
-r--r--r-- 1 root root 4096 May 15 11:16 cpuinfo_transition_latency
-r--r--r-- 1 root root 4096 May 15 11:16 related_cpus
-r--r--r-- 1 root root 4096 May 15 11:16 scaling_available_governors
-r--r--r-- 1 root root 4096 May 15 11:16 scaling_driver
-rw-r--r-- 1 root root 4096 May 15 11:13 scaling_governor
-rw-r--r-- 1 root root 4096 May 15 11:16 scaling_max_freq
-rw-r--r-- 1 root root 4096 May 15 11:16 scaling_min_freq
-rw-r--r-- 1 root root 4096 May 15 11:16 scaling_setspeed

With a previous kernel it is:-

[root@pip cpufreq]# uname -a
Linux pip.chuzzlewit.co.uk 3.12.13-desktop-2.mga4 #1 SMP Sat Feb 22 23:45:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[root@pip cpufreq]# ll
total 0
-r--r--r-- 1 root root 4096 May 14 16:21 affected_cpus
-r--r--r-- 1 root root 4096 May 14 16:21 bios_limit
-r-------- 1 root root 4096 May 14 16:21 cpuinfo_cur_freq
-r--r--r-- 1 root root 4096 May 14 16:21 cpuinfo_max_freq
-r--r--r-- 1 root root 4096 May 14 16:21 cpuinfo_min_freq
-r--r--r-- 1 root root 4096 May 14 16:21 cpuinfo_transition_latency
-r--r--r-- 1 root root 4096 May 14 16:21 freqdomain_cpus
-r--r--r-- 1 root root 4096 May 14 16:21 related_cpus
-r--r--r-- 1 root root 4096 May 14 16:19 scaling_available_frequencies
-r--r--r-- 1 root root 4096 May 14 16:21 scaling_available_governors
-r--r--r-- 1 root root 4096 May 14 16:19 scaling_cur_freq
-r--r--r-- 1 root root 4096 May 14 16:21 scaling_driver
-rw-r--r-- 1 root root 4096 May 14 16:19 scaling_governor
-rw-r--r-- 1 root root 4096 May 14 16:21 scaling_max_freq
-rw-r--r-- 1 root root 4096 May 14 16:21 scaling_min_freq
-rw-r--r-- 1 root root 4096 May 14 16:21 scaling_setspeed

One important difference is that scaling_available_frequencies is missing. This prevents a plasmoid called CPUFreqDisplay from starting, and I wonder whether it is a reason for "ondemand" to stop working.

CC: (none) => deri

(In reply to Deri James from comment #5)
...
> One important difference is that scaling_available_frequencies is missing.
> This prevents a plasmoid called CPUFreqDisplay from starting, and I wonder
> whether it is a reason for "ondemand" to stop working.

As next Mageia user reported gkrellm (HW monitoring system) - 0 MHz for all CPUs.

To see actual frequencies:
$ watch grep \"cpu MHz\" /proc/cpuinfo

For what I can tell (trying mga4 with a i5-4200M), the intel_pstate seems to be the better solution, but it has a bug, which was only resolved in kernel 3.14, see https://bugzilla.kernel.org/show_bug.cgi?id=66581

Would it be possible to backport the changes into the current kernel, or get a new kernel version for mga4 ?

CC: (none) => kriks

Also seen on M5 alpha 1 (current kernel)

Version: 4 => Cauldron
Whiteboard: (none) => 5alpha1

In my experience fixing in Cauldron seems to have best chance of getting stable versions fixed as well (correct me if I'm wrong).

Seeing this also with kernel-desktop-3.15.6-1.mga5 on a laptop, but not with kernel-server-3.15.6-1.mga5 on a large memory desktop machine:

# systemctl status cpupower.service
cpupower.service - ...
   Loaded: loaded ...
   Active: failed (Result exit code) since ... 
   ... code=exited, status=237

The laptop is a < 1 year old Toshia Satellite C55-A with Intel Celeron 1037U (x86_64 dual core).

CC: (none) => dvgevers
Whiteboard: 5alpha1 => MGA4TOO; 5alpha2

Re Comment #c9: this goes for first built 5alpha2 wth dual DVD (64 bits) and classical 32 bits DVD.

For me it is fixed in current Cauldron and in fresh install from M5 beta1 with latest M5 kernels !!

Whiteboard: MGA4TOO; 5alpha2 => MGA4TOO;

(In reply to Christian Pernot from comment #7)
> For what I can tell (trying mga4 with a i5-4200M), the intel_pstate seems to
> be the better solution, but it has a bug, which was only resolved in kernel
> 3.14, see https://bugzilla.kernel.org/show_bug.cgi?id=66581
> 
> Would it be possible to backport the changes into the current kernel, or get
> a new kernel version for mga4 ?


We have 3.14 series in mga4 now, 

(In reply to Dick Gevers from comment #11)
> For me it is fixed in current Cauldron and in fresh install from M5 beta1
> with latest M5 kernels !!


when the 3.14.22 currently in updates_testing is released, cpupower is switched to performance governor like I have done in Cauldron

indeed, now cpupower is switched to performance governor by default in mga4 through last updates (3.14.24-desktop-1.mga4), which seems wrong for me, as it causes more energy consumption for no benefit.
(acpi-cpufreq is what my computer is using though)

[jice@localhost ~]$ uname -a
Linux localhost.localdomain 3.14.24-desktop-1.mga4 #1 SMP Sat Nov 15 23:54:03 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[jice@localhost ~]$ cat /etc/modprobe.preload.d/cpufreq
acpi-cpufreq
cpufreq_powersave
cpufreq_conservative
cpufreq_ondemand

So I did the following:
[fred@localhost ~]$ cat /etc/sysconfig/cpupower
# See 'cpupower help' and cpupower(1) for more info
#CPUPOWER_START_OPTS="frequency-set -g performance"
#CPUPOWER_STOP_OPTS="frequency-set -g performance"
# JCC 22-nov-2014
CPUPOWER_START_OPTS="frequency-set -g ondemand"
CPUPOWER_STOP_OPTS="frequency-set -g ondemand"

CC: (none) => mageia

Setting performance always on a laptop is not really perfect no ?
(it looks it doesn't change the govervor with or without AC.)

Can someone confirm that intel_pstate driver works on mga4. If yes, this bug should be closed.

CC: (none) => dirteat

Setting version to Mageia 4 as per comment #15. For Mageia 5, release notes or errata contain words about the change.

Keywords: (none) => NEEDINFO
Version: Cauldron => 4
Whiteboard: MGA4TOO; => (none)

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD