Notice that the kernel will not sync the clock if it is more than 15 minutes wrong, you might want to force-set it once manually.

Looks like you were right here. I just intentionally set the clock 2 or 3 minutes slow in the BIOS. As soon as I booted into Linux, the system clock got set back to the correct time with NTP. Then, it took about 20 minutes or so but it did sync up the hardware clock. I just had the hardware clock too far off before it seems.

]]>https://bbs.archlinux.org/profile.php?id=592672012-10-09T22:21:55Zhttps://bbs.archlinux.org/viewtopic.php?pid=1173254#p1173254Notice that the kernel will not sync the clock if it is more than 15 minutes wrong, you might want to force-set it once manually.]]>https://bbs.archlinux.org/profile.php?id=374712012-10-08T20:35:48Zhttps://bbs.archlinux.org/viewtopic.php?pid=1172655#p1172655I've been noticing this as well, only because I don't boot into Windows all that much, I've been too lazy to investigate it. But I find my system behaving the same as weirddan455's. Here's my info:

]]>https://bbs.archlinux.org/profile.php?id=319732012-10-08T13:39:46Zhttps://bbs.archlinux.org/viewtopic.php?pid=1172497#p1172497Okay, That looks pretty good. I wanted to double check the system flags and that the stratum is reasonable. If the stratum (a measure of the quality of your server) is too high, the system might not trust the time to the point where it will use it to set the HW clock. Doesn't seem to be the problem.]]>https://bbs.archlinux.org/profile.php?id=272892012-10-07T20:04:46Zhttps://bbs.archlinux.org/viewtopic.php?pid=1172160#p1172160

]]>https://bbs.archlinux.org/profile.php?id=592672012-10-07T18:29:50Zhttps://bbs.archlinux.org/viewtopic.php?pid=1172129#p1172129can you post the output of ntpdc -c sysinfo ??]]>https://bbs.archlinux.org/profile.php?id=272892012-10-07T18:16:18Zhttps://bbs.archlinux.org/viewtopic.php?pid=1172124#p1172124This is a fresh install with the new install disc. I'm dual booting with Windows 7 and I followed the advice in the beginner's guide to set the hardware clock to UTC and then modify the registry in Windows so that it can also use UTC time. Well, before I modified the registry, Windows would sync the time to the internet every week or so and also sync the hardware clock every time I shut down. After I modified the registry, Windows leaves the hardware clock completely alone which is expected behavior with the "hack" I did and would be fine EXCEPT:

Now nothing is auto syncing the hardware clock leaving it free to get as out of sync as it wants. I'm running NTPD as a daemon in /etc/rc.conf and according to the wiki here:

It should be syncing the hardware clock every 11 minutes. Only it's not touching it at all. I can see NTPD running as soon as I boot the computer by running date (shows the system time, not the hardware time) as soon as I log in it shows the out of sync time then a couple seconds later, it connects to the server and date shows the correct time. But when I look at my hardware clock by running "hwclock --show" it still shows the out of sync time I started with. I was able to set the hardware clock manually by running "hwclock -w" and that worked fine but I'm really looking for a way to do this all automatically.

I'm kind of thinking that wiki is wrong. Also I haven't been able to try doing it the systemd way because if I type systemctl I just get