Visor & Pilot-xfer - Not synching up regularly
I'm attempting to get my Handspring Visor to work with
Debian stable and I'm running into some errors that
for the life of me I can't figure out.
(somewhat lengthy post but I want to make sure I give
as much data as possible)
Some info:
Kernel: 2.4.25
Debian 3.0 (stable)
All kernel configurations according to the HOWTO at
Linuxpda.com have been completed. The USB devices work
(I can verify if via 'usbview').
My issue is strange in that the visor works once in a
while, but when it does and how and why seem to be
completly random. For example, this morning I pushed
the hotsynch button and typed in pilot-xfer -p
/dev/ttyUSB1 -l and I got a listing of the files. A
few minutes later, I repeated it and got the same
result. I then managed to do a KPilot backup, no
problem.
However, about ten minutes after that, I attempted to
synch up again and it failed. I had made no changes
whatsoever to the system. I double checked to make
sure I'd killed the Kpilot daemon in case it was
confusing things. No go. I rebooted the computer to
get to the 'clean' state that I had the first time I
tried to synch up. No go.
The system recognizes the visor as seen in 'usbview'
(shows my scanner, printer, and visor). It doesnt see
it until I press the hotsynch button and it 'creates'
the device, but I understand that's normal.
When I do a pilot-xfer -p /dev/ttyUSB1 -l I get the
following responses:
$ pilot-xfer -p /dev/ttyUSB1 -l
Listening to port: /dev/ttyUSB1
Please press the HotSync button now...
Error accepting data on /dev/ttyUSB1
/var/log/messages
Apr 3 23:39:45 dragon kernel: hub.c: new USB device
00:02.0-2.1, assigned address 6
Apr 3 23:39:45 dragon kernel: usbserial.c: Handspring
Visor / Treo / Palm 4.0 / Clié 4.x converter detected
Apr 3 23:39:45 dragon kernel: visor.c: Handspring
Visor / Treo / Palm 4.0 / Clié 4.x: Number of ports: 2
Apr 3 23:39:45 dragon kernel: visor.c: Handspring
Visor / Treo / Palm 4.0 / Clié 4.x: port 1, is for
Generic use and is bound to ttyUSB0
Apr 3 23:39:45 dragon kernel: visor.c: Handspring
Visor / Treo / Palm 4.0 / Clié 4.x: port 2, is for
HotSync use and is bound to ttyUSB1
Apr 3 23:39:45 dragon kernel: usbserial.c: Handspring
Visor / Treo / Palm 4.0 / Clié 4.x converter now
attached to ttyUSB0 (or usb/tts/0 for devfs)
Apr 3 23:39:45 dragon kernel: usbserial.c: Handspring
Visor / Treo / Palm 4.0 / Clié 4.x converter now
attached to ttyUSB1 (or usb/tts/1 for devfs)
Apr 3 23:40:16 dragon kernel: visor.c: Bytes In = 276
Bytes Out = 0
^[`Apr 3 23:40:38 dragon kernel: usb.c: USB
disconnect on device 00:02.0-2.1 address 6
Apr 3 23:40:38 dragon kernel: usbserial.c: Handspring
Visor / Treo / Palm 4.0 / Clié 4.x converter now
disconnected from ttyUSB0
Apr 3 23:40:38 dragon kernel: usbserial.c: Handspring
Visor / Treo / Palm 4.0 / Clié 4.x converter now
disconnected from ttyUSB1
Modules are installed (lsmod)
Module Size Used by Tainted: P
nvidia 1964192 6 (autoclean)
visor 10560 0
usbserial 16160 0 [visor]
usb-ohci 16192 0 (unused)
usbcore 54944 1 [visor usbserial
usb-ohci]
emu10k1 51360 0
ac97_codec 12032 0 [emu10k1]
8139too 11744 1
mii 2384 0 [8139too]
crc32 2832 0 [8139too]
Here's a confusing thing to throw in: I have attempted
this on two computers with the same kernel. I get the
same issues on both machines. That partially leads me
to think that something is up with the Visor itself,
but it HAS synched on a handful of occasions, and it
always synchs on my Windows OS, so I'm hesitant to say
that somethings up with the Visor itself.
For the record I have used /dev/ttyUSB0, /dev/pilot,
/dev/visor, etc.
I'm sort of lost as to where to go from here, thus any
advice people can give would be greatly appreciated.
Thanks
H
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
Reply to: