On Tuesday 25 April 2006 14:11, Mattia Dongili wrote:
> On Tue, Apr 25, 2006 at 12:34:29AM -0500, anoop aryal wrote:
> > On Monday 24 April 2006 13:03, Mattia Dongili wrote:
>
> [...]
>
> > summry:
> > the config file seems fine the way it is. i really don't see setting
> > individual CPU cores to different speeds/governors. in fact, it seems
> > that
>
> Fine, seems the best/easiest action, other more complex may be dealt
> with in specifically crafted scripts from sysadmins.
>
> [...]
>
> > i'm putting in the patch i had sent to you earlier with your suggested
> > changes for the RETVAL. i think that is exactly what i want. you might
> > want to tweak the detection of the different CPUs as you mentioned but it
> > also works the way it is - at least on my system.
>
> I'm attaching the script I have here, could you kindly test it (I
> suppose it is identical to yours)?
> I also have an "if" statement commented out that checks if the cpu is to
> be managed alone or together with a different one. Uncomment line 57 and
> 60 of the script if you want to try it.
>
> > btw, KDEs acpi stuff also only sets one core. and since the other
> > defaults to performance and since the Duo falls under category 2, the
> > result is not what i want - both cores running at the higher of the two
> > speeds. so i will be using cpufrequtils with the patch for Duo core.
>
> cpufreqd does set a policy on all available cpus ;)
aahh, but only with the attached patch ;)
you forgot the --cpu flag without which we are back at where we started.
but the rest works. thanks.
>
> Thanks again
--
anoop aryal
[EMAIL PROTECTED]
--- cpufrequtils.fix 2006-04-25 15:41:22.000000000 -0500
+++ cpufrequtils.init 2006-04-25 15:40:28.000000000 -0500
@@ -56,7 +56,7 @@
for cpu in $CPUS ; do
# if [ $(cpufreq-info -a --cpu $cpu) -eq $cpu ] ; then
log_progress_msg "CPU${cpu} "
- $PROGRAM $CPUFREQ_OPTIONS 2>&1 > /dev/null || RETVAL=$?
+ $PROGRAM --cpu $cpu $CPUFREQ_OPTIONS 2>&1 > /dev/null || RETVAL=$?
# fi
done
log_action_end_msg $RETVAL "$FAIL_MESG"
