NTP Serial GPS not working in 2.6.0-RELEASE
-
Noticed this weeks ago but haven't had the opportunity to dig in until today...
(Garmin) GPS was working flawlessly in 2.5, in 2.6 it's a no-go. No real changes in a long time since NTP is basically set-it-and-forget-it.
Only thing suspicious in the log is:
May 29 18:37:14 ntpd 98558 kernel reports TIME_ERROR: 0x41: Clock Unsynchronized May 29 18:37:14 ntpd 98558 kernel reports TIME_ERROR: 0x41: Clock UnsynchronizedAnd on the status page I see:
Unreach/Pending 127.127.20.0where the GPS connection should be in the list of peers.Curious if anyone's seen similar behavior. I don't see anything in the changelog to suggest any changes here, but maybe it's something FreeBSD related.
-
@digitalgimpus Is the GPS device USB? If so, heed this warning from here: https://docs.netgate.com/pfsense/en/latest/services/ntpd/gps.htm
-
@nollipfsense Negative, I should have mentioned that. It's a serial GPS.
-
@digitalgimpus Make sure that the console (or other service) are not directed to the serial port. I recall some changes recently regarding this matter (console).
I am running NTP with a serial Garmin GPS with few problems on 22.01-RELEASE (amd64).
Ted
-
Mmm, I'm not aware of any particular issues in 2.6.
Make sure it's still sending useful data to the port.Those errors are normal when ntpd first starts. It doesn't sync until it has valid data to use which can rake some time.
Steve
-
@tquade Checking in advanced, set to video console and the serial console is unchecked. So unless there's something else that can use it, I don't think that's the case.
-
@digitalgimpus Try running cu against the serial port to see if NMEA Sentences are being pushed out.
cu -l cuaU0 -s 4800
Ted
-
It might be 9600bps. Or it might have reverted to defaults causing the problem?
The port is a real serial port so it will be cuau0 or cuau1. The upper case U implies a USB connected serial port.
Steve
