From owner-freebsd-questions Tue Oct 2 14:53:47 2001 Delivered-To: freebsd-questions@freebsd.org Received: from pinky.us.net (pinky.us.net [216.181.215.124]) by hub.freebsd.org (Postfix) with ESMTP id 412A437B401 for ; Tue, 2 Oct 2001 14:53:41 -0700 (PDT) Received: (qmail 17711 invoked from network); 2 Oct 2001 21:53:40 -0000 Received: from pinky.us.net ([216.181.215.124]) (envelope-sender ) by pinky.us.net (qmail-ldap-1.03) with SMTP for ; 2 Oct 2001 21:53:40 -0000 Date: Tue, 2 Oct 2001 17:53:38 -0400 (EDT) From: Brian Skrab To: Jason Stephenson Cc: "freebsd-questions@freebsd.org" Subject: Re: Syncing Handspring Visor over USB In-Reply-To: <200109041543.f84FhTI16815@blackbird.ecc.engr.uky.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jason, Which Visor model are you using? My Visor Deluxe (PalmOS 3.1) works flawlessly over the USB cradle to my FreeBSD box. The newer models (Platinum, Prism, Edge, Neo, Pro) all use PalmOS 3.5 which seems to be the common factor in breaking Coldsync's ability to talk USB to the Visor. I have personally tried Coldsync with the Edge and the Pro with the same results. The author of the Coldsync software is aware of this issue and is working to find a solution. He believes that both ends of the connection are blocking on reads from each other. Coldsync is waiting on a packet that the Visor believes it sent, and the Visor is waiting on a reply from Coldsync. The lock ends when the Visor times out and drops the connection. As a workaround, you can pick up a serial cradle which works without a problem, albeit quite a bit slower. Hope this helps. ~brian skrab bgs@pinky.us.net On Tue, 4 Sep 2001, Jason Stephenson wrote: > I've tried both of the following with coldsync: > > coldsync -t usb -p /dev/ugen0 -l sync.log -mI > coldsync -t usb -p /dev/ugen0 -l sync.log -mb palmstuff > > both as root and as my regular user account. I've chmod'd both /dev/ugen0 and > /dev/ugen0.2 0666, and I've made sure that all of the USB devices are > compiled into my kernel. > > Regardless of which user I run it as or which command I try above, I get the > following in my sync.log: > > Log started on Tue Sep 4 11:33:50 2001 > 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. > > Log closed on Tue Sep 4 11:34:08 2001 > > If I try the other USB port on the back of the machine, I get a different > error: > > Log started on Tue Sep 4 11:35:51 2001 > pconn_usb_open: Can't open USB device. > open: Bad file descriptor > Error: Can't open connection. > > Log closed on Tue Sep 4 11:36:22 2001 > > I assume that's because ugen0 is the "1st" USB port. > > Here's the output of uname -a, if that's also helpful: > > FreeBSD blackbird.ecc.engr.uky.edu 4.3-RELEASE-p14 FreeBSD 4.3-RELEASE-p14 > #1: Thu Aug 23 16:38:51 EDT 2001 > root@blackbird.ecc.engr.uky.edu:/usr/src/sys/compile/BLACKBIRD i386 > > Anyone seen anything like this before? Any help would be helpful, and greatly > appreciated. :-) > > -- > Jason Stephenson UNIX Administrator > University of Kentucky College of Engineering Computing Services > 280 Anderson Hall 257-5497 > jjas@engr.uky.edu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message