Hi, Is there anyone on the list who is familiar with kpilot and palm pilots? I have just bought a Tungsten T3 and am trying to set it up to run under FC2. After connecting the device the var/log/messages seems to report Two usb connections, one on ttyUSB0 and the other on ttyUSB1. (See log below) I've tried both to no avail. Kpilot log shows an attempt to connect to ttyUSB0, but says it is not read-write. The commandline test as per the kpilot tests at the portal report a similar lack of connection in the shell. I've checked the KDE and kpilot sites and the kpilot user guide. Does anyone have any hints? Cheers Paul mailto:fiction@xxxxxxxxxxxxxx ps. copy of the two logs follow ... I tailed my /var/log/messages and got this as the device connected: --------------------------------------------------------------------------------------------------- Jun 19 16:56:11 localhost kernel: usb 1-4.3: new full speed USB device using address 8 Jun 19 16:56:11 localhost kernel: ehci_hcd 0000:02:0e.2: qh 1e543500 (#0) state 1 Jun 19 16:56:11 localhost kernel: usbserial 1-4.3:1.0: Handspring Visor / Palm OS converter detected Jun 19 16:56:11 localhost kernel: usb 1-4.3: Handspring Visor / Palm OS converter now attached to ttyUSB0 (or usb/tts/0 for devfs) Jun 19 16:56:11 localhost kernel: usb 1-4.3: Handspring Visor / Palm OS converter now attached to ttyUSB1 (or usb/tts/1 for devfs) <end> Kpilot Log Follows: ------------------------------- Version: KPilot 4.4.1 Version: pilot-link 0.11.8 Version: KDE 3.2.2-3 Red Hat Version: Qt 3.3.2 HotSync Log KPilot has been reported to cause data loss. Please check with kdepim-users@xxxxxxxx 16:51:23 Starting the KPilot daemon ... 16:51:23 Daemon status is `' 16:51:23 Pilot device /dev/ttyUSB0 is not read-write. 16:51:24 Trying to open device /dev/ttyUSB0... 16:51:24 Could not open device: /dev/ttyUSB0 (will retry) <end> -- Paul Thompson mailto:fiction@xxxxxxxxxxxxxx
