It's somewhat unusual to see gnome-pilot failing when pilot-link is reliable (especially in this way, which seems to be in the initial handshake with the PDA).
Here are a few things to try:
1. Run pilot-xfer with a '-t 2' option. (This does the handshake in a way more
like gnome-pilot).
2. Run gnome-pilot with a timeout setting of zero (edit the device using the
control applet, under the 'Devices' tab). This does the handshake more
like the way pilot-xfer does by default.
There's a slight chance that (1) will lock up your device and (2) will magically fix the problem, but I don't hold out great hope. Worth checking out, though.
If that doesn't fix things, next:
3. Run gpilotd from a terminal, and enable the following pilot-link
environment variables to get extra debugging. Then send us
the output: PILOT_DEBUG="DEV SLP CMP PADP NET SOCK" PILOT_DEBUG_LEVEL="DEBUG"
And finally a possible workaround to help you get syncing while we get to the bottom of this:
4. We can use pi-nredir to redirect the pda connection to the network,
and configure a network sync in gnome-pilot. First configure
your PDA. On my PalmOS5 device it goes like this:
a. specify 'Local' hotsync.
b. edit hotsync 'LANsync preferences' and specify 'LANSync' instead
of 'Local HotSync'.
c. edit 'Primary PC Setup' in hotsync preferences, and specify '!!' as
the primary PC name, specify the IP address of the machine where
you'll run gnome-pilot in the 'Primary PC Address' box -- 127.0.0.1
would be fine if you're on the same machine as your usb cable.
d. enter an appropriate subnet mask. 255.255.255.0 will probably do
fine.
Now, open the gnome-pilot configuration applet, and delete your USB
device and create a 'Network' device.
Finally, press hotsync on your PDA and quickly run pi-nredir from a
terminal window:
> pi-nredir -p /dev/pilot
---- or '-p /dev/ttyUSBx', whatever you use.
If all goes well, pi-nredir should redirect the incoming USB connection
to the network and gnome-pilot should connect.
It's somewhat unusual to see gnome-pilot failing when pilot-link is reliable (especially in this way, which seems to be in the initial handshake with the PDA).
Here are a few things to try:
1. Run pilot-xfer with a '-t 2' option. (This does the handshake in a way more
like gnome-pilot).
2. Run gnome-pilot with a timeout setting of zero (edit the device using the
control applet, under the 'Devices' tab). This does the handshake more
like the way pilot-xfer does by default.
There's a slight chance that (1) will lock up your device and (2) will magically fix the problem, but I don't hold out great hope. Worth checking out, though.
If that doesn't fix things, next:
PILOT_ DEBUG=" DEV SLP CMP PADP NET SOCK"
PILOT_ DEBUG_LEVEL= "DEBUG"
3. Run gpilotd from a terminal, and enable the following pilot-link
environment variables to get extra debugging. Then send us
the output:
And finally a possible workaround to help you get syncing while we get to the bottom of this:
4. We can use pi-nredir to redirect the pda connection to the network,
and configure a network sync in gnome-pilot. First configure
your PDA. On my PalmOS5 device it goes like this:
a. specify 'Local' hotsync.
b. edit hotsync 'LANsync preferences' and specify 'LANSync' instead
of 'Local HotSync'.
c. edit 'Primary PC Setup' in hotsync preferences, and specify '!!' as
the primary PC name, specify the IP address of the machine where
you'll run gnome-pilot in the 'Primary PC Address' box -- 127.0.0.1
would be fine if you're on the same machine as your usb cable.
d. enter an appropriate subnet mask. 255.255.255.0 will probably do
fine.
Now, open the gnome-pilot configuration applet, and delete your USB
device and create a 'Network' device.
Finally, press hotsync on your PDA and quickly run pi-nredir from a
terminal window:
> pi-nredir -p /dev/pilot
---- or '-p /dev/ttyUSBx', whatever you use.
If all goes well, pi-nredir should redirect the incoming USB connection
to the network and gnome-pilot should connect.