My computer got messed up because of a power failure and so I had to
rebuild my system. It worked fine before, but after I rebuilt my system
I couldn't sync and kept getting the dreaded Unable to bind to pilot
message. I can't see what's wrong at all; the device is getting created
by udev with the right permissions and it syncs ok with my computer at
home. (I'm running kernel 2.6.14 in Gentoo Linux.)
When I push the sync button I get these messages in the log:
Dec 2 13:54:12 musuko hub 1-0:1.0: state 5 ports 2 chg 0000 evt 0002
Dec 2 13:54:12 musuko uhci_hcd 0000:00:11.2: port 1 portsc 0093,00
Dec 2 13:54:12 musuko hub 1-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
Dec 2 13:54:12 musuko hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
Dec 2 13:54:12 musuko usb 1-1: new full speed USB device using uhci_hcd and address 6
Dec 2 13:54:12 musuko usb 1-1: ep0 maxpacket = 16
Dec 2 13:54:12 musuko usb 1-1: default language 0x0409
Dec 2 13:54:12 musuko usb 1-1: new device strings: Mfr=1, Product=2, SerialNumber=5
Dec 2 13:54:12 musuko usb 1-1: Product: Palm Handheld
Dec 2 13:54:12 musuko usb 1-1: Manufacturer: Palm, Inc.
Dec 2 13:54:12 musuko usb 1-1: SerialNumber: 00TA35826B9Y
Dec 2 13:54:12 musuko usb 1-1: hotplug
Dec 2 13:54:12 musuko usb 1-1: adding 1-1:1.0 (config #1, interface 0)
Dec 2 13:54:12 musuko usb 1-1:1.0: hotplug
Dec 2 13:54:12 musuko usbserial_generic 1-1:1.0: usb_probe_interface
Dec 2 13:54:12 musuko usbserial_generic 1-1:1.0: usb_probe_interface - got id
Dec 2 13:54:12 musuko visor 1-1:1.0: usb_probe_interface
Dec 2 13:54:12 musuko visor 1-1:1.0: usb_probe_interface - got id
Dec 2 13:54:12 musuko visor 1-1:1.0: Handspring Visor / Palm OS converter detected
Dec 2 13:54:12 musuko usb 1-1: Handspring Visor / Palm OS converter now attached to ttyUSB0
Dec 2 13:54:12 musuko usb 1-1: Handspring Visor / Palm OS converter now attached to ttyUSB1
Dec 2 13:54:12 musuko hub 1-0:1.0: state 5 ports 2 chg 0000 evt 0002
The device shows up properly, with the owner being me:
ll /dev/pilot
crw-rw-rw- 1 sl70 root 189, 3 Dec 2 13:39 /dev/pilot
But when I try to do pilot-xfer -l I get this:
Unable to bind to port: /dev/pilot
Please use --help for more information
Does anyone know what I've overlooked?
Thanks.
--
Stuart Luppescu -=-=- s-luppescu <AT> uchicago <DOT> edu
CCSR at U of C ,.;-*^*-;., www.consortium-chicago.org
(^_^)/ 才文と智奈美の父
Thank God I'm an atheist!
Attachment:
smime.p7s
Description: S/MIME cryptographic signature