| Art Alexion on 3 Nov 2006 16:07:57 -0000 |
|
On Thursday 02 November 2006 21:41, Jeff Abrahamson wrote: > I upgrade && dist-upgrade. Now jpilot won't sync. I can't find any > relevant bugs against jpilot, so I submitted one (396751). In the > mean time: > > I tell jpilot to sync, hit the button on the cradle, the handheld starts > to do its thing, then says the communication was cut. Meanwhile > jpilot is still waiting. I can cat from the port that jpilot is using > (/dev/ttyS0) and see the garbage that says I can read the port and > that the handheld is writing to it. Jpilot eventually gives up with > a connection error. > > dlp_ReadSysInfo error > Exiting with status SYNC_ERROR_PI_CONNECT > Finished > > Any thoughts on what might be happening? Anyone aware of any other > issues that might be coming into play. I also upgraded kernel 2.6.16 > --> 2.6.17, for example. Can you connect directly with pilot-xfer? -- _____________________________________________________________ Art Alexion PGP fingerprint: 52A4 B10C AA73 096F A661 92D2 3B65 8EAC ACC5 BA7A Keyserver: hkp://subkeys.pgp.net The attachment - signature.asc - is my electronic signature; no need for alarm. Info @ http://mysite.verizon.net/art.alexion/encryption/signature.asc.what.html _____________________________________________________________ Attachment:
pgpxjEgqKtIJc.pgp ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|