Bug 215228

Summary: cpuspeed configuration file unhelpful
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: cpuspeedAssignee: Jarod Wilson <jarod>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-01-08 15:56:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michal Jaegermann 2006-11-12 16:41:09 UTC
Description of problem:

First of all one would expect, following a general schema,
/etc/sysconfig/cpuspeed for that configuration file and not
/etc/cpuspeed.conf as it is now.

The second issue is that, AFAICS at least with i686 kernel,
currently there are two "cpu/cpufreq" modules.  Namely
acpi-cpufreq.ko and p4-clockmod.ko.  The first is used,
if only possible, by /etc/init.d/cpuspeed if no other driver module
is specified; which really leaves p4-clockmod.  A default
/etc/cpuspeed.conf says:

# uncomment this and set to the name of your CPUFreq module
#DRIVER="powernow-k7"

Why not "p4-clockmod" at least?

'VMAJOR=1' and 'VMINOR=1' also do not seem to serve any useful
purpose.

Some documentation would also be nice.  'cpuspeed --help' printed
on stderr, so sending that to 'less' is not straightforward, is not
overly convenient.

Version-Release number of selected component (if applicable):
cpuspeed-1.2.1-1.40.fc6

Comment 1 Jarod Wilson 2007-01-08 15:56:15 UTC
The latest rawhide cpuspeed build (1.48.fc7) carries what I think is a far more
useful config file. Adding further documentation will be tracked under bug
172655, closing this one out. Once we've had the rawhide build stabilized for a
little while, I'll push it for fc6 as well.