Re: Unable to bind to pilot



On Tue, 2006-02-21 at 23:02 +0000, Matt Davey wrote:
> > 
> > > Have you tried connecting to ttyUSB0 / ttyUSB1 with
> > > pilot-xfer -p /dev/ttyUSB0 -l
> > 
> > It says the device doesn't exist.
> 
> http://www.pilot-link.org/node/111 suggests the m515 might
> use ttyUSB1.  But you've probably tried that... 

Yup. I tried both. Same results.

> What device
> are you using on your other machine, that you say is working
> fine?  Can you do a "ls -l /dev/ttyUSB*" to double check the
> permissions on the device files, as well as the pilot symlink?

ll /dev/ttyUSB*
/bin/ls: /dev/ttyUSB*: No such file or directory

There is no pilot symlink since I'm using udev. The device node is
created as needed. The entry is:

 ll /dev/pilot
crw-rw-rw-  1 sl70 root 189, 267 Feb 22 08:48 /dev/pilot

> At the risk of stating the obvious, this 'missing device' seems
> likely to be the root of your problem.
> 
> > > What behaviour do you get on the palm?  Does it time out, or get an
> > > error quite quickly?
> > 
> > Times out.
> 
> OK, that makes it less likely that any communication is occuring.
> Strange that you didn't get any pilot-link debug output.  Try it
> without the attempt to send it to a debug file.

I copied the /etc/udev/rules.d/10-udev.rules that creates the device
node from my machine at home where it does work to my machine at work,
where it doesn't, but I'm still getting the same results. I'm beginning
to think there may be a problem with the cradle at work. I'll try
bringing in an extra hot sync cable I have at home and see if that
helps.
-- 
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



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]