On Tue, Jun 18, 2013 at 9:30 AM, Rob <[email protected]> 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?
/ # ntpq -pn
remote refid st t when poll reach delay offset
jitter
==============================================================================
*127.127.28.0 .SHMg. 0 l 4 16 377 0.000 10.131
6.341
127.127.28.1 .SHMp. 0 l - 16 0 0.000 0.000
0.000
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
