i am running slackware 9, which is 2.4.21. i have a visor
deluxe pda, and i connected the cradle to the usb
port. the following modules are loaded:
visor, usbserial,uhci,usbcore
when i push the hotsync button, the devices
/dev/ttyUSB0 and /dev/ttyUSB1 are available, with 666,
but then pilot-xfer just sits there saying push
hotsync button now. (no matter which order i do things
in, or even as root, do i get an actual sync to occur).
any pointers.

-gong

Have you had a look at 'man pilot-link' and 'man pilot-xfer'?

Usually it's just a sybolic link keeping default installs from working out-of-the-box. What does 'ls -la /dev/pilot' show you?

I got this in an email from a LUG - I don't know if it's relevant or if you've even tried it. I also had good results after upgrading my mail client and the jpilot/kpilot software. But I wasn't on USB with it.

"OK this is what I did. The usbserial and visor modules werent detecting
the Palm Zire I have. I tracked it down to the usbserial module for
somereason didnt know the vendor/product ids (perhaps a bit of playing
with the hotplug config files might be in order). All I did then was to
insmod the usbserial module like so:


insmod usbserial vendor=0x830 product=0x70


Then load the visor module as normal and now it creates the /dev/ttyUSB1
device and now I can coldsync and all thats left is getting kpilot to
compile and work."

i read the manpages, the link points to /dev/ttyUSB1
i dont think the link is completely necessary since
the mini-howto says you should use the command

pilot-xfer -p /dev/ttyUSB1 -b pilotbackupdir

and the link can be used in place of /dev/ttyUSB1. it
also says you can call the link /dev/visor.
seems people have had minimal difficulty with this, but
i can't get mine to work!

in /var/log/messages, i see that when i press the hotsync
button, the tty's are initialized. when pilot-xfer
runs, it says "listening to port /dev/ttyUSB1" but
then after a while it says error accepting data on
/dev/ttyUSB1. in messages it says visor.c
bytes in = 276 bytes out = 0. when the visor finally
gives up on hotsync, there are more /var/log/messages
indicating the converter is now disconnected from
ttyUSB1 etc.

thanks for looking at this.

-gong

You need to be sure that the visor is really on /dev/ttyUSB1. Try unplugging the visor cradle and plug it back in again. Type 'dmesg' and you should see some line regarding what usb devide it was assigned.