Rocketfish USB Bluetooth Adapter (Rebranded Broadcom BCM2045B3)

[alharaka]

I am running FC9 on my old Compaq Presario R3000. I recently purchased a Bluetooth USB adapter at Best Buy to test it with a headset for Skype. As always when buying their crap, I was quickly disappointed. The USB dongle is from Rocketfish, but dmesg clearly indicates it is a rebranded Broadcom BCM2045B3 chip. See the output below:

dmesg

usb 2-2.2: Product: BCM2045B3 ROM
usb 2-2.2: Manufacturer: Broadcom Corp
usb 2-2.3: new full speed USB device using ohci_hcd and address 12
usb 2-2.3: configuration #1 chosen from 1 choice
input: Broadcom Corp BCM2045B3 ROM as /devices/pci0000:00/0000:00:02.0/usb2/2-2/2-2.3/2-2.3:1.0/input/input16
input,hidraw1: USB HID v1.11 Mouse [Broadcom Corp BCM2045B3 ROM] on usb-0000:00:02.0-2.3
usb 2-2.3: New USB device found, idVendor=0a5c, idProduct=4503
usb 2-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-2.3: Product: BCM2045B3 ROM
usb 2-2.3: Manufacturer: Broadcom Corp
usb 2-2.2: USB disconnect, address 11
usb 2-2.3: USB disconnect, address 12
usb 2-2: reset full speed USB device using ohci_hcd and address 10
usb 2-2: device descriptor read/64, error -62
usb 2-2: device descriptor read/64, error -62
usb 2-2: reset full speed USB device using ohci_hcd and address 10
usb 2-2: device descriptor read/64, error -62
usb 2-2: device descriptor read/64, error -62
usb 2-2: reset full speed USB device using ohci_hcd and address 10
usb 2-2: device not accepting address 10, error -62
usb 2-2: reset full speed USB device using ohci_hcd and address 10
usb 2-2: device not accepting address 10, error -62
hub 2-2:1.0: hub_port_status failed (err = -19)
hub 2-2:1.0: hub_port_status failed (err = -19)
hub 2-2:1.0: hub_port_status failed (err = -19)
hub 2-2:1.0: activate --> -19
usb 2-2: USB disconnect, address 10
usb 2-2: new full speed USB device using ohci_hcd and address 13
usb 2-2: device descriptor read/64, error -62
usb 2-2: device descriptor read/64, error -62
usb 2-2: new full speed USB device using ohci_hcd and address 14
usb 2-2: device descriptor read/64, error -62
usb 2-2: device descriptor read/64, error -62
usb 2-2: new full speed USB device using ohci_hcd and address 15
usb 2-2: device not accepting address 15, error -62
usb 2-2: new full speed USB device using ohci_hcd and address 16
usb 2-2: device not accepting address 16, error -62
hub 2-0:1.0: unable to enumerate USB device on port 2
usb 2-2: new full speed USB device using ohci_hcd and address 17
usb 2-2: device descriptor read/64, error -62
usb 2-2: device descriptor read/64, error -62
usb 2-2: new full speed USB device using ohci_hcd and address 18
usb 2-2: device descriptor read/64, error -62
usb 2-2: device descriptor read/64, error -62
usb 2-2: new full speed USB device using ohci_hcd and address 19
usb 2-2: device not accepting address 19, error -62
usb 2-2: new full speed USB device using ohci_hcd and address 20
usb 2-2: device not accepting address 20, error -62
hub 2-0:1.0: unable to enumerate USB device on port 2

I assume the errors above are from using the wrong driver, I could be wrong. In any event, I plug into a different USB port, and it loads the same way, just without all the error messages above. As dmesg indicates, Fedora sees the device as a keyboard/mouse (USB Human Interface Device). This seems to be a fairly common problem with the crappier dongles. The end result is the incorrect drivers being loaded, and then the real fun begins. So I checked, and it appears to be loading the usbhid driver instead of hci_usb. See the output from more /proc/usb/bus/devices below:

Selection from /proc/bus/usb/devices

T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 26 Spd=12  MxCh= 3
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0a5c ProdID=4500 Rev= 1.00
S:  Manufacturer=Broadcom
S:  Product=BCM2045B2
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=255ms

T:  Bus=03 Lev=02 Prnt=26 Port=01 Cnt=01 Dev#= 27 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0a5c ProdID=4502 Rev= 1.00
S:  Manufacturer=Broadcom Corp
S:  Product=BCM2045B3 ROM
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=  2mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms

T:  Bus=03 Lev=02 Prnt=26 Port=02 Cnt=02 Dev#= 28 Spd=12  MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0a5c ProdID=4503 Rev= 1.00
S:  Manufacturer=Broadcom Corp
S:  Product=BCM2045B3 ROM
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=  2mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

Is there a way I can manually prevent usbhid loading, and load hci_usb instead? I have been using Linux for a year or so, but I am not good with the really heavy, low-level systems administration. My question highlights my ignorance, so laugh me off and tell me if it is not possible. I searched the forum, and no one has posted about this for Fedora. Many Ubuntu users are having problems with this, even a ticket opened (starting this month). Any suggestions?

[bd54338rre]

does this answers your question?
http://www.cyberciti.biz/tips/avoid-...toloading.html

[bd54338rre]

it seems that /etc/modprobe.conf does not exists in fedora 10
take a look at /etc/modprobe.d

etc]$ cd modprobe.d
[evert@localhost modprobe.d]$ ls
anaconda   blacklist-visor  i915modeset
blacklist  floppy-pnp       modprobe.conf.dist

i assume you have to edit modprobe.conf.dist

[bd54338rre]

If you are using Debian / Ubuntu Linux...

open /etc/modprobe.d/blacklist file and add drivername using following syntax:
blacklist driver-name

this looks better i think, since the /etc/modprobe.d/blacklist exists in fedora as well

[alharaka]

Thanks, bd54338rre. I was snooping around there, and some people had blacklisted certain drivers for other USB Bluetooth adapters. My concern is that usb_hid seems to be a fairly important driver. So if I blacklist it, reboot, and plug in my USB mouse later, will it cause major kernel problems?

As for loading the other driver hci_usb manually, how would I go about and do that exactly? I am not sure of how to do that. Googling was informative, but not enough to get the wheels moving, so to speak.

[bd54338rre]

hey alharaka

as for this question:

So if I blacklist it, reboot, and plug in my USB mouse later, will it cause major kernel problems?

i do not think it will cause kernel problems, since you are not root, when plugin an usb -device.
however, when a module not has been loaded, it's highley possible that some devices not working.
Blacklisting a modulle = not loading a module.

As for loading the other driver hci_usb manually, how would I go about and do that exactly? I am not sure of how to do that. Googling was informative, but not enough to get the wheels moving, so to speak.

i remember there is a command called modprobe, that has been used to manually load a module
my knowledge for linux goes is unfortunaly beyond that.