Hi,
I just bought a Treo 650 and was looking for info about how to use it with FC4 when I found a posting which says FC4 is "completely broken with respect to Palm syncronization". Is this supposed to be addressed in FC5, or should I "downgrade" to FC3? Has anybody synced a Treo with Evolution in FC5-test1? I asked this message on fedora-list and somebody responded saying that there was a discussion on this list. But I haven't been able to find anything definitive that says whether FC5 is supposed to fix the FC4 syncing problems. Does anyone know? Will I be able to sync a Treo 650 with evolution?
Thanks...
David
_________________________________________________________________ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/
On Fri, 2005-12-23 at 18:42 -0800, David L wrote:
I just bought a Treo 650 and was looking for info about how to use it with FC4 when I found a posting which says FC4 is "completely broken with respect to Palm syncronization". Is this supposed to be addressed in FC5, or should I "downgrade" to FC3?
My Handspring Visor Platinum works with JPilot on FC4 provided that I manually create the /dev/ttyUSB* files before each synchronization.
Yeah, it's broken.
On Sat, 2005-12-24 at 00:35 -0800, Florin Andrei wrote:
On Fri, 2005-12-23 at 18:42 -0800, David L wrote:
I just bought a Treo 650 and was looking for info about how to use it with FC4 when I found a posting which says FC4 is "completely broken with respect to Palm syncronization". Is this supposed to be addressed in FC5, or should I "downgrade" to FC3?
My Handspring Visor Platinum works with JPilot on FC4 provided that I manually create the /dev/ttyUSB* files before each synchronization.
Yeah, it's broken.
I fixed this problem some time ago, IIRC, by simply adding a file "/etc/udev/rules.d/95-visor.rules" that has just this line:
KERNEL="ttyUSB1",SYMLINK="pilot"
HTH... If not, I'm sure if you check Bugzilla you'll find the answer. I should note my wife uses a Sony Clie and not a Treo, but if your Treo syncs on ttyUSB1, this will work. Otherwise, just alter the KERNEL parameter appropriately. If you leave the symlink name as "pilot" you won't have to fiddle as much with the gnome-pilot stuff.
In the future, shouldn't these issues go to fedora-list and not fedora-devel-list?
On Sat, 24 Dec 2005 08:46:58 -0500, "Paul W. Frields" stickster@gmail.com wrote:
My Handspring Visor Platinum works with JPilot on FC4 provided that I manually create the /dev/ttyUSB* files before each synchronization.
I fixed this problem some time ago, IIRC, by simply adding a file "/etc/udev/rules.d/95-visor.rules" that has just this line:
KERNEL="ttyUSB1",SYMLINK="pilot"
This seems to be a different problem, unless the other guy is not seriously mistaken. In his case the original device nodes were not created.
In the future, shouldn't these issues go to fedora-list and not fedora-devel-list?
If we were talking about a proposed patch for udev, it would belong here. I keep the hope.
There would also be a significant development content if we dicussed how to find a Pilot in a more robust way with udev. The thing is, we cannot ship KERNEL="ttyUSB1", because of dynamic numbering.
-- Pete
On Sat, 2005-12-24 at 16:55 -0800, Pete Zaitcev wrote:
On Sat, 24 Dec 2005 08:46:58 -0500, "Paul W. Frields" stickster@gmail.com wrote:
My Handspring Visor Platinum works with JPilot on FC4 provided that I manually create the /dev/ttyUSB* files before each synchronization.
I fixed this problem some time ago, IIRC, by simply adding a file "/etc/udev/rules.d/95-visor.rules" that has just this line:
KERNEL="ttyUSB1",SYMLINK="pilot"This seems to be a different problem, unless the other guy is not seriously mistaken. In his case the original device nodes were not created.
Whoops, I didn't read carefully enough. I guess the OP might be able to rememdy through editing /etc/hotplug/ stuff, if the attachment's being picked up (q.v. lsusb), right?
In the future, shouldn't these issues go to fedora-list and not fedora-devel-list?
If we were talking about a proposed patch for udev, it would belong here. I keep the hope.
There would also be a significant development content if we dicussed how to find a Pilot in a more robust way with udev. The thing is, we cannot ship KERNEL="ttyUSB1", because of dynamic numbering.
Not to mention that it's not entirely clear which PalmOS devices use the even device numbers as opposed to odd -- e.g. ttyUSB0 or ttyUSB1. I'm sure this information can be discovered, but I've not looked for a list either.
On Sat, 2005-12-24 at 16:55 -0800, Pete Zaitcev wrote:
On Sat, 24 Dec 2005 08:46:58 -0500, "Paul W. Frields" stickster@gmail.com wrote:
My Handspring Visor Platinum works with JPilot on FC4 provided that I manually create the /dev/ttyUSB* files before each synchronization.
I fixed this problem some time ago, IIRC, by simply adding a file "/etc/udev/rules.d/95-visor.rules" that has just this line:
KERNEL="ttyUSB1",SYMLINK="pilot"This seems to be a different problem, unless the other guy is not seriously mistaken. In his case the original device nodes were not created.
In the future, shouldn't these issues go to fedora-list and not fedora-devel-list?
If we were talking about a proposed patch for udev, it would belong here. I keep the hope.
There would also be a significant development content if we dicussed how to find a Pilot in a more robust way with udev. The thing is, we cannot ship KERNEL="ttyUSB1", because of dynamic numbering.
I've been gifted yesterday with a Palm Z22 and I've got it working with: BUS="usb", KERNEL="ttyUSB*", SYMLINK="pilot"
I've also seen KERNEL="ttyUSB[13579]" all around on the net, so it seems the odd device - among the two created - is the one used to communicate with the pilot.
The Z22 always picks the ttyUSB1 device.
Hi.
Iago Rubio fedora@iagorubio.com wrote:
I've also seen KERNEL="ttyUSB[13579]" all around on the net, so it seems the odd device - among the two created - is the one used to communicate with the pilot.
The Z22 always picks the ttyUSB1 device.
That depends on how many USB/serial adapters you have inserted into the system at that time.
On Mon, 2005-12-26 at 21:51 +0100, Ralf Ertzinger wrote:
Hi.
Iago Rubio fedora@iagorubio.com wrote:
I've also seen KERNEL="ttyUSB[13579]" all around on the net, so it seems the odd device - among the two created - is the one used to communicate with the pilot.
The Z22 always picks the ttyUSB1 device.
That depends on how many USB/serial adapters you have inserted into the system at that time.
Yes, I know :)
I meant it always picks the ttyUSB1 among ttyUSB0 and ttyUSB1, so it always picks the odd device.
On Tue, 2005-12-27 at 09:52 +0100, Iago Rubio wrote:
On Mon, 2005-12-26 at 21:51 +0100, Ralf Ertzinger wrote:
Hi.
Iago Rubio fedora@iagorubio.com wrote:
I've also seen KERNEL="ttyUSB[13579]" all around on the net, so it seems the odd device - among the two created - is the one used to communicate with the pilot.
The Z22 always picks the ttyUSB1 device.
That depends on how many USB/serial adapters you have inserted into the system at that time.
Yes, I know :)
I meant it always picks the ttyUSB1 among ttyUSB0 and ttyUSB1, so it always picks the odd device.
You can get more specific, to help it pick the right device. I have these lines in for my Sony Clie:
BUS="usb", SYSFS{product}="Palm Handheld*", KERNEL="ttyUSB*", SYMLINK="pilot" BUS="usb", SYSFS{idVendor}="054c", SYSFS{idProduct}="0144", NAME="clie% n"
Sorry if that ends up line-wrapped; it should only be two lines.
I found the information about the product and id values using hal-device-manager (from the hal-gnome package).
--Guy
On 12/23/05, David L idht4n@hotmail.com wrote:
I just bought a Treo 650 and was looking for info about how to use it with FC4 when I found a posting which says FC4 is "completely broken with respect to Palm syncronization". Is this supposed to be addressed in FC5, or should I "downgrade" to FC3? Has anybody synced a Treo with Evolution in FC5-test1? I asked this message on fedora-list and somebody responded saying that there was a discussion on this list. But I haven't been able to find anything definitive that says whether FC5 is supposed to fix the FC4 syncing problems. Does anyone know? Will I be able to sync a Treo 650 with evolution?
The updates to pilot-link in FC4 fixed the synchronization issues for me. The pilot-link is rawhide has been working. The remaining issue in FC4 for me is that it takes a long time for the /dev/ttyUSB1 device node to be created. I use a static device node as a work around. The udev in rawhide creates the device nodes much faster. This solves the final issue in using the pilot-link utilities.
I don't know about the GUI programs which use pilot-link library, like evolution, jpilot, and gnome-pilot. The pilot-link API changed with the 0.12-pre versions which means the programs need to be updated for the new API and don't know if that has been done yet.
- Ian
-
David -
Florin Andrei -
Guy Streeter -
Iago Rubio -
Ian Burrell -
Paul W. Frields -
Pete Zaitcev -
Ralf Ertzinger