[opensuse] 10.3 and powermanagement
I am sure it is something very obvious, yet I can't seem to find a way to configure the powermanagement in openSUSE 10.3. YaST is missing the power-management module and in KPowersave all options are 'greyed out'. Any pointers? -- Gruß Andreas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 28 October 2007 19:55, Andreas wrote:
I am sure it is something very obvious, yet I can't seem to find a way to configure the powermanagement in openSUSE 10.3. YaST is missing the power-management module and in KPowersave all options are 'greyed out'.
Any pointers?
What hardware are you using? How have you configured your BIOS options? Here's just one tiny example of how sensitive the power management features are to the hardware configuration: I have Core 2 Duo E6700 (nominal 2.66 GHz using a 266 x10 clock) installed in an ASUS P5B Deluxe. If you enable CPU clock multiplier control, the Intel Enhanced SpeedStep (EIST) option goes away and KPowersave cannot give you control over the "CPU Frequence Policy." If you don't enable C1E ("enhanced stop state") other power management capabilities are unavailable. And this is just for this CPU family. "It's all very complicated."
-- Gruß Andreas
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Sonntag, 28. Oktober 2007 20:14:18 schrieb Randall R Schulz:
"It's all very complicated."
After some more digging I found that the powermanagement is now done by hal, and not only does hal reject a regular user, but stand-by and suspend-to-disk do not work anymore on my computer. I am getting really annoyed by this hal crap :( -- Gruß Andreas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
See the thread "Suspend to swap replacement on 10.3 for Thinkpad T41".
Powermanagement is now down by the pm utilities. pm-hibernate does suspend to
disk and pm-suspend does suspend to RAM fine on my Thinkpad T41.
HTH,
Jeffrey
Quoting Andreas
Am Sonntag, 28. Oktober 2007 20:14:18 schrieb Randall R Schulz:
"It's all very complicated."
After some more digging I found that the powermanagement is now done by hal, and not only does hal reject a regular user, but stand-by and suspend-to-disk do not work anymore on my computer.
I am getting really annoyed by this hal crap :(
-- Gruß Andreas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Quoting Jeffrey L. Taylor
See the thread "Suspend to swap replacement on 10.3 for Thinkpad T41". Powermanagement is now down by the pm utilities. pm-hibernate does suspend to
Oops, Powermanagement is now DONE by the pm utilities. Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jeffrey L. Taylor wrote:
... Oops, Powermanagement is now DONE by the pm utilities.
This brings up a problem (my first in 10.3) that I'm having. In 10.1 and 10.2, KPowersave Just Worked on my hp dv6000 laptop. I installed 10.3 Saturday, and after an idle period, it suspended to disk just fine, as far as I can tell. Since then, it has not shut down at all. Until yesterday, it at least locked the screen after the usual time of idleness, or when I closed the lid. Today, it stopped doing even that. I opened the lid after several hours, and there was my session ready to go where I had left off. Thinking I'd messed up the KPowersave configuration somehow, I opened it to reconfigure it. _Everything_ is now grayed out. I can't do anything. Recalling the recent comment that 10.3 uses PM, I started reading up to try fixing things. In summary, /etc/pm/config.d, sleep,d, and power.d are all empty. I can't find any documentation to tell me what to put into them. There's a lot of text about bash scripts, being careful not to touch /usr/lib/pm, etc. Nothing about what to put into /etc/pm/*. http://en.opensuse.org/S2ram doesn't help at any level I can understand; in fact, running the advised s2ram --test says my machine is not supported. en.opensuse.org/Projects_KPowersave is even less help. I looked at /var/log/pm-suspend.log, and all I can confidently understand is that it went to hibernation at 15:07 Saturday, which more or less matches my recollection. The list of steps it executed seemed to be in the correct order as far as I can see. This seems to me to imply that it had instruction from somewhere, but I can't find any that I can understand, unless it's the defaults in /usr/lib/pm (which I don't really understand). I really would like to get my laptop's powersave working correctly again. I have to go on a long trip at the end of November, and I don't want my battery life shortened between stops at a power source. Help? John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Mittwoch 31 Oktober 2007 04:42:34 schrieb John E. Perry:
Thinking I'd messed up the KPowersave configuration somehow, I opened it to reconfigure it. _Everything_ is now grayed out. I can't do anything. Recalling the recent comment that 10.3 uses PM, I started reading up to try fixing things.
Well, the pm-utils are only used to go into (and later restore from) powersaving mode (s2ram or s2disk), but not for activating them. If you are using kpowersave, it will further use hal which will forward the request via triggering pm-utils.
In summary, /etc/pm/config.d, sleep,d, and power.d are all empty. I can't find any documentation to tell me what to put into them. There's a lot of text about bash scripts, being careful not to touch /usr/lib/pm, etc. Nothing about what to put into /etc/pm/*.
Have you had a look at http://en.opensuse.org/Pm-utils ? (in regards of pm-utils this is the documentation you probably were looking for)
http://en.opensuse.org/S2ram doesn't help at any level I can understand; in fact, running the advised s2ram --test says my machine is not supported. en.opensuse.org/Projects_KPowersave is even less help.
As long as you only want to use suspend to disk this is fine, you don't need s2ram-support to be able to use suspend to disk.
I looked at /var/log/pm-suspend.log, and all I can confidently understand is that it went to hibernation at 15:07 Saturday, which more or less matches my recollection. The list of steps it executed seemed to be in the correct order as far as I can see. This seems to me to imply that it had instruction from somewhere, but I can't find any that I can understand, unless it's the defaults in /usr/lib/pm (which I don't really understand).
Those instructions and setting will only tell what to do on s2disk, but not when to activate it.
I really would like to get my laptop's powersave working correctly again. I have to go on a long trip at the end of November, and I don't want my battery life shortened between stops at a power source.
Help?
I am not quite sure i understand your problem regarding the suspend triggering. First i thought you were having the problem that nothing is triggered at all, but now i have the impression that you try to say you had a suspend to disk without any obvious reasons. But regarding the all-greyed-out kpowersave i would guess there is a problem with the services it depends on (dbus, hal, policykit). Have you tried restarting those? Frank -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Frank Seidel wrote:
Am Mittwoch 31 Oktober 2007 04:42:34 schrieb John E. Perry:
Thinking I'd messed up the KPowersave configuration somehow, I opened it to reconfigure it. _Everything_ is now grayed out. ... In summary, /etc/pm/config.d, sleep,d, and power.d are all empty. I can't find any documentation to tell me what to put into them. There's a lot of text about bash scripts, being careful not to touch /usr/lib/pm, etc. Nothing about what to put into /etc/pm/*.
Have you had a look at http://en.opensuse.org/Pm-utils ? (in regards of pm-utils this is the documentation you probably were looking for)
Well, yes, I read it before I posted before. Just now, I read it again. I see nothing there about _what_ to put there -- just how to do it.
http://en.opensuse.org/S2ram doesn't help at any level I can understand; in fact, running the advised s2ram --test says my machine is not supported. en.opensuse.org/Projects_KPowersave is even less help.
As long as you only want to use suspend to disk this is fine, you don't need s2ram-support to be able to use suspend to disk.
OK, I misunderstood the references to s2ram, then.
... This seems to me to imply that it had instruction from somewhere, but I can't find any that I can understand, unless it's the defaults in /usr/lib/pm (which I don't really understand).
Those instructions and setting will only tell what to do on s2disk, but not when to activate it.
So I understood that correctly, at least. But where do I determine how to trigger these scripts? (solved? later)
I am not quite sure i understand your problem regarding the suspend triggering. First i thought you were having the problem that nothing is triggered at all,
Exactly, at first (except for Saturday afternoon). but now i have the impression that you try to say
you had a suspend to disk without any obvious reasons.
Well, no; it triggered Saturday afternoon when I left the computer idle for several hours, as it should have. After that, nothing I could do would trigger a suspend.
But regarding the all-greyed-out kpowersave i would guess there is a problem with the services it depends on (dbus, hal, policykit). Have you tried restarting those?
OK, I knew nothing about those, except as vague references in the documents. However, based on your comment, when I had to shut down the computer to go to a client site, I used the K menu to shut down completely. When I brought it back up, everything seemed to be in order. I guess one or more of dbus, etc. got hung up somehow. All seems to be working well now. Thanks, Frank. This seems to have solved my problem. ...well, one thing has nagged me since I put 10.1 on this thing last year, but it's never been enough of an issue to prod me into asking about it. The battery indication is completely nonsensical. If I calibrate the battery under XP, it performs as advertised, and all the indications are more or less accurate. Under all versions of suse, the battery monitor says things like "99% charged, 15:35 hours to completion" at one extreme, or "3.4% charged, 27:14 hours remaining". Is this a matter of hp (on my dv6000) not providing enough or correct information to the linux facilities, or is there something I can do to get more reasonable indications? Actually, it just occurred to me to ask on hp's support forum. I'd still like to hear from you, though. jp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John E. Perry wrote:
Thanks, Frank. This seems to have solved my problem.
...well, one thing has nagged me since I put 10.1 on this thing last year, but it's never been enough of an issue to prod me into asking about it. The battery indication is completely nonsensical. If I calibrate the battery under XP, it performs as advertised, and all the indications are more or less accurate. Under all versions of suse, the battery monitor says things like "99% charged, 15:35 hours to completion" at one extreme, or "3.4% charged, 27:14 hours remaining". Is this a matter of hp (on my dv6000) not providing enough or correct information to the linux facilities, or is there something I can do to get more reasonable indications?
Actually, it just occurred to me to ask on hp's support forum. I'd still like to hear from you, though.
What did HP say? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Aaron Kulkis wrote:
John E. Perry wrote:
Thanks, Frank. This seems to have solved my problem.
...well, one thing has nagged me since I put 10.1 on this thing last year, but it's never been enough of an issue to prod me into asking about it. The battery indication is completely nonsensical. ...
Actually, it just occurred to me to ask on hp's support forum. I'd still like to hear from you, though.
What did HP say?
Sorry, I've been on a trip for the last two months, and my ISP doesn't allow me access to smtp from outside the Cox network. Webmail sucks too bad for me to deal with it unless I absolutely have to. HP told me to wipe my suse partition and restore the thing to the original XP configuration, then they'd think about helping me. While I was gone, other problems cropped up, so now I guess I have to do it so I can find out whether I need to send the thing back for repair. At least they're talking about extending the warranty period for my series of machines. I never heard any more from Frank. John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John E. Perry wrote:
Aaron Kulkis wrote:
John E. Perry wrote:
Thanks, Frank. This seems to have solved my problem.
...well, one thing has nagged me since I put 10.1 on this thing last year, but it's never been enough of an issue to prod me into asking about it. The battery indication is completely nonsensical. ...
Actually, it just occurred to me to ask on hp's support forum. I'd still like to hear from you, though.
What did HP say?
Sorry, I've been on a trip for the last two months, and my ISP doesn't allow me access to smtp from outside the Cox network. Webmail sucks too bad for me to deal with it unless I absolutely have to.
HP told me to wipe my suse partition and restore the thing to the original XP configuration, then they'd think about helping me.
While I was gone, other problems cropped up, so now I guess I have to do it so I can find out whether I need to send the thing back for repair. At least they're talking about extending the warranty period for my series of machines.
Have you asked them when they're going to give real support for basic linux functionality (not any distro in particular...just the software which the distributers collect to make a distribution, such as, in this case, releasing information to the battery-monitoring software teams so that the battery monitor software actually gives at least reasonably approximate battery-life indications)? It's not like HP is completely unfamiliar with Unix in general, or even Linux in particular. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Aaron Kulkis -
Andreas -
Frank Seidel -
Jeffrey L. Taylor -
John E. Perry -
Randall R Schulz