PDA

View Full Version : problem installing pilot-link


ryancw
08-29-2006, 10:03 PM
Running LN 3.0 mostly stock.
Son just bought a Tapwave Zodiac PDA thing. It runs a version of PalmOS. I have searched Google and found various references to the Zodiac working with jPilot and pilot-link.

I went to install pilot-link 0.11.8 from Debian stable. Things were going fine, and as it installed I was presented with some bluish configuration screens that I have seen before with other apps. I was asked what port I wanted to communicate with the Zodiac. It suggested various serial ports (ttyS[digit]) or USB ports (ttyUSB[digit]). Since I would be using a USB port, I chose ttyUSB0 (not knowing any better).

Turns out pilot-link and jpilot default to using /dev/pilot

Turns out I have no ttyUSB0 on my system.

I uninstalled and purged pilot-link, thinking I could reinstall it and start over. But at reinstall, I was not asked for a communication port--it seemed to automatically adopt the ttyUSB0 that I had put in before. Now I'm stuck.

Any suggestions? Any experienced users of pilot-link, jpilot, and perhaps a Zodiac?

Thanks.

bhobjj
08-30-2006, 06:54 AM
The /dev/ttyUSB0 and /dev/ttyUSB1 are used by the device. These do not exist and will be automaticly created when you plug the device in your USB port.

In Jpilot you can set the port with:
File --> Preferences --> Then the Settings tab in the dialog box
In the serial port box type in /dev/ttyUSB1
(this will over-ride whatever default link you have for pilot-link)




You can also create a link for dev/pilot:
Edit the /etc/udev/links.conf file
add a line like this:

L pilot /dev/ttyUSB1


You can verify that the hardware is recognized by plugging in the device and pushing the hotsync button. Then run dmesg.
# dmesg

You should see something like this at the end:


usb 2-2: new full speed USB device using ohci_hcd and address 4
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
usbcore: registered new driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OS
drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 5.0visor 2-2:1.0: Handspring Visor / Palm OS converter detected
usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB0
usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB1
usbcore: registered new driver visor


It's probably not necessary, but if you:
# dpkg-reconfigure pilot-link
You should see the dialog for configuring pilot-link.

ryancw
08-31-2006, 12:11 AM
Thanks for your help. I did the dpkg-reconfigure thing and chose ttyUSB1. Set it the same in jpilot.

I tried hotsync-dmesg sequence many times. Below is the result of trials 7 through 18. I seem to get mostly "khusbd timed out" errors, and "device descriptor read/64, error -71" errors, whatever those are. The results seem to alternate between those two depending on how I hold the hot sync cable (the connection to the Zodiac seems a little flimsy. Maybe I have a bad connection or cable.)

At any rate, my computer seems to notice that *something* is newly connected to the USB port, but it doesn't seem to know what it is or what to do with it. I don't get what you show in your message.

Using pilot-link from Debian stable, by the way; version 0.11.8 I think.

Grateful for any other advice.

--Chris


usb 1-1.2: new full speed USB device using uhci_hcd and address 7
usb 1-1.2: khubd timed out on ep0in
usb 1-1.2: USB disconnect, address 7
usb 1-1.2: new full speed USB device using uhci_hcd and address 8
usb 1-1.2: khubd timed out on ep0in
usb 1-1.2: USB disconnect, address 8
usb 1-1.2: new full speed USB device using uhci_hcd and address 9
usb 1-1.2: device descriptor read/64, error -71
usb 1-1.2: device descriptor read/64, error -71
usb 1-1.2: new full speed USB device using uhci_hcd and address 10
usb 1-1.2: device descriptor read/64, error -71
usb 1-1.2: device descriptor read/64, error -71
usb 1-1.2: new full speed USB device using uhci_hcd and address 11
usb 1-1.2: khubd timed out on ep0in
usb 1-1.2: USB disconnect, address 11
usb 1-1.2: new full speed USB device using uhci_hcd and address 12
usb 1-1.2: new full speed USB device using uhci_hcd and address 13
usb 1-1.2: khubd timed out on ep0in
usb 1-1.2: USB disconnect, address 13
usb 1-1.2: new full speed USB device using uhci_hcd and address 14
usb 1-1.2: khubd timed out on ep0in
usb 1-1.2: USB disconnect, address 14
usb 1-1.2: new full speed USB device using uhci_hcd and address 15
usb 1-1.2: new full speed USB device using uhci_hcd and address 16
usb 1-1.2: khubd timed out on ep0in
usb 1-1.2: USB disconnect, address 16
usb 1-1.2: new full speed USB device using uhci_hcd and address 17
usb 1-1.2: device descriptor read/64, error -71
usb 1-1.2: device descriptor read/64, error -71
usb 1-1.2: new full speed USB device using uhci_hcd and address 18
usb 1-1.2: device descriptor read/64, error -71
usb 1-1.2: device descriptor read/64, error -71

ryancw
08-31-2006, 12:19 AM
PS--

I got this message from the dpkg-reconfigure pilot-link command:

[root@ryanlibranet:/home/ryancwrf]# dpkg-reconfigure pilot-link
chmod: cannot access `/dev/ttyUSB1': No such file or directory
[root@ryanlibranet:/home/ryancwrf]#


Any signficance?

Thanks again.

--Chris

bhobjj
08-31-2006, 08:16 AM
Make sure that the visor module is loaded:

# modprobe visor

and try it again.


If I plug in my palm Zire, I get this with dmesg:


usb 2-2: new full speed USB device using ohci_hcd and address 18
usb 2-2: device descriptor read/64, error -110
usb 2-2: device descriptor read/64, error -110


After I press the hot-sync button and run dmesg again I see this:


usb 2-2: new full speed USB device using ohci_hcd and address 19
visor 2-2:1.0: Handspring Visor / Palm OS converter detected
usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB0
usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB1



Some related discussion from the Libranet Archives:
http://www.debianquestions.com/ln-archive/viewtopic.php?t=7171&start=0