Date: Thu, 12 Jan 2006 10:36:42 +1030 From: "scycoon@internode.on.net" <scycoon@internode.on.net> To: freebsd-bluetooth@freebsd.org Subject: Bluetooth Device Failing to Initialize Message-ID: <43c59d92.36a.33a6.26043@internode.on.net>
next in thread | raw e-mail | index | archive | help
Hi There, I am have a problem with a linksys usbbt100 bluetooth dongle. I am running 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Sat Jan 7 08:48:40 CST 2006 >From dmesg I get this ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2 ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2 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 I have setup the /etc/rc.bluetooth file as described in the handbook, and am using the ng_ubt module that is said to be the correct one. When i run /etc/rc.bluetooth start ubt0 I get bash-2.05b# /etc/rc.bluetooth start ubt0 BD_ADDR: 00:0c:41:e2:01:84 Features: 0xff 0xff 0xf 00 00 00 00 00 <3-Slot> <5-Slot> <Encryption> <Slot offset> <Timing accuracy> <Switch> <Hold mode> <Sniff mode> <Park mode> <RSSI> <Channel quality> <SCO link> <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD> <Paging scheme> <Power control> <Transparent SCO data> Max. ACL packet size: 192 bytes Number of ACL packets: 8 Max. SCO packet size: 64 bytes Number of SCO packets: 8 Could not execute command "initialize". Device not configured if i run hccontrol -n ubt0hci initialize i get bash-2.05b# hccontrol -n ubt0hci initialize Could not execute command "initialize". Device not configured I am running hcidump at the same time, which doesnt seem to see the initialize command; bash-2.05b# hcidump HCIDump - HCI packet analyzer ver 1.5 device: any snap_len: 65535 filter: 0xffffffff < HCI Command: Reset(0x03|0x0003) plen 0 > HCI Event: Command Complete(0x0e) plen 4 < HCI Command: Read BD ADDR(0x04|0x0009) plen 0 > HCI Event: Command Complete(0x0e) plen 10 < HCI Command: Read Local Supported Features(0x04|0x0003) plen 0 > HCI Event: Command Complete(0x0e) plen 12 < HCI Command: Read Buffer Size(0x04|0x0005) plen 0 > HCI Event: Command Complete(0x0e) plen 11 < HCI Command: Write Scan Enable(0x03|0x001a) plen 1 > HCI Event: Command Complete(0x0e) plen 4 < HCI Command: Write Class of Device(0x03|0x0024) plen 3 > HCI Event: Command Complete(0x0e) plen 4 < HCI Command: Change Local Name(0x03|0x0013) plen 248 > HCI Event: Command Complete(0x0e) plen 4 The device looks like it is ok, but something freaky is not allowing it to initialize properly and subsequent inquiry commands just time out. I should also point out that I have had the dongle working in Windows Land. Would this failure to initialize be preventing me from successfuly inquiring another device? Any help would be greatly appreciated. Regards Chriso
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43c59d92.36a.33a6.26043>