[Bug 45986] Re: unable to bind to pilot

[Matt Price]

hello gnome-pilot folks,

not sure this really belongs to you, as I'm currently unable to sync my
Palm TX with pilot-link or jpilot either (did only minimal testing on
jpilot).

Just upgraded my ubuntu laptop to edgy last night, mostly because I
wanted to sync my new Palm TX and can't do it on dapper due to the
well-known bug with ubuntu's 2.6.15 kernel and/or udev.  Anyway,
upgraded went pretty well, I now have evolution 2.8, pilot-link
0.12.1-4, gnome-pilot 2.0.14-0ubuntu1, libusb-0.1-4 0.1.12-2.  

I have tried unsuccessfully to sync the TX using both the
old-fashioned /dev/ttyUSB ports and the new usb: nomenclature.  In
pursuit of the latter I have followed the libusb howto in the pilot-link
package, namely:

- added blacklist-palm to /etc/modprobe.d, with "blacklist visor".  I
cna confirm that this works -- without this line, the visor module loads
and generates /dev/ttyUSB0/1 (or sometimes 2/3, which is of course
problematic), while with it, usbserial loads by itself and that's
that.  
- added 60-libpisock.rules to /etc/udev/rules.d
- added the /proc/bus/usb rule to /etc/fstab

restarted everything.

nonetheless, pilot-xfer -p usb: -l just hangs and eventually gives up.

similarly, if I allow the visor module to load and bind the palm
device, 
pilot-xfer -p /dev/ttyUSB[0,1] -l similarly hangs.  

what should I try next?  it's nice to have edgy and all but a working
palm was what I was after.  I haven't had a single sync yet so I'm
deathly afraid of losing the thing...

thanks,

matt

-- 
unable to bind to pilot
https://launchpad.net/bugs/45986