1.1.6 build fails on FC30
Udo van den Heuvel
udovdh at xs4all.nl
Sun Nov 3 11:29:00 UTC 2019
On 03-11-2019 12:15, Udo van den Heuvel via devel wrote:
> On 03-11-2019 12:06, Hal Murray wrote:
>>> We do see pps and nmea but ntpd does not choose the local gps. Why?
>> How do you "see" them?
> I use `ntpq -pn` to see what the status is.
>>> NMEA(0) .GPS. 0 l 8 64 377 0.0000 0.0000 0.0019
>> I don't understand what's going on. The 377 says it is working, but the
>> 0.0000 and 0.0019 say that it isn't working.
>> Do you have the baud rate correct?
> `cat /dev/gps0` shows the NEMA stream.
>> What is in clockstats?
> We have clocklist:
> ntpq> clocklist
> associd=0 status=0012 1 event, clk_bad_format,
> poll=14, noreply=0, badformat=1, baddata=0, fudgetime1=0.0,
> fudgetime2=260.0, stratum=0, refid=GPS, flags=5, device="NMEA GPS Clock"
> Then the 'badformat' is worrying.
> What is wrong and how can I fix this?
> Also: when the GPS gives bad data, then why doesn't it use a different
> clock as peer?
We furthermore find:
Nov 3 11:58:32 bv ntpd: REFCLOCK: refclock_ppsapi:
time_pps_create: Operation not supported
Nov 3 11:58:32 bv ntpd: REFCLOCK: NMEA(0) flag1 1 but PPSAPI fails
# grep PPS .config
# CONFIG_PPS_DEBUG is not set
# PPS clients support
# CONFIG_PPS_CLIENT_PARPORT is not set
# CONFIG_PPS_CLIENT_GPIO is not set
# PPS generators support
More information about the devel