Bug 8295

Summary: Power management: cpufreqd cannot start
Product: Mageia Reporter: Pierre Jarillon <jarillon>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: mageia, mageia, n54
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: cpufreq CVE:
Status comment:

Description Pierre Jarillon 2012-12-04 10:14:32 CET 
Laptop Fujitsu-Siemens - Processor: Intel Pentium 4, 2.66 GHz - 1 Core
The frequency is always locked at 2.67 GHz and cpufreqd cannot start

# LC_ALL=C cpupower frequency-info
analyzing CPU 0:
  driver: p4-clockmod
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.00 ms.
  hardware limits: 333 MHz - 2.67 GHz
  available frequency steps: 333 MHz, 667 MHz, 1000 MHz, 1.33 GHz, 1.67 GHz, 2.00 GHz, 2.33 GHz, 2.67 GHz
  available cpufreq governors: ondemand, conservative, powersave, userspace, performance
  current policy: frequency should be within 667 MHz and 2.67 GHz.

Messages found:
 systemd[1]: Failed to start LSB: CPU frequency scaling daemon.
 systemd[1]: Unit cpufreqd.service entered failed state
 systemd[1]: cpufreqd.service never wrote its PID file. Failing.

Cpufreq was working with previous releases Mdv and Mga
Manuel Hiebel 2012-12-08 22:11:07 CET

CC: (none) => mageia, n54, sander.lepik
Source RPM: (none) => cpufreq

Comment 1 Colin Guthrie 2013-01-06 19:08:11 CET 
Seems the PIDfile header in the initscript is just wrong. This should have also been broken on mga2 as far as I can tell, but unless someone reports that explicitly I won't look!

cpufreqd itself is more or less useless these days anyway, so I'd generally recommend simply uninstalling it (it doesn't even work for me here - fails to load for other reasons).

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