Re: can't sync with Tungsten T2

Hey Darren,

You could try loading gpilotd from a console, so you can see any error 
messages.

To do that, first remove the sync applet from the task bar. Then open a 
terminal and run gpilotd (it could be /usr/libexec/gpilotd or 
/usr/bin/gpilotd) then press the sync button.

That might provide some useful errors.

Cheers,


Callum.

daz wrote:
> I've just recently installed Ubuntu 7.04 from a downloaded CD image.
> I'm running on an IBM A31 laptop.
> Gnome-Pilot-Applet is 2.0.15
>
> I've been unable to sync my Palm Tungsten T2 via the USB port. It just
> freezes completely and requires a soft reset to come back to life (even
> the light that indicates that its charging stays on!).
>
> I've added visor to /etc/modules as advised in one of the forum items
> and rebooted.
> I've run the modprobe -l  and can see that visor has been loaded.
>
> When I plug it in via the USB port it can be seen.
> >From syslog:
>
> Aug 18 18:44:40 daz-laptop kernel: [ 3780.584000] usb 2-2.3: new full
> speed USB device using uhci_hcd and address 5
> Aug 18 18:44:40 daz-laptop kernel: [ 3780.704000] usb 2-2.3:
> configuration #1 chosen from 1 choice
> Aug 18 18:44:40 daz-laptop kernel: [ 3780.708000] visor 2-2.3:1.0:
> Handspring Visor / Palm OS converter detected
> Aug 18 18:44:40 daz-laptop kernel: [ 3780.708000] usb 2-2.3: Handspring
> Visor / Palm OS converter now attached to ttyUSB0
> Aug 18 18:44:40 daz-laptop kernel: [ 3780.708000] usb 2-2.3: Handspring
> Visor / Palm OS converter now attached to ttyUSB1
>
> from /dev:
>
> daz@daz-laptop:~$ ls -l /dev/ttyUS*
> crw-rw-r-- 1 root dialout 188, 0 2007-08-18 18:44 /dev/ttyUSB0
> crw-rw-r-- 1 root dialout 188, 1 2007-08-18 18:44 /dev/ttyUSB1
> daz@daz-laptop:~$ ls -l /dev/pilot
> lrwxrwxrwx 1 root root 7 2007-08-18 18:44 /dev/pilot -> ttyUSB1
>
> gpilotd recognises the palm and has its ID, my name etc, and has created
> the target directories for the sync.
>
> I am able to sync with win XP at the office no problems.
>
> Once after a sync with XP I tried a sync here with only the address
> conduit enabled and it succeeded. However I've not been able to perform
> any type of sync again.
>
> What should I do next?
> What other diagnostics/traces can I run to provide more data?
>
> Darren
>
> _______________________________________________
> gnome-pilot-list mailing list
> [email protected]
> http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
>
>
>