Re: [coldsync-hackers] FreeBSD 4.3 + m505

[Andrew Arensburger <arensb+CShackers@ooblick.com>]

On Sat, Aug 18, 2001 at 05:14:42PM +0000, daniel webster wrote:
> I've read through the archives, but am still having no luck
> with coldsync 2.2.0 snap, and 4.3-STABLE, with my Palm m505

	Just so you know: the m50x Palms aren't well-supported. In
fact, I don't think there's been a report of them working under
FreeBSD. But it's (hopefully) getting there; you'll have most luck
with the latest snapshot.

> In my homedir (as dsw), i have the following in my .coldsyncrc:
> 
> listen usb {
> 	device: "/dev/ugen0";
>         protocol: m50x;
> 
> }

	Try
	protocol: net;
instead: currently, the "m50x" protocol includes a hack to work around
a bug in Linux. "net" is exactly the same as "m50x", but without the
workaround.

> Also, in my /etc/usbd.conf file, I have added the following 
> entry:
> 
> device "Palm m505"
> vendor  0x0830
> attach "/usr/local/bin/coldsync -mI -t usb -p /dev/ugen0 -P m50x"

	By the way, could you please send me the product and release
numbers? Plug in your Palm, press the HotSync button, and run
	usbdevs -v
that should give you all the above information.

	Also, have you tried simply running ColdSync on the command
line? As long as you have read and write permission on /dev/ugen0 and
/dev/ugen0.2, it ought to work (but check your local reality).

> I get the nasty error:
> 
> drednort$ coldsync -t usb -p /dev/ugen0 -P m50x
> Please press the HotSync button.
> pconn_usb_open: Warning: Unexpected USB vendor ID 0x830.

	This is because the USB code was originally written for
Handspring Visors, so when it checks the device vendor code, it
expects to see a Handspring. The fix is to edit
libpconn/PConnection_usb.c : after the definition of
HANDSPRING_VENDOR_ID, add a similar line for Palm. Further down, where
it checks the device vendor ID (the only place where
HANDSPRING_VENDOR_ID is actually used), have it check for Palm's ID as
well.

> [ ... after a timeout period ... ]
> 
> usb read: Input/output error
> slp_read: read: Input/output error
> Error during cmp_read: (1) Error in system call or library function.
> Error: Can't connect to Palm.

	Looking at the source for ugen, there are about half a dozen
reasons why a read() might fail this way, so unfortunately this isn't
very informative.
	Given that this is happening in cmp_read(), it would appear
that the early part of the negotiation with the Palm has succeeded,
and the problem is occurring later on.
	Unfortunately, I don't have a m50x to experiment with, so
there's little I can do to help. If you could run ColdSync with

	-dsync:5 -dmisc:5 -dio:5

and send me the output, that might shed some light on the problem.
Also, "-dio:N" turns on debugging in the USB driver, so there should
also be some relevant stuff in the output of 'dmesg' or in
/var/log/messages.
	I hesitate to ask you to send this data to the list, as it's
likely to be rather long.

-- 
Andrew Arensburger                      This message *does* represent the
arensb@ooblick.com                      views of ooblick.com
	 "Stop quoting me, you blubbering twit!" -- Confucius
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.