This site is having major problems keeping me logged in, and the login button only works from the homepage. Plus it's having problems serving pages at all, and I get blank pages until I refresh again. Bleagh.
Anyway, I've had several palms: a Vx, an m505, and a Zire 31, and I have used jpilot for years as I use Linux exclusively. My Zire just bit the dust, so I splurged for a TX. I really wanted to get away from Palm's weirdness as a company, but the Windows PC stuff is worse and DEFINITELY doesn't want to talk to Linux, and I've got everything locked up in PDB files.
Of course I had problems getting it to sync. I've spent all night working with it as I might return it Monday for an E2 or something.
It looks like it does the same thing as a Lifedrive. When you plug it in to the USB port, it connects as a device. When you hit the hotsync button, it immediately disconnects, reconnects, pauses for a second or so, then disconnects and reconnects again.
You can only talk to it if you catch it during that pause.
I'm using the 2.6.19.1 kernel with visor disabled, libusb 0.1.2, pilot-link 0.12.1, and udev 103.
I've noticed that there's Lifedrive/TX support in darwinusb.c - I wonder if there's any chance getting that backported? The comments in the code are really good, maybe I'll take a crack at that myself.
At the moment I've american-engineered my udev script to count connects/disconnects and only sync every 2nd time.
If anyone wants to collaborate on it, I can work with them.
Workaround for T|X connection problems
I've seen the same wierdness with my new T|X (Remind me why I keep buying palms again?)
I'm syncing over USB to a Linux machine (FC5). What works for me is keeping a "tail -f" on the /var/log/messages file, so I can see what device my Palm is currently at.
When first connected, it briefly becomes /dev/ttyUSB0, disconnects, then stays a while at /dev/ttyUSB1. The next time it connects it will briefly be ttyUSB2, then stay at ttyUSB3. After that, it's back to ttyUSB0 and ttyUSB1 again. So I only ever use ttyUSB1 and ttyUSB3, depending on what's at the bottom of /var/log/messages. This is working very reliably, though of course it's still a hassle. Maybe this information will help people understand what's wrong or at least work around the problem.