On Monday 26 January 2004 13:50, Ralph Siemsen wrote:
> On Sun, Jan 25, 2004 at 09:44:19PM +0100, Adrian 'Dagurashibanipal' von
Bidder wrote:
> > Is anythin known about the builtin clock on netwinders? After a short
> > time running, ntpd runs away and ends up detecting all available time
> > sources as falsetickers or unavailable, and the frequency running away to
> > (-)500.00, with a huge jitter (several 100s)
>
> Hmm, _without_ NTP running it is a known issue. But with NTP your
> clock should be solid.
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*.
> Check what revision of netwinder hardware you have (/proc/cpuinfo).
> In the very early models the clocks were "shaken" but that was
> corrected for Rev 4 and 5 - the firmware picks a nonshaken clock and
> calibrates itself against the RTC.
Processor : StrongARM-110 rev 3 (v4l)
BogoMIPS : 185.95
Features : swp half 26bit fastmult
Hardware : Rebel-NetWinder
Revision : 52ff
Serial : 0000000000000ce7
Not sure what that tells me. rev3 is the CPU. So 52ff is perhaps a rev5?
thanks & greets
-- vbi
--
pub 1024D/92082481 2002-02-22 Adrian von Bidder <avbidder@fortytwo.ch>
Key fingerprint = EFE3 96F4 18F5 8D65 8494 28FC 1438 5168 9208 2481