From owner-freebsd-current@FreeBSD.ORG Sat Mar 28 11:04:24 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB3AE106566C; Sat, 28 Mar 2009 11:04:23 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from mail.0x20.net (unknown [IPv6:2001:aa8:fffb::3]) by mx1.freebsd.org (Postfix) with ESMTP id 878AC8FC13; Sat, 28 Mar 2009 11:04:23 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: by mail.0x20.net (Postfix, from userid 1002) id 8F77B38EDA; Sat, 28 Mar 2009 12:04:22 +0100 (CET) Date: Sat, 28 Mar 2009 12:04:22 +0100 From: Lars Engels To: Hans Petter Selasky Message-ID: <20090328110421.GF64269@e.0x20.net> Mail-Followup-To: Lars Engels , Hans Petter Selasky , freebsd-current@freebsd.org, current@freebsd.org References: <20090328095030.GD64269@e.0x20.net> <200903281100.33957.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ncSAzJYg3Aa9+CRW" Content-Disposition: inline In-Reply-To: <200903281100.33957.hselasky@c2i.net> X-Editor: VIM - Vi IMproved 7.2 X-Operation-System: FreeBSD 5.5-RELEASE-p19 User-Agent: Mutt/1.5.19 (2009-01-05) Cc: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: Problems with usb bluetooth device X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Mar 2009 11:04:24 -0000 --ncSAzJYg3Aa9+CRW Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 28, 2009 at 11:00:32AM +0100, Hans Petter Selasky wrote: > On Saturday 28 March 2009, Lars Engels wrote: > > Hi all, > > > > yesterday I bought a shiny new hama usb bluetooth dongle but I am having > > some problems using it: > > > > before loading ng_ubt: > > usb2_alloc_device:1480: set address 2 failed (ignored) > > usb2_alloc_device:1516: getting device descriptor at addr 2 failed! > > usb2_req_re_enumerate:1421: addr=3D2, set address failed! (ignored) > > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 faile= d! > > usb2_req_re_enumerate:1421: addr=3D2, set address failed! (ignored) > > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 faile= d! > > ugen0.2: <> at usbus0 (disconnected) > > after loading ng_ubt: > > uhub_reattach_port:413: could not allocate new device! > > ubt0: > 2.00/1.00, addr 2> on usbus2 ^^^^^^^^^^ > > internal bluetooth device > > WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() > > WARNING: attempt to net_add_domain(netgraph) after domainfinalize() > > ugen0.2: at usbus0 > > ubt1: > 2.00/48.39, addr 2> on usbus0 ubt1: ubt_bulk_read_callback:837: bulk-in > > transfer failed: USB_ERR_STALLED ubt1: ubt_intr_read_callback:741: > > interrupt transfer failed: USB_ERR_STALLED ubt1: at uhub0, port 1, addr= 2 > > (disconnected) > > ugen0.2: at usbus0 (disconnected) > > device re-inserted: > > usb2_alloc_device:1480: set address 2 failed (ignored) > > usb2_alloc_device:1516: getting device descriptor at addr 2 failed! > > usb2_req_re_enumerate:1421: addr=3D2, set address failed! (ignored) > > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 faile= d! > > usb2_req_re_enumerate:1421: addr=3D2, set address failed! (ignored) > > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 faile= d! > > ugen0.2: <> at usbus0 (disconnected) > > uhub_reattach_port:413: could not allocate new device! > > > > So the device is no longer recognized after I re-connect it. usbconfig = does > > not show it: ugen0.1: at usbus0, cfg=3D0 md=3DHOST > > spd=3DFULL (12Mbps) pwr=3DON ugen1.1: at usbus1, = cfg=3D0 > > md=3DHOST spd=3DFULL (12Mbps) pwr=3DON ugen2.1: a= t usbus2, > > cfg=3D0 md=3DHOST spd=3DFULL (12Mbps) pwr=3DON ugen3.1: at > > usbus3, cfg=3D0 md=3DHOST spd=3DFULL (12Mbps) pwr=3DON ugen4.1: > Intel> at usbus4, cfg=3D0 md=3DHOST spd=3DHIGH (480Mbps) pwr=3DON ugen2= =2E2: > Bluetooth 2.0 plus EDR Broadcom Corp> at usbus2, cfg=3D0 md=3DHOST spd= =3DFULL > > (12Mbps = =20 > > pwr=3DON > > > > It only lists the internal device... > > > > My CURRENT was compiled two days ago, so I should be up-to-date. >=20 > Does it work when you use an external USB HUB? Yes, it's working with a usb hub: Hub inserted: Mar 28 11:46:30 maggie kernel: ugen4.2: at usbus4 Mar 28 11:46:30 maggie kernel: uhub5: on usbus4 Mar 28 11:46:31 maggie kernel: uhub5: 4 ports with 4 removable, self powe= red Dongle inserted: Mar 28 11:46:41 maggie root: Unknown USB device: vendor 0x0a12 product 0x= 0001 bus uhub5 Mar 28 11:46:41 maggie kernel: ugen4.3: at usbu= s4 Mar 28 11:46:41 maggie kernel: ubt1: on usbus4 >=20 > Does this device have some kind of autoinstall on it? I don't think so. There was a windows driver cd included. > You could try enabling uhci/ehci debugging. > sysctl hw.usb2.uhci.debug =3D 15 Do you really want that? :) It produced hundreds of thousands of lines, so I trimmed it a bit: I inserted the dongle at 11:50:09 and copied you the next ~7 seconds to http://people.freebsd.org/~lme/messages.trimmed.bz2 > Then we would know the exact cause of the error. I hope you can see more in the messages than me ;-) --ncSAzJYg3Aa9+CRW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAknOBDUACgkQKc512sD3afjTSwCfZUTOEzfF134wS16pPiKo3HIB i+oAoIA59Z58LCVWVK2snJuaUXo8XKj+ =IXTf -----END PGP SIGNATURE----- --ncSAzJYg3Aa9+CRW--