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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to