| 1 |
2008/2/6, ionut cucu <cuciferus@×××××.com>: |
| 2 |
> |
| 3 |
> On Mon, 4 Feb 2008 15:52:18 +0000 |
| 4 |
> Beso <givemesugarr@×××××.com> wrote: |
| 5 |
> |
| 6 |
> > right now i'm studying some scripts to adapt them to your hw. i'll |
| 7 |
> > let you know when i finish them and i'll post them for you to test. |
| 8 |
> |
| 9 |
> Wouldn't you rather give me a few hints first on how to get my |
| 10 |
> trip_points set first? Afterwards I can also test the scripts. You can |
| 11 |
> understand my impacience here. |
| 12 |
|
| 13 |
|
| 14 |
|
| 15 |
the trip_points cannot be set manually, since the trip_points file is |
| 16 |
readonly |
| 17 |
for the moment my problem is that i cannot make the script to read the acpi |
| 18 |
temperature. |
| 19 |
for now i'd suggest for you to add some sensor monitor, like kima for kde, |
| 20 |
or some others and use them to identify the acpi temperature. when your |
| 21 |
thermal reaches 80° you'd have to set the cpufreq to powersave so that the |
| 22 |
processor goes to the lowest freq and the thermal |
| 23 |
temperature goes down. the console command to do this is: |
| 24 |
cpufreq-set -g powersave |
| 25 |
when the temperature goes around 60°-62° you can reset the conservative |
| 26 |
governor so that you will have the processor go faster when you need it. |
| 27 |
cpufreq-set -g conservative. |
| 28 |
|
| 29 |
as soon as i finish the scripts to automatically adjust the processor based |
| 30 |
on thermal readings i'll post them to you. |
| 31 |
|
| 32 |
-- |
| 33 |
dott. ing. beso |
Archives