Bug 114166 - cpuspeed fails to start without modprobing additional modules
Summary: cpuspeed fails to start without modprobing additional modules
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel-utils
Version: rawhide
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-01-23 15:43 UTC by Joe Ammond
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-02-07 17:28:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Patch to /etc/init.d/cpuspeed (391 bytes, patch)
2004-01-23 15:44 UTC, Joe Ammond
no flags Details | Diff

Description Joe Ammond 2004-01-23 15:43:32 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5)
Gecko/20031007 Firebird/0.7

Description of problem:
Hardware: Dell Latitide D600
Kernel: kernel-2.6.1-1.53

On my Dell Latitude D600 laptop, cpuspeed fails to start even
with the speedstep-centrino module in the DRIVER= line in
/etc/cpuspeed.conf.  The cpufreq_userspace module needs to
be loaded as well for cpuspeed to function.  As a work-around,
I modified /etc/init.d/cpuspeed to treat the DRIVER= line
from cpuspeed.conf as a list of modules, and modprobe each
accordingly.  Another work-around is to modprobe cpufreq_userspace
first, then re-run /etc/init.d/cpuspeed manually.

Version-Release number of selected component (if applicable):
kernel-utils-2.4-9.1.115

How reproducible:
Always

Steps to Reproduce:
1. Power on the machine, cpuspeed fails to start due because
cpufreq_userpsace isn't present.


Additional info:

Comment 1 Joe Ammond 2004-01-23 15:44:41 UTC
Created attachment 97211 [details]
Patch to /etc/init.d/cpuspeed

Comment 2 Michael McCabe 2004-02-06 13:03:47 UTC
I've got the same problem right now.

Comment 3 Joe Ammond 2004-02-06 23:06:18 UTC
From rpm -q --changelog kernel :

* Tue Jan 27 2004 Dave Jones <davej>

- Update to 2.6.2-rc2-bk1
- Set default CPUFREQ governor to userspace instead of performance.

This eliminates the problem I had with cpuspeed starting.  Given
that, I'd consider this closed.



Note You need to log in before you can comment on or make changes to this bug.