Daniel asked for a _complete_ log just 3 hours after the initial bug
report (Ticket #265). But no answer until now...
well, i assumed, the op would have provided one.
anyway. i did a
grep ogpsd
over my frameworkd.log (almost 100.000 lines since 2008.11.29 00:07:12)
and there still are about
Am Do 27. November 2008 schrieb arne anka:
I don know why, and I'm not shure if it was solved by the changes I have
made, but after time and timezone was correct fso-gpsd fixed in less then
2min.
if that's really the cause it needs fixing -- my fr is always about 3 min
behind in time
Either the GPS knows where to look for the sats (due to accurate data
being supplied by AGPS)
true, o pharao -- but afair the issue was, that no fix at all was obtained.
and if that is caused by whatever feeds the ublox with agps data, the
feeding routine has to be more tolerant, ie issue a
...right now i'm still no able to get a fix, so maybe it's better for me to
downgrade to 4.0 if this is the only solution (hoping that debian mantains
the right enumeration... 0.4.3 is my current version).
d
On Sat, Nov 29, 2008 at 4:01 PM, arne anka [EMAIL PROTECTED] wrote:
Either the GPS
Am Sa 29. November 2008 schrieb arne anka:
Either the GPS knows where to look for the sats (due to accurate data
being supplied by AGPS)
true, o pharao -- but afair the issue was, that no fix at all was obtained.
and if that is caused by whatever feeds the ublox with agps data, the
AGPS is *not* disabling normal non-A operation of GPS (means there is
well, agps doesn't come from heaven -- it has to be programmed somehow.
and i simply think it possible that there something goes wrong.
btw: It seems to me as if 3 minutes difference in time shouldn't make any
trouble.
Hi,
On Sat, Nov 29, 2008 at 06:34:18PM +0100, arne anka wrote:
atm there's no fix at all, neither after 3 nor after 10 minutes.
the log is full of
Discarded data not UBX ...
and ubx seems, afair, to be the format the agps uses/needes.
so far there's no statement of the fso developers, what
I've put milestone 4 back on, and I'm now getting UBX messages in the debug
log, so something clearly broke in 4.1 . Took a while (it's raining hard and
I'm indoors) but I finally got a fix.
Methinks something's broken between 4 and 4.1 - there doesn't appear to be an
existing bug for this so
--FSO--GPS--No-Fix-tp1521077p1584706.html
Sent from the Openmoko Community mailing list archive at Nabble.com.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
My FSO 4.1 is running the fso-gpsd too.
The only oddity with mine is that it lives on the SD card. I deliberately kept
everything clean as far as the install goes - I just installed tangoGPS after
installing FSO 4.1, then when the GPS didn't work I did a opkg update/upgrade
on 24th and tried
Technologies - http://www.solutiontrax.com
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
--
View this message in context:
http://n2.nabble.com/-Debian--FSO--GPS
.nabble.com/-Debian--FSO--GPS--No-Fix-tp1521077p1585370.html
Sent from the Openmoko Community mailing list archive at Nabble.com.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
I don know why, and I'm not shure if it was solved by the changes I have
made, but after time and timezone was correct fso-gpsd fixed in less then
2min.
if that's really the cause it needs fixing -- my fr is always about 3 min
behind in time when rebooted and i do not always have a ntp
/listinfo/community
--
View this message in context:
http://n2.nabble.com/-Debian--FSO--GPS--No-Fix-tp1521077p1578295.html
Sent from the Openmoko Community mailing list archive at Nabble.com.
___
Openmoko community mailing list
community
On Tue, Nov 25, 2008 at 10:24 PM, glownan [EMAIL PROTECTED] wrote:
Hi, I'm using SHR and having the same problem.
SHR latest image was shipped with gpsd instead of fso-gpsd.
Just opkg remove --force-depends gpsd; opkg install fso-gpsd and it'll work.
Future images will be corrected.
--
--FSO--GPS--No-Fix-tp1521077p1578627.html
Sent from the Openmoko Community mailing list archive at Nabble.com.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
I'm using FSO 4.1 , and have a similar problem. Enabling debug on framework
gives messages that suggest it is sending NMEA data when frameworkd is
expexting UBX data. There's a curious message in the logs - 'exception
0x8040 was trapped' .The GPS clearly has power. Here's some of the log:
On Wed, 19 Nov 2008 23:56:33 -0800 (PST)
Fragggy [EMAIL PROTECTED] wrote:
I think so.
cat
/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron
shows a 1
I have put the Freerunner next to a window over Night and logt the output of
/dev/ttySAC1.
After a few
Hi,
On Wed, Nov 19, 2008 at 11:56:33PM -0800, Fragggy wrote:
I think so.
cat
/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron
shows a 1
I have put the Freerunner next to a window over Night and logt the output of
/dev/ttySAC1.
After a few minutes I got
2947
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
pa
GPSD,P=?,A=?
It would be nice if someone has a hint, where I could start debuging.
Greetings
Dennis M
--
View this message in context:
http://n2.nabble.com/-Debian--FSO--GPS--No-Fix-tp1521077p1521077.html
Sent from
Fragggy [EMAIL PROTECTED] writes:
But the most important thing for me is, that after the update i get no gps
fix anymore.
Does the GPS chip have power?
___
Openmoko community mailing list
community@lists.openmoko.org
,3,2,11,29,19,200,27,12,83,044,28,30,50,263,37,02,18,113,29*78
$GPGSV,3,3,11,14,42,290,33,32,05,344,33,31,04
but still no fix this morning.
--
View this message in context:
http://n2.nabble.com/-Debian--FSO--GPS--No-Fix-tp1521077p1556214.html
Sent from the Openmoko Community mailing list archive at Nabble.com
22 matches
Mail list logo
