Hi Rich, I experienced similar issue with my 680 coming up as multiple ttyUSBX device files. What I found I had to do was hit HotSync on the Treo first in order for linux to see the device and create the /dev/pilot symlink to whichever of the /dev/ttyUSBX device files it wanted. Then I'd hit sync from jpilot and it'd work. Hopefully that'll work for you as it was the only sequence that did for me. Best regards, -Charlie Rich Shepard wrote: > I spent a lot of time last weekend trying to load the databases on the > Treo. Somehow, managed to have pilot-xfer actually connect and copy over > AddressbookDB,pdb, but could not re-establish the connection to move the > others across the wire. This means that I won't be able to sync the two > until I get this all fixed. > > Here's the scenario, and what I learned from some local folks: > > First, I upgraded pilot-link from -0.11.8 to -0.12.2. Second, I rebuilt > jpilot-0.99.9 using that version of pilot-link. Then, I plugged the PDA to a > USB port on the front of the workstation/server. Initially, > /var/log/messages reported it was connected on ttyUSB0 and ttyUSB1. That's > apparently a quirk with many of these units and the 2.6.x kernel series. > However, the next time I plugged it in, it was connected on ttyUSB2 and > ttyUSB3. > > However, as soon as I pressed the sync button on the cable end, > /ver/log/messages reported that the device was now connected on ttyUSB4 and > ttyUSB5. Well, as you can well imagine, I cannot get the correct port on the > pilot-xfer command line when it's playing musical ports with me. As soon as > I press the button again, or I disconnect the PDA, /var/log/messages shows > it disconnecting from all four ports, one pair at a time. > > The two successful connections were on ttyUSB1 and ttyUSB3, so I assume > that the odd-number devices are the real ones ... when it works. > > Now, someone local running FC7 (rather than my Slackware-11.0) pointed me > to /etc/udev/rules.d/nn-libpisock.rules. Initially, those numbers were '80', > but I changed the name to 5-libpisock.rules. Still no joy. > > I know that the Treo 700p must work with pilot-link and jpilot on boxes > running a 2.6.x kernel. I seem stuck with changing USB numbers, and I really > need some expert help here so I can transfer all the database files, > reliably sync the PDA and jpilot, and put this issue behind me. > > So, while I was able -- on two separate days -- to transfer files to the > PDA using pilot-xfer, I cannot sync the PDA and desktop wither from within > jpilot or from the command line with pilot-xfer. I'd be very grateful for > some help on resolving this issue. > > Rich >
More information about the jpilot mailing list