Have you tried jpilot? It works great for me (Sony Clie SL10). I have had no luck at all with pilot-link and gnome-pilot (haven't tried coldsync). Pilot-link was problematic with my old serial Palm as well.
With jpilot, start the hotsync on your Palm first, then hit the sync button. Works like a charm. Dan On Sun, 2002-09-08 at 20:46, Dan Shookowsky wrote: > I'm trying to sync a Palm m515 under Redhat 7.3/KDE3/kernel 2.4.19 and > I'm not having any luck. I have synced with this cradle/palm under > Windows, but I'd rather not have to go there. I've already tried a soft > reset on the palm to see if that was holding things up, but that didn't > change anything. > > I sent a message earlier, and the one response that I had (link > /dev/pilot to /dev/ttyUSB0 instead of /dev/ttyUSB1) didn't work (Thanks > anyway). I have made some progress in that I'm pretty sure that I have > hotplug and the USB device filesystem installed correctly. > > My problem is that whenever I try coldsync or pilot-link, they just sit > there saying "Please press hotsync button" I'm pretty sure that I have > everything setup correctly for USB - when I hit the hotsync button, the > palm shows up in usbview, and I see messages like this with dmesg > > usb.c: new device strings: Mfr=1, Product=2, SerialNumber=5 > usb.c: USB device number 20 default language ID 0x409 > Manufacturer: Palm, Inc. > Product: Palm Handheld > SerialNumber: 00RN33D260PK > usbserial.c: Palm 4.0 converter detected > visor.c: Palm 4.0: Number of ports: 2 > visor.c: Palm 4.0: port 1, is for Generic use and is bound to ttyUSB0 > visor.c: Palm 4.0: port 2, is for HotSync use and is bound to ttyUSB1 > usbserial.c: Palm 4.0 converter now attached to ttyUSB0 (or usb/tts/0 > for devfs) > usbserial.c: Palm 4.0 converter now attached to ttyUSB1 (or usb/tts/1 > for devfs) > usb.c: serial driver claimed interface cb53b940 > usb.c: kusbd: /sbin/hotplug add 20 > hub.c: port 1, portstatus 100, change 0, 12 Mb/s > hub.c: port 2, portstatus 103, change 0, 12 Mb/s > > Does anyone have any idea why pilot-link and coldsync can't talk with > the device? > > Here's the log from coldsync: > Log started on Sun Sep 8 22:26:38 2002 > Summary of sync configuration: > Listen: > Type: 0 > Device: [/dev/pilot] > Speed: 57600 > Protocol: 2 > Flags: TRANSIENT > Known PDAs: > PDA: > Serial number: [00RN33D260PK] > Directory: [(null)] > Username: [Dan Shookowsky] > UserID: 0 > Flags: DEFAULT > The queue of conduits: > Conduit: > flavors: 0x0004 SYNC > Creator/Types: > [/] (0x00000000/0x00000000) > Path: [[generic]] > DEFAULT > Headers: > Preferences: > Log started on Sun Sep 8 22:26:38 2002 > Opening device [/dev/pilot] > Warning: no device on /dev/pilot. Sleeping > Warning: no device on /dev/pilot. Sleeping > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > [EMAIL PROTECTED] > To unsubscribe, use the last form field at: ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
