Treo 650

[Craig White]

On Wed, 2005-10-05 at 13:53 -0700, Simon Chatfield wrote:
> OK, I got it working with my Treo 600 and FC4. Not the
> exact situation as you guys with FC3 and the 650, but
> pretty similar. The longest problem for me was
> actually trying to get evolution to use the conduits.
> 
> After adding:
> 
> BUS="usb", SYSFS{product}="Palm Handheld*",
> KERNEL="ttyUSB[13579]", SYMLINK="pilot"
> 
> to /etc/udev/rules.d/10-visor.rules I was seeing udev
> correctly create the device and changing ownership to
> the correct user. As mentioned earlier, it is a slow
> process so you need to set the timeout high.
> 
> from here, when I pushed the hotsync button, I saw
> usb/udev pickup and assign the device in
> /var/log/messages output.
> 
> step one complete.
> 
> For some reason the gpilot applet/daemon was not
> wanting to work. After doing research I found that I
> needed to upgrade rpms for the following (for FC4)
> which were not provided by redhat.
> 
> gnome-pilot-2.0.13-4.i386.rpm
> gnome-pilot-conduits-2.0.13-2.i386.rpm
> evolution-data-server-1.2.2-3.i386.rpm
> pilot-link-0.12.0-0.pre4.0.fc4.2.i386.rpm
> 
> After that, everything worked... Note, there were many
> failed attempts with other rpms/src's until coming to
> this solution.
> 
> I know for FC3, there is an evolution-pilot rpm, but
> for FC4 there was no such nicety.
> 
> Hope this helps guys and good luck.
----
Actually, I got this working this morning but had to deal with a
customer crisis so I was unable to post back until now.

FC-3 - apparently udev is the issue so I am providing a manual
workaround in the interim.

as root...

mknod /tmp/pilot c 188 1
chown craig /tmp/pilot

plug in treo and press hotsync button

as craig (cli)

pilot-xfer -L -p /tmp/pilot

Works - got file list from Treo

so to make gpilotd work I had to add...

 <!-- Handspring Treo 650 -->
 <device vendor_id="0830" product_id="0061" />

to /usr/share/gnome-pilot/devices.xml

bugzilla entry that led me here...
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=158809

Thanks all

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.