Date: Sat, 28 Mar 2009 11:00:32 +0100 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-current@freebsd.org Cc: Lars Engels <lars.engels@0x20.net>, current@freebsd.org Subject: Re: Problems with usb bluetooth device Message-ID: <200903281100.33957.hselasky@c2i.net> In-Reply-To: <20090328095030.GD64269@e.0x20.net> References: <20090328095030.GD64269@e.0x20.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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=2, set address failed! (ignored) > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > usb2_req_re_enumerate:1421: addr=2, set address failed! (ignored) > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > ugen0.2: <> at usbus0 (disconnected) > after loading ng_ubt: > uhub_reattach_port:413: could not allocate new device! > ubt0: <Broadcom Corp Foxconn Bluetooth 2.0 plus EDR, class 224/1, rev > 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: <Cambridge Silicon Radio> at usbus0 > ubt1: <Cambridge Silicon Radio Bluetooth USB dongle, class 224/1, rev > 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: <Cambridge Silicon Radio> 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=2, set address failed! (ignored) > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > usb2_req_re_enumerate:1421: addr=2, set address failed! (ignored) > usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed! > 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: <UHCI root HUB Intel> at usbus0, cfg=0 md=HOST > spd=FULL (12Mbps) pwr=ON ugen1.1: <UHCI root HUB Intel> at usbus1, cfg=0 > md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: <UHCI root HUB Intel> at usbus2, > cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: <UHCI root HUB Intel> at > usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: <EHCI root HUB > Intel> at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen2.2: <Foxconn > Bluetooth 2.0 plus EDR Broadcom Corp> at usbus2, cfg=0 md=HOST spd=FULL > (12Mbps > pwr=ON > > It only lists the internal device... > > My CURRENT was compiled two days ago, so I should be up-to-date. Does it work when you use an external USB HUB? Does this device have some kind of autoinstall on it? You could try enabling uhci/ehci debugging. sysctl hw.usb2.uhci.debug = 15 Then we would know the exact cause of the error. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200903281100.33957.hselasky>