Bug 115731

Summary: Dynamic cpu frequency not working on laptop
Product: [Fedora] Fedora Reporter: Chris Thomas <cwt137>
Component: kernel-utilsAssignee: Arjan van de Ven <arjanv>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: athlon   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:01:17 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:
Attachments:
Description Flags
Device descriptions and log files none

Description Chris Thomas 2004-02-15 15:19:36 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040115

Description of problem:
I have fedora core 2 test 1.

I think that the dynamic cpu is not working because of this error
message i get at boot:

Error: Could not open file for writing:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

The /sys filesystem is mounted. ACPI also works because the cpu fan
changes speed and the batterie monitor works.

Cpuspeed doesnt start
Here are the specs on my compaq 2195us laptop:

Athlon XP 2500+ Mobile
part ALi, part ATI 320 IGP chipset
512MB DDR RAM
30GB HD
Intergrated 802.11g and regular NIC





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

How reproducible:
Always

Steps to Reproduce:
1. type in at the CLI: service cpuspeed start
2.
3.
    

Actual Results:  Error: Could not open file for writing:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

Expected Results:  [OK]

Additional info:

Comment 1 Chris Thomas 2004-02-15 15:33:27 UTC
Created attachment 97689 [details]
Device descriptions and log files

Comment 2 Chris Thomas 2004-02-15 16:20:16 UTC

*** This bug has been marked as a duplicate of 115720 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:01:17 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.