On 8/28/08, Wayne Sierke <[EMAIL PROTECTED]> wrote:
> Hi,
>
>  I've got a couple of bluetooth USB adapters here and tried them out
>  recently on this i386 7-STABLE GENERIC kernel. I'm sure I had at least
>  one of them working previously, however neither of them seem to work
>  with ng_ubt(4):
>
>  ubt0: <Broadcom Corp BCM92045DG-Flash_UHE, class 224/1, rev 2.00/1.00, addr 
> 4> on uhub6
>  ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
>  ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; 
> wMaxPacketSize=64; nframes=5, buffer size=320
>  Unknown USB device: vendor 0x0a5c product 0x2100 bus uhub6
>  ubt_bulk_in_complete2: ubt0 - Bulk-in xfer failed, STALLED (17). No new xfer 
> will be submitted!
>  ubt_intr_complete2: ubt0 - Interrupt xfer failed, IOERROR (13). No new xfer 
> will be submitted!

that looks like some sort of usb problem.

>  and also
>
>  ubt0: <vendor 0x1131 product 0x1001, class 224/1, rev 1.10/1.34, addr 3> on 
> uhub4
>  ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
>  ubt0: Interface 1 (alt.config 2) endpoints: isoc-in=0x83, isoc-out=0x3; 
> wMaxPacketSize=17; nframes=16, buffer size=272
>  Unknown USB device: vendor 0x1131 product 0x1001 bus uhub4
>  WARNING: attempt to net_add_domain(bluetooth) after domainfinalize()
>  WARNING: attempt to net_add_domain(netgraph) after domainfinalize()

that actually looks normal to me.

>  But in the archives it looks as though others have used both of these
>  adapters successfully before.
>
>  e.g. Mihai Tanasescu reported in Aug 2007:
>         2. usbdevs -dv (freezes for about 1-2 seconds while displaying the 
> first device):
>
>         Controller /dev/usb0:
>         addr 1: full speed, self powered, config 1, UHCI root hub(0x0000),
>         VIA(0x0000), rev 1.00
>           uhub0
>          port 1 addr 2: full speed, self powered, config 1, ISSCBTA(0x1001),
>         vendor 0x1131(0x1131), rev 3.73
>            ubt0
>
>
>  and Bruce Cran reported in Sep 2007:
>         ubt0: <Broadcom Corp BCM92045DG Non-UHE, class 224/1, rev 2.00/0.00, 
> addr 2> on uhub1
>         ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, 
> bulk-out=0x2
>         ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, 
> isoc-out=0x3;
>         wMaxPacketSize=49; nframes=6, buffer size=294
>
>  Admittedly that looks like a slightly different revision of the BCM device.
>
>  Has support for these devices been removed or requires patches, etc?

no. those should work (i do not see any reason why they would not)

>  My usbdevs -lv (with the ISSC device attached to hub):

do you mean external usb hub? have you tried to connect your devices
directly (i.e. without external hub)?

[...]

>  In spite of adapters showing as associated with ubt and listed as ubt0,
>  I don't see any /dev/ubt* devices and /etc/rc.d/bluetooth start ubt0
>  fails:

there will not be any /dev/ubtX device nodes. there will be 'ubtX'
netgraph nodes. use 'ngctl li' to see if there are any nodes and how
many attached hooks they have. also, '/etc/rc.d/bluetooth start' will
be called automatically from by devd(8) when device is plugged. so all
you have to do is plug the device and everything should just work.

>         # /etc/rc.d/bluetooth start ubt0
>         /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for 
> device ubt0

yes, if you call 'start' when everything was already started it will
fail. the safer thing is to do 'restart' or 'stop' and then 'start'.

>         # kldstat
>         Id Refs Address    Size     Name
>          1   29 0xc0400000 979ad0   kernel
>          2    1 0xc0d7a000 5464     vesa.ko
>          3    4 0xc0d80000 28678    linux.ko
>          4    1 0xc0da9000 6f88     snd_ich.ko
>          5    2 0xc0db0000 4a62c    sound.ko
>          6    1 0xc0dfb000 4e0ef0   nvidia.ko
>          7    1 0xc12dc000 6a2c4    acpi.ko
>          8    1 0xc5171000 7000     linprocfs.ko
>          9    1 0xc5454000 2000     green_saver.ko
>         10    1 0xc52e8000 2000     rtc.ko
>         11    1 0xc5f9f000 7000     ng_ubt.ko
>         12    5 0xc5fa6000 b000     netgraph.ko
>         13    4 0xc5fd6000 2000     ng_bluetooth.ko
>         14    1 0xc5fd8000 d000     ng_hci.ko
>         15    1 0xc5ff2000 f000     ng_l2cap.ko
>         16    1 0xc6001000 1a000    ng_btsocket.ko
>         17    1 0xc601b000 4000     ng_socket.ko

this looks normal.

thanks,
max
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to