[Bug 832179] Power management guide is wrong for frequency scaling in Fedora 17

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=832179

--- Comment #6 from Jack Reed <jreed at redhat.com> ---
(In reply to comment #4)

> Yes, please delete the first step (about modprobe).

Sure, done. I've removed Procedure 3.1 as per Comment 2 and the first step from
Procedure 3.2. This has effectively stripped that section down to the two
commands and...

> > 
> Great, I hardly follow all the changes :). But your substitution command is
> not correct.
> "cpupower frequency-info --governors" will show all available governors, but
> enable the specific governor by:
> "cpupower frequency-set --governor GOVERNOR" or simply by "cpupower
> frequency-set -g GOVERNOR". This will change governer on all cores (CPUs).
> You can also modify governor on specific core only (if supported by HW) by
> using the -c switch. 

... this: I've also added an example command to explain the -c switch.

And oops - that was a typo with frequency-info. I had distinguished them
properly in the XML but not here in Comment 3.

> 
> > The command "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor" that
> > you've asked to be retained has also been replaced, by "cpupower
> > frequency-info --policy". 
> > 
> OK, no problem, just be consistent.
> 
> > I just want to be sure that this is acceptable and you don't actually want
> > the existing cat and echo commands to be retained despite the emphasis on
> > cpupower.
> > 
> The admon box from RHEL guide that very briefly noted that there are also
> the sysfs "echo/cat" alternatives is enough.

Great, OK. All is well then. Thanks Jaroslav.

The commits can be viewed here:

For the removal of the procedures -
http://git.fedorahosted.org/cgit/docs/power-management-guide.git/commit/?id=93244bc92f60a57a2037c53e4282804169666ea2

For the addition of -c -
http://git.fedorahosted.org/cgit/docs/power-management-guide.git/commit/?id=c9a4d7118603c8fde5012555117a1c2d0a8670be

-- 
You are receiving this mail because:
You are the QA Contact for the bug.