On Thu, 2007-08-23 at 17:49 -0400, Pete Holsberg wrote:
Aug 23 17:46:15 linux kernel: [117701.459636] usb 2-1: USB
disconnect,
address 57
Aug 23 17:46:15 linux kernel: [117701.459940] visor ttyUSB0:
Handspring
Visor / Palm OS converter now disconnected from ttyUSB0
Aug 23 17:46:15 linux kernel: [117701.460038] visor ttyUSB1:
Handspring
Visor / Palm OS converter now disconnected from ttyUSB1
Aug 23 17:46:15 linux kernel: [117701.460058] visor 2-1:1.0: device
disconnected
Aug 23 17:46:16 linux kernel: [117702.218275] usb 2-1: new full speed
USB device using uhci_hcd and address 58
Aug 23 17:46:16 linux kernel: [117702.391552] usb 2-1: configuration
#1
chosen from 1 choice
Aug 23 17:46:16 linux kernel: [117702.396452] visor 2-1:1.0:
Handspring
Visor / Palm OS converter detected
Aug 23 17:46:16 linux kernel: [117702.396839] usb 2-1: Handspring
Visor
/ Palm OS converter now attached to ttyUSB0
Aug 23 17:46:16 linux kernel: [117702.396954] usb 2-1: Handspring
Visor
/ Palm OS converter now attached to ttyUSB1
The above snippet looks suspisciously like it connects, disconnects,
then reconnects again... I wonder if this is Yet Aother Palm where they
try to be sneaky with that "Drive Mode" garbage.
Try this... disconnect your Palm, hit HotSync, count to 4, then connect
the cable, and *THEN* launch your pilot-xfer or pilot-dlpsh command
against either /dev/ttyUSB0 or /dev/ttyUSB1. You'll have to play around
with both of them to figure out which one is the right port for your
specific device and usb configuration.
Also, make sure you're *NOT* using ehci_hcd for this; you have to use
uhci_hcd or ohci_hcd, depending on your specific motherboard chipset.
If this doesn't work, we'll probably have to play with your specific
udev configuration.
When I then try
pilot-dlpsh -p /dev/ttyUSB1
I get
ERROR: Specify exactly one of -c or -i
And what happens when you do as requested? "pilot-dlpsh --help" will
provide you with explanations of both parameters.
