hotsync palm t3 question

mcdermottpa · Tux's lil' helper Joined: 06 Oct 2004 Posts: 95

I'm trying to get hotsyncing to work with my palm t3 but have thus far had no luck. I have my usb cradle hooked up and have tried using the following resources to get things working

http://www.redbug.uklinux.net/palm/
http://www.linuxpda.com/visor/howto/current/

I compiled my kernel with usbserial and visor modules. Then modprobed visor but when I press the sync button on my cradle I don't get a /dev/ttyUSB1. I do see the following in /proc/bus/usb/devices when the palm is trying to sync though:

mcdermottpa · Tux's lil' helper Joined: 06 Oct 2004 Posts: 95

-bump- Anyone have a t3 working? How did you do it?
_________________
Murphy's Military Laws:
#19.There is no such thing as an atheist in a foxhole.
#54. Killing for peace is like screwing for virginity.

R.D.Olivaw · Posted: Sat Dec 04, 2004 11:28 am Post subject:

Hello There,

yes mine works.
by simply following the instruction in http://www.linuxpda.com/visor/howto/current/
do you get
Dec 4 12:20:59 dell visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0
Dec 4 12:20:59 dell visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1
in your log? (/var/log/messages if you're using syslog)

if you do then check if the following directory exist
/dev/usb/tts/
it should have two files in it '0,1'
you can make the following link

ln -s /dev/pilot /dev/usb/tts/1

then use /dev/pilot to sync with your palm

What are you trying to sync with?
if you are using pilot-link then try the following
connect your palm and press the sync buttong on it
pilot-xfer -p /dev/pilot -b t3backup

this would backup the pilot in a directoty calleed t3backup

hope this helps

edit: corrected the code to create a symblic link

Zviratko · Posted: Sat Dec 04, 2004 3:47 pm Post subject:

Mine worked, a colleague just got one and it works as well - upon pressing a hotsync button, ttyUSB0 and ttyUSB1 appear, I set up a link /dev/ttyUSB1 -> /dev/pilot and set gnome-pilot (or kpilot or whatever) to use that serial device -> all done

mcdermottpa · Tux's lil' helper Joined: 06 Oct 2004 Posts: 95

Thanks so much for the replies! I had kind of given up on getting my t3 working but after reading that howto (again) it was... well easy. I just had to compile usb serial and visor modules in the kernel and make a symbolic link to /var/usb/tts/1 (hard link not permitted).

R.D.Olivaw doing a backup with:

R.D.Olivaw · Posted: Sun Dec 05, 2004 5:43 pm Post subject:

I'm glad that it worked.
actually if you try

mcdermottpa · Tux's lil' helper Joined: 06 Oct 2004 Posts: 95

I ran into the problem with gnome-pilot and never tried pilot-xfer as a regular user.
_________________
Murphy's Military Laws:
#19.There is no such thing as an atheist in a foxhole.
#54. Killing for peace is like screwing for virginity.

meyerm · Posted: Sat Dec 11, 2004 4:45 pm Post subject:

Hi,

may I ask you a question? I want to buy a Thungsten E but heard rumours about problems syncing them with Linux. With the available conduits you can't sync f.ex. the birthday of your contacts. I'd like to sync with the KDE suite of PIM apps.

Is this still true?

Thanks,
Marcel

R.D.Olivaw · Posted: Sun Dec 12, 2004 3:22 pm Post subject:

unfortuately that's true.
You can't sync the BDs and with the current stable version in portage you cannot install to the SD card.

meyerm · Posted: Sun Dec 12, 2004 3:26 pm Post subject:

Sad... Any idea why this is so? Is PALM not publishing needed specs or are the conduits only unmantained and therefore too old?

asiobob · Posted: Wed Feb 16, 2005 9:24 pm Post subject:

apologies for bumping.
I've got my T|E working, with the current stable in portage, so far I've only tried piliot-xf
My device was in /dev/tts/USB1 but I made a udev rule so the BUS="usb" SYSINFO{product}="Palm Handheld" NAME="pilot" (iue /dev/pilot) and MODE="0666". I'm using the udev 54 (i think, not at the box atm) and it has the rules and permissions in the same file now. Please becareful of the above rule it's probably wrong, I just pulled it out of my head.

Now when I hit hte hotsync button regular users can have access to the device.
I've tried "plucker" (and plucker-dekstop) and its great. Just the current ebuild doesn't install the plucker plam prc files because well the pakcage contains the source and you'd need a ARM toolchain to compile the palm stuff so it's much easier to go to the plucker site and download the precompiled version. I'm working to integrate the two into the ebuild