Unable to hotsync Palm with JPilot 1.6.1

andrew.46 · 01-08-2009, 05:54 AM

Hi,

Running Slackware 12.2 I am having trouble hotsynching my Palm T|X using JPilot 1.6.1. The Palm is detected as:

Code:

usb 4-2: New USB device found, idVendor=0830, idProduct=0061
usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
usb 4-2: Product: Palm Handheld
usb 4-2: Manufacturer: Palm, Inc.
usb 4-2: SerialNumber: PN70M218V1TR
usbcore: registered new interface driver usbserial
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
usbserial: USB Serial support registered for Handspring Visor / Palm OS
usbserial: USB Serial support registered for Sony Clie 3.5
usbserial: USB Serial support registered for Sony Clie 5.0
visor 4-2:1.0: Handspring Visor / Palm OS converter detected
usb 4-2: Handspring Visor / Palm OS converter now attached to ttyUSB0
usb 4-2: Handspring Visor / Palm OS converter now attached to ttyUSB1
usbcore: registered new interface driver visor
visor: USB HandSpring Visor / Palm OS driver

In JPilot I have set the usb device as both /dev/ttyUSB1 and /dev/ttyUSB0 but when attempting to hotsync I get the following error message:

Code:

****************************************
 Syncing on device /dev/ttyUSB1
 Press the HotSync button now
****************************************
pi_bind error: /dev/ttyUSB1 Permission denied
Check your serial port and settings
Exiting with status SYNC_ERROR_BIND
Finished.

Permissions are set as follows:

Code:

andrew@skamandros~$ ls -l /dev/ttyUSB*
crw-rw---- 1 root uucp 188, 0 2009-01-08 22:42 /dev/ttyUSB0
crw-rw---- 1 root uucp 188, 1 2009-01-08 22:42 /dev/ttyUSB1

which I suspect may be the problem but I am a little uncertain about changing these permissions.

Any advice would be appreciated.

Andrew

andrew.46 · 01-08-2009, 06:09 AM

Hi,

I am sooooo stupid! The hint of course was here:

Code:

andrew@skamandros~$ ls -l /dev/ttyUSB*
crw-rw---- 1 root uucp 188, 0 2009-01-08 22:42 /dev/ttyUSB0
crw-rw---- 1 root uucp 188, 1 2009-01-08 22:42 /dev/ttyUSB1

I made myself a member of uucp and now all works well.

Andrew

dungkal · 05-21-2009, 10:26 PM

I had the same situation with Fedora 11. The solution is not to point the port to /dev/ttyUSB1 but to usb:. I did the same to gpilotd-control-applet.

T3slider · 05-21-2009, 10:33 PM

I had this problem with my T3, and I didn't want to add my user to the uucp group (I am not particularly familiar with this group *at all*, but I think there may be security implications in adding a user to this group...but take that with a grain of salt). I added some udev rules to change the group ownership of /dev/ttyUSB0 and /dev/ttyUSB1 to the plugdev group, of which I am of course a member. I created the file /etc/udev/rules.d/10-local.rules containing the following line:

Code:

BUS=="usb", SYSFS{product}=="Palm Handheld*", KERNEL=="ttyUSB[13579]", SYMLINK+="pilot", GROUP="plugdev", MODE="0660", OPTIONS+="last_rule"

Without the last_rule option the plugdev group change will be overridden and the uucp group will still be set. If you prefer different permissions you can modify the above line.

[edit]The above line creates a /dev/pilot symlink to the correct ttyUSB device...so you would use /dev/pilot instead of hard-coding a /dev/ttyUSB1, for example. The reason it looks for 13579 instead of the first ttyUSB device is because some Palm-to-memory-card apps create an extra ttyUSB device with an even number, I believe. The /dev/pilot link here just takes all of the effort out of syncing.