pilot-xfer can not connect to treo 650 in FC4

[philippo]

Hi,

I've got a completely updated (kernel 2.6.11-1.1366_FC4, only standard RH repositories) FC4 install on my Dell C400 laptop (pIII 1.2Ghz, 512m RAM). I have never been able to sync my treo, or even do a simple backup with pilot-xfer.

Everything starts out looking OK - USB works (I use a USB keyboard/mouse most of the time), and when I have initiated the sync on the treo I can see it:

[root@chucky ~]# lsusb
Bus 003 Device 002: ID 0830:0061 Palm, Inc.
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 002: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

And output from /var/log/messages looks good:

May 31 13:15:37 chucky kernel: usb 3-2: new full speed USB device using uhci_hcd and address 2
May 31 13:15:40 chucky kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
May 31 13:15:40 chucky kernel: usbcore: registered new driver usbserial_generic
May 31 13:15:40 chucky kernel: usbcore: registered new driver usbserial
May 31 13:15:40 chucky kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
May 31 13:15:40 chucky kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OSMay 31 13:15:40 chucky kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5
May 31 13:15:40 chucky kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 5.0
May 31 13:15:40 chucky kernel: visor 3-2:1.0: Handspring Visor / Palm OS converter detected
May 31 13:15:40 chucky kernel: usb 3-2: Handspring Visor / Palm OS converter now attached to ttyUSB0
May 31 13:15:40 chucky kernel: usb 3-2: Handspring Visor / Palm OS converter now attached to ttyUSB1
May 31 13:15:40 chucky kernel: usbcore: registered new driver visor
May 31 13:15:40 chucky kernel: drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver v2.1

However, pilot-xfer cannot communicate with the device over /dev/ttyUSB0 or /dev/ttyUSB1 - it errors:

[root@chucky ~]# pilot-xfer -b /home/philip/treo -p /dev/ttyUSB1

Listening to port: /dev/ttyUSB1

Please press the HotSync button now...
Error accepting data on /dev/ttyUSB1

Or just hangs (on ttyUSB0). Eventually the Treo times out and disconnects thusly:
May 31 13:17:48 chucky kernel: usb 3-2: USB disconnect, address 2
May 31 13:17:48 chucky kernel: visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0
May 31 13:17:48 chucky kernel: visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1
May 31 13:17:48 chucky kernel: visor 3-2:1.0: device disconnected

Attempting to do this via gpilot-applet results in gpilotd repeadedly crashing out underneath it, but that's a whole otehr story.

any ideas?

[fozz]

I've got the same symptoms. I can get kpilot to do a backup... but no sync.

[LinuxHippy]

Make a file (if it doesn't exist) called ~/bash_profile and add this:

export PILOTPORT=/dev/pilot
export PILOTRATE=115200

Then link your usb to /dev/pilot:

ln -s /dev/ttyUSB1 /dev/pilot

Then I used chmod 0666 /dev/pilot as root so that any user would have full use of my pilot.

I use a Palm VIIx on ttyS0 or ttyS1 and this works. For some odd reason my soundcard conflicts with the speed of my hotsync and results in it not connecting to my pc. I've had to use a slower speed on my 1 pc. I think I use:

export PILOTRATE=9200

in ~/bash_profile

You'll need to logout of your account and then back in.

test with pilot-xfer -l

[LinuxHippy]

Make a file (if it doesn't exist) called ~/bash_profile and add this:

export PILOTPORT=/dev/pilot
export PILOTRATE=115200

Then link your usb to /dev/pilot:

ln -s /dev/ttyUSB1 /dev/pilot

Then I used chmod 0666 /dev/pilot as root so that any user would have full use of my pilot.

I use a Palm VIIx on ttyS0 or ttyS1 and this works. For some odd reason my soundcard conflicts with the speed of my hotsync and results in it not connecting to my pc. I've had to use a slower speed on my 1 pc. I think I use:

export PILOTRATE=9200

in ~/bash_profile

You'll need to logout of your account and then back in.

test with pilot-xfer -l

I found this thread: http://www.fedoraforum.org/forum/showthread.php?t=23565&highlight=udev+pilot