Palm Synchronisation

mdbarton · 11-19-2003, 01:50 AM

I am having trouble synchronising my palm (a Sony Clie) with KDE. I found (by running 'dmesg' as root) that I needed to hotsync on /dev/ttyUSB1 and saw advise somewhere on these forumns to link this to /dev/pilot. I did this then ran kpilot, configured the conduits and hotsynced no problem.

However I cannot hotsync since the first one. dmesg shows the following:

Code:

hub.c: new USB device 00:1f.4-2, assigned address 2
usb.c: USB device 2 (vend/prod 0x54c/0x66) is not claimed by any active driver.
usbserial.c: USB Serial support registered for Handspring Visor / Palm 4.0 / Clié 4.x
usbserial.c: Handspring Visor / Palm 4.0 / Clié 4.x converter detected
visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: Number of ports: 2
visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 1, is for Generic use and is bound to ttyUSB0
visor.c: Handspring Visor / Palm 4.0 / Clié 4.x: port 2, is for HotSync use and is bound to ttyUSB1
usb-uhci.c: interrupt, status 2, frame# 41
Unable to handle kernel NULL pointer dereference at virtual address 00000018
 printing eip:
cea38570
*pde = 00000000
Oops: 0000 2.4.20-4GB #1 Wed Aug 6 18:26:21 UTC 2003
CPU:    0
EIP:    0010:[<cea38570>]    Tainted: P 
EFLAGS: 00010046
eax: 00000000   ebx: 00000000   ecx: 00000246   edx: 00000000
esi: c5f248e0   edi: c5f24800   ebp: ffffffea   esp: cd53ded0
ds: 0018   es: 0018   ss: 0018
Process kpilotDaemon (pid: 2256, stackpage=cd53d000)
Stack: c5f24888 c59a0874 c5f24888 cbebc000 00000000 00000000 c5957e60 c01b972b
       cbebc000 c01b9650 0000000a c5957e60 00000400 c01b6817 cbebc000 c5957e60
       00000000 00000000 c01538fd c5957e60 00000000 00000145 cd53c000 7fffffff
Call Trace:    [<c59a0874>] [<c01b972b>] [<c01b9650>] [<c01b6817>] [<c01538fd>]
  [<c0153c5a>] [<c0144b4d>] [<c0108c33>]
Modules: [(visor:<cea38060>:<cea3a368>)] [(usbserial:<c59a0060>:<c59a481c>)]
Code: 83 78 18 8d 75 ed 81 c3 00 03 00 00 42 83 fa 17 7e e7 51 9d
 usb_control/bulk_msg: timeout
visor.c: visor_startup - error getting first unknown palm command
usb_control/bulk_msg: timeout
visor.c: visor_startup - error getting second unknown palm command

This would seem to indicate that kpilotDaemon has crashed. KPilot locks up and I have to kill it.

Any ideas?

tyiooo · 11-22-2003, 02:20 PM

Hi,

have you tried this ?

kwixson posted a good one here and there's even a post about how to sync it with Ximian Evolution

http://www.linuxquestions.org/questi...highlight=Palm

It worked fine for me

mdbarton · 12-01-2003, 08:07 AM

tyiooo

I tried the instructions on the link you gave. Still the same result I'm afraid. I'm going to see if the latest versions of pilot-link and kpilot work (if I can compile and install them ok).

regards

Matt

downinthemine · 12-01-2003, 04:29 PM

Matt - Try the latest version of kpilot and using J-Pilot as your desktop client. I have a Clie PEG-SJ20 and it works just fine.

Andy

mdbarton · 12-02-2003, 01:59 AM

Andy

I uninstalled all the KDEPIM apps and pilot-link. Tried to build the latest pilot-link from source but that didn't work so tried re-installing pilot-link of the distro cd.

I set the environment variables for PILOTPORT=/dev/ttyUSB1 and PILOTRATE=57600.

Using

Code:

pilot-xfer -l

I get the list of databases on the palm!

The only thing is it seems to work the second time I hotsync after booting the computer. The first time I get the message:

Code:

   Listening to port: /dev/ttyUSB1

   Please press the HotSync button now...

But I have already pressed the hotsync button before running pilot-xfer (else I get an error message saying 'press hotsync before running this conduit' or something like that). After I time out or cancel, the second time I get the same 'press the Hotsync button now...' message, but it says 'connected' and lists the databases on the Clie straightaway. Do you get anything similar?

I'll download J-Pilot and give it a try.

Cheers!

Matt

mdbarton · 12-02-2003, 01:26 PM

It's working! I guess that kpilot was a waste of time. JPilot works fine!

Thanks for the tip downinthemine

I still have to hotsync twice though

downinthemine · 12-02-2003, 03:42 PM

In terms of syncing twice. I've found that after a reboot, it won't sync on the first time. I think that if you wait a few seconds more before pressing sync in J-Pilot, it might solve your syncing twice problem.

mdbarton · 12-04-2003, 12:54 AM

I waited five seconds (after the beep indicating a device had connected) before pressing sync in j-pilot, still wouldn't have it. I suspect this may be a bug in pilot-link - but it atleast I can sync after that!

I've reported this as a bug

mdbarton · 12-09-2003, 08:05 AM

OK, posted a bug on the pilot-link website and got this response:

Quote:

Try disabling hotplug (consult the docs for it), blacklist the visor
driver in /etc/hotplug/blacklist, and statically loading your visor module
after bootup as a test, to see if the problem goes away.

Any one know what this actually means?