Hello

I have a Dell Inspiron 1100 laptop and I run FC2 on
it.
The suspend-to-ram feature never used to work and i
was told (on Dell forums) this is due to some problem
with the BIOS on this particular machine.

However when I recently updated the kernel on this
machine (using yum) to 2.6.10-1.9_FC2 suddenly (to my
delight) the suspend-to-ram feature has started
working. What I mean by that is, when I close the lid,
X shuts down, the network shutsdown and the machine
enters a power-save mode and when I open the lid,
everything is restored back to the state it was. The
only problem is, when everything is restored back, I
find that the clock has been messed up and it now
shows a time which is couple of hours _ahead_ of what
it should be. I don't understand why this happens.
When ever this happens, I restart ntpd and that sets
the time back to the correct time.

My question is this: is there a way to prevent this
from happening. Even if I cannot prevent this from
happening, is there a way I can have the machine
automatically restart ntpd when its restoring the
network and other settings when its waking up.
I don't even know what script the suspend-to-ram
functions runs when the machine wakes up.

Any help given will be appreciated.
Thanks!

"The only problem is, when everything is restored back, I
find that the clock has been messed up and it now
shows a time which is couple of hours _ahead_ of what
it should be. "

By any chance is the time being reset to Greenwich time?

-------------------------
Steve Stites

Thats a good suggestion.. however, the amount of time discrepancy seems to depend on how long the machine was in the sleep state.

Any other thoughts?
regards

I have a similar problem when I do suspend to disk on my sony vaio s260 -- the time stays where it was when it suspended.

My friend with the same laptop encounteres the same problem as I do.

--Shade

I can understand if the time doesn't change when the laptop is in the
sleep mode.
For me the time moves ahead!
I really don't understand it!

I've been havinng the same problem with my IBM thinkpad R40. My clock is set ahead - the longer I have the lid shut the greater the discrepancy. Is this an apm issue by any chance? Did any of you guys figure it out? I have a script that I run as a cron job to fix the time, but it only runs every hour. I could just manually run it when waking the laptop up, but it would also be nice to fix the problem.

Regards,
-geomatt

My laptop uses acpi. So, no, its not an APM issue.
I still have that problem. I can't figure out which script is controlling this sleep/wake-up behaviour.
Once we have that, we can always add lines in that script making it copy the hardware time onto system time.

Did you have a look in /var/log/acipd? That should tell you what is happening in response to what acpi events. I've just switched to acpi and used that info to actually get it to work on my machine.

Regards,
-geo