http://www.linux-club.de/ftopic58729.html

After long try have I it created a Hotsync in addition-get. Thus: use Suse Linux 10,0 64-bit with kde desktop as the first time kpilot geupdated by means of yast. here a version excerpt from hotsync minutes in the k-pilot Version: KPilot 4.5.4 (dreumes) version: pilot left 0.11.8 version: KDE 3.4.2 level "b" version: Qt 3.3.4 have then kpilot by means of Alt-F2 udn kdesu kpilot in the root mode started then on attitudes and KPilot furnishing went and have then the attitude assistant called then at "PDA and user determine" clicked hotsync from the PDA started automatically and in the Kpilot on to continue clicked. it everything recognized then on to use with kde clicked then under general attitudes - - turns out in the Kpilot the speed completely up-turned and with evasion solutions on "Zire 31, 72, Tungsten T5" placed then one should still adjust which one all to syncen wants. as the latter I do not have still under general attitudes - - Hotsync hook with "alignment Bildschirmschoner run so long" with me there always ne error message came far away there that it status bildschirmschoners determine could not. then in kpilot to file and hotsync clicked and on pda hotsync button. me then without problems hotsync accomplished a complete. however I had to kpilot still times again start for a renewed hotsync. and without root-right it does not have up to now also yet functioned can to me however present that I for it usbport for my user to de-energise would have. hope it was understandable and is useful to you which.

kpilot log:

Version: KPilot 4.5.4 (dreumes)

Version: pilot-link 0.11.8

Version: KDE 3.4.2 Level "b"

Version: Qt 3.3.4

 

HotSync Log

17:16:12 Starting the KPilot daemon ...

17:16:12 Daemon status is `not running'

17:16:12 Pilot device /dev/ttyUSB0 does not exist. Probably it is a USB device and will appear during a HotSync.

17:16:41 Device link ready.

17:16:48 Trying to open device /dev/ttyUSB0...

17:16:48 Device link ready.

17:16:54 Trying to open device /dev/ttyUSB0...

17:16:54 Device link ready.

17:17:00 Trying to open device /dev/ttyUSB0...

17:17:00 Device link ready.

17:17:03 Unable to read system information from Pilot

17:17:37 Pilot device /dev/ttyUSB0 does not exist. Probably it is a USB device and will appear during a HotSync.

17:17:41 Pilot device /dev/ttyUSB0 does not exist. Probably it is a USB device and will appear during a HotSync.

17:18:53 Changed username to `martin'.

17:18:53 Pilot device /dev/ttyUSB0 does not exist. Probably it is a USB device and will appear during a HotSync.

17:18:53 Next HotSync will be: HotSync. Please press the HotSync button.

17:19:10 Device link ready.

17:19:16 Trying to open device /dev/ttyUSB0...

17:19:16 Device link ready.

17:19:23 Trying to open device /dev/ttyUSB0...

17:19:23 Device link ready.

17:19:29 Trying to open device /dev/ttyUSB0...

17:19:29 Device link ready.

17:19:35 Trying to open device /dev/ttyUSB0...

17:19:35 Device link ready.

17:19:42 Trying to open device /dev/ttyUSB0...

17:19:42 Could not open device: /dev/ttyUSB0 (will retry)

17:19:43 Device link ready.

17:19:45 Checking last PC...

17:19:46 KPilot 4.5.4 (dreumes) HotSync starting...

17:19:46 Using encoding ISO 8859-15 on the handheld.

17:19:46 [File Installer]

17:19:46 No Files to install

17:19:46 [Internal Editors]

17:19:46 Databases with changed records:

17:19:46 Databases with changed flags:

17:19:46 Databases with changed AppBlock:

17:19:46 [Conduit knotes-conduit]

17:19:46 KNotes is not running. The conduit must be able to make a DCOP connection to KNotes for synchronization to take place. Please start KNotes and try again.

17:19:46 The conduit knotes-conduit could not be executed.

17:19:46 [Conduit notepad-conduit]

at this point it locked up

 

 

The above polling sequence seems to go on indefinitely, to see a longer section.

This suggests to me that a valid response is being received from the Palm (requesting irOBEX protocol?) but this seems to have no effect?

When I realised that the sequence appears to be continuous, I clicked 'close', which brought up the following:

This looks promising! I clicked yes.

This brought up another dialog, very briefly, as the configuration was written. But it disappeared before I had a chance to read or capture it.

After this I tried KPilot again, but no change, it still does not work:

irda0 never appears even when I switch on the palm. I then realised that irda0 might be the low level device name and that we may need a different device name to talk to the IR stack, I did some searching on the web and found some references to /dev/ircomm0 and /dev/ircomm1, so I went into 'Settings'->'General Setup'->'Device' and tried these names:

the logs says they are not read-write, so I started a root session and typed:

 

linux:~ # chmod 666 /dev/ircomm0
linux:~ #

When I pressed 'sync' on the palm i got the following error messages:

and KPilot / Knotes crashed:

So I disabled notes for now:

I then tried again:

Success !!!

 

It took over an hour to backup everything but it worked!