From owner-freebsd-questions@FreeBSD.ORG Tue Oct 17 21:08:58 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBA8816A403 for ; Tue, 17 Oct 2006 21:08:58 +0000 (UTC) (envelope-from dwiest@vailsys.com) Received: from dprobd02.vailsys.com (dprobd02.vailsys.com [63.149.73.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D98F43D5C for ; Tue, 17 Oct 2006 21:08:58 +0000 (GMT) (envelope-from dwiest@vailsys.com) Received: from dfsfbd06.vail (dfsfbd06.vail [192.168.129.190]) by dprobd02.vailsys.com (Postfix) with ESMTP id DA19E8A5C9D for ; Tue, 17 Oct 2006 16:08:57 -0500 (CDT) Received: from dfwdamian.vail (dfwdamian.vail [192.168.129.233]) by dfsfbd06.vail (Postfix) with ESMTP id B0D14323E9B for ; Tue, 17 Oct 2006 16:08:57 -0500 (CDT) Received: from dfwdamian.vail (dwiest@localhost.vail [127.0.0.1]) by dfwdamian.vail (8.13.4/8.13.4) with ESMTP id k9HL7fHD027773 for ; Tue, 17 Oct 2006 16:07:41 -0500 (CDT) Received: (from dwiest@localhost) by dfwdamian.vail (8.13.4/8.13.4/Submit) id k9HL7ekN023456 for freebsd-questions@freebsd.org; Tue, 17 Oct 2006 16:07:40 -0500 (CDT) X-Authentication-Warning: dfwdamian.vail: dwiest set sender to dwiest@vailsys.com using -f Date: Tue, 17 Oct 2006 16:07:40 -0500 From: Damian Wiest Cc: freebsd-questions@freebsd.org Message-ID: <20061017210740.GB9251@dfwdamian.vail> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Subject: Re: Problems with USB Palm sync X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2006 21:08:58 -0000 On Tue, Oct 17, 2006 at 04:29:49PM -0400, Jonathan Arnold wrote: > Has anyone had any luck using pilot-link to sync JPilot to a Palm > device via the USB? I'm trying to sync my Handspring Visor and it just > doesn't seem to be noticing it. I have the following in my > /dev/usbd.conf file: > > device "Handspring Visor" > devname "ugen[0-9]+" > vendor 0x082d > product 0x0100 > release 0x0100 > attach "chmod 0666 /dev/ugen*" > > as per the code that was in there for the coldsync. When I press the > sync button on the cradle, these devices show up: > > crw-rw-rw- 1 root operator 0, 181 Oct 17 13:45 /dev/ugen0 > crw-rw-rw- 1 root operator 0, 182 Oct 17 13:45 /dev/ugen0.1 > crw-rw-rw- 1 root operator 0, 183 Oct 17 13:45 /dev/ugen0.2 > > And the following shows up in my dmesg: > > ugen0: Handspring Inc Handspring Visor, rev 1.00/1.00, addr 5 > ugen0: at uhub6 port 4 (addr 5) disconnected > All threads purged from ugen0.2 > All threads purged from ugen0.1 > All threads purged from ugen0 > ugen0: detached > > But the pilot-link command fails immediately: > > $ pilot-xfer -p /dev/ugen0 -l > Unable to bind to port: /dev/ugen0 > Please use --help for more information > > Any ideas? I've googled all over the place, but I only see similiar > questions. And the FreeBSD.README on the pilot-link web site seems to > be misleading at best. > > -- > Jonathan Arnold (mailto:jdarnold@buddydog.org) > Daemon Dancing in the Dark, a FreeBSD weblog: > http://freebsd.amazingdev.com/blog/ > > UNIX is user-friendly. It's just a bit picky about who its friends are. I've had success syncing my Palm OS based phone (SPH-i500 FWIW) to my laptop using jpilot with a USB connection. Do you have permissions to access /dev/ugen0? -Damian