[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [coldsync-hackers] coldsync 2.3.0 / m505 problems
On Thu, Jan 31, 2002 at 01:48:01AM -0800, David A. Desrosiers wrote:
>
> > I set that option, recompiled, but there was no difference, as usual
> > I had to try the hotsync twice. Everything goes as modules.
>
> Let's walk through this step by step. You cradle your Palm, you
> load the proper modules (usb-uhci or usb-ohci, depending on your
> controller hardware, usbserial, and visor). You hit the HotSync button
> _on the cradle_ and then check your logs in /var/log/messages (or
> wherever you catch kernel events). Does it show something similar to
> the following:
I do not hit the button on the cradle, because my device is a Sony Clie
320 which did not come with a cradle, but just with a cable.
>
> Jan 31 01:27:02 broccoli kernel: usbserial.c: Palm 4.0 converter now
> attached to ttyUSB0 (or usb/tts/0 for devfs)
> Jan 31 01:27:02 broccoli kernel: usbserial.c: Palm 4.0 converter now
> attached to ttyUSB1 (or usb/tts/1 for devfs)
> Jan 31 01:27:02 broccoli kernel: usb.c: serial driver claimed interface
> dbda8a00
>
> If you get that far, your kernel is at least recognizing the
> device.
The kernel is recognizing my device, when I try to hotsync
(unsuccessfully) I get:
Feb 2 17:35:44 fernani kernel: hub.c: USB new device connect on bus1/2, assigned device number 2
Feb 2 17:35:44 fernani kernel: usb.c: USB device 2 (vend/prod 0x54c/0x66) is not claimed by any active driver.
Feb 2 17:35:45 fernani /etc/hotplug/usb.agent: Modprobe and setup visor for USB product 54c/66/100
Feb 2 17:35:45 fernani kernel: usb.c: registered new driver serial
Feb 2 17:35:45 fernani kernel: usbserial.c: USB Serial Driver core v1.4
Feb 2 17:35:45 fernani kernel: usbserial.c: USB Serial support registered for Handspring Visor
Feb 2 17:35:45 fernani kernel: usbserial.c: USB Serial support registered for Palm 4.0
Feb 2 17:35:45 fernani kernel: usbserial.c: USB Serial support registered for Sony Clié 3.5
Feb 2 17:35:45 fernani kernel: usbserial.c: USB Serial support registered for Sony Clié 4.0
Feb 2 17:35:45 fernani kernel: usbserial.c: Sony Clié 4.0 converter detected
Feb 2 17:35:45 fernani kernel: visor.c: Sony Clié 4.0: Number of ports: 2
Feb 2 17:35:45 fernani kernel: visor.c: Sony Clié 4.0: port 1, is for Generic use and is bound to ttyUSB0
Feb 2 17:35:45 fernani kernel: visor.c: Sony Clié 4.0: port 2, is for HotSync use and is bound to ttyUSB1
Feb 2 17:35:45 fernani kernel: usbserial.c: Sony Clié 4.0 converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
Feb 2 17:35:45 fernani kernel: usbserial.c: Sony Clié 4.0 converter now attached to ttyUSB1 (or usb/tts/1 for devfs)
Feb 2 17:35:45 fernani kernel: visor.c: USB HandSpring Visor, Palm m50x, Sony Clié driver v1.5
>
> The reason I stress hitting HotSync on the cradle, is that if
> you have your HotSync icon set to Ir/Serial for example, tapping on
> that icon on the screen would try to send the serial data out the IrDA
> port, not the physical USB port. Hitting HotSync on the cradle ensures
> that you are using the USB port (a little-known trick, so you don't
> have to keep changing modes all the time).
I don't use IR at all anyway, it's set to Cradle/Cable. Now, when I hit
hotsync for a second time, beside the messages above, I also get
something from hotplug:
Feb 2 17:41:09 fernani /etc/hotplug/usb.agent: Modprobe and setup visor for USB product 54c/66/100
And I can hotsync with no problem. Occasionally, this will work the
first time, but I haven't found any way to reproduce either failure or
success.
--
Ivan Fernández
ivan.fernandez@vanderbilt.edu
--
This message was sent through the coldsync-hackers mailing list. To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body. For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.