For some reason, my clock goes extremely fast. When I switched to XFCE from KDE/GNOME yesterday, it started going even faster. :?
For example: I set my Windows box (hey, I'm at work..) and my Arch laptop to the time at time.nrc.ca at roughly 4:50PM EDT.
My work machine now says 5:09PM, and my laptop says 5:15.
I started up ntpd hoping to alleviate it...
hmm ... i have the experience that the 2.6.x kernel slows down my clock by about 200 to 400s / day or so .... and before telling i see ghosts, i made as root an alias:
alias zeit='ntpdate 220.127.116.11'
to update the clock
any ideas why this happens? in windows or older 2.4. kernels i did not realized this
here the latest synch from some min ago
[root@Asteraceae /]# zeit Looking for host 18.104.22.168 and service ntp host found : metasweb01.admin.ch 16 Jun 00:29:52 ntpdate: step time server 22.214.171.124 offset 132.515055 sec
The impossible missions are the only ones which succeed.
make it a cronjob
Turns out I'm not the only one with this problem. This was reported on the kernel Bugzilla.
In the original poster's case, he is also using an HP laptop.
Anyone else out there with an HP laptop running kernel 2.6.6 or later who doesn't have this problem?
I had this problem when I had my system clock set to UTC. Changing it to reflect my local time alleviated the problem for me.
You could use adjtimex to slow your clock down. There's an option that estimates the error and then you give this result to adjtimex in /etc/rc.local. I can't remember how it goes so check the manpage. Or use ntpd.
I have this problem too. My computer is an athlon xp 1800+ on an abit mothercard. But I only have this problem on Arch Linux.
I switched to Arch 2 weeks ago. Before this, I was using Debian and I never had the problem. Is this because they path their kernel ?
how to set timezone for this "zeit" alias?
I have this problem too. My computer is an athlon xp 1800+ on an abit mothercard.
I think if you go into the BIOS and set FSB Spread and AGP Spread to Disable, it will fix this. I don't know why. It's associated with some Nforce2 boards.