Thanks to Blackcrack's tip about systemctl I ran it a find that
cpupower.service is failed. I don't know if it is supposed to be working?
# systemctl status cpupower.service
cpupower.service - Configure CPU power related settings
Loaded: loaded (/lib/systemd/system/cpupower.service; enabled)
Active: failed (Result: exit-code) since Sun 2015-06-07 10:16:51
CDT; 13min ago
Process: 3642 ExecStart=/usr/bin/cpupower $CPUPOWER_START_OPTS
(code=exited, status=237)
Main PID: 3642 (code=exited, status=237)
CGroup: /system.slice/cpupower.service
Jun 07 10:16:51 localhost.localdomain cpupower[3642]: Error setting new
values. Common errors:
Jun 07 10:16:51 localhost.localdomain cpupower[3642]: - Do you have
proper administration rights? (super-user?)
Jun 07 10:16:51 localhost.localdomain cpupower[3642]: - Is the governor
you requested available and modprobed?
Jun 07 10:16:51 localhost.localdomain cpupower[3642]: - Trying to set an
invalid policy?
Jun 07 10:16:51 localhost.localdomain cpupower[3642]: - Trying to set a
specific frequency, but userspace governor is not available,
Jun 07 10:16:51 localhost.localdomain cpupower[3642]: for example
because of hardware which cannot be set to a specific frequency
Jun 07 10:16:51 localhost.localdomain cpupower[3642]: or because the
userspace governor isn't loaded?
Jun 07 10:16:51 localhost.localdomain systemd[1]: cpupower.service: main
process exited, code=exited, status=237/n/a
Jun 07 10:16:51 localhost.localdomain systemd[1]: Failed to start
Configure CPU power related settings.
Jun 07 10:16:51 localhost.localdomain systemd[1]: Unit cpupower.service
entered failed state.
[root@localhost ~]# systemctl start cpupower.service
Job for cpupower.service failed. See 'systemctl status cpupower.service'
and 'journalctl -xn' for details.
journalctl -xn seems to repeat same errors:
# journalctl -xn
-- Logs begin at Sat 2015-04-18 20:42:23 CDT, end at Sun 2015-06-07
10:31:57 CDT. --
Jun 07 10:31:57 localhost.localdomain cpupower[5600]: Error setting new
values. Common errors:
Jun 07 10:31:57 localhost.localdomain cpupower[5600]: - Do you have
proper administration rights? (super-user?)
Jun 07 10:31:57 localhost.localdomain cpupower[5600]: - Is the governor
you requested available and modprobed?
Jun 07 10:31:57 localhost.localdomain cpupower[5600]: - Trying to set an
invalid policy?
Jun 07 10:31:57 localhost.localdomain cpupower[5600]: - Trying to set a
specific frequency, but userspace governor is not available,
Jun 07 10:31:57 localhost.localdomain cpupower[5600]: for example
because of hardware which cannot be set to a specific frequency
Jun 07 10:31:57 localhost.localdomain cpupower[5600]: or because the
userspace governor isn't loaded?
Jun 07 10:31:57 localhost.localdomain systemd[1]: cpupower.service: main
process exited, code=exited, status=237/n/a
Jun 07 10:31:57 localhost.localdomain systemd[1]: Failed to start
Configure CPU power related settings.
Jun 07 10:31:57 localhost.localdomain systemd[1]: Unit cpupower.service
entered failed state.
Any ideas or illumination?
From ArchWiki:
cpupower
cpupower <https://www.archlinux.org/packages/?name=cpupower> is a set of
userspace utilities designed to assist with CPU frequency scaling. The
package is not required to use scaling, but is highly recommended
because it provides useful command-line utilities and a systemd
<https://wiki.archlinux.org/index.php/Systemd> service to change the
governor at boot.
The configuration file for /cpupower/ is located in
|/etc/default/cpupower|. This configuration file is read by a bash
script in |/usr/lib/systemd/scripts/cpupower| which is activated by
/systemd/ with |cpupower.service|. You may want to enable
|cpupower.service| to start at boot.
No files '|/etc/default/cpupower' or
'||/usr/lib/systemd/scripts/cpupower'. Maybe they'd be in a different
location in OpenMandriva?|
||
--
Ben Bullard
ben79
--------------------
OpenMandriva-QA Team
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
