PalmOS syncing (Ubuntu)
 

Having some difficulty syncing my new Palm m515 with ubuntu. Been playing with gpilot/kpilot to no avail.

Found something that could possibly be useful,
if I run a pilot-xfer -p /dev/ttyUSB1 -l
it gives me the error that /dev/ttyUSB1 doesn't exist (which it doesn't), however, if I hit the "sync" button on the palm first, it will create /dev/ttyUSB1. Once created, if I run the above command, it latches to the correct device, and then sits there, waiting for me to hit "sync" on the device (which I already did, to make it create the devices in the first place).

Its a catch-22 it seems, I have to hit "sync" to create the devices, but I have to hit "sync" after the devices are created to start the sync.

Any ideas?

First make sure g/KPilot is set to communicate with the appropriate device, either ttyUSB0 or ttyUSB1. Then after pressing sync on the m515 (which makes /dev/ttyUSBx appear) check the permissions on it to make sure your user can read/write, either by making it 0666 or adding your user to the group that owns it. After that it should be start syncing after just pressing the button on the m515. I haven't used gpilot, but that's how KPIlot works for me.

If you're using a 2.6 kernel with udev I recommend making a rule to setup the device with 0666 permissions upon connection.

i've found this is a timing issue. gpilotd for some reason on my machine seems immune to it, but using kpilot or pilot-xfer you need to:
1) connect the usb, verify where it's attached (it likes to randomly reset to USB3/5/7 etc sometimes). dmesg for me shows 2 connections, ttyUSB0/1, or 2/3, or 4/5, etc. use the highest number (eg ttyUSB1, not ttyUSB0).
2) hit the hotsync button on the palm. wait for it to say "connecting..."
3) execute kpilot or pilot-xfer.
with kpilot i need to start it with the connection set to somewhere where the palm ISN'T, like ttyUSB12; otherwise it automatically attempts to connect and screws everything up. i've posted elsewhere on this if this isn't clear. hth.