Bug 153993 - D-Link Bluetooth DBT-120 adaptor doesn't work
D-Link Bluetooth DBT-120 adaptor doesn't work
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: udev (Show other bugs)
4
powerpc Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
:
Depends On:
Blocks: fedora-ppc
  Show dependency treegraph
 
Reported: 2005-04-06 10:45 EDT by Andrew Cagney
Modified: 2007-11-30 17:11 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-04-21 09:07:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrew Cagney 2005-04-06 10:45:11 EDT
(is this a kernel, doco, anaconda, or ... bug?)

The DBT-120 adaptor doesn't work out-of-the-box.  The driver reports;

bcm203x_probe: Mini driver request failed
bcm203x: probe of 1-1:1.0 failed with error -5

You need to fetch the firmware from:

http://www.bluez.org/download.html

and install the files:

BCM2033-MD.hex BCM2033-FW.bin

in /lib/firmware (the firmware tar ball will do it if you do: ./configure; make;
make install).
Comment 1 Colin Charles 2005-04-07 01:37:51 EDT
FWIW, tried it on Rawhide/x86 (its almost FC4test2 now)
Bluetooth: Core ver 2.7
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: HCI USB driver ver 2.8
usbcore: registered new driver hci_usb

And it worked. I recall this working with Rawhide (pre-fc4t1) on powerpc as
well, however I haven't rolled an install out in a while (and am away from my
ppc boxes now)

lsusb reports the adapter (a dbt-120) as:
Bus 003 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
(HCI mode)

IIRC, on irc, you reported your lsusb output as being:
<cagney> Bus 001 Device 002: ID 0a5c:2033 Broadcom Corp. BCM2033 Bluetooth

So guess this isn't the first time they release the same product model and
change the internals of it with a different manufacturer..
Comment 2 Andrew Cagney 2005-04-07 12:40:14 EDT
PS: The above, while correct, isn't working.

(Following DWMW2's pointer) I'm fi that /etc/hotplug/firmware.agent fails with:

+ cp /lib/firmware/BCM2033-MD.hex /sys//class/firmware/1-1/data
cp: cannot create regular file `/sys//class/firmware/1-1/data': No such file or
directory
+ echo 0
/etc/hotplug/firmware.agent: line 49: /sys//class/firmware/1-1/loading: No such
file or directory
Comment 4 Harald Hoyer 2005-04-11 11:28:39 EDT
could you try:
ftp://people.redhat.com/harald/udev/udev-056-1.src.rpm
Comment 5 Harald Hoyer 2005-04-11 12:03:01 EDT
needs udev-056 and 2.6.12 or patch for 2.6.11 
http://kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/driver/firmware-timeout.patch
Comment 7 Ziga Mahkovec 2005-04-12 09:51:11 EDT
I've also been having issues with firmware loading (ipw2100) and it turned out
to be a problem with the initial event timeout in udevd:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145283#c10

This too is fixed in udev-056, but doesn't require the kernel patch.  So if
firmware loading only fails during boot, it's likely a startup timeout issue. 
The kernel patch avoids the issue completely by allowing firmware events to
bypass the udevd queue.
Comment 8 Andrew Cagney 2005-04-12 10:56:39 EDT
Harold,

Should 2.6.11-1.1236_FC4 and udev-050-10 work (it doesn't appear to) or do I
also need to also build / install the udev-056 rpm?

$ uname -a
Linux localhost.localdomain 2.6.11-1.1236_FC4 #1 Mon Apr 11 12:23:42 EDT 2005
ppc ppc ppc GNU/Linux
$ rpm -q udev
udev-050-10
$ sudo hciconfig
$ dmesg | tail
ADB keyboard at 2, handler 1
ADB mouse at 3, handler set to 4 (trackpad)
adb: finished probe task...
usb 1-1: new full speed USB device using ohci_hcd and address 2
Bluetooth: Broadcom Blutonium firmware driver ver 1.0
Bluetooth: HCI USB driver ver 2.8
bcm203x_probe: Mini driver request failed
bcm203x: probe of 1-1:1.0 failed with error -5
usbcore: registered new driver bcm203x
usbcore: registered new driver hci_usb
$
Comment 9 Harald Hoyer 2005-04-12 11:28:04 EDT
Andrew, my name is Harald and please test udev-056.
Comment 10 Andrew Cagney 2005-04-12 18:29:37 EDT
Ok, I've tested udev-056-1 and finally get:
# hciconfig
hci0:   Type: USB
        BD Address: 00:80:C8:50:F9:5C ACL MTU: 377:10 SCO MTU: 16:0
        UP RUNNING PSCAN ISCAN
        RX bytes:101 acl:0 sco:0 events:13 errors:0
        TX bytes:300 acl:0 sco:0 commands:13 errors:0
my phone sees my mac; but not the reverse; try again, ah there it is now for a
dial out ...

Note You need to log in before you can comment on or make changes to this bug.