I think the first thing to do is make sure the bios batter is still working. Turn on the computer, go to bios, correct the time, then turn off computer. Next day, turn on the computer, get in bios again and see if the time is correct. -----Original Message----- From: fedora-test-list-bounces@xxxxxxxxxx [mailto:fedora-test-list-bounces@xxxxxxxxxx] On Behalf Of Alexander Todorov Sent: Tuesday, December 09, 2008 9:37 AM To: For testers of Fedora Core development releases Subject: Re: F10: PC clock lacking behind with 20 minutes John5342 wrote: > Just a stab in the dark. What if it is ntp causing the drift because it is > trying to converge on an incorrect time. Could potentially be possible if > ntp thinks your in a different time-zone to which you actually are. Thats a > problem i faced some time ago. Cant remember how ntp decides what timezone > your in though. I am probably way off the mark but hey. > > NTP doesn't seem to be the problem here. Leaving the system running for a while it reached the 20min offset. Now I'll try one last thing to rule out if the motherboard battery is at fault. I'll set the BIOS time to the correct value, reboot and leave the PC at the BIOS settings screen, i.e. no interaction with the OS and see what happens after several hours. -- Alexander. -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
