On Thu, 28 Jun 2007, jpilot-ml at gory.org wrote: > 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. Charlie, I've tried that; and the suggestion of someone local to me to click the Treo cable button, cancel it on the screen, then click on the jpilot link button. It's not working. I think the problem is with port naming. /var/log/messages shows the connections on, for example, ttyUSB0 and ttyUSB1. However, unless I change /etc/udev/rules.d/udev.rules, there are no ttyUSB devices. There are /dev/tts/USB0 and /dev/tts/USB1 devices (the plain serial ports are /dev/tts/0-4), and that's what jpilot wants in the port setting. Jpilot does not recognize ttyUSBn. Even when I make a symlink /dev/pilot -> /dev/tts/USB1, jpilot does not connect because -- I think -- the kernel is seeing the connection as ttyUSB1. This is all well beyond my linux knowledge, particularly in what is for me the arcane discussion of the relative values of udev and devfs. I just want to learn how to have the ports named consistently so the PDA will talk with the desktop. The two successful pilot-xfer connections specifed '-p /dev/tts/USB1' on the command line. So, why jpilot is not happy with that I've no idea. Thanks, Rich -- Richard B. Shepard, Ph.D. | The Environmental Permitting Applied Ecosystem Services, Inc. | Accelerator(TM) <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863
More information about the jpilot mailing list