[ntp:questions] ntpd connect gpsd shared memory driver

Rob nomail at example.com
Tue Jun 18 17:16:18 UTC 2013

Richard Cagley <rcagley at gmail.com> wrote:
> On Tue, Jun 18, 2013 at 9:30 AM, Rob <nomail at example.com> wrote:
>> I stand corrected, the "no probe matched" is indeed a fatal error.
>> Try to fix that first.
>> There should be more logging then, and the next step is to check
>> if there is a fix to the satellites.
> adding the -b flag to gpsd seemed to do the trick. I now seem to get some
> timing info. I do still get the "no probe matched". I can't tell if it's
> fatal or not. I mean if I'm getting timing info now on the shared memory
> that ntpd can see...is it really fatal?

Does it stop there or is there logging that indicates that it receives
and understands data from the receiver?

> / # ntpq -pn
>      remote           refid      st t when poll reach   delay   offset
>  jitter
> ==============================================================================
> *    .SHMg.           0 l    4   16  377    0.000   10.131
> 6.341
>    .SHMp.           0 l    -   16    0    0.000    0.000
> 0.000

It now locks to the serial data but not yet to the PPS.
What happens when you add some external timeserver(s)?
Are you within a fraction of a second from those?

More information about the questions mailing list