Here's more information. As you both suggested, gpsd is feeding bad time to
chronyd.
Starting chrony with the -s option, it still sets the clock to 1999-08-22.
Presumably the drift file had the time set incorrectly in a previous run:
$ cat /var/lib/chrony/chrony.*
72.210307196.256213
1
I'm trying to set up something simple. I want chrony to grab NMEA time as soon
as it's available, and then sync to PPS. This system (BBB) has no
battery-backed RTC and no network access.
When the time is initially correct (set via NTP when connected to network),
chrony seems to work, and lock