b...@kernel.crashing.org said:
> Ok, I do have one though somewhere with OS X on it. If you give me
> instructions on how to test (I know near to nothing about ntpsec), I should
> be able to compile and run it.
I'm assuming you are already running the normal ntpd from ntp classic, or
Apple's ver
Thanks.
b...@kernel.crashing.org said:
> Right, we just use the value provided by Open Firmware. Any chance you can
> try with MacOS X ?
Not easily. I'm using boxes from eBay. They didn't come with CDs and I've
already installed other software.
> From the value in the properties you showed
Hiya,
Ben's email may have got bounced by the ntpsec list so forwarding here
for folk following along :)
Cheers,
Hugh
Forwarded Message
Subject: Re: Timekeeping oddities on MacMini G4s
Date: Wed, 01 Feb 2017 14:34:48 +1100
From: Benjamin Herrenschmidt
To: Hugh Blemings , li
Hi,
I've recently been lurking on the ntpsec project mailing list.
One of the developers (Hal Murray, CCd) has been doing some tests of the
codebase using FreeBSD and Debian on a G4 based Mac Mini - this largely
motivated by checking all is well on a big-endian system.
Hal has identified wha
Yo Hal!
On Tue, 31 Jan 2017 17:05:21 -0800
Hal Murray wrote:
> >> Looks like ntpd is happy now.
> > And what was the magic incantation? Can you reset and make ntpd
> > fail again?
>
> Installing adjtimex.
>
> Aside from the command line, it's got a mode where tries to adjust
> the drift l
>> Looks like ntpd is happy now.
> And what was the magic incantation? Can you reset and make ntpd fail again?
Installing adjtimex.
Aside from the command line, it's got a mode where tries to adjust the drift
like ntpd does. I think saves stuff on the disk so when you run it again it
can see
Yo Hal!
On Tue, 31 Jan 2017 15:16:42 -0800
Hal Murray wrote:
> > There was a time I used to buy and provision 10 identical servers
> > at a time. Of the 10, one often had this problem. The fix was
> > chrony.
>
> If you ever get another system where ntpd doesn't work but chrony
> does, I'd
g...@rellim.com said:
> I think we are heading the wrong way on this. It is not an Open Firmware
> problem and it is not a Mac problem. I have seen this before with NTP
> Classic. I have verified before that Chronyd does not have the same issue.
> There was a time I used to buy and provision
Yo Hal!
On Tue, 31 Jan 2017 14:38:45 -0800
Hal Murray wrote:
> h...@blemings.org said:
> > Embarrassingly it only just occurred to me to apply some google fu
> > to "Mac Mini G4 clock problem" and it yielded some interesting
> > hits.
>
> > "Clock Drift on Mac Mini (G4-based), ajdtimex, ntp"
h...@blemings.org said:
> Embarrassingly it only just occurred to me to apply some google fu to "Mac
> Mini G4 clock problem" and it yielded some interesting hits.
> "Clock Drift on Mac Mini (G4-based), ajdtimex, ntp" - undated http://i1.dk/
> misc/mac_mini_clock_drift_adjtimex_ntp.html
> "Syst
Hi Gary, Hal, All,
On 1/02/2017 06:19, Gary E. Miller wrote:
Yo Hal!
On Tue, 31 Jan 2017 01:35:41 -0800
Hal Murray wrote:
Does a 1.42 GHz Mac mini really run at 1.42? Why does Open Firmware
say 1.41?
I think we are heading the wrong way on this. It is not an Open
Firmware problem and
Yo Hal!
On Tue, 31 Jan 2017 01:35:41 -0800
Hal Murray wrote:
> Does a 1.42 GHz Mac mini really run at 1.42? Why does Open Firmware
> say 1.41?
I think we are heading the wrong way on this. It is not an Open
Firmware problem and it is not a Mac problem. I have seen this before
with NTP Cl
Hiya Hal, All,
On 31/01/2017 22:25, Hal Murray wrote:
h...@blemings.org said:
Oh ok, did it make any sort of sensible change ? Did tweaking the clock
parameter the "wrong" way make it better I wonder ?
I didn't try that. The change I tried seemed reasonable. I might have
fatfingered somet
h...@blemings.org said:
> Oh ok, did it make any sort of sensible change ? Did tweaking the clock
> parameter the "wrong" way make it better I wonder ?
I didn't try that. The change I tried seemed reasonable. I might have
fatfingered something. It takes just long enough to try something tha
Hi Hal,
On 31/01/2017 20:35, Hal Murray wrote:
I poked around enough in Open Firmware to "fix" the clock parameters. But it
made things worse rather than better. I assume some step in my thinking is
backwards.
Oh ok, did it make any sort of sensible change ? Did tweaking the clock
parame
I poked around enough in Open Firmware to "fix" the clock parameters. But it
made things worse rather than better. I assume some step in my thinking is
backwards.
> When I get some time later today/tonight I'll summarise what we have so far
> into a single email and send that off to the linu
16 matches
Mail list logo
