From owner-freebsd-mobile Sat Oct 26 21: 7:23 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1817B37B401 for ; Sat, 26 Oct 2002 21:07:22 -0700 (PDT) Received: from strange.eng.utoledo.edu (strange.eng.utoledo.edu [131.183.18.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFC6143E42 for ; Sat, 26 Oct 2002 21:07:19 -0700 (PDT) (envelope-from rafege@mail.com) Received: from strange.eng.utoledo.edu ([131.183.21.44]) by strange.eng.utoledo.edu (8.9.3/8.9.3/1.1) with SMTP id AAA16668 for ; Sun, 27 Oct 2002 00:07:18 -0400 (EDT) Message-Id: <200210270407.AAA16668@strange.eng.utoledo.edu> Received: by strange.eng.utoledo.edu (sSMTP sendmail emulation); Sun, 27 Oct 2002 00:07:14 -0400 Date: Sun, 27 Oct 2002 00:07:14 -0400 From: rafege@mail.com (G.E. Rafe) To: freebsd-mobile@freebsd.org Subject: Re: coldsync-2.2.5 w/Palm m130 via USB ? Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org !Sure, here we go: !Sep 27 16:06:55 piglet /kernel: ucom0: Palm, Inc. Palm Handheld, rev !1.00/1.00, addr 3 ! !> Or give more info... !> this is my output. !> Kernel has : ucom, uplcom and uvscom devices/support !> Sep 27 13:04:51 dori /kernel: ugen0: Palm, Inc. Palm Handheld, rev !> 1.00/1.00, addr 2 ! !It is important that you don't let the ugen driver get the device. !This means you either should load uvisor (kldload uvisor) prior to !pressing the sync button (for e.g. in /etc/rc.local) or you should !configure usbd to load the driver (which means the first sync will !fail - or at least I don't know how to do it ;). ! !Put the following lines in /etc/usbd.conf for the second approach: !device "Palm m125" ! vendor 0x830 ! product 0x0040 ! release 0x0100 ! attach "if ! kldstat -n uvisor > /dev/null 2>&1 ; then kldload uvisor; fi" Hank -- We just upgraded our Toshiba Satellite Pro 4600 to 4.7-R and gave our USB-connected Palm m130 cradle a go with the information you forwarded earlier. With devices "ucom" & "uvisor" compiled into the kernel, we still get the ugen0 connection when the HotSync button is pressed: ugen0: Palm, Inc. Palm Handheld, rev 1.00/1.00, addr 5 With the Palm device connected, "usbdevs -v" returns: port 4 addr 5: self powered, config 1, Palm Handheld(0x0050), Palm, Inc.(0x0830), rev 1.00 Following your original suggestion, we took the ucom & uvisor devices out of the kernel, recompiled, and updated /etc/usbd.conf with "product 0x0050", as noted in usbdevs. Pressing the HotSync button loads the ucom & uvisor kernel modules OK, but ugen continues to pick it up, instead ! I suppose the next step is to build a kernel without "ugen" & see how the kernel reacts to the HotSync button. Perhaps there's still another trick to force a connection with ucom/uvisor. -- Gary E. RAFE, PhD grafe@eng.utoledo.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message