Really need help to get my Palm TX syncing

Reploid · 2008-06-11 23:07:35

I am pulling my hairs out RTFM and all TF posts I can find.

This is what I've tried:
gpasswd -a reploid tty
added 'visor' to modules in /etc/rc.conf
played around with multiple settings in the preferences window, /dev/tty/USB1, USB0, /dev/pilot
edited /etc/group and put my username under tty
removed the symlink /dev/pilot according to this thread: http://bbs.archlinux.org/viewtopic.php?id=10944

A) #ln -s /dev/tts/USB1 /dev/pilot

* now if you get a #ln -s /dev/tts/USB1 /dev/pilot
ln: `/dev/pilot': File exists *
all you have to do is

B) #rm /dev/pilot
this just removes the link to the old port no worries
then just run command A) again ^
now you will want correct premissions wink

C) # chmod 0777 /dev/pilot
now this should give your normal user premissions to access the sync function of your palm pilot

I haven't messed around with udev yet.

dmesg shows this:

visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0
visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1
visor 3-1:1.0: device disconnected
hub 2-0:1.0: unable to enumerate USB device on port 3
usb 3-1: new full speed USB device using uhci_hcd and address 25
usb 3-1: configuration #1 chosen from 1 choice
visor 3-1:1.0: Handspring Visor / Palm OS converter detected
usb 3-1: Handspring Visor / Palm OS converter now attached to ttyUSB0
usb 3-1: Handspring Visor / Palm OS converter now attached to ttyUSB1
usb 3-1: USB disconnect, address 25
visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0
visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1

Any clues on where I should start, or what I should do? Please? Pretty please with sugar on top?

brebs · 2008-06-12 07:10:48

Symlinking manually is absolutely the wrong way to do it

Use udev - that's what it's for. The Palm "device" is only exposed during the hotsync.

Reploid · 2008-06-12 08:16:45

Great. Now what do I do to reverse the symlinking back to normal?

I have tried different versions of udev rules now. I made a backup of the file: 40-pilot-link.rules and changed it into this:

BUS=="usb", SYSFS{product}=="Palm Handheld*", KERNEL=="ttyUSB[02468]", SYMLINK+="pilot", NAME="%k", GROUP="uucp", MODE="0660", OWNER="My Palmnamel"

Last edited by Reploid (2008-06-12 08:21:16)

Reploid · 2008-06-12 08:55:17

brebs wrote:

Symlinking manually is absolutely the wrong way to do it
Use udev - that's what it's for. The Palm "device" is only exposed during the hotsync.

What does this line from your post in the gentoo forums mean?

USB_SERIAL_VISOR=y

Where do I enter that?

And adding myself to the group "usb" doesn't work either, there is no group called usb on my computer. Hmm...

Last edited by Reploid (2008-06-12 09:01:44)

brebs · 2008-06-12 09:05:18

In "make menuconfig" - it's a kernel module. The standard kernel will include it.

Try "modprobe visor" and "lsmod | grep visor", to check.

Last edited by brebs (2008-06-12 09:06:51)

Reploid · 2008-06-12 09:50:56

[root@archcomputer reploid]# lsmod | grep visor
visor 16012 0
usbserial 30312 1 visor
usbcore 129776 7 hci_usb,visor,usbserial,usbhid,ehci_hcd,uhci_hcd

That means I don't have to include that line, right?

I would try to put this line in my udev, but I don't have a group on my computer called "usb". Is that a difference between gentoo and arch? Or do I need to create a group (how) called usb in order to get my palm up and running??

SUBSYSTEMS=="usb", ATTRS{product}=="Palm Handheld*", KERNEL=="ttyUSB*[1,3,5,7,9]", ACTION=="add", SYMLINK+="pilot", GROUP="usb",

brebs · 2008-06-12 09:59:32

Your kernel is OK then.

Remove the syntax-error-inducing comma from the end of your line

Use "users" instead of "usb".

grep users /etc/group

Different distros have different user group configurations, just to confuse us.

Last edited by brebs (2008-06-12 10:00:49)

Reploid · 2008-06-12 10:52:21

Arite, this just ain't working.

My udev:

SUBSYSTEMS=="usb", ATTRS{product}=="Palm Handheld*", KERNEL=="ttyUSB*[1,3,5,7,9]", ACTION=="add", SYMLINK+="pilot", GROUP="users", MODE="0660", RUN+="/home/reploid/bin/backuppalm"

dmesg:

visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0
visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1
visor 3-1:1.0: device disconnected
hub 2-0:1.0: unable to enumerate USB device on port 3
usb 3-1: new full speed USB device using uhci_hcd and address 3
usb 3-1: configuration #1 chosen from 1 choice
visor 3-1:1.0: Handspring Visor / Palm OS converter detected
usb 3-1: Handspring Visor / Palm OS converter now attached to ttyUSB0
usb 3-1: Handspring Visor / Palm OS converter now attached to ttyUSB1

And:

ls -l /dev/pilot
lrwxrwxrwx 1 root root 8 2008-06-12 00:50 /dev/pilot -> tts/USB1

Suggestions for next step? Should I replace usb with users after subsystems as well?

brebs · 2008-06-12 13:49:37

Debug it. The "product" might be different for you, since Palm keep changing the name to confuse us.

Google for the magic word "udevinfo", and the magic phrase "udev debugging".

Reploid · 2008-06-12 15:47:56

Thanks for the help so far Paul. I'm gonna read some manpages now to see if I can get it sorted out without asking stupid questions.

spaceturnip · 2008-06-26 07:16:28

tty isn't the right group. If you look at /dev/tts/USB1 you'll see that the group you need to be in is 'uucp' At least that's what udev assigns that device to on my system. You shouldn't need to do anything else once you get the permissions correct. Just remember to start the hotsync on the palm first as that's what creates the device notes.

briest · 2008-06-26 19:29:23

Maybe my experiences with T5 will be of any use:
- don't mangle with udev rules, they are OK
- add yourself to uucp group
- find the right device to use; for me, tts/USB1 is the one, but it seems to change between different models
- (it took me some time to figure) start hotsync on Palm, wait about three seconds and then start sync on desktop (no matter whether via jpilot or pilot-link - the time seems to be needed by udev); if you start desktop part first, it would likely hang, eating your CPU; if you don't wait, connection would fail.

I have never used 'daemonized' solutions such as gpilotd though, that would simplify the process probably.

Reploid · 2008-08-16 16:13:43

I am on a new Arch Install now. After adding myself to uucp, installing jpilot, pushing hotsync on palm and waiting 3sek + before pressing jpilot's sync button, my palm connects to jpilot. Yay!! Thank u.

There is still a few problems:
1) I can only sync if I start jpilot by typing sudo jpilot in the terminal. Otherwise I get this error message:

[reploid@archcomputer tts]$ jpilot

(jpilot:12332): Gtk-WARNING **: Unable to locate theme engine in module_path: "mist",

(jpilot:12332): Gtk-WARNING **: Unable to locate theme engine in module_path: "mist",
Error opening file: ToDoDB.pdb
Error opening file: DatebookDB.pdb
Error opening file: DatebookDB.pdb
Unable to open jpilot.alarms file
pi_bind error: /dev/tts/USB1 Permission denied ###(It is the same for /dev/pilot)
Check your serial port and settings
Exiting with status SYNC_ERROR_BIND
Finished

Now what the heck?
My permissions are the following:

in /dev
lrwxrwxrwx  1 root root           8 2008-08-16 16:42 pilot -> tts/USB1
crw-rw-rw-  1 root tty       5,   0 2008-08-16 13:08 tty
in /dev/tts:
crw-rw----  1 root uucp 188,  0 2008-08-16 16:42 USB0
crw-rw----  1 root uucp 188,  1 2008-08-16 16:42 USB1

So what permissions do I need to set??

2 question:
typing gnome-pilot, gpilot or kpilot doesn't bring up neither application. I am on openbox, so I need to figure out how to configure the menu/ what command that will start gnome-pilot.

Again, thanx for all help so far, I am happy that the palm is recognized on my arch system, and this n00b greatly appreciates your input.

briest · 2008-08-18 19:10:30

Permissions seem OK; did you use newgrp or re-logged in after joining uucp group? And, given you ran jpilot via sudo before, *pdb files are probably owned by root, not your user; change ownership of ~/.jpilot and its contents.

gnome-pilot/kpilot... I'm afraid I can't help here, jpilot works for me, so I had no urge to find another solution.

m3tr0g33k · 2008-08-31 14:09:00

After lots of mucking about, I got this off the palm-usb howto: www.pilot-link.org/README.usb.
I put this in 40-pilot-links.rules:

BUS=="usb", SYSFS{product}=="Palm Handheld*|Handspring *", KERNEL=="ttyUSB*", NAME="ttyUSB%n", SYMLINK="pilot", GROUP="usb", MODE="0666"

Except, since I have an Abacus Wrist PDA (a super uber-geek toy), I changed:

SYSFS{product}=="Wrist PDA"

Jpilot works fine now.

brebs · 2008-08-31 19:01:19

Post the link correctly.

Arch Linux

#1 2008-06-11 23:07:35

Really need help to get my Palm TX syncing

#2 2008-06-12 07:10:48

Re: Really need help to get my Palm TX syncing

#3 2008-06-12 08:16:45

Re: Really need help to get my Palm TX syncing

#4 2008-06-12 08:55:17

Re: Really need help to get my Palm TX syncing

#5 2008-06-12 09:05:18

Re: Really need help to get my Palm TX syncing

#6 2008-06-12 09:50:56

Re: Really need help to get my Palm TX syncing

#7 2008-06-12 09:59:32

Re: Really need help to get my Palm TX syncing

#8 2008-06-12 10:52:21

Re: Really need help to get my Palm TX syncing

#9 2008-06-12 13:49:37

Re: Really need help to get my Palm TX syncing

#10 2008-06-12 15:47:56

Re: Really need help to get my Palm TX syncing

#11 2008-06-26 07:16:28

Re: Really need help to get my Palm TX syncing

#12 2008-06-26 19:29:23

Re: Really need help to get my Palm TX syncing

#13 2008-08-16 16:13:43

Re: Really need help to get my Palm TX syncing

#14 2008-08-18 19:10:30

Re: Really need help to get my Palm TX syncing

#15 2008-08-31 14:09:00

Re: Really need help to get my Palm TX syncing

#16 2008-08-31 19:01:19

Re: Really need help to get my Palm TX syncing

Board footer