can not sync palm device

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

I have replaced the Beta version of Ubuntu 8.04 with the recently released version of 8.04, and still cannot sync my Kyocera 7135 with Evolution. The settings for G-Pilot are the same as those that worked successfully with Ubuntu 7.10, but all that happens when I press the HotSync button on the cradle is that it locks up the phone.
I did have this trouble with 7.10 until I read how to create a custom rule in /udev/rules.d (as posted above. I suspect that I need to create such a rule in Hardy, but do not know how to go about this. I do know the device vendor id and product id, these are listed in /usr/share/gnome-pilot/devices.xml.
I do not know how to obtain a log of what is happening when I try to sync: I am still a tyro using the console. If somebody can give me some instruction how to get whatever information is required to throw light on this I will endeavour to carry out what is required.
Regards,
Bruce

I just upgraded to Hardy Heron 8.04 and could not get my Zire to sync with J-pilot. After tinkering around a bit, I used the usb device name usb: and it worked. Go figure. Feisty wanted /dev/ttyUSB1 to work. Since I do not know enough about this distro or Linux to get in trouble, I am a tinkerer like many.
Hope this helps.
Cheers
John

John, can you elaborate more?
I am using pilot-xfer command line utility. With ubuntu 7.10 I was able to use
pilet-xfer -p /dev/ttyUSB0
after upgrading to 8.04 I don't see any /dev/ttyUSB* device created.

I installed jpilot so I could follow your post, and I tried using both "usb" and "usb:" as the port,
but jpilot says:

  pi_bind error: usb No such file or directory
  Check your serial port and settings

Can you figure out what device jpilot is using ?

By the way, kernel 2.6.24 has a bug redarging the visor module,
which I'm experiencing:
http://bugzilla.kernel.org/show_bug.cgi?id=10118

Where you experiencing the same dmesg error?
visor: probe of xxxx failed with error -5

Kernel 2.6.25 fixes that bug, by the way.

sordna,
First off I upgraded to 8.04 and had many things that were not working
that did in 7.10. After toying around with them, I decided to do a clean
install and reinstalled 8.04 completely. There were just too many things
to fix. After the reinstall, I got everything working except the J-pilot
sync with my Zire. "usb:" works great for me, but as the bug reports,
visor may be broken if you did an upgrade. I know it is not suppose to
happen in Linux but my machine was a mess. My guess is that Visor is
fixed with the new Kernel, and you should be good with "usb:". I had the
same:

pi_bind error: usb No such file or directory
  Check your serial port and settings

but I had that with /dev/ttyUSB1 that worked before. That was the second
set of USB headers on my mother board. I see below that you used USB0
which would be the first header on the mother board. That should not
matter. "usb:" seems to be the cover all statement for all of the USB
headers.
Hope that helps,
John

sordna wrote:
> Question #29037 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/29037
>
> sordna requested for more information:
> John, can you elaborate more?
> I am using pilot-xfer command line utility. With ubuntu 7.10 I was able to use
> pilet-xfer -p /dev/ttyUSB0
> after upgrading to 8.04 I don't see any /dev/ttyUSB* device created.
>
> I installed jpilot so I could follow your post, and I tried using both "usb" and "usb:" as the port,
> but jpilot says:
>
> pi_bind error: usb No such file or directory
> Check your serial port and settings
>
> Can you figure out what device jpilot is using ?
>
> By the way, kernel 2.6.24 has a bug redarging the visor module,
> which I'm experiencing:
> http://bugzilla.kernel.org/show_bug.cgi?id=10118
>
> Where you experiencing the same dmesg error?
> visor: probe of xxxx failed with error -5
>
> Kernel 2.6.25 fixes that bug, by the way.
>
>

It seems at least some of my problem is in the 2.6.24 Kernel, and it is fixed in 2.6.25.
Can anyone point me in the direction of a "simple" tutorial that will walk me through updating the kernel?
Regards,
Bruce

Thanks sordna, that solved my question.

Instead of using the device "/dev/ttyUSB0" or "/dev/ttyUSB1" simply use "usb:"
Works great. Got it from http://ubuntuforums.org/showthread.php?t=351029

It didn't work for me (Garmin iQue 3600).
So... what's "usb:" anyway? Can you run j-pilot with strace and tell me which device
under /dev "usb:" ends up using?

usb: doesn't work for me either.
My machine definitely knows there is a Kyocera device connected to the port when I put it in the cradle, but it won't communicate with it, either via Gpilot or j-pilot.
I understand that the visor module is broken in the current kernel, and I am not game to compile my own kernel, particularly as I have seen several caveats about the nvidia graphics driver with the 2.6.25 kernel.
I will just bide my time and hope a fix comes for the kernel sooner rather than later.
This is not the only bugbear I have with 8.04 compared to 7.10.
I never thought I would use WinXP again as much as I am doing at the moment, to cover the difficulties visited on me by Ubuntu 8.04.
Regards,
Bruce.

I really don't know what "usb:" exactly is, or whether it refers to a device in /dev or a group of devices. I will try to use strace and post my results here.
But it just worked for me in both j-pilot and gpilotd (Sony Clie PEG TJ35 having Palm OS 5.2.0). But there was another bug *sigh* in sync between evolution and gpilotd. So I am currently using jpilot, which is for me much much better than using XP. And yes the new kernel has many other problems (e.g. cannot run vmware!!)

I too had many issues after upgrade from Gutsy. It was painful, but I
did a clean install of Heron on the system and my problems have gone
away. Gutsy was an upgrade from Feisty, so it was probably time to clean
things up.

As for j-pilot, usb: works for me. Palm OS 4.x (older version). It did
not work until I reloaded the system.
"strace" gives me allot of information, but I can not find the usb call.
I know it should be listed as a serial device.

fadyek wrote:
> Question #29037 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/29037
>
> fadyek posted a new comment:
> I really don't know what "usb:" exactly is, or whether it refers to a device in /dev or a group of devices. I will try to use strace and post my results here.
> But it just worked for me in both j-pilot and gpilotd (Sony Clie PEG TJ35 having Palm OS 5.2.0). But there was another bug *sigh* in sync between evolution and gpilotd. So I am currently using jpilot, which is for me much much better than using XP. And yes the new kernel has many other problems (e.g. cannot run vmware!!)
>
>

Latest kernel updates received this morning have fixed my problems with xsane, but still nothing happens with syncing the Kyocera, either with Evolution or J-Pilot. I may yet have to bite the bullet and try compiling my own kernel, but I am VERY apprehensive about that.
Cheers,
Bruce

I had problems between evolution on Hardy Heron and a Treo 680 with Plam OS 5.4.9. I kept loading all the suggested updates to Ubuntu. Now I have found that if I run gpilot from the command line and then press hotsync on th phone, it works. . . . however gpilot does not exit when the sync is over, so I just Ctrl-C it and everyone is happy.

Tried that, Andy, and this is what I get:
(With visor module loaded, and using /dev/ttyUSB1)
us@Linfred:~$ gpilotd
gpilotd-Message: gnome-pilot 2.0.15 starting...
gpilotd-Message: compiled for pilot-link version 0.12.3
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0
gpilotd-Message: Watching cradle (/dev/ttyUSB1)
gpilotd-Message: Found 4766, 0001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0502, 0736
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 091e, 0004
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 115e, f100
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 082d, 0100
gpilotd-Message: Using net FALSE
gpilotd-Message: Found 082d, 0200
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 082d, 0300
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0c88, 0021
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0002
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0003
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0020
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0031
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0040
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0050
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0060
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0061
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0070
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0080
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 04e8, 8001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 04e8, 6601
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0038
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0066
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0095
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 009a
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00c9
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00da
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00e9
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0144
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0169
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 12ef, 0100
gpilotd-Message: Using net TRUE
gpilotd-Message: setting PILOTRATE=57600

(gpilotd:7915): gpilotd-WARNING **: Unable to bind to PDA

(With no visor module, and using usb:)
us@Linfred:~$ gpilotd
gpilotd-Message: gnome-pilot 2.0.15 starting...
gpilotd-Message: compiled for pilot-link version 0.12.3
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0
gpilotd-Message: Watching cradle (usb:)
gpilotd-Message: Found 4766, 0001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0502, 0736
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 091e, 0004
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 115e, f100
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 082d, 0100
gpilotd-Message: Using net FALSE
gpilotd-Message: Found 082d, 0200
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 082d, 0300
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0c88, 0021
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0002
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0003
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0020
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0031
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0040
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0050
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0060
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0061
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0070
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0080
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 04e8, 8001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 04e8, 6601
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0038
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0066
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0095
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 009a
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00c9
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00da
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00e9
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0144
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0169
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 12ef, 0100
gpilotd-Message: Using net TRUE
gpilotd-Message: setting PILOTRATE=57600

(gpilotd:6439): gpilotd-WARNING **: An error occurred while getting the PDA's system data

(gpilotd:6439): gpilotd-WARNING **: error -201 from pi_close.
gpilotd-Message: Exiting (caught SIGINT)...

And I have no idea what that is telling me. Is this a result of whatever is broken in the Visor module? Looks to me like the sync fails at the same point with or without visor. If that is so, is it a permissions issue?
It used to work under Feisty and Gutsy, now it doesn't under Hardy. I don't see this as a giant step forward.

Why don't you simply download a 2.6.25 kernel from http://kernel-archive.buildserver.net/debian-kernel/pool/main/l/linux-2.6/ ?
A selection will be added to your grub menu, and won't affect your other kernel(s).
Which means you can try the newer kernel risk free, and go back/forth as often as you like.
It's been working great for me and my Garmin iQue 3600, so I made 2.6.25 my default selection in grub.

I have the kernel, linux headers and what all sitting on my desktop, but just at the moment I need my PC to be working at a moment's notice: I cannot afford the time to reinstall if I mess things up, nor do I want to lose my access to email for any length of time.
It is simpler (and potentially quicker) to maintain a backup of the Kyocera on my WinXP partition than it is to risk losing the PC at a critical moment, then climb into my leathers, then get on my bike, then find a friend's machine I can use, or an internet cafe, then come home on the bike and reinstall my machine.
My knowledge of Linux commands just isn't up to being CERTAIN I could complete the task. When the urgent need for a functioning pc goes away, and I can foul it up and reinstall as necessary, then I will give it a shot. I definitely don't want to go back to WinXP for all purposes: I have over a year of using Ubuntu behind me now, and managed to sort any problems with Feisty and Gutsy by following step-by-step solutions off the web. Chances are I will be able to compile a kernel the same way, just not while I NEED the computer running. (Some of us are old and a bit stupid, we need time to work ourselves up to anything that looks technical.)

Long weekend ahead, bit of spare time, compile the new kernel.
Smoked my Nvidia Graphics Driver, as the warnings said was likely to happen. Too much trouble to fix, reinstall the OS. Still can't sync, plus other problems elsewhere.
Jump forward to the past: pull out my 7.10 live CD, reinstall that, all my problems go away. Everything just WORKS!
You can keep your 8.04 until it's fixed.

Here a way to get Ubuntu 8.04 sync your Palm devices without using the visor kernel module,
which is broken in the kernel that comes with 8.04.
Instead of visor, you can use libusb (userland).

First do "apt-get install libusb-dev".
Then download the latest pilot-link sources from pilot-link.org. Read README.libusb
for enlightening information.
The pilot-link sources come with a 60-libpisock.rules file that needs to be placed into
/etc/udev/rules.d/ followed by a reboot so it's read by the system.
After that, the command "pilot-xfer -p usb: -l"
prints a message:
  Listening for incoming connection on usb:...
instead of saying "Unable to bind to port".
This "Listening" is an indicator that libusb is being used and hitting the hotsync button
allowed my Garmin iQue 3600 to by synced using ubuntu's 8.04 stock kernel !!!

I'm using pilot-link directly (the pilot-xfer conduit) but I believe the 60-libpisock.rules file should help
users of other software like gnome-pilot since most of them use pilot-link under the hood.