From owner-freebsd-questions@FreeBSD.ORG Tue Apr 6 11:47:36 2004 Return-Path: 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 E631816A4CE for ; Tue, 6 Apr 2004 11:47:36 -0700 (PDT) Received: from totem.fix.no (totem.fix.no [80.91.36.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB7C743D39 for ; Tue, 6 Apr 2004 11:47:36 -0700 (PDT) (envelope-from espent@totem.fix.no) Received: from localhost (totem.fix.no [80.91.36.20]) by totem.fix.no (Postfix) with ESMTP id 1765C2ED39C for ; Tue, 6 Apr 2004 20:46:49 +0200 (CEST) Received: from totem.fix.no ([80.91.36.20]) by localhost (totem.fix.no [80.91.36.20]) (amavisd-new, port 10024) with LMTP id 45078-01-3 for ; Tue, 6 Apr 2004 20:46:48 +0200 (CEST) Received: by totem.fix.no (Postfix, from userid 1032) id 44B692ED399; Tue, 6 Apr 2004 20:46:48 +0200 (CEST) Date: Tue, 6 Apr 2004 20:46:48 +0200 From: Espen Tagestad To: freebsd-questions@freebsd.org Message-ID: <20040406184648.GA45019@totem.fix.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i Subject: FreeBSD 4.9-STABLE and Palm Tungsten T USB X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Apr 2004 18:47:37 -0000 Hi, Has anyone managed to get the Palm Tungsten T USB working properly with the FreeBSD uvsior/ucom interface and pilot-link? I tried several solutions written on the web, including the one which suggest Hotsync over network by running a ppp-daemon to make the connection with the Palm. None of them worked. Some weeks ago I tried pilot-link on a Debian GNU/Linux computer, and it 'just worked'. The message I get from my FreeBSD box when pressing the hotsync-button on the cradle is as follows: ucom0: Palm, Inc. Palm Handheld, rev 1.10/1.00, addr 2 ucom0: Palm, Inc. Palm Handheld, rev 1.10/1.00, addr 2 ucom0: init failed, TIMEOUT device_probe_and_attach: ucom0 attach returned 6 uhub0: port 1, set config at addr 2 failed uhub0: device problem, disabling port 1 I know the Tungsten T product_id has been added to the usbdevs-files in the kernel source tree, but still I can't get it to work. Anyway, pilot-xfer will not accept /dev/ucom0 as a valid device. Does anyone have a solution that might work? regards, Espen Tagestad