Zire 31 working with Dapper anyone ?

[Roshan Mansinghani]

Does your script use ttyUSB1 or pilot?  I have found that continually trying
to sync will cause the module to produce not just ttyUSB1 and ttyUSB0, but
ttyUSB2 and ttyUSB3 as well.  Everytime you hit the hotsync button, you
should run dmesg in another terminal to see which /dev nodes were created.
The easiest way around this is to use a udev rule that maps all of them to
/dev/pilot.  This is the way I have it set up (though I do not use a Zire
31).  In /etc/udev/rules.d/10-custom.rules I have the following line:

BUS="usb", SYSFS{product}="Palm Handheld*", KERNEL=="ttyUSB*",
SYMLINK="pilot",
MODE="666"

See if that can get you some more consistency on the timings between when
you press the hotsync button and when you run your sync command.



On 8/15/06, Anita Lewis <ajlewis2 at highstream.net> wrote:
>
> Rob Blomquist wrote:
> > when I use KPilot to sync with my Zire 31, I open Kpilot, connect the
> PDA, then reset the KPilot daemon, and tap the sync button on the PDA. I
> also use /dev/ttyUSB1, and not /dev/pilot as the device to sync to.
> >
> > If I don't do it in this order I may not connect, and its a pretty
> frustrating experience.
> >
> > In the case of running pilot-link, you may want to connect the PDA
> first, and start pilot-link second.
> >
> > Rob
>
> Are you using a hub?  I think that is my main problem.
>
> Anita
>
>
> --
> kubuntu-users mailing list
> kubuntu-users at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/kubuntu-users/attachments/20060815/26994643/attachment.html>