On Thu, Sep 28, 2017 at 11:31:37AM -0400, Phil Susi wrote:
> On 9/28/2017 9:51 AM, Mattia Dongili wrote:
> > On Wed, Sep 27, 2017 at 03:16:52PM -0400, Phil Susi wrote:
> >> Package: cpufrequtils
> >> Version: 008-1
> > ...
> >> is the case, should cpufrequtils not be removed now?
> >
> > Yes, indeed it should. Thanks for nagging.
> > There's a little more work required to smooth the transition.
> >
> > $ apt-cache rdepends cpufrequtils
> > cpufrequtils
> > Reverse Depends:
> > cpufreqd
> > powertop
> > pm-utils
> > mate-applets
> > parl-desktop-strict
>
> Are the tools from the kernel package a drop in replacement so will
> satisfy these depends? If so then maybe we just need a Replaces: or
> Provides: added to the kernel package?
Functionality wise, yes, cpupower provides what cpufrequtils used to.
The binaries have different names.
E.g.:
$ cpufreq-info -c 0
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpuf...@vger.kernel.org, please.
analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 0.97 ms.
hardware limits: 800 MHz - 3.00 GHz
available cpufreq governors: performance, powersave
current policy: frequency should be within 800 MHz and 3.00 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency is 1.41 GHz.
$ cpupower -c 0 frequency-info
analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: Cannot determine or is not supported.
hardware limits: 800 MHz - 3.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 3.00 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 1.42 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
I notice some differences in the output too (transition latency and an error
about frequency).
--
mattia
:wq!
