Hmmm, it works flawlessly with jpilot 0.99.7, so it appars not to be related to pilot-link... Pascal Pascal A. Niklaus wrote: > Update: > > kpilot actually sync's from the PDA to the PC, but never PC->PDA. I > tried different sync settings in "configure -> kpilot -> sync", > without success... > > Any hint? > > Pascal > > Pascal.Niklaus@unibas.ch wrote: > >> Hi all, >> >> I'm trying to get a Palm Zire21 to sync with kpilot. However, >> although HotSync >> is executed, the data I enter on the PDA are never displayed in >> kpilot, nor is >> data transferred the other way round. >> >> What might be the reason for this? >> >> The PDA reports "HotSync operation complete", but at the end of >> kpilot's log, >> there is a message saying: >> >> 17:15:25 HotSync Completed. >> 17:15:28 Trying to open device /dev/ttyUSB1... >> 17:15:28 Could not open device: /dev/ttyUSB1 (will retry) >> >> Is this ok? After HotSync, the PDA disconnects, so that I'm not >> surprised that >> /dev/ttyUSB1 cannot be opened again. >> >> Thanks for your help >> >> Pascal >> >> ----------------------------- >> >> kpilot is version 4.4.1 (compiled from source in kdepim-3.2.2) >> pilot-link is version 0.11.8 (installed from distro) >> the whole thing runs on SuSE 9.1 >> >> ========= Full HotSync Log >> >> Version: KPilot 4.4.1 >> Version: pilot-link 0.11.8 >> Version: KDE 3.2.2 >> Version: Qt 3.3.2 >> >> KPilot has been reported to cause data loss. Please check with >> kdepim-users@kde.org. >> >> 17:14:15 Starting the KPilot daemon ... >> 17:14:16 Daemon status is `' >> 17:14:16 Pilot device /dev/ttyUSB1 doesn't exist. Assuming the >> device uses >> DevFS. >> 17:14:17 Trying to open device /dev/ttyUSB1... >> 17:14:17 Could not open device: /dev/ttyUSB1 (will retry) >> 17:14:25 Using character set ISO 8859-2 on the handheld. >> 17:14:25 Pilot device /dev/ttyUSB1 doesn't exist. Assuming the >> device uses >> DevFS. >> 17:14:26 Trying to open device /dev/ttyUSB1... >> 17:14:26 Could not open device: /dev/ttyUSB1 (will retry) >> 17:15:23 Device link ready. >> 17:15:24 Checking last PC... >> 17:15:24 KPilot 4.4.1 HotSync starting... >> >> 17:15:24 Synchronizing changes by the internal editors of KPilot: >> 17:15:24 Databases with changed records: >> 17:15:24 Databases with changed flags: >> 17:15:24 Databases with changed AppBlock: >> 17:15:24 End of HotSync >> >> 17:15:25 HotSync Completed. >> 17:15:28 Trying to open device /dev/ttyUSB1... >> 17:15:28 Could not open device: /dev/ttyUSB1 (will retry) >> >> ========= var/log/messages: >> >> May 21 17:15:23 linux kernel: usb 2-2: new full speed USB device >> using address >> 27 >> May 21 17:15:23 linux kernel: usb 2-2: Product: Palm Handheld >> May 21 17:15:23 linux kernel: usb 2-2: Manufacturer: Palm, Inc. >> May 21 17:15:23 linux kernel: usb 2-2: SerialNumber: PalmSN12345678 >> May 21 17:15:23 linux kernel: usbserial 2-2:1.0: Handspring Visor / >> Palm OS >> converter detected >> May 21 17:15:23 linux kernel: usb 2-2: Handspring Visor / Palm OS >> converter now >> attached to ttyUSB0 (or usb/tts/0 for devfs) >> May 21 17:15:23 linux kernel: usb 2-2: Handspring Visor / Palm OS >> converter now >> attached to ttyUSB1 (or usb/tts/1 for devfs) >> May 21 17:15:23 linux /etc/hotplug/usb.agent[10945]: need a device >> for this >> command >> May 21 17:15:23 linux /etc/hotplug/tty.agent[10963]: add tty device >> /class/tty/ttyUSB0 >> May 21 17:15:23 linux /etc/hotplug/tty.agent[10981]: add tty device >> /class/tty/ttyUSB1 >> May 21 17:15:25 linux kernel: usb 2-2: control timeout on ep0in >> May 21 17:15:26 linux kernel: usb 2-2: USB disconnect, address 27 >> May 21 17:15:26 linux kernel: visor ttyUSB0: Handspring Visor / Palm OS >> converter now disconnected from ttyUSB0 >> May 21 17:15:26 linux kernel: visor ttyUSB1: Handspring Visor / Palm OS >> converter now disconnected from ttyUSB1 >> May 21 17:15:26 linux kernel: usbserial 2-2:1.0: device disconnected >> May 21 17:15:26 linux /etc/hotplug/tty.agent[11099]: TTY try 1 while >> waiting for >> /class/tty/ttyUSB1's bus_id >> May 21 17:15:26 linux /etc/hotplug/tty.agent[11083]: TTY try 1 while >> waiting for >> /class/tty/ttyUSB0's bus_id >> May 21 17:15:26 linux /etc/hotplug/usb.agent[11117]: need a device >> for this >> command >> May 21 17:15:27 linux /etc/hotplug/tty.agent[11083]: TTY try 2 while >> waiting for >> /class/tty/ttyUSB0's bus_id >> May 21 17:15:27 linux /etc/hotplug/tty.agent[11099]: TTY try 2 while >> waiting for >> /class/tty/ttyUSB1's bus_id >> May 21 17:15:28 linux /etc/hotplug/tty.agent[11083]: TTY try 3 while >> waiting for >> /class/tty/ttyUSB0's bus_id >> May 21 17:15:28 linux /etc/hotplug/tty.agent[11099]: TTY try 3 while >> waiting for >> /class/tty/ttyUSB1's bus_id >> May 21 17:15:29 linux /etc/hotplug/tty.agent[11083]: TTY try 4 while >> waiting for >> /class/tty/ttyUSB0's bus_id >> May 21 17:15:29 linux /etc/hotplug/tty.agent[11099]: TTY try 4 while >> waiting for >> /class/tty/ttyUSB1's bus_id >> May 21 17:15:30 linux /etc/hotplug/tty.agent[11083]: TTY try 5 while >> waiting for >> /class/tty/ttyUSB0's bus_id >> May 21 17:15:30 linux /etc/hotplug/tty.agent[11099]: TTY try 5 while >> waiting for >> /class/tty/ttyUSB1's bus_id >> >> >> ---------- > _______________________________________________ kde-pim mailing list kde-pim@mail.kde.org https://mail.kde.org/mailman/listinfo/kde-pim kde-pim home page at http://pim.kde.org/