I've spent several hours over the last few days reading everything I can find about syncing a Visor using a USB cradle. From what I can glean, it's not easy. First I should say that I'm on the Ximian Evolution list (where the current opinion seems to be that the syncing problems can be traced to gpilotd), and I've read the information at the SourceForge project usbvisor (which has apparently not been updated in over a year). I've also spent some time reading the threads here in an effort to apply the information in them to my issue, but none of the situations seem to be quite the same, although many have referred to similar issues. I'm using a RH8 box with the latest updates using Red Carpet. Here are the particulars: > [root hunter dev]# uname -orp > 2.4.20-20.8 i686 GNU/Linux > [root hunter dev]# rpm -qa | grep pilot > gnome-pilot-applet-2.0.10-0.ximian.5.1 > pilot-link-0.11.5-4.ximian.1 > gnome-pilot-2.0.10-0.ximian.5.1 > gnome-pilot-devel-2.0.10-0.ximian.5.1 > pilot-link095-compat-0.9.5-20 > jpilot-0.99.2-8 > evolution-pilot-1.4.4-0.ximian.5.1 > pilot-link-devel-0.11.5-4.ximian.1 > kdepim-pilot-3.0.5a-1 > gnome-pilot-conduits-2.0.10-0.ximian.5.1 > [root hunter dev]# ll | grep pilot > lrwxrwxrwx 1 root uucp 12 Sep 22 13:11 pilot -> > /dev/ttyUSB0 /proc/bus/usb/devices contains: > T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 13 Spd=12 MxCh= 0 > D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=16 #Cfgs= 1 > P: Vendor=082d ProdID=0100 Rev= 1.00 > S: Manufacturer=Handspring Inc > S: Product=Handspring Visor > C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 2mA > I: If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=00 Prot=00 Driver=serial > E: Ad=81(I) Atr=02(Bulk) MxPS= 16 Ivl=0ms > E: Ad=01(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms > E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms gpilot doesn't even allow me to configure it for this, so I tried to see if the pilot-xfer -l trick might work. Initially, I received errors indicating that the permissions were wrong. After I chmod'd the /dev/ttyUSB* to allow write-access, those problems went away, but then the system responded with: > [root hunter dev]# pilot-xfer -l > No $PILOTPORT specified and no -p <port> given. > Defaulting to '/dev/pilot' > > > ERROR: No such device > Unable to bind to port '/dev/pilot' > Please use --help for more information After I press the hotsync button, the message indicates it's listening in on the /dev/pilot port, and instructs me to press the hotsync... which yields nothing. After a few moments, the connection times out on the PDA, and I have to kill the pilot-xfer process. So... what am I doing wrong? -- -Bob James Pentar InfoSystems www.keyserver.net KeyID FEBEC3DB
Attachment:
signature.asc
Description: This is a digitally signed message part