Re: Abysmal clock chip on netwinder?
On Mon, Jan 26, 2004 at 02:20:02PM +0100, Adrian von Bidder wrote:
> Hmm. Seems good enough right now. I had it running 4 hours at least yesterday,
> and during that time the clock ran away 2000ms. Now it's been stable for the
> last 2h (offset <1ms to the local timeserver). *shrug*.
Hmm, there is another "feature", I believe in adjtime() or somesuch,
which will not correct the clock if going backwards. This can cause
the initial ntpdate command to fail. Kludge fix is to set date
manually to Jan 1, 1970 and then run ntpdate. After that ntpd should
be able to hold it steady.
> Revision : 52ff
Yep, that's rev5.2 (which has all the clock fixes). The ff means
plastic case and regular (tulip+serial) daughtercard.