Habilitar Treo 650 en Evolution
Para habilitar palm en evolution, con sincronizacion de gnome-pilot, se debe hacer lo siguiente:
From Evolution go to the Tools->Pilot Settings Menu option. If this is the first time you have run the tool it will ask you about the device.
/dev/pilot is often a symbolic link to a serial port. I am using the USB cradle to sync so I had to use a different port. The port should be /dev/ttyUSB1. Also make sure you choose USB for the type.
Next open a terminal and su to root and run:
# tail -f /var/log/messages
Put the treo in the cradle and press the sync buttion, the devicename appears somewhere in the output.
For Example:
Oct 11 08:12:45 localhost kernel: visor 1-4.3:1.0: Handspring Visor / Palm OS converter detected
Oct 11 08:12:45 localhost kernel: usb 1-4.3: Handspring Visor / Palm OS converter now attached to ttyUSB0
Oct 11 08:12:45 localhost kernel: usb 1-4.3: Handspring Visor / Palm OS converter now attached to ttyUSB1
You want to use the last device mentioned. You might not get ttyUSB1 it might be a higher number if you have other devices.
Press ctrl-c in the terminal window to end the tail.
Now for some reason the device is not listed in the devices.xml file.
So you have to edit gnome-pilot's device identification file located at: /usr/share/gnome-pilot/devices.xml
Add the following lines to the devices.xml file:
<!-- Treo 650 -->
<device vendor_id="0830" product_id="0061" />
There are also some permission problems with the ttyUSB1 file. If you have a different device number use that number and replace ttyUSB1 with your device number.
So you have to create some permssions files.
create a file /etc/udev/permissions.d/10-visor.permissions
inside the file put this one line carriage return at the end:
ttyUSB1:$local:uucp:0660
create a file /etc/udev/rules.d/1—visor.rules
inside the file put this one line carriage return at the end:
KERNEL=”ttyUSB1” SYMLINK=”pilot”
Now go back to Evolution and finish the gnome pilot wizard and follow the instructions and it should work.
That is what I had to do to get my Treo 650 to sync under CentOS4. I hope that helps you.
This should also work for FC3, FC4 and RHEL 3 & 4
One Follow-up to my message.
I had to make a change to the /etc/udev/rules.d/1-visor.rules file
It seems that my device is not always ttyUSB1 and sometimes comes up as ttyUSB3 and ttyUSB5
The contens of the file /etc/udev/rules.d/1-visor.rules should now be :
BUS="usb", KERNEL="ttyUSB[13579]", SYMLINK="pilot"
In evolution update the Tools->Pilot Settings
Click on the Devices Tab and EDIT the device setting to be /dev/pilot
That way the symlink to /dev/pilot is linked to the proper device no matter how it comes up.
Y funciona!!
Para habilitar palm en evolution, con sincronizacion de gnome-pilot, se debe hacer lo siguiente:
From Evolution go to the Tools->Pilot Settings Menu option. If this is the first time you have run the tool it will ask you about the device.
/dev/pilot is often a symbolic link to a serial port. I am using the USB cradle to sync so I had to use a different port. The port should be /dev/ttyUSB1. Also make sure you choose USB for the type.
Next open a terminal and su to root and run:
# tail -f /var/log/messages
Put the treo in the cradle and press the sync buttion, the devicename appears somewhere in the output.
For Example:
Oct 11 08:12:45 localhost kernel: visor 1-4.3:1.0: Handspring Visor / Palm OS converter detected
Oct 11 08:12:45 localhost kernel: usb 1-4.3: Handspring Visor / Palm OS converter now attached to ttyUSB0
Oct 11 08:12:45 localhost kernel: usb 1-4.3: Handspring Visor / Palm OS converter now attached to ttyUSB1
You want to use the last device mentioned. You might not get ttyUSB1 it might be a higher number if you have other devices.
Press ctrl-c in the terminal window to end the tail.
Now for some reason the device is not listed in the devices.xml file.
So you have to edit gnome-pilot's device identification file located at: /usr/share/gnome-pilot/devices.xml
Add the following lines to the devices.xml file:
<!-- Treo 650 -->
<device vendor_id="0830" product_id="0061" />
There are also some permission problems with the ttyUSB1 file. If you have a different device number use that number and replace ttyUSB1 with your device number.
So you have to create some permssions files.
create a file /etc/udev/permissions.d/10-visor.permissions
inside the file put this one line carriage return at the end:
ttyUSB1:$local:uucp:0660
create a file /etc/udev/rules.d/1—visor.rules
inside the file put this one line carriage return at the end:
KERNEL=”ttyUSB1” SYMLINK=”pilot”
Now go back to Evolution and finish the gnome pilot wizard and follow the instructions and it should work.
That is what I had to do to get my Treo 650 to sync under CentOS4. I hope that helps you.
This should also work for FC3, FC4 and RHEL 3 & 4
One Follow-up to my message.
I had to make a change to the /etc/udev/rules.d/1-visor.rules file
It seems that my device is not always ttyUSB1 and sometimes comes up as ttyUSB3 and ttyUSB5
The contens of the file /etc/udev/rules.d/1-visor.rules should now be :
BUS="usb", KERNEL="ttyUSB[13579]", SYMLINK="pilot"
In evolution update the Tools->Pilot Settings
Click on the Devices Tab and EDIT the device setting to be /dev/pilot
That way the symlink to /dev/pilot is linked to the proper device no matter how it comes up.
Y funciona!!
Comentarios