/etc/default/cpupower configuration file was deleted after this stable update.
I don’t know for what reason
After rename /etc/default/cpupower.pacsave in /etc/default/cpupower lead also to instant system freezes after a system boot.
Anyone has a idea how i can run process govervor in performance mode again?
I want a stable all cores at 4500Mhz ergo 4.50Ghz
cpupower.pacsave (which i believe has stored the old settings which i used for 5 year’s now
but no longer working now, when i change the filename):
# Define CPUs governor
# valid governors: ondemand, performance, powersave, conservative, userspace.
governor='performance'
# Limit frequency range
# Valid suffixes: Hz, kHz (default), MHz, GHz, THz
min_freq="4.50GHz"
max_freq="4.50GHz"
# Specific frequency to be set.
# Requires userspace governor to be available.
# Do not set governor field if you use this one.
#freq=
# Utilizes cores in one processor package/socket first before processes are
# scheduled to other processor packages/sockets.
# See man (1) CPUPOWER-SET for additional details.
#mc_scheduler=
# Utilizes thread siblings of one processor core first before processes are
# scheduled to other cores. See man (1) CPUPOWER-SET for additional details.
#smp_scheduler=
# Sets a register on supported Intel processore which allows software to convey
# its policy for the relative importance of performance versus energy savings to
# the processor. See man (1) CPUPOWER-SET for additional details.
#perf_bias=
# vim:set ts=2 sw=2 ft=sh et:
Maybe that feature is unsupported right now, because Intel stopped support for Linux?
It looks that arch wiki isn’t updated to the recent changes.
Upstream included files based on those from this repo.
Which now causes some duplicated and useless files (double conf file, script in /usr/libexec/ which is unused and the wrong location).
This commit switches to the files supplied by upstream but adjusts the install locations to mostly keep the old structure. Only mostly, because the config file got renamed.
/etc/default/cpupower-service.conf:
# Configuration file for cpupower.service systemd service unit
#
# Edit this file (uncommenting at least one of the options, depending on
# your preferences) and then enable cpupower.service, if you want cpupower
# to run at boot with these settings.
# --- CPU clock frequency ---
# Define CPU governor
# Valid governors: ondemand, performance, powersave, conservative, userspace
#GOVERNOR='ondemand'
Edit configuration file with root privileges:
sudo nano +15 /etc/default/cpupower-service.conf
Change #GOVERNOR='ondemand' to GOVERNOR='performance'
and use Cttl + S to save changes and Ctrl + X to exit nano
Im wondering why did the maintainer change the name from this package,
now i have to deal with this problems.
BG405 recommend in my old topic (which is unlisted right now) a reinstall from the package.
I need to go afk for a while, but later i reboot my system and give it a try.
Because i’m out of ideas, hopefully this maintainer not destroyed his own package
Make a backup copy of the configuration files first, and then delete the original ones before reinstalling the package. That way, you’ll get the defaults from upstream, and then you can compare the settings in both.
Yes, but my point is that the files that are there now might prevent the new default configuration files from being written out when the package gets reinstalled. So by removing them, it’ll install a fresh default configuration again, which you can then tweak.
Edit: After reinstalling cpupower, don’t forget to make sure it’s enabled…
If you prefer to run CPU at a fixed frequency instead of using a governor to scale CPU frequencies, I would suggest changing Line 25: #FREQ= to FREQ="4.50GHz
I can only confirm that deamon-reload is enough for my old desktop system.
If more is needed for other systems, reboot and enable the service as already suggested:
Or use the “old-school” command instead of the systemd service;
sudo cpupower -c all frequency-set -g performance
Or install cpupower-gui from AUR
As far as I can recall, the cpupower.service was created a few years ago by Arch, but was not available on other distributions until this upstream commit last year:
One of the most typical use cases of the ‘cpupower’ utility works as
follows: run ‘cpupower’ at boot with the desired command-line options
and then forget about it.
Add a systemd service (disabled by default) that automates this use
case (for environments where the initialization system is ‘systemd’),
by running ‘cpupower’ at boot with the settings read from a default
configuration file.
The systemd service, the associated support script and the
corresponding default configuration file are derived from what is
provided by the Arch Linux package (under “GPL-2.0-or-later” terms),
modernized and enhanced in various ways (the script has also been
checked with ‘shellcheck’).
