[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NTP issue aarch64
From: |
Gary E. Miller |
Subject: |
Re: NTP issue aarch64 |
Date: |
Thu, 30 May 2024 12:34:43 -0700 |
Yo Nick!
On Thu, 30 May 2024 09:58:00 +0100
Nick Taylor <nicktaylor@dataskill.uk> wrote:
> New issue - we are evaluating a new platform based on aarch564 which
> includes a u-blox receiver
Raspberry Pi's are very popular for NTP servers.
> I'd like to sync to chrony using NTP - I don't mind whether it's by
> shm or socket but in the past I've only used shm as socket didn't
> seem to work for me
Both can work fine.
> Problem is that we don't seem to be getting ntp feed
Oh, boy. Not a lot of details there. Please run gpsdenuginfo, as root,
ans share the results. Get it from git head, or the web:
https://gpsd.io/gpsdebuginfo
> I'm attaching some debug commands and logs - please advise if there's
> anything else you need to check further
Well, one big obvious problem:
root@A14LKN:~# gpsd -D9 -N /dev/ttymxc5
You forgot the -n option. Without -n, gpsd waits for a client to
connect before reading from the GNSS receiver. When gpsd is not
reading from the receiver, it has no time stamp to pass on to the shm
or sock.
Maybe spend some time studying the Time Service Howto:
https://gpsd.io/gpsd-time-service-howto.html
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
gem@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can't measure it, you can't improve it." - Lord Kelvin
pgpsZ_4FSSZi6.pgp
Description: OpenPGP digital signature