<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">The PC settings are usually stored in the clock chip. If the battery is run down, then the bios settings would be lost and the system would not boot. The problem is elsewhere. Perhaps the system is used for dual boot., Leslie --- On Mon, 12/8/08, Patrick O'Callaghan <pocallaghan@gmail.com> wrote: <blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">From: Patrick O'Callaghan <pocallaghan@gmail.com> Subject: Re: F10: PC clock lacking behind with 20 minutes To: "For testers of Fedora Core development releases" <fedora-test-list@redhat.com> Date: Monday, December 8, 2008, 11:54 PM <pre>On Tue, Dec 9, 2008 at 6:00 AM, Affix <affix@ihack.co.uk> wrote: > Hello, > Have you tried to set the interval when it syncs with the ntp server? > > On Mon, Dec 8, 2008 at 9:34 AM, Alexander Todorov <atodorov@redhat.com> > wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA512 >> >> Hi all, >> after upgrade to F10 I noticed that the my laptop has begun to show >> incorrect >> time. What I did yesterday is: >> >> 1) Set the BIOS clock to correct time (UTC) >> 2) Boot the computer and adjust ntp, time zone, etc... >> 3) after one day now the pc shows incorrect time with about 20 minutes >> offset. >> >> I've never had such problems with F9 or other distros. Any ideas how can I >> debug >> what's going wrong ? Silly question, but could your motherboard battery be run down? It's hard to see how an ntp problem could give you clock drift of 20 minutes in only a day. poc -- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list </pre></blockquote></td></tr></table>