On Sunday 26 March 2006 17:43, Carlos E. R. wrote:
The Sunday 2006-03-26 at 17:17 -0500, J. Scott Thayer wrote:
I usually get beat up whenever I post here but it is probably my fault usually, in ANY case... There was another response to your message that purported to solve this problem. I set my clock via KDE to my trusty atomic clock on the wall. I then set the hardware clock and deleted /etc/adjtime. So what? It is now 1537 but the taskbar says it is 1708. No I didn't reboot, if someone actually thinks that would matter, let me know. The point remains, the software clock runs too fast in SOME hardware/software configurations and no one has figured out why. If I have missed the simple solution somewhere I apologize and please point me in the right direction.
There are two different issues here, namely:
1) * Symptom: right after a reboot the clock is off by large ammounts, and stays with the same difference if you do nothing about it. * Solution: setup the clock by your prefered method hwclock --systohc rm /etc/adjtime
(in that order)
2) * Symptom: after seting up the clock, it drifts while the computer is running. * Solution: probable kernel problem.
Note: when in doubt about the clock, use the command "date" on a console or xterm. Do not trust applets, like the kde clock.
-- Cheers, Carlos Robinson
My problem is number 2. I also just went to a console via Cntrl-Alt F2, ran date and got the same result as showing in the KDE applet. This way I was fully out of KDE and X yet no change in the issue. I believe it IS a kernel problem but the kernel gurus have not identified it (they HAVE looked). Scott