Re: fso-gps..
On Thu, 2009-04-09 at 12:24 +0200, Daniel Willmann wrote: On Tue, 17 Mar 2009 00:38:17 +0100 Michael 'Mickey' Lauer mic...@openmoko.org wrote: 2009.03.16 23:06:54 frameworkd.persist ERRORno persist data for subsystem ogpsd No problem, it will be generated next time. Daniel, should we turn this into an INFO rather than an ERROR? Hmm, this is coming from the persist code. Jan, any objections to turning this into an INFO? Sure, this should really be INFO. I'll change that. -- Jan Lübbe jlue...@lasnet.dehttp://sicherheitsschwankung.de gpg-key 1024D/D8480F2E 2002-03-20 fingerprint 1B25 F91F 9E7B 5D4F 1282 02D6 8A83 8BE4 D848 0F2E ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-gps..
On Tue, 17 Mar 2009 00:38:17 +0100 Michael 'Mickey' Lauer mic...@openmoko.org wrote: 2009.03.16 23:06:54 frameworkd.persist ERRORno persist data for subsystem ogpsd No problem, it will be generated next time. Daniel, should we turn this into an INFO rather than an ERROR? Hmm, this is coming from the persist code. Jan, any objections to turning this into an INFO? Regards, Daniel Willmann signature.asc Description: PGP signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR/FSO] - GPS - no fix, ogpsd.pickle question
have you guys tried this: http://trac.freesmartphone.org/ticket/265 ? On Mon, Mar 30, 2009 at 3:45 AM, roby hariseldo...@gmail.com wrote: On Fri, Mar 20, 2009 at 6:17 PM, Yorick Moko yorickm...@gmail.com wrote: i also didn't get fixes with shr-testing it used to work fine it also still works with openmok-agpsui, but not with tangogps I have noticed that if i -start with agpsui, -Power on, -wait for the fix (without moving the phone) -close agpsui without Power off -start tangogps it works well.. so it seems like tangogps is unable to stimulate the gps daemon to start. let me know if it's the same for you ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR/FSO] - GPS - no fix, ogpsd.pickle question
Yeap. I was recently fixed and it works now on SHR-Unstable. So for those who still have problems - try upgrading frameworkd. Leonti On Mon, Mar 30, 2009 at 6:06 PM, Yorick Moko yorickm...@gmail.com wrote: have you guys tried this: http://trac.freesmartphone.org/ticket/265 ? On Mon, Mar 30, 2009 at 3:45 AM, roby hariseldo...@gmail.com wrote: On Fri, Mar 20, 2009 at 6:17 PM, Yorick Moko yorickm...@gmail.com wrote: i also didn't get fixes with shr-testing it used to work fine it also still works with openmok-agpsui, but not with tangogps I have noticed that if i -start with agpsui, -Power on, -wait for the fix (without moving the phone) -close agpsui without Power off -start tangogps it works well.. so it seems like tangogps is unable to stimulate the gps daemon to start. let me know if it's the same for you ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR/FSO] - GPS - no fix, ogpsd.pickle question
On Fri, Mar 20, 2009 at 6:17 PM, Yorick Moko yorickm...@gmail.com wrote: i also didn't get fixes with shr-testing it used to work fine it also still works with openmok-agpsui, but not with tangogps I have noticed that if i -start with agpsui, -Power on, -wait for the fix (without moving the phone) -close agpsui without Power off -start tangogps it works well.. so it seems like tangogps is unable to stimulate the gps daemon to start. let me know if it's the same for you ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR/FSO] - GPS - no fix, ogpsd.pickle question
I've flashed to shr-testing a few days ago, and *never* managed to get a fix since. I've noticed the following line in the log, when starting tangoGPS for example : Mar 20 16:22:53 om-gta02 user.debug kernel: [63639.39] rxerr: port ch=0x00, rxs=0x000c Happens when opening and closing the app, so i guess it's when the GPS is started/stopped. Nothing else in my log. Has someone ever faced this issue? -- View this message in context: http://n2.nabble.com/-SHR-FSOGPS---no-fix%2C-ogpsd.pickle-question-tp2384123p2509470.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
Re: [SHR/FSO] - GPS - no fix, ogpsd.pickle question
On Freitag 20 März 2009 16:26:53 KaZeR wrote: I've flashed to shr-testing a few days ago, and *never* managed to get a fix since. I've noticed the following line in the log, when starting tangoGPS for example : Mar 20 16:22:53 om-gta02 user.debug kernel: [63639.39] rxerr: port ch=0x00, rxs=0x000c Happens when opening and closing the app, so i guess it's when the GPS is started/stopped. Nothing else in my log. Has someone ever faced this issue? i havn't also any fix with the TESTING-shr.. with UNSTABLE-shr (13. march) it work's good.. i had the same expirience with the phone of a friend (i'm his supporter :p ) i didn't check the log for failures.. so don't know if it's the same.. which log does you check? greets ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR/FSO] - GPS - no fix, ogpsd.pickle question
i also didn't get fixes with shr-testing it used to work fine it also still works with openmok-agpsui, but not with tangogps also waited long, and removed that pickle On Fri, Mar 20, 2009 at 4:51 PM, Vinzenz Hersche hers...@puzzle.ch wrote: On Freitag 20 März 2009 16:26:53 KaZeR wrote: I've flashed to shr-testing a few days ago, and *never* managed to get a fix since. I've noticed the following line in the log, when starting tangoGPS for example : Mar 20 16:22:53 om-gta02 user.debug kernel: [63639.39] rxerr: port ch=0x00, rxs=0x000c Happens when opening and closing the app, so i guess it's when the GPS is started/stopped. Nothing else in my log. Has someone ever faced this issue? i havn't also any fix with the TESTING-shr.. with UNSTABLE-shr (13. march) it work's good.. i had the same expirience with the phone of a friend (i'm his supporter :p ) i didn't check the log for failures.. so don't know if it's the same.. which log does you check? greets ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-gps..
ok, i will testing again.. but with the previus system there was also no failure.. and my brother had 7 fixes in anything about 5 minutes, me 0.. also after restart, disabeling and enabeling etc.. but good cause the code work's :) ps: see you @ openmoko-stand by openexpo bern, i heard? (i work also there) :) it's cool for me to see one of the fso-developers :D On Dienstag 17 März 2009 00:38:17 Michael 'Mickey' Lauer wrote: No failure -- see above. Device should be up and running now. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
fso-gps..
hello there, i had a problem with my gps-daemon. i hadn't a file which is needed to start the gps-daemon. r...@om-gta02 ~ $ cat /var/log/frameworkd.log | grep gps 2009.03.16 22:35:36 frameworkd.controller INFO launching internal subsystem ogpsd 2009.03.16 22:35:36 frameworkd.subsystem INFO Scanned subsystem via method 'auto', result is ['om.py', 'gpsdevice.py', 'helpers.py', 'eten.pyo', 'helpers.pyo', 'eten.py', 'ubx.pyo', 'gpschannel.pyo', 'gpschannel.py', '__init__.py', 'nmea.py', 'om.pyo', 'factory.pyo', 'nmea.pyo', '__init__.pyo','ubx.py', 'factory.py', 'gpsdevice.pyo'] 2009.03.16 22:35:41 ogpsdWARNING (could not write to '/sys/bus/platform/devices/neo1973-pm-gps.0/power_on': [Errno 2] No such file or directory:'/sys/bus/platform/devices/neo1973-pm-gps.0/power_on') 2009.03.16 22:35:42 ogpsdWARNING (could not write to '/sys/bus/platform/devices/neo1973-pm-gps.0/power_on': [Errno 2] No such file or directory:'/sys/bus/platform/devices/neo1973-pm-gps.0/power_on') 2009.03.16 22:35:42 ogspd.gpsdevice INFO GTA02Device initialized. Serving org.freedesktop.Gypsy at /org/freedesktop/Gypsy 2009.03.16 22:35:42 frameworkd.subsystem INFO subsystem ogpsd took 5.85 seconds to startup 2009.03.16 22:36:45 ogspd.gpsdevice INFO disabling 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING (could not write to '/sys/bus/platform/devices/neo1973-pm-gps.0/power_on': [Errno 2] No such file or directory:'/sys/bus/platform/devices/neo1973-pm-gps.0/power_on') so i searched for /sys/bus/platform/devices/neo1973-pm-gps.0/power_on in the shr-tar, but the /sys/-directory is empty :s (but not on the moko itself, so i think, the content is created by the system..) so, is there a way to reconfigure this file? it works by my brother (but he's sleeping, so i couldn't copy the file yet :p ) i tried also to create the file with ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
fso-gps..
hello there.. my gps-daemon isn't running, because it want's a file which isn't exist in my installation (shr-testing, with jffs2).. r...@om-gta02 ~ $ cat /var/log/frameworkd.log | grep gps 2009.03.16 22:35:36 frameworkd.controller INFO launching internal subsystem ogpsd 2009.03.16 22:35:36 frameworkd.subsystem INFO Scanned subsystem via method 'auto', result is ['om.py', 'gpsdevice.py', 'helpers.py', 'eten.pyo', 'helpers.pyo', 'eten.py', 'ubx.pyo', 'gpschannel.pyo', 'gpschannel.py', '__init__.py', 'nmea.py', 'om.pyo', 'factory.pyo', 'nmea.pyo', '__init__.pyo','ubx.py', 'factory.py', 'gpsdevice.pyo'] 2009.03.16 22:35:41 ogpsdWARNING (could not write to '/sys/bus/platform/devices/neo1973-pm-gps.0/power_on': [Errno 2] No such file or directory:'/sys/bus/platform/devices/neo1973-pm-gps.0/power_on') 2009.03.16 22:35:42 ogpsdWARNING (could not write to '/sys/bus/platform/devices/neo1973-pm-gps.0/power_on': [Errno 2] No such file or directory:'/sys/bus/platform/devices/neo1973-pm-gps.0/power_on') 2009.03.16 22:35:42 ogspd.gpsdevice INFO GTA02Device initialized. Serving org.freedesktop.Gypsy at /org/freedesktop/Gypsy 2009.03.16 22:35:42 frameworkd.subsystem INFO subsystem ogpsd took 5.85 seconds to startup 2009.03.16 22:36:45 ogspd.gpsdevice INFO disabling 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 22:36:45 ogpsdWARNING (could not write to '/sys/bus/platform/devices/neo1973-pm-gps.0/power_on': [Errno 2] No such file or directory:'/sys/bus/platform/devices/neo1973-pm-gps.0/power_on') so i searched in the tar-file of shr for this file, but the /sys-directory is empty. is there a way to create this file? i tried to create it by touch: r...@om-gta02 ~ $ touch /sys/bus/platform/devices/neo1973-pm-gps.0/power_on touch: /sys/bus/platform/devices/neo1973-pm-gps.0/power_on: No such file or directory is it using a tool or does i need a complet new installation? was it just a upload-failure of dfu-util? hope, someone could help me.. :) greets and a good night signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-gps..
so, is there a way to reconfigure this file? it works by my brother (but he's sleeping, so i couldn't copy the file yet :p ) even if he's awake -- no chance. sysfs is created by the kernel upon boot and mounted at /sys. most likely your kernel is too new and/or your fso-framework too old. here, with debian and kernel 2.6.28-20090105.git69b2aa26 (and fso-frameworkd 0.8.4.9-20090130-3) /sys/bus/platform/devices/neo1973-pm-gps.0/pwron exists. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-gps..
it's very strange, i tried also with a actuall download of the testing-kernel and testing lite-image and a new flash of both (so they should be new), but it also doesn't work.. r...@om-gta02 ~ $ cat /var/log/frameworkd.log | grep gps 2009.03.16 23:06:48 frameworkd.controller INFO launching internal subsystem ogpsd 2009.03.16 23:06:48 frameworkd.subsystem INFO Scanned subsystem via method 'auto', result is ['om.py', 'gpsdevice.py', 'helpers.py', 'eten.pyo', 'helpers.pyo', 'eten.py', 'ubx.pyo', 'gpschannel.pyo', 'gpschannel.py', '__init__.py', 'nmea.py', 'om.pyo', 'factory.pyo', 'nmea.pyo', '__init__.pyo','ubx.py', 'factory.py', 'gpsdevice.pyo'] 2009.03.16 23:06:54 ogpsdWARNING (could not write to '/sys/bus/platform/devices/neo1973-pm-gps.0/power_on': [Errno 2] No such file or directory:'/sys/bus/platform/devices/neo1973-pm-gps.0/power_on') 2009.03.16 23:06:54 ogpsdWARNING (could not write to '/sys/bus/platform/devices/neo1973-pm-gps.0/power_on': [Errno 2] No such file or directory:'/sys/bus/platform/devices/neo1973-pm-gps.0/power_on') 2009.03.16 23:06:54 frameworkd.persist ERRORno persist data for subsystem ogpsd 2009.03.16 23:06:55 ogspd.gpsdevice INFO GTA02Device initialized. Serving org.freedesktop.Gypsy at /org/freedesktop/Gypsy 2009.03.16 23:06:55 frameworkd.subsystem INFO subsystem ogpsd took 6.78 seconds to startup 2009.03.16 23:08:37 ogspd.gpsdevice INFO disabling 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:38 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:38 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:38 ogpsdWARNING (could not write to '/sys/bus/platform/devices/neo1973-pm-gps.0/power_on': [Errno 2] No such file or directory:'/sys/bus/platform/devices/neo1973-pm-gps.0/power_on') 2009.03.16 23:09:09 ogspd.gpsdevice INFO enabling 2009.03.16 23:09:09 ogpsdWARNING (could not write to '/sys/bus/platform/devices/neo1973-pm-gps.0/power_on': [Errno 2] No such file or directory:'/sys/bus/platform/devices/neo1973-pm-gps.0/power_on') same failure.. :( On Montag 16 März 2009 23:36:04 arne anka wrote: so, is there a way to reconfigure this file? it works by my brother (but he's sleeping, so i couldn't copy the file yet :p ) even if he's awake -- no chance. sysfs is created by the kernel upon boot and mounted at /sys. most likely your kernel is too new and/or your fso-framework too old. here, with debian and kernel 2.6.28-20090105.git69b2aa26 (and fso-frameworkd 0.8.4.9-20090130-3) /sys/bus/platform/devices/neo1973-pm-gps.0/pwron exists. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fso-gps..
Am Dienstag, den 17.03.2009, 00:13 +0100 schrieb Vinzenz Hersche: it's very strange, i tried also with a actuall download of the testing-kernel and testing lite-image and a new flash of both (so they should be new), but it also doesn't work.. r...@om-gta02 ~ $ cat /var/log/frameworkd.log | grep gps 2009.03.16 23:06:48 frameworkd.controller INFO launching internal subsystem ogpsd 2009.03.16 23:06:48 frameworkd.subsystem INFO Scanned subsystem via method 'auto', result is ['om.py', 'gpsdevice.py', 'helpers.py', 'eten.pyo', 'helpers.pyo', 'eten.py', 'ubx.pyo', 'gpschannel.pyo', 'gpschannel.py', '__init__.py', 'nmea.py', 'om.pyo', 'factory.pyo', 'nmea.pyo', '__init__.pyo','ubx.py', 'factory.py', 'gpsdevice.pyo'] 2009.03.16 23:06:54 ogpsdWARNING (could not write to '/sys/bus/platform/devices/neo1973-pm-gps.0/power_on': [Errno 2] No such file or directory:'/sys/bus/platform/devices/neo1973-pm-gps.0/power_on') 2009.03.16 23:06:54 ogpsdWARNING (could not write to '/sys/bus/platform/devices/neo1973-pm-gps.0/power_on': [Errno 2] No such file or directory:'/sys/bus/platform/devices/neo1973-pm-gps.0/power_on') Looks good. FSO supports two kernel versions with two different sysfs paths, so one will always be missing. 2009.03.16 23:06:54 frameworkd.persist ERRORno persist data for subsystem ogpsd No problem, it will be generated next time. Daniel, should we turn this into an INFO rather than an ERROR? 2009.03.16 23:06:55 ogspd.gpsdevice INFO GTA02Device initialized. Serving org.freedesktop.Gypsy at /org/freedesktop/Gypsy 2009.03.16 23:06:55 frameworkd.subsystem INFO subsystem ogpsd took 6.78 seconds to startup It's successfully up. 2009.03.16 23:08:37 ogspd.gpsdevice INFO disabling It's disabling the hardware to synchronize the hardware status with the logic status (power off by default). 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:37 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:38 ogpsdWARNING Attempted to send something while serial is not open. 2009.03.16 23:08:38 ogpsdWARNING Attempted to send something while serial is not open. It's sending commands to shut it down, in case it was online previously (which we don't know on first start, since something else could have run before). 2009.03.16 23:08:38 ogpsdWARNING (could not write to '/sys/bus/platform/devices/neo1973-pm-gps.0/power_on': [Errno 2] No such file or directory:'/sys/bus/platform/devices/neo1973-pm-gps.0/power_on') 2009.03.16 23:09:09 ogspd.gpsdevice INFO enabling 2009.03.16 23:09:09 ogpsdWARNING (could not write to '/sys/bus/platform/devices/neo1973-pm-gps.0/power_on': [Errno 2] No such file or directory:'/sys/bus/platform/devices/neo1973-pm-gps.0/power_on') same failure.. :( No failure -- see above. Device should be up and running now. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR/FSO] - GPS - no fix, ogpsd.pickle question
Hi! I'm running latest SHR unstable distribution and there is no way I can get gps fix. 1. System time and timezone are set correctly. 2. ogps.pickle removed. 3. Phone restarted. Still no fix. I even tried to reflash phone to om 2008.08 distro - Locations application can get my GPS position. When I'm back to SHR - no fix. I'm checking for fix with Zhone to 'cut the middle-man' and be sure it's gps, not fso-gpsd or any other problem. So shortly after I launch Zhone and press 'gps' button I see in terminal: Requested debug packet NAV-SVINFO gps fix status changed: 1 #it can't be real fix, because it happens in a few seconds gps got ubxdebug packet gps got ubxdebug packet # to infinity and beyond Please notice, that this test was made in the same exact location with an external antenna at approximately same time with om 2008.8 distro and SHR unstable with (2.6.28 kernel). I know a lot of people have problems with GPS in SHR Unstable, so it would be beneficial for all of us to find the problem. Can someone point me to low-level stuff I should check to get to the bottom of this? Leonti ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR/FSO] - GPS - no fix, ogpsd.pickle question
Since my update of yesterday evening I have successfully obtain a fix (and /etc/init.d/fso-gpsd stop rm ogps.pickle reboot) Try to do the update :if it works it was a regression, if not it confirms another problem, getting a fix is very tricky. Best regards, Xavier ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
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 40.000 lines -- i cannot check them all for maybe private information (should be none, but who knows), so i won't attach it publicly viewable. shall send it to you as pm? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
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 when rebooted and i do not always have a ntp source available to sync. wasn't there recently something about fso feeding the u-blox data on startup and that the data needs to match time and so on? then this routine needs to be more tolerant. Feeding GPS with correct data about recent sat positions isn't something you can make more tolerant. Either the GPS knows where to look for the sats (due to accurate data being supplied by AGPS), or it needs to scan all possibilities to find where to get an actual signal (which may take quite a while). cheers jOERG [[position and where used herein as a synonym for frequency/channel. Though the position in space also needs to be known to calculate exact GPS-data]] signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
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 fallback to scanning instead of solely relying on agps. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
...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 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 fallback to scanning instead of solely relying on agps. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
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 feeding routine has to be more tolerant, ie issue a fallback to scanning instead of solely relying on agps. AGPS is *not* disabling normal non-A operation of GPS (means there is no need for a paricular fallback scheme - GPS starts and operates in fallback-mode all the time, A just updates a few variables more quickly than the GPS-chip would do anyway, so the chip finds his channels/sats/fix. Even if we would write completely bogus info to the chip, it wouldn't be worse off than without AGPS and starting on default values. btw: It seems to me as if 3 minutes difference in time shouldn't make any trouble. cheers jOERG signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
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. 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 that means -- and according to the git ogpsd wasn't changed for more than a month now, so downgrading seems not really sensible. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
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 that means -- and according to the git ogpsd wasn't changed for more than a month now, so downgrading seems not really sensible. Daniel asked for a _complete_ log just 3 hours after the initial bug report (Ticket #265). But no answer until now... Greetings, Sascha ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
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 I'll stick something on. On Thursday 27 November 2008 09:45:48 [EMAIL PROTECTED] wrote: 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 it again, then I enabled logging and reported on my findings. Anyone got any pointers ? I'm a bit of a noob with the freerunner though I've been sysadmining on Linux for, um, more years than I care to remember :-) On Tuesday 25 November 2008 22:13:08 Julien Cassignol wrote: 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. -- Antony King - 01908 268 901 Systems Consultant SolutionTrax Technologies - http://www.solutiontrax.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
Yesterday I flashed the latest SHR image and the problem has disappeared, everything is working fine again. I don't know where the problem was as before flashing I was doing an opkg update/upgrade everyday and the issue was still there. ant wrote: 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 it again, then I enabled logging and reported on my findings. Anyone got any pointers ? I'm a bit of a noob with the freerunner though I've been sysadmining on Linux for, um, more years than I care to remember :-) On Tuesday 25 November 2008 22:13:08 Julien Cassignol wrote: 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. -- Antony King - 01908 268 901 Systems Consultant SolutionTrax 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--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
Re: [Debian -FSO -GPS] No Fix
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 it again, then I enabled logging and reported on my findings. Anyone got any pointers ? I'm a bit of a noob with the freerunner though I've been sysadmining on Linux for, um, more years than I care to remember :-) On Tuesday 25 November 2008 22:13:08 Julien Cassignol wrote: 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. -- Antony King - 01908 268 901 Systems Consultant SolutionTrax Technologies - http://www.solutiontrax.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
this seems to a debian thread, no? i still have no gps fix, neither the number of satellites after the upgrading of fso on my debian... this is very annoying! any hints? logs needed? d On Thu, Nov 27, 2008 at 11:17 AM, glownan [EMAIL PROTECTED] wrote: Yesterday I flashed the latest SHR image and the problem has disappeared, everything is working fine again. I don't know where the problem was as before flashing I was doing an opkg update/upgrade everyday and the issue was still there. ant wrote: 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 it again, then I enabled logging and reported on my findings. Anyone got any pointers ? I'm a bit of a noob with the freerunner though I've been sysadmining on Linux for, um, more years than I care to remember :-) On Tuesday 25 November 2008 22:13:08 Julien Cassignol wrote: 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. -- Antony King - 01908 268 901 Systems Consultant SolutionTrax 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--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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
For me setting the corect timezone (/etc/localtime) and time (ntpdate) solved the gps problem. 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. -- View this message in context: http://n2.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
Re: [Debian -FSO -GPS] No Fix
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 source available to sync. wasn't there recently something about fso feeding the u-blox data on startup and that the data needs to match time and so on? then this routine needs to be more tolerant. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
... updated debian and now sephora is not working and no gps fix... very annoying d On Thu, Nov 20, 2008 at 11:06 AM, Sascha Wessel [EMAIL PROTECTED] wrote: 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 Messages like this: $GPRMC,073904.00,A,5127.73160,N,00651.01957,E,0.229,279.62,201108,,,A*6 6 $GPVTG,279.62,T,,M,0.229,N,0.424,K,A*3E $GPGGA,073904.00,5127.73160,N,00651.01957,E,1,09,0.92,26.1,M,47.5,M,,*6 E $GPGSA,A,3,05,04,09,29,12,30,02,14,321.49,0.92,1.17*07 $GPGSV,3,1,11,05,78,276,25,17,03,039,,04,21,068,32,09,48,135,28*7A $GPGSV,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. Restart and then please do not read/write from/to /dev/ttySAC1. For further informations, search the ml archives... Greetings, Sascha ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Antony King - 01908 268 901 Systems Consultant SolutionTrax 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--No-Fix-tp1521077p1578295.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
Re: [Debian -FSO -GPS] No Fix
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. -- Julien Cassignol http://www.ainulindale.net ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
Ummm, Looks like that is not the problem, gpsd is not installed and fso-gpsd is. This is what I got when tried to uninstall/install gpsd/fso-gpsd [EMAIL PROTECTED] ~ $ opkg remove --force-depends gpsd No packages removed. [EMAIL PROTECTED] ~ $ opkg install fso-gpsd Package fso-gpsd (0.7+gitr25+d10a69e11287a8f7a6477ad9c31d53ce18be9a8f-r1.1) installed in root is up to date. Does someone know what the meaning of that Exception 0x8040 was trapped ! message is? It is received soon after the gps chip is powered on by ogpsd and the almanac data is uploaded to the gps chip. Don't know if it is related to this problem. This is the whole message where it appears 2008.11.25 22:55:46 ogpsdDEBUGDiscarded data not UBX '\n$GPTXT,' 2008.11.25 22:55:46 ogpsdDEBUGDiscarded data not UBX '01,01,00' 2008.11.25 22:55:46 ogpsdDEBUGDiscarded data not UBX ',Excepti' 2008.11.25 22:55:46 ogpsdDEBUGDiscarded data not UBX 'on 0x800' 2008.11.25 22:55:46 ogpsdDEBUGDiscarded data not UBX '00040 wa' 2008.11.25 22:55:46 ogpsdDEBUGDiscarded data not UBX 's trappe' 2008.11.25 22:55:46 ogpsdDEBUGDiscarded data not UBX 'd !*7E\r\n' Julien Cassignol wrote: 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. -- Julien Cassignol http://www.ainulindale.net ___ 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--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
Re: [Debian -FSO -GPS] No Fix
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:
Nov 24 14:44:45 om-gta02 user.info 2008.11.24 14:44:45 ogpsdINFO
enabling
Nov 24 14:44:45 om-gta02 user.debug 2008.11.24 14:44:45 ogpsdDEBUG
(writing '1'
to
'/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron')
Nov 24 14:44:45 om-gta02 user.debug 2008.11.24 14:44:45 ogpsdDEBUG
Sending UBX packet of type CFG-SBAS: {'usage': 7, 'scanmode': 0, 'mode':
1, 'maxsbas': 3}
Nov 24 14:44:45 om-gta02 user.debug 2008.11.24 14:44:45 ogpsdDEBUG
Sending UBX packet of type CFG-PRT: []
followed by some almenac data and then this interesting snippet:
Nov 24 14:44:48 om-gta02 user.debug 2008.11.24 14:44:48 ogpsdDEBUG
Discarded data not UBX '$GPTXT,01,01,02,u-blox '
Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
Discarded data not UBX 'ag - www.u-blox.com*50\r\n'
Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
Discarded data not UBX '$GPTXT,01,01,02,ANTARIS ATR062x HW
80040001*26\r\n$GPTXT,01,01,02,ROM CORE 5.00Jan 09 20'
Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
Discarded data not UBX '06 12:00:00*76\r\n'
Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
Discarded data not UBX '$GPTXT,01,01,02,'
Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
Discarded data not UBX 'LIC 1EBF'
Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
Discarded data not UBX '-BD07-E8'
Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
Discarded data not UBX '3D-6BE1-'
Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
Discarded data not UBX '0F7A*50\r'
Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
Discarded data not UBX '\n$GPTXT,'
Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
Discarded data not UBX '01,01,00'
Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
Discarded data not UBX ',Excepti'
Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
Discarded data not UBX 'on 0x800'
Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
Discarded data not UBX '00040 was trappe'
Nov 24 14:44:49 om-gta02 user.debug 2008.11.24 14:44:49 ogpsdDEBUG
Discarded data not UBX 'd !*7E\r\n'
On Saturday 22 November 2008 09:24:55 Davide Scaini wrote:
I have the same problem... updated debian and now sephora is not working
and no gps fix... very annoying
d
On Thu, Nov 20, 2008 at 11:06 AM, Sascha Wessel [EMAIL PROTECTED] wrote:
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 Messages like this:
$GPRMC,073904.00,A,5127.73160,N,00651.01957,E,0.229,279.62,201108,,,A*6
6 $GPVTG,279.62,T,,M,0.229,N,0.424,K,A*3E
$GPGGA,073904.00,5127.73160,N,00651.01957,E,1,09,0.92,26.1,M,47.5,M,,*6
E $GPGSA,A,3,05,04,09,29,12,30,02,14,321.49,0.92,1.17*07
$GPGSV,3,1,11,05,78,276,25,17,03,039,,04,21,068,32,09,48,135,28*7A
$GPGSV,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.
Restart and then please do not read/write from/to /dev/ttySAC1.
For further informations, search the ml archives...
Greetings,
Sascha
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
--
Antony King - 01908 268 901
Systems Consultant
SolutionTrax Technologies - http://www.solutiontrax.com
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
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 minutes I got Messages like this: $GPRMC,073904.00,A,5127.73160,N,00651.01957,E,0.229,279.62,201108,,,A*66 $GPVTG,279.62,T,,M,0.229,N,0.424,K,A*3E [...] but still no fix this morning. [...] I am not sure that I follow. The 'A' in the third field above indicates valid autonomous GPRMC data, i.e., you do have a fix. Regards, Gora ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
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 Messages like this: $GPRMC,073904.00,A,5127.73160,N,00651.01957,E,0.229,279.62,201108,,,A*66 $GPVTG,279.62,T,,M,0.229,N,0.424,K,A*3E $GPGGA,073904.00,5127.73160,N,00651.01957,E,1,09,0.92,26.1,M,47.5,M,,*6E $GPGSA,A,3,05,04,09,29,12,30,02,14,321.49,0.92,1.17*07 $GPGSV,3,1,11,05,78,276,25,17,03,039,,04,21,068,32,09,48,135,28*7A $GPGSV,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. Restart and then please do not read/write from/to /dev/ttySAC1. For further informations, search the ml archives... Greetings, Sascha ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Debian -FSO -GPS] No Fix
Hallo, I updated my Debian today with apt-get update and apt-get dist-upgrade. The update switched some FSO related files. I think to FSO M4. After the update some strange things happend. The first thing is, that the openmoko-panel-plugin is removed because it is linked to frameworkd. But the most important thing for me is, that after the update i get no gps fix anymore. fso-gpsd is installd and running. The zhone build in gps application an tango gps get no fix. tail -f /dev/ttySAC1 shows nothing, telnet localhost gps connects but shows on pa input only debian-gta02:~# telnet localhost 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 the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
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 http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
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 Messages like this: $GPRMC,073904.00,A,5127.73160,N,00651.01957,E,0.229,279.62,201108,,,A*66 $GPVTG,279.62,T,,M,0.229,N,0.424,K,A*3E $GPGGA,073904.00,5127.73160,N,00651.01957,E,1,09,0.92,26.1,M,47.5,M,,*6E $GPGSA,A,3,05,04,09,29,12,30,02,14,321.49,0.92,1.17*07 $GPGSV,3,1,11,05,78,276,25,17,03,039,,04,21,068,32,09,48,135,28*7A $GPGSV,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. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[FSO] GPS-problems / tangogps in testing-feed broken
Hi,
(I'm mailing to this list because I don't know where to post bug reports
targetting the package-management in the fso-{testing,unstable}-feeds.
Is trac.freesmartphone.org the right place?)
My problem: I'm experiencing problems with GPS since an upgrade with the
fso-testing-feed.
After the upgrade neither tangogps (tangogps-fso_0.9.2-r1) nor zhone
(0.0.0+gitr69e029bd85a1caaad4e5d61087836a8e1ea20dcc-r8) are getting a
fix which hadn't been such a problem before (same outdoors place as
before, rather grey weather conditions but not entirely clouded, 30 mins
waiting).
One problem definitely is that tangogps throwing two TypeErrors which
show that it's having trouble with the dbus-interface[1].
Has there been a change in the dbus-interface which hasn't been followed
in the packages? Is this part of the yesterday on this list mentioned
major frameworkd changes[3]? If yes: How comes they're in the
testing-feed (would expect them in unstable, if at all)?
zhone only tells gps ok[2], so I don't know if it's suffering from the
same problem or just having a bad time with the available gps data.
As the weather is quite bad ATM, I cannot debug further. It might also
be that zhone and agpsui (didn't know there's a fso-compatible version
until a few minutes ago) would show a fix once the sky is clear again
(probably next april... :/), but the tangogps-error probably should be
taken care of.
Anybody else having problems?
Thanks and Greetings,
/Ben
[1]
** (tangogps:1439): WARNING **: Cannot get position: Traceback
(most recent call last):
File /usr/lib/python2.5/site-packages/dbus/service.py, line 745, in
_message_cb
_method_reply_return(connection, message, method_name, signature, *retval)
File /usr/lib/python2.5/site-packages/dbus/service.py, line 252, in
_method_reply_return
reply.append(signature=signature, *retval)
TypeError: More items found in D-Bus signature than in Python arguments
** (tangogps:1439): WARNING **: Cannot get accuracy: Traceback (most recent
call last):
File /usr/lib/python2.5/site-packages/dbus/service.py, line 745, in
_message_cb
_method_reply_return(connection, message, method_name, signature, *retval)
File /usr/lib/python2.5/site-packages/dbus/service.py, line 252, in
_method_reply_return
reply.append(signature=signature, *retval)
TypeError: More items found in D-Bus signature than in Python arguments
[2]
DEBUG gps ok: Interface ProxyObject wrapping dbus._dbus.SystemBus (system)
at 0x12cf90 :1.3 /org/freedesktop/Gypsy at 0x12f930 implementing
'org.freedesktop.Gypsy.Accuracy' at 0x12fb30, Interface ProxyObject wrapping
dbus._dbus.SystemBus (system) at 0x12cf90 :1.3 /org/freedesktop/Gypsy at
0x12f930 implementing 'org.freedesktop.Gypsy.Position' at 0x12fc30,
Interface ProxyObject wrapping dbus._dbus.SystemBus (system) at 0x12cf90
:1.3 /org/freedesktop/Gypsy at 0x12f930 implementing
'org.freedesktop.Gypsy.Satellite' at 0x12fd30
[3]
Message-ID: [EMAIL PROTECTED]
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO] GPS-problems / tangogps in testing-feed broken
Hello,
On Fri, Aug 22, 2008 at 8:51 PM, Benito Torres [EMAIL PROTECTED] wrote:
Hi,
(I'm mailing to this list because I don't know where to post bug reports
targetting the package-management in the fso-{testing,unstable}-feeds.
Is trac.freesmartphone.org the right place?)
My problem: I'm experiencing problems with GPS since an upgrade with the
fso-testing-feed.
FWIW, I am running FSO-testing on my Neo 1973 (not the FreeRunner). I
am using an external antenna, and have verified that it is workng on
my FreeRunner (which doesn't run FSO).
Since this is a 1973, I have installed gllin[1], and dbus-monitor
shows that gps events are sent:
[EMAIL PROTECTED]:~# dbus-monitor --system
signal sender=org.freedesktop.DBus - dest=:1.9
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus;
member=NameAcquired
string :1.9
signal sender=:1.3 - dest=(null destination) path=/org/gpsd;
interface=org.gpsd; member=fix
double nan
int32 1
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
signal sender=:1.3 - dest=(null destination) path=/org/gpsd;
interface=org.gpsd; member=fix
double nan
int32 1
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
And the output from gpsd shows that it gets a fix:
[EMAIL PROTECTED]:~# cat /tmp/nmeaNP | grep GPRMC
$GPRMC,212405.00,A,5955.147356,N,01045.531408,E,000.0,000.0,220808,,,A*5B
$GPRMC,212406.00,A,5955.147356,N,01045.531408,E,000.0,000.0,220808,,,A*58
$GPRMC,212407.00,A,5955.147356,N,01045.531408,E,000.0,000.0,220808,,,A*59
$GPRMC,212408.00,A,5955.147356,N,01045.531408,E,000.0,000.0,220808,,,A*56
$GPRMC,212410.00,A,5955.147356,N,01045.531408,E,000.0,000.0,220808,,,A*5F
$GPRMC,212412.00,A,5955.147356,N,01045.531408,E,000.0,000.0,220808,,,A*5D
$GPRMC,212413.00,A,5955.148148,N,01045.532991,E,000.0,000.0,220808,,,A*50
$GPRMC,212414.00,A,5955.148405,N,01045.532836,E,000.0,000.0,220808,,,A*57
$GPRMC,212415.00,A,5955.148596,N,01045.532664,E,000.0,000.0,220808,,,A*54
$GPRMC,212416.00,A,5955.148760,N,01045.532491,E,000.0,000.0,220808,,,A*54
$GPRMC,212417.00,A,5955.148760,N,01045.532491,E,000.0,000.0,220808,,,A*55
$GPRMC,212419.00,A,5955.148760,N,01045.532491,E,000.0,000.0,220808,,,A*5B
$GPRMC,212421.00,A,5955.149661,N,01045.531970,E,000.0,000.0,220808,,,A*50
$GPRMC,212422.00,A,5955.149853,N,01045.531870,E,000.0,000.0,220808,,,A*5D
$GPRMC,212423.00,A,5955.150058,N,01045.531689,E,000.0,000.0,220808,,,A*5F
$GPRMC,212424.00,A,5955.150058,N,01045.531689,E,000.0,000.0,220808,,,A*58
$GPRMC,212425.00,A,5955.150058,N,01045.531689,E,000.0,000.0,220808,,,A*59
$GPRMC,212426.00,A,5955.150058,N,01045.531689,E,000.0,000.0,220808,,,A*5A
$GPRMC,212427.00,A,5955.150883,N,01045.531326,E,000.0,000.0,220808,,,A*55
Nut neither zhone nor tangoGPS gets anything, not even time from the gps.
References:
1) http://wiki.openmoko.org/wiki/Gllin
--
Regards,
Torfinn Ingolfsen
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO] GPS-problems / tangogps in testing-feed broken
Hi, On Fri, Aug 22, 2008 at 23:27 (+0200), Torfinn Ingolfsen wrote: signal sender=:1.3 - dest=(null destination) path=/org/gpsd; interface=org.gpsd; member=fix I don't see this kind of message. Maybe that's due to different daemon-implementations on different hardware? Also all dbus-paths start with /org/freesmartphone/ here. Anyway I'm sure this is an application/dbus-problem as in the meantime I ran agpsui successfully: 90 seconds for the first fix. But even after agpsui having a fix, zhone is still clueless -- which can be explained by agpsui parsing ttySAC1 directly. (Interesstingly I can start and stop gpsd to my pleasure without any changes for agpsui or zhone. What's gpsd for, anyway?) Manually asking Gypsy via dbus reveals, that the dbus-interface is broken as it prints the same message that tangogps reported: dbus-send --system --print-reply --dest=org.freesmartphone.ogpsd /org/freedesktop/Gypsy org.freedesktop.Gypsy.Position.GetPosition Error org.freedesktop.DBus.Python.TypeError: Traceback (most recent call last): File /usr/lib/python2.5/site-packages/dbus/service.py, line 745, in _message_cb _method_reply_return(connection, message, method_name, signature, *retval) File /usr/lib/python2.5/site-packages/dbus/service.py, line 252, in _method_reply_return reply.append(signature=signature, *retval) TypeError: More items found in D-Bus signature than in Python arguments Other methods like GetAccuracy fail, too, while GetSatellites successfully returns an empty array and GetConnectionStatus returns 1. Could anybody with more insights to the frameworkd/dbus-development shed some light on this? Is this a known problem? Should we simply wait for the next package? Thanks, /Ben ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
