Re: NMEA driver - off by 1024 weeks but says 4096

fallenpega...@gmail.com said: > I suggest running it with gpsd for a while instead of NTPsec, and see if > gpsd's logging identifies the issue. > Or if the ntpd log contains the NMEA strings, it may be possible to > reconstruct a gpsd playback file, and play it into gpsd, and see what it > says.

Re: Let's get back to work

Some additional suggested work items: * ntpsec.pool.ntp.org registered (I will take that one) * do we KNOW that the DEB and RPM distro packaging works? * get into the distros: ** setup an Ubuntu PPA (I will take that) ** setup a YUM repo (JDB, can you do that, working with GEM?) ** Debian as an alt

Re: NMEA driver - off by 1024 weeks but says 4096

I suggest running it with gpsd for a while instead of NTPsec, and see if gpsd's logging identifies the issue. Or if the ntpd log contains the NMEA strings, it may be possible to reconstruct a gpsd playback file, and play it into gpsd, and see what it says. ESR and GEM might could help with that.