QUOTE(CktRider @ Mar 27 2007, 04:42 PM)
QUOTE(daniel3000 @ Mar 27 2007, 03:55 AM)
please make sure that atd is running.
Yes, atd has been running, per ps. I restarted it and still have the problem.
I have a C1000 running the latest apm package, and I've eliminated the clock problems per other threads. I'm using your controllable clock, Daniel--thank you for that good work, as well as all the work for many years among the HPLX community.
so do I know you from the HPLX community?
This forum is quite different, as here people don't usually post using their real names. That helped to make the HPLX mailing list such a familiar and cordial place, knowing some more about the people you talked to.
Well, if atd is running, you may follow the single steps of the kopi-apm init script and try to find out if one of the steps is broken...
THe script is in /etc/apm/scripts.d and must be linked into the suspend directory, so it is really executed on suspend. It does some calculations, using KO/PI's "next alarm" file and makes sure a resume is triggered shortly before the alarm comes up.
(I tell this all from memory, I don't have the exact script and file names handy now).
Somewhere in that chain may be an error.
Maybe only a missing link to the script?