Message from discussion What is the NTP recovery time from 16s step in GPS server?
Received: by 10.66.86.39 with SMTP id m7mr2758727paz.4.1352353823784;
Wed, 07 Nov 2012 21:50:23 -0800 (PST)
From: Rob <nom...@example.com>
Subject: Re: What is the NTP recovery time from 16s step in GPS server?
User-Agent: slrn/pre1.0.0-18 (Linux)
Date: 31 Oct 2012 18:35:41 GMT
X-Trace: 1351708541 news.xs4all.nl 6859 [2001:888:0:1::888]:35125
David Taylor <david-tay...@blueyonder.co.uk.invalid> wrote:
> Ignoring the offset for the moment, if I power up the Rasberry Pi from
> cold while it sees the PPS signals (to an interrupt-driver GPIO pin) is
> never sees gpsd data ( and trying cgps -s also times out with a can't
> connect). I've left it for about 30 minutes but gpsd never sees data.
> When I then do a warm reboot NTP sees data from gpsd right away and cgps
> -s works as well.
> My feeling is that I should concentrate on getting the PC to see GPS
> cold from a cold boot first, and then worry about any 16-second step.
> Would you not agree? If so, what magic file to I have to edit and how
> to delay gpsd starting?
> Actually, I'm not even sure myself, as I recall that from a cold boot,
> stopping and restarting gpsd isn't enough to start the data flow, the
> GPS receiver itself has to be plugged out and back in, but I'm happy to
> try a delayed gpsd start.
> What do you think?
I don't know much about the raspberry.
I think it is sort of standard Linux, but then there really is no
standard Linux anymore due to all the silly changes that Ubuntu people
have been bringing.
What does the /etc/rc.d/gpsd file look like as it is now?
Is there a /etc/udev/rules.d/ directory with some .rules files in it?