Xavier Vello wrote:
>> The power management plasmoid contained in plasma-widgets-workspace has the
>> ability to switch between supported CPU policies ("More..." ->
>> "Capabilities"). However, this requires that the relevant kernel modules
>> that implement these policies are loaded; otherwise no CPU policies are
>> available. Loading the relevant kernel modules is the job of the
>> cpufrequtils package. Hence, plasma-widgets-workspace should recommend the
>> cpufrequtils package to the user when being installed.
>
> Hello
>
> First, the recommend should be put on the kdebase-workspace-bin package, as
> the component responsible for power management is powerdevil (in kdebase-
> workspace) and not plasma (which is just an interface to the daemon).
>
> I agree that /etc/init.d/loadcpufreq is in the cpufrequtils package and is
> the
> easier way to ensure the governor modules are loaded, although powerdevil
> doesn't use /usr/bin/cpufreq*Is kdebase-workspace-bin accessing this interface directly via /sys or does it use hal (via Solid) for that? If the latter, it would probably be better if hal declared such a dependency. FWIW, hal currently recommends pm-utils which in turn suggests cpufrequtils. Another option could be, to compile the cpufreq* modules statically into the Debian kernel. I would argue that all x86 cpus sold today have power management capability so enabling them by default might be a good idea (unless there a regressions in certain areas). Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
