Did you try entering /dev/ttyUSB1 into JPilot?
-TR
On Monday 04 September 2006 22:12, Elizabeth Dodd wrote:
> On Tuesday 05 September 2006 12:31, Elizabeth Dodd wrote:
> > One machine has a working udev rule in
> > /etc/udev/rules.d/60-symlinks.rules # Create /dev/pilot symlink for Palm
> > Pilots
> > KERNEL=="ttyUSB*", SYSFS{product}=="Palm Handheld*", \
> > SYMLINK+="pilot"
> >
> > and a later install has a non-working version
> > # Create /dev/pilot symlink for Palm Pilots
> > KERNEL=="ttyUSB*", SYSFS{product}=="Palm Handheld*", \
> > SYMLINK+="pilot", GROUP=="tty",
> > MODE=="0666"
> >
> > David Desrosiers preferred syntax is
> > BUS="usb", SYSFS{product}="Palm Handheld*", KERNEL="ttyUSB*",
> > NAME="ttyUSB%n", SYMLINK="pilot", GROUP="usb", MODE="0666"
> >
> >
> > would the difference in the group make all the difference?
>
> I've tried copying version 1 and version 3 to the machine that doesn't have
> a working connection. Restarted udev and still no effect
> ****************************************
> Syncing on device /dev/pilot
> Press the HotSync button now
> ****************************************
> dlp_ReadSysInfo error
> Exiting with status SYNC_ERROR_PI_CONNECT
> Finished
>
> the device is recognised, /dev/pilot is created but no sync possible.
> I find that /dev/pilot is linked to /dev/ttyUSB1.
> with pilot-link I can talk to the machine on /dev/ttyUSB0
> but setting jpilot to this doesn't help
>
> ****************************************
> Syncing on device /dev/ttyUSB0
> Press the HotSync button now
> ****************************************
> dlp_ReadSysInfo error
> Exiting with status SYNC_ERROR_PI_CONNECT
> Finished
>
>
>
> what else can i fiddle with / investigate (etc)?
> Liz
More information about the jpilot mailing list