lubuntu-desktop team mailing list archive

[Phillip Whiteside <phillw@xxxxxxxxxx>]

Hi Adam,

I've had a stab at putting the frequency scaling information together over
at http://forum.phillw.net/viewtopic.php?f=18&t=104 please let myself or Bob
know any alterations that need making. For a discussion with someone who has
a dual core, Bob can probably help the best as my laptop is the proud owner
of a single Intel Celeron M 440. He also has moderator priveleges on the
baby forum so any discussions you both have he can put on without needing me
;-) It is his thread :-D

Once they're settled and ready I can check with the development team and get
them onto the Wiki area. I'm sure you know that getting documentation
together does require that we do it, the team is very small.

Thanking you in advance for helping lubuntu,

Phill.

P.S. to everyone, if you have comments to add or if you have any "How To's"
please let me know, I'd be really happy to hear from you.

On Tue, Jun 22, 2010 at 6:53 PM, Adam Smith <asmith4726@xxxxxxxxx> wrote:

> Okay so you might notice that your nice dual core laptop is cooking your
> lap or overheating while it's sitting there doing nothing. CPU Scaling
> lowers both energy consumption and temperature. first....
>
> sudo aptitude install cpufreqd cpufrequtils
>
> then run cpufreq-info and find your ranges your cpu or cores can do like
> so:
>
>
> -------------------------------
> rabidweezle@RedQueen:~/sarai_conky$ cpufreq-info
> cpufrequtils 006: cpufreq-info (C) Dominik Brodowski 2004-2009
> Report errors and bugs to cpufreq@xxxxxxxxxxxxxxx, please.
> analyzing CPU 0:
>   driver: powernow-k8
>   CPUs which run at the same hardware frequency: 0
>   CPUs which need to have their frequency coordinated by software: 0
>   maximum transition latency: 1000 ns.
>   hardware limits: 1000 MHz - 2.00 GHz
>   available frequency steps: 2.00 GHz, 1000 MHz
>   available cpufreq governors: conservative, ondemand, userspace,
> powersave, performance
>   current policy: frequency should be within 1000 MHz and 2.00 GHz.
>                   The governor "ondemand" may decide which speed to use
>                   within this range.
>   current CPU frequency is 1000 MHz.
>   cpufreq stats: 2.00 GHz:39.87%, 1000 MHz:60.13%  (11821)
> analyzing CPU 1:
>   driver: powernow-k8
>   CPUs which run at the same hardware frequency: 1
>   CPUs which need to have their frequency coordinated by software: 1
>   maximum transition latency: 1000 ns.
>   hardware limits: 1000 MHz - 2.00 GHz <-- [** RANGE YOU CAN DO **]
>   available frequency steps: 2.00 GHz, 1000 MHz
>   available cpufreq governors: conservative, ondemand, userspace,
> powersave, performance
>   current policy: frequency should be within 1000 MHz and 2.00 GHz.
>                   The governor "ondemand" may decide which speed to use
>                   within this range.
>   current CPU frequency is 1000 MHz.
>   cpufreq stats: 2.00 GHz:39.46%, 1000 MHz:60.54%  (7643)
> -------------------------------
>
> Now on my CPU it looks like I can only go 50% down.
>
> Edit /etc/cpufreqd.conf (with sudo privs)
>
> here's mine... basically change the performance modes to be the proper
> range and set to ondemand so it instantly gives you full power only when you
> need it.
>
> -------------------------------------
>
> # this is a comment
> # see CPUFREQD.CONF(5) manpage for a complete reference
> #
> # Note: ondemand/conservative Profiles are disabled because
> #       they are not available on many platforms.
>
> [General]
> pidfile=/var/run/cpufreqd.pid
> poll_interval=2
> verbosity=4
> #enable_remote=1
> #remote_group=root
> [/General]
>
> #[acpi]
> #acpid_socket=/var/run/acpid.socket
> #[/acpi]
>
> #[nforce2_atxp1]
> #vcore_path=/some/path
> #vcore_default=1500
> #[/nforce2_atxp1]
>
> #[sensors_plugin]
> #sensors_conf=/some/file
> #[/sensors_plugin]
>
> #[Profile]
> #name=On Demand High
> #minfreq=40%
> #maxfreq=100%
> #policy=ondemand
> #[/Profile]
> #
> #[Profile]
> #name=On Demand Low
> #minfreq=20%
> #maxfreq=80%
> #policy=ondemand
> #[/Profile]
>
> [Profile]
> name=Performance High
> minfreq=50%
> maxfreq=100%
> policy=ondemand
> #exec_post=echo 8 > /proc/acpi/sony/brightness
> [/Profile]
>
> [Profile]
> name=Performance Low
> minfreq=50%
> maxfreq=100%
> policy=ondemand
> [/Profile]
>
> [Profile]
> name=Powersave High
> minfreq=60%
> maxfreq=60%
> policy=powersave
> [/Profile]
>
> [Profile]
> name=Powersave Low
> minfreq=40%
> maxfreq=40%
> policy=powersave
> [/Profile]
>
> #[Profile]
> #name=Conservative High
> #minfreq=33%
> #maxfreq=100%
> #policy=conservative
> #[/Profile]
> #
> #[Profile]
> #name=Conservative Low
> #minfreq=0%
> #maxfreq=66%
> #policy=conservative
> #[/Profile]
>
> ##
> # Basic states
> ##
> # when AC use performance mode
> [Rule]
> name=AC Rule
> ac=on                    # (on/off)
> profile=Performance High
> [/Rule]
>
> # stay in performance mode for the first minutes
> [Rule]
> name=AC Off - High Power
> ac=off                   # (on/off)
> battery_interval=70-100
> #exec_post=echo 5 > /proc/acpi/sony/brightness
> profile=Performance Low
> [/Rule]
>
> # conservative mode when not AC
> [Rule]
> name=AC Off - Medium Battery
> ac=off                   # (on/off)
> battery_interval=30-70
> #exec_post=echo 3 > /proc/acpi/sony/brightness
> profile=Powersave High
> [/Rule]
>
> # conservative mode when not AC
> [Rule]
> name=AC Off - Low Battery
> ac=off                   # (on/off)
> battery_interval=0-30
> #exec_post=echo 3 > /proc/acpi/sony/brightness
> profile=Powersave Low
> [/Rule]
>
> ##
> # Special Rules
> ##
> # CPU Too hot!
> [Rule]
> name=CPU Too Hot
> acpi_temperature=55-100
> cpu_interval=50-100
> profile=Performance Low
> [/Rule]
>
> # use performance mode if I'm watching a movie
> # I don't care for batteries!
> # But don't heat too much.
> [Rule]
> name=Movie Watcher
> programs=xine,mplayer,gmplayer
> battery_interval=0-100
> acpi_temperature=0-60
> cpu_interval=0-100
> profile=Performance High
> [/Rule]
>
> ----------------------------------------------
>
> then restart the daemon...
> sudo /etc/init.d/cpufreqd restart
>
> check to see if it worked with cpufreq-info and it should reflect your new
> settings
>