You are not logged in.
Pages: 1
After my PC wakes up from sleep, as soon as it connects to my network the time goes haywire. It goes several days in the future. NTPD is running and it is not fixing the time.
Offline
I have the same issue here, like about 1 month or so. My laptop is ASUS N52DA - I think that posting some details can be useful.
https://gist.github.com/1491574
If someone needs any other info - please ask. Setting up NTPD doesn't help anything. On Windows it works fine.
Offline
Sorry for double-posting, but I found out that disabling ntpd before going to sleep fixes it now. Apparently main cause of this issue are problems with ntpd's support of s2ram.
Offline
Nope, even with the NTPD daemon disabled my clock still shows inaccurate time. But the time changes(to the inaccurate state) when I connect to the network. If I am not connected to a network my clock is fine.
Offline
What I can personally suggest as a temporary fix is triggering ntpdate somehow after connection is made.
Offline
But the problem is after suspend I cannot run ntpdate. It says that ntpd is running. And if I kill it, i cannot start it after I run ntpdate.
Offline
Strange. You're sure that it's dead? Check in /var/lock and it's subfolders if it haven't left some kind of lockfiles in /var/lock or any pidfile.
Offline
The /var/lock is empty. No files or folders. But rc.d list shows the daemon as started. And if I try to stop it from there it fails.
Offline
Pages: 1