Hi Timo, Timo Juhani Lindfors a écrit , Le 03/05/2010 16:51: > Gilles Filippini <p...@debian.org> writes: >> Since a recent upgrade I've not been able to have a GPS fix using gpsd. >> In such a case I usually monitor /dev/ttySAC1 using cat. But this time >> it seems useless : >> >> * when using the Zhone GPS feature, I have a fix but "cat /dev/ttySAC1" >> returns *nothing* at all ; >> * when using navit as a gpsd client, "cat /dev/ttySAC1" returns binary >> garbage instead of the usual text records. > > I assume you are using debian.
You assume right :)
> Make sure that no process is using
> ttySAC1 and then
> om gps power 0
> om gps power 1
> hexdump -C /dev/ttySAC1
This way "cat /dev/ttySAC1" delivers correct NMEA records (text).
The binary spitting up starts when I launch a gpsd client wrapped with
fsoraw. E.g.:
$ fsoraw -rGPS navit
But I start understanding what's going on: ogpsd initializes the GPS
device in binary mode. Hence no problem so far. And when monitoring GPS
with "gpspipe -r" it seems there is a fix after a while.
But no gpsd client can see the fix ; I've tried with navit as well as
with xgps.
So I guess it might be a gpsd bug. I'll give a try downgrading gpsd to 2.92.
Thoughts?
Thanks,
_g.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
