Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nixos/cpufreq: Remove the alias to set the cpu frequency governor #53301

merged 1 commit into from
Jan 3, 2019


Copy link

This PR temporarily fixes the issue with PR 53041 as explained here:

#53041 (comment)

The alias powerManagement.cpufreq.governor to powerManagement.cpuFreqGovernor has been removed.

Motivation for this change

This fixes a bad interaction between the TLP module and powerManagement.cpuFreqGovernor which has been set in nixos-generate-config.

Pinging @infinisil because of his suggestion to revert this change, as well as @eadwu since he originally reported the error.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits

This PR temporarily fixes the issue with PR 53041 as explained

NixOS#53041 (comment)

The alias `powerManagement.cpufreq.governor` to
`powerManagement.cpuFreqGovernor` has been removed.
Copy link

Why there is still a TODO says This should be aliased to powerManagement.cpufreq.governor. in the code if the alias is not a good idea? Maybe we should delete the TODO?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

Successfully merging this pull request may close these issues.

None yet

4 participants