>>> Has anyone managed to get a Tungsten T5 to network sync with a Linux
>>> box? For some reason I have had to disable USB in the BIOS to get the
>>> computer to run...
>>
>> Ya, I got it to work over Bluetooth and WiFi (much faster) once I got my
>> WiFi card.
>>
>> There are several sites on the web that describe how to set everything up.
>>
>> As a matter of fact, I never did get the USB stuff working for my TX and I
>> always network sync it.
>
>Are you using any front end such as kpilot, gpilit, or jpilot? They often
>come with a wizard that assumes a connection via USB (you can specify the
>device path, e.g. /dev/usb/ttyUSB0). I never had any difficulties with
>SuSE and Ubuntu Palm synchronisation. Just a couple of minutes to set up,
>given that all the software is ready 'out of the box'. For what it's
>worth, here is the extensive HOWTO that has become a valuable reference
>for troubleshooting:
>
>http://www.faqs.org/docs/Linux-HOWTO/PalmOS-HOWTO.html
This document is from 2002. This is way older than PalmOS 5 and
my TX.
I really wish the pilot-link stuff would document all the stuff
that can be used to specify the connection, which is *NOT* always
a device name. I also suspect that usb:/dev/usb/ttyUSB0 has a much
better chance at working than /dev/usb/ttyUSB0 .
I have tried using the 'uvisor' driver on FreeBSD. It doesn't work.
There are methods for talking to the Palm to get info on what USB
pipe does what, and it comes up with nonsense, determined after
adding extensive debugging to the driver. The code in there
distinguishes between PalmOS 4 and 3.5, but it doesn't have code
for PalmOS 5. There must be a different way to obtain this information
for PalmOS 5.
I have gotten sync to work over WiFi, but not USB. Another thing
documented it seems only in source code is using net: as the device name.
Gordon L. Burditt
|
|
