Bug 316353 – powernowd reports "cpu0/cpufreq/affected_cpus: No such file or directory"

• Status: RESOLVED WORKSFORME
• Product: Gentoo Linux

[Description Peter Sliepenbeek 2010-04-20 13:18:42 UTC]

# /etc/init.d/powernowd start
 * Starting powernowd ...
cpu0/cpufreq/affected_cpus: No such file or directory                     [ ok ]

Reproducible: Always

Steps to Reproduce:
1. /etc/init.d/powernowd stop
2. /etc/init.d/powernowd start

Actual Results:  
# /etc/init.d/powernowd stop
 * Stopping powernowd ...                                                 [ ok ]
# /etc/init.d/powernowd start
 * Starting powernowd ...
cpu0/cpufreq/affected_cpus: No such file or directory                     [ ok ]

Expected Results:  
# /etc/init.d/powernowd stop
 * Stopping powernowd ...                                                 [ ok ]
# /etc/init.d/powernowd start
 * Starting powernowd ...                                                 [ ok ]

[Comment 1 jnbagui 2010-05-15 22:52:07 UTC]

To run the command, you should be in the directory 
/sys/devices/system/cpu

[Comment 2 jnbagui 2010-05-15 22:53:33 UTC]

To run the command, you must be in the directory
/sys/devices/system/cpu

[Comment 3 Jeroen Roovers (RETIRED) 2011-05-31 00:06:16 UTC]

I bet you didn't have the correct kernel configuration back then. We need more info if this bug report is to be reopened.