The neverending time zone issue

After rebooting from Windows, the time is off by 5:00 and nothing seems to fix it (short of a direct setting of the clock.) This is a very nagging issue, and I have gone through most of the posts regarding the issue with no luck. Here is the output of "timedatecrtl"

At the time of running the command the time was around 11:30 am EST. I am hoping NTPD sets the clock automatically after every boot as Windows seems to mess up the hardware clock. (I have fiddled with Windows side with no luck.) NTP does not seem to do anything even when doing "ntpd -qg" ...

Re: The neverending time zone issue

amiara wrote:

After rebooting from Windows, the time is off by 5:00 and nothing seems to fix it (short of a direct setting of the clock.) This is a very nagging issue, and I have gone through most of the posts regarding the issue with no luck. Here is the output of "timedatecrtl"

Re: The neverending time zone issue

@aesiris I have tried that and it does not have the desired effect. Besides I get that nice warning (This mode is not fully supported ...). It just sets RTC time to be the same as local time (the wrong local time ...), but "ntpd -qg" still has no effect.

@Scimmia I am using Windows 7 and have tried that registry hack "something like RTC is universal" ... As much as I like a cure, I am convinced that there is none and will be happy with a band-aid (aka a working ntp)

Re: The neverending time zone issue

How did you apply the registry change? If you entered it manually, are you positive you you didn't have any typos and created a dword entry? It's best to copy/paste the supplied reg file to avoid any of those issues. Did you also disable windows internet time sync?

NTP isn't working because the clock is too far off, it's a sanity check. Making ntp do the job is a bad thing, though, because it doesn't apply until the system is fully up. You end up with a situation where the system boots, then the clock goes way back in time, throwing everything off. Please don't do this.

If you absolutely must run Windows with a localtime RTC, you need to fix your linux setup to use it as well. Check /etc/adjtime, it should be three lines with the third one being "localtime".

Re: The neverending time zone issue

@Scimmia: Thanks. I reapplied the registry change through the .reg file, and it has not yet taken effect. (I am not sure whether Windows decides to write down the clock at each shutdown or just some of the times ... we will see.) I have not disabled time sync in Windows as I don't see a reason. I want windows to be able to sync time.

My question is really why ntp has no effect. That -g switch in "ntpd -qg" is supposed to force it to change the clock, no matter how off it is (?). I don't want it to sanity check on my behalf. Is there a way to force ntp to set the clock? I suspect there is something wrong with my ntp setup ... I have set the time manually (say off by 1 minute) and expected it to get fine-tuned, but doesn't seem to happen.

Re: The neverending time zone issue

@Lone_Wolf, thanks. I forgot to check this thread for a while. The ntpq command is interesting. What if none of the peers has a star besides it? I have three of them and the jitter and offsets are nonzero for all of them.

Re: The neverending time zone issue

The * is the server ntp will use first to synchronize, servers with + before them are second choice.Servers with - before them are considered not stable enough (or your connection to them is not good enough).