Re: Is there any valid reason to add an idiotic script to /etc/init.d by an default Debian install that only cause a PITA?

[Camaleón <noelamac@gmail.com>]

On Tue, 14 Jun 2011 19:24:22 +0200, Ralf Mardorf wrote:

> On Tue, 2011-06-14 at 17:00 +0000, Camaleón wrote:
>> sm01@stt008:~$ grep -i "CONFIG_CPU_FREQ_DEFAULT_GOV"
>> /boot/config-2.6.26-2-amd64 CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y #
>> CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set #
>> CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set #
>> CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set #
>> CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
>> 
>> Ha! :-P
> 
> Too funny!
> 
> Regarding to this I can't resist to reply again.
> 
> Bizarre that my kernel is set to ondemand and yours to performance :D!
> It should be vv ;).

The nice about that is that both of us can get our desired setting! :-)
 
> But just because I made a mistake when building my kernel and just
> because the Debian's kernel default has got the wrong default too, the
> script isn't good.

The script is indeed very much needed:

sm01@stt008:~$ cpufreq-info | grep governor
  available cpufreq governors: powersave, userspace, ondemand, conservative, performance
                  The governor "ondemand" may decide which speed to use
(...)

sm01@stt008:~$ cpufreq-info | grep current
  current policy: frequency should be within 2.00 GHz and 2.83 GHz.
  current CPU frequency is 2.00 GHz.
(...) 

Thanks to it (to the script) my CPU is not wasting resources nor energy 
blindingly:

sm01@stt008:~$ cpufreq-info | grep stats
  cpufreq stats: 2.83 GHz:1,55%, 2.67 GHz:0,02%, 2.33 GHz:0,04%, 2.00 GHz:98,40%  (6327)
  cpufreq stats: 2.83 GHz:1,83%, 2.67 GHz:0,03%, 2.33 GHz:0,05%, 2.00 GHz:98,10%  (6833)
  cpufreq stats: 2.83 GHz:1,66%, 2.67 GHz:0,02%, 2.33 GHz:0,05%, 2.00 GHz:98,26%  (6102)
  cpufreq stats: 2.83 GHz:1,51%, 2.67 GHz:0,02%, 2.33 GHz:0,03%, 2.00 GHz:98,44%  (5240)

Greetings,

-- 
Camaleón