Re: clockvar reporting from generic (DCF77)

>> I suspect the problem is back in ntpd, which is sending bad mode 6. > Fortunately, that kind of thing is easy to fix once characterized. And I > know that code *really* well. Post an issue one you've figured out what's > going wring, I'll be on it instantly. The ntpd side of ntpq -c "cv &"

Re: clockvar reporting from generic (DCF77)

Eric S. Raymond writes: > Achim, can I get a merge request from you for the DCF77 fix? I've sent a formatted patch to the list. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld:

Re: clockvar reporting from generic (DCF77)

Gary E. Miller : > I suspect the problem is back in ntpd, which is sending bad mode 6. Fortunately, that kind of thing is easy to fix once characterized. And I know that code *really* well. Post an issue one you've figured out what's going wring, I'll be on it instantly. Achim,

Re: clockvar reporting from generic (DCF77)

Yo Achim! On Mon, 20 Feb 2017 19:43:39 +0100 Achim Gratz wrote: > Gary E. Miller writes: > > Can you provide a few more details? Like how your refclock is > > setup in your ntp.conf and where the output you showed comes from? > > The refclock is configured in the usual

Re: clockvar reporting from generic (DCF77)

Gary E. Miller writes: > Can you provide a few more details? Like how your refclock is setup in > your ntp.conf and where the output you showed comes from? The refclock is configured in the usual way and I'm talking about the output of 'ntpq -c "cv &1"'. The first problem is that ntpq seems to

clockvar reporting from generic (DCF77)

The CV reporting from the generic drivers (tested with DCF77) needs some attention. Before the clock first synchronizes, the output is severely broken: --8<---cut here---start->8--- associd=30868 status= no events, clk_unspec, device="RAW DCF77 CODE