From owner-freebsd-usb@FreeBSD.ORG Sun Jul 19 15:54:00 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0FE01065672 for ; Sun, 19 Jul 2009 15:54:00 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.swip.net [212.247.154.161]) by mx1.freebsd.org (Postfix) with ESMTP id 4AC148FC08 for ; Sun, 19 Jul 2009 15:54:00 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=Bx_xhd6jh-gA:10 a=hlIU1J3LQChSjWV/CGRL5g==:17 a=pguAPB8zN9Ghd5BfnTkA:9 a=EEwoTqm4VVoa6DfzAmRao1ZQswsA:4 Received: from [193.217.167.6] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe06.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1280147914; Sun, 19 Jul 2009 17:53:58 +0200 From: Hans Petter Selasky To: Michael Gmelin Date: Sun, 19 Jul 2009 17:53:44 +0200 User-Agent: KMail/1.11.4 (FreeBSD/8.0-BETA2; KDE/4.2.4; i386; ; ) References: <4A62187E.1000506@bindone.de> <200907191530.05768.hselasky@c2i.net> <4A63393C.7020907@bindone.de> In-Reply-To: <4A63393C.7020907@bindone.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907191753.45762.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: [usb2] Garmin Edge 705 disconnects immediately X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jul 2009 15:54:01 -0000 On Sunday 19 July 2009 17:18:20 Michael Gmelin wrote: > Hans Petter Selasky wrote: > > On Sunday 19 July 2009 14:14:23 Michael Gmelin wrote: > >> Hans Petter Selasky wrote: > >>> On Saturday 18 July 2009 20:46:22 Michael Gmelin wrote: > >>>> Hello, > >>>> > >>>> I'm trying to access a Garmin Edge 705 bike computer, which should > >>>> show up as a mass storage device. > >>>> > >>>> kldload usb2_controller_uhci|ehci > >>>> > >>>> Jul 18 19:37:55 ufo kernel: ugen2.2: at usbus2 > >>>> Jul 18 19:37:55 ufo kernel: ugen2.2: at usbus2 > >>>> (disconnected) > >>>> > >>>> kldload usb2_storage_mass > >>>> kldload usb2_controller_uhci > >>>> Jul 18 19:38:06 ufo kernel: ugen2.2: at usbus2 > >>>> Jul 18 19:38:06 ufo kernel: umass0: >>>> class 0/0, rev 1.10/5.09, addr 2> on usbus2 > >>>> Jul 18 19:38:06 ufo kernel: umass0: SCSI over Bulk-Only; quirks = > >>>> 0x0000 Jul 18 19:38:08 ufo kernel: umass0:1:0:-1: Attached to scbus1 > >>>> Jul 18 19:38:08 ufo kernel: umass0: at ushub2, port 1, addr 2 > >>>> (disconnected) Jul 18 19:38:08 ufo kernel: ugen2.2: >>>> International> at usbus2 (disconnected) > >>>> > >>>> Tried various quirks without any success for usb2_storage_mass (afaik > >>>> it should be SCSI | BBB). Also tried all possible orders of attaching > >>>> the device/ > >>>> > >>>> Setting various debugging sysctls didn't give any useful hints (didn't > >>>> see anything extraordinary). > >>>> usbconfig doesn't show anything because the device disappears > >>>> immediately. I would assume that this is not a problem with _storage > >>>> but the device expecting some initialization which doesn't happen (or > >>>> happens too often). Also tried various usb2_quirk settings, all > >>>> without success. > >>>> > >>>> VendorId: 0x091e > >>>> ProductId: 0x2271 > >>>> > >>>> Maybe someone can give me a hint where to start debugging this. > >>> > >>> You can try: > >>> > >>> sysctl hw.usb.debug=15 > >>> > >>> I suspect that the USB stack in your device has some bugs. Sounds like > >>> the bike-computer manufacturer are not the ones to spend the most money > >>> on USB. > >>> > >>> --HPS > >> > >> I attached you the log output which clearly indicates trouble. Maybe > >> some more info on the device: It has in-built memory + a memory card, > >> which should come up as separate devices. It boots up and shows that it > >> is connected to a computer, after a couple of seconds (once detach > >> failed) it will fallback to charging mode. I think the device could also > >> used as a serial device to gather GPS input, so maybe that's part of the > >> problem. > >> > >> Considering the price of the device I wish they would have spent more > >> money on usb. On the other hand the GPS sensor is fantastic and the > >> device overall is really awesome (it seems to mount ok under linux and I > >> couldn't find anyone who had to do any patching for that, the linux > >> kernel also no quirks for it, so I hope it's just a minor flaw in the > >> protocol that makes usb2 fail because it aims to be standard compliant > >> :). > > > > Could you redo the trace without umass loaded? > > > > --HPS > > Here it comes Aren't there any printouts before: Jul 19 17:16:31 ufo kernel: usb2_alloc_device:1625: new dev (addr 2), udev=0x86f2c000, parent_hub=0x86f2f000 Looking at Google, it might look like your device needs a skip-set-config quirk. --HPS