On Fri, 2005-11-04 at 17:31 +0100, Patrick Mulder wrote:
Dear experts,
I am a bit stuck with connecting the Palm TX via the
USB to my Debian system. I upgraded to the 2.6.13.4
Kernel and using an ASUS A7N8X-X motherboard. I am
quite sure that the USB port is recognized correctly
(excerpt from /proc/bus/usb/devices )
--snip--
But somehow the dplsh and pilot-xfer still do not work
properly:
# pilot-xfer -p /dev/ttyUSB1 -l
Listening to port: /dev/ttyUSB1
Please press the HotSync button now... connected!
Error read system info on /dev/ttyUSB1
The latest output of /var/log/messages is:
--snip--
I've spent a lot of time in the last couple of months wrestling with all
things Pilot related on my system. The one thing that actually works
pretty well in the whole setup is the visor module.
Most of the problems end up being caused by the software you use to
sync. While I'm not sure about the TX, I can tell you that with my T5,
the default use of pilot-xfer for me doesn't work. The T5 connects to
the system as soon as you plug it in. After starting a hotsync, it
actually disconnects and then immediately re-connects. In this case,
what you need to do with pilot-xfer is:
1) plug in the Palm and let it settle for a second or two
2) start the hotsync ON THE PALM
3) run pilot-xfer on your machine
Using this method, I can always get the connection to succeed.
There are plenty of other problems to be encountered. If you happen to
decide to use gnome-pilot you will be largely on your own as the
maintainer is almost completely unresponsive. Filed bugs are an average
of 2 years old, and the only bugs that have been closed recently have
either been fixed by an NMU or by a different package which gnome-pilot
uses being fixed by the maintainer for that package.