1 |
Hi, |
2 |
Is there any documentation on how to use powermgr? |
3 |
|
4 |
On 7/27/05, Thomas Tuttle <tom@×××××××××××××××××××××××.org> wrote: |
5 |
> |
6 |
> Okay, the best way to do that would be to (using powermgr) create a |
7 |
> profile named "hot" and then write your script like so: |
8 |
> |
9 |
> #!/bin/pseudocode-interpreter |
10 |
> if (TEMP > $HOT) { |
11 |
> echo "System is actually hot, slowing everything down."; |
12 |
> powermgr --profile hot; |
13 |
> sleep 5; |
14 |
> if (TEMP > $HOT) { |
15 |
> echo "System is about to explode, shutting down."; |
16 |
> poweroff; |
17 |
> } else { |
18 |
> echo "System has cooled down, returning to normal." |
19 |
> powermgr --auto; |
20 |
> } |
21 |
> } else { |
22 |
> echo "System is just being foolish and is not hot."; |
23 |
> } |
24 |
> |
25 |
> The "hot" profile would probably look like this: |
26 |
> |
27 |
> Profile hot |
28 |
> cpu frequency = 0% |
29 |
> EndProfile |
30 |
> |
31 |
> That way it would slow down the CPU frequency without playing with other |
32 |
> stuff like brightness. |
33 |
> |
34 |
> On Wed, 2005-07-27 at 10:33 -0400, Devon Miller wrote: |
35 |
> > Thanks Thomas, I'll definitely check it out. One feature I would like |
36 |
> > to see is the ability to throttle the cpu to manage temperature. |
37 |
> > |
38 |
> > My laptop occasionally reports spurious high temperatures. Within 3 |
39 |
> > polls the temperature might be reported as 70C, 97C, 70C. When the |
40 |
> > kernel sees the 97C it powers off the system. |
41 |
> > |
42 |
> > I've hacked around this by patching the kernel to run /sbin/overheat |
43 |
> > instead of /sbin/poweroff. Overheat checks the temp again and if it's |
44 |
> > still hot, shuts down powernowd and sets the cpufreq to its minimum |
45 |
> > value It then sleeps for 5 seconds and if the temp is still 90C+, |
46 |
> > calls poweroff. |
47 |
> > |
48 |
> > The downside is the system is now left in a very slow state. I have |
49 |
> > not written something to bring it back to a dynamic clocking state. A |
50 |
> > daemon that would manage all of this would be really appreciated! (Of |
51 |
> > course, the kernel would still need to be patched to not poweroff |
52 |
> > until the daemon has had a chance to try cooling things down.) |
53 |
> > |
54 |
> > <dcm> |
55 |
> > |
56 |
> > |
57 |
> > On 7/13/05, Thomas Tuttle <tom@×××××××××××××××××××××××.org> wrote: |
58 |
> > I've been working on a program called powermgr. It's a daemon |
59 |
> > written |
60 |
> > in Perl that can control many power management functions on |
61 |
> > Linux, |
62 |
> > including CPU frequency and/or governor, screen brightness, |
63 |
> > laptop mode, |
64 |
> > fan speed, wireless power management, as well as runlevel and |
65 |
> > services, |
66 |
> > based on the state of the system. |
67 |
> > |
68 |
> |
69 |
> |
70 |
> -----BEGIN PGP SIGNATURE----- |
71 |
> Version: GnuPG v1.4.1-ecc0.1.6 (GNU/Linux) |
72 |
> |
73 |
> iD8DBQBC556Z/UG6u69REsYRAo8qAJ9w8ab8s183nvc3cN/AXh1tqeUt3wCfYSUT |
74 |
> fu3lk34QqS3XwoUdpQtK48U= |
75 |
> =/Lqt |
76 |
> -----END PGP SIGNATURE----- |
77 |
> |
78 |
> |
79 |
> |