Date: Tue, 20 May 2008 01:48:34 +0000 From: "Leonardo Santagostini" <lsantagostini@gmail.com> To: "Maksim Yevmenkin" <maksim.yevmenkin@gmail.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Problem with a BCM2035B dongle Message-ID: <9ab7eeeb0805191848p11e3b6d4u9bdd423e4e7d2533@mail.gmail.com> In-Reply-To: <bb4a86c70805191032l283cab0dpb44546260855e597@mail.gmail.com> References: <9ab7eeeb0805190319u30ccbeefq1511afa063bd75fe@mail.gmail.com> <bb4a86c70805191032l283cab0dpb44546260855e597@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry, but, by the way. In the manufacturer page says: The BCM2035 is based on the production and UnPlugFest proven architecture of the BCM2033 <http://broadcom.com/products/BCM2033>; Bluetooth baseband core (BBC), peripheral transport unit (PTU) http://broadcom.com/products/Bluetooth/Bluetooth-RF-Silicon-and-Software-Solutions/BCM2035 Do you think we can make something ? Yours, Leonardo 2008/5/19 Maksim Yevmenkin <maksim.yevmenkin@gmail.com>: > Hello, > > > I was already googling and browsing over Internet about mi problem. > > Im using FreeBSD 7.0-RELEASE and the problem is that the donlge dont want > to > > work. > > > > I tried kldloanding various modeules, here comes my kldstat > > pcleo# kldstat > > Id Refs Address Size Name > > 1 32 0xc0400000 9130cc kernel > > 2 1 0xc0d14000 ce30 if_wi.ko > > 3 1 0xc0d21000 14324 snd_hda.ko > > 4 2 0xc0d36000 4a5ac sound.ko > > 5 1 0xc0d81000 19f34 if_ral.ko > > 6 1 0xc0d9b000 80ea28 nvidia.ko > > 7 2 0xc15aa000 28658 linux.ko > > 8 1 0xc15d3000 3130 ubtbcmfw.ko > > 9 1 0xc15d7000 802c ng_ubt.ko > > 10 6 0xc15e0000 d3a0 netgraph.ko > > 11 1 0xc15ee000 1bdc wlan_xauth.ko > > 12 1 0xc15f0000 6a32c acpi.ko > > 13 4 0xc5529000 2000 ng_bluetooth.ko > > 14 1 0xc552b000 d000 ng_hci.ko > > 15 1 0xc5558000 f000 ng_l2cap.ko > > 16 1 0xc5569000 19000 ng_btsocket.ko > > 17 1 0xc558b000 4000 ng_socket.ko > > looks fine > > > The /var/log/messages tells: > > > > May 19 07:09:47 pcleo root: Unknown USB device: vendor 0x0a5c product > 0x2035 > > bus uhub1 > > May 19 07:09:47 pcleo kernel: ubt0: <Broadcom Corp BCM2035B, class 224/1, > > rev 2.00/1.00, addr 3> on uhub1 > > May 19 07:09:47 pcleo kernel: ubt0: Interface 0 endpoints: > interrupt=0x81, > > bulk-in=0x82, bulk-out=0x2 > > May 19 07:09:47 pcleo kernel: ubt0: Interface 1 (alt.config 4) endpoints: > > isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 > > May 19 07:09:47 pcleo root: /etc/rc.d/bluetooth: ERROR: Unable to setup > > Bluetooth stack for device ubt0 > > this does not look good. > > i been trying bcmfw without results, in fact, when i do a ls -l /dev/u* i > > cant see an ubtbcmfw device created. > > > > pcleo# ls -l /dev/u* > > crw-r--r-- 1 root operator 0, 79 May 19 06:29 /dev/uhid0 > > crw------- 1 root wheel 0, 77 May 19 06:29 /dev/ukbd0 > > lrwxr-xr-x 1 root wheel 6 May 19 06:29 /dev/urandom -> > random > > crw-rw---- 1 root operator 0, 38 May 19 06:29 /dev/usb > > crw-rw---- 1 root operator 0, 37 May 19 06:29 /dev/usb0 > > crw-rw---- 1 root operator 0, 39 May 19 06:29 /dev/usb1 > > crw-rw---- 1 root operator 0, 40 May 19 06:29 /dev/usb2 > > ubtbcmfw(4) is a firmware driver for broadcom bcm2033 chip based > bluetooth usb devices. since you have bcm2035b this driver will not > work and you do not even need it. > > > I followed the instructions for dumping my device, here is. > > ok, i think, i know what problem is. here is the fragment of the dump > you sent, i.e. > > beetle% ./hcidump -xr ~/init.dump > HCIDump - HCI packet analyzer ver 1.5 > < HCI Command: Reset(0x03|0x0003) plen 0 > > HCI Event: Command Complete(0x0e) plen 4 > 01 03 0C 00 > < HCI Command: Read BD ADDR(0x04|0x0009) plen 0 > > HCI Event: Command Complete(0x0e) plen 10 > 01 09 10 00 00 00 00 00 00 00 > > it appears that in response to the hci "read bd addr" command your > device returns an invalid bd_addr, i.e. 00:00:00:00:00:00. i saw a > post in one of the linux bluetooth related mailing lists that > describes exactly the same problem > (http://www.spinics.net/lists/linux-bluetooth/msg00020.html). i have > no idea how to fix it at this point, and, inclined to say that this > device is broken or needs some non-standard initialization sequence. > i'd suggest to get a different dongle if possible. > > thanks, > max > -- Saludos.- Leonardo Santagostini
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9ab7eeeb0805191848p11e3b6d4u9bdd423e4e7d2533>