Zaire still won't connect
Joel Hammer
Joel
Mon May 17 11:49:15 PDT 2004
Still trying to get my Zaire to connect via usb. Just love progress!
I have upgraded lindows and now see this when I attach my Zaire:
hub.c: new USB device 00:11.2-2, assigned address 10
usbserial.c: Handspring Visor / Palm 4.0 / Clii 4.x converter detected
visor.c: Handspring Visor / Palm 4.0 / Clii 4.x: Number of ports: 2
visor.c: Handspring Visor / Palm 4.0 / Clii 4.x: port 1, is for Generic use and is bound to ttyUSB0
visor.c: Handspring Visor / Palm 4.0 / Clii 4.x: port 2, is for HotSync use and is bound to ttyUSB1
usbserial.c: Handspring Visor / Palm 4.0 / Clii 4.x converter now attached to ttyUSB0 (or usb/tts/0 for devfs
usbserial.c: Handspring Visor / Palm 4.0 / Clii 4.x converter now attached to ttyUSB1 (or usb/tts/1 for devfs
This all looks good, although I don't understand how the visor module
binds to both usb ports. Seems odd. However, I still can't get jpilot
to talk to the Zaire, even through I tried all four ports suggested
by this output. (/dev/ttyUSB0, /dev/tts/0, etc). I tried sticking
the cable into both usb ports. I don't get much in the way of error
messages. In fact, no error messages, even starting jpilot from the
command line.
All I get is this:
J-Pilot: press the hotsync button on the cradle or "kill 4181"
Of course, I have already pressed the hotsync button. If you don't, devfs
doesn't create /usb/tts/1 etc and then things really just don't work.
Any suggestions welcome.
Joel
BTW, not impressed by the upgrade with lindows. Lindows seems determined
to kill its product with false advertising. The upgrade wasn't one
click. You have to reinstall the whole thing.
Joel
More information about the Linux-users
mailing list