Thanks Miroslav,
On Mon, Sep 11, 2017 at 8:04 PM Miroslav Lichvar
wrote:
> On Mon, Sep 11, 2017 at 03:01:13AM +, Simon Haines wrote:
> > The GPS is connected through gpsd using the SHM driver, and I've
> confirmed
> > it is working (refclock log is below). Here is my chrony.conf:
> > # cat /
William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273
Physics&Astronomy _|___ Advanced Research _| Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca
Canada V6T 1Z1 | and Gravity __|_ www.theory.physics.ubc.ca/
On Mon, 11 S
On Mon, Sep 11, 2017 at 03:01:13AM +, Simon Haines wrote:
> The GPS is connected through gpsd using the SHM driver, and I've confirmed
> it is working (refclock log is below). Here is my chrony.conf:
> # cat /etc/chrony.conf
> refclock PPS /dev/pps0 lock NMEA
> refclock SHM 0 offset 0.5 delay 0
Thanks Denny,
On Mon, Sep 11, 2017 at 3:39 PM Denny Page wrote:
> A few things come to mind:
>
> - You didn’t include any information about your gpsd configuration.
>
>
The GPS device is a UBlox LEA 6S connected via a CP210X UART-to-USB bridge
to a USB port and is mounted as /dev/ttyUSB0. The da
A few things come to mind:
- You didn’t include any information about your gpsd configuration.
- With the approach you are taking, you have to start gpsd before you start
chronyd. Are you?
- Are you sure you are looking at the right PPS device? There may be PPS
devices for other PPS sources su
I am configuring chrony (3.1 from buildroot) for an isolated system with an
attached GPS+PPS and trying to get it to set the system time as quickly as
possible. The device does not have a battery-backed RTC and will never have
access to a network. It boots with the system time of 1970-01-01T00:00:0
