Ask Your Question
1

No Bluetooth adapters found (Broadcom BCM2046B1... or Dell Wireless 365 Bluetooth?)

asked 2013-10-26 11:17:39 -0500

remjg gravatar image

updated 2013-10-27 12:27:17 -0500

Bluetooth is working out of the box in Ubuntu since a few releases already. On Fedora 19 (and now Fedora 20), I can't make it work unfortunately.

My laptop is a Dell Vostro 3300, and the bluetooth chip seems to be a Broadcom BCM2046B1:

$ lsusb | grep Bluetooth
Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)

I think I have installed all the required packages, you can check out the list below:

$ rpm -qa | grep bluez
bluez-hid2hci-5.10-2.fc20.x86_64
pybluez-0.18-7.fc20.x86_64
bluez-5.10-2.fc20.x86_64
bluez-hcidump-2.5-3.fc20.x86_64
bluez-cups-5.10-2.fc20.x86_64
bluez-libs-5.10-2.fc20.x86_64

$ rpm -qa | grep bluetooth
gnome-bluetooth-libs-3.10.0-1.fc20.x86_64
pulseaudio-module-bluetooth-4.0-7.gitf81e3.fc20.x86_64
gnome-bluetooth-3.10.0-1.fc20.x86_64

The bluetooth service is active:

# systemctl status bluetooth.service
bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
   Active: active (running) since Sat 2013-10-26 18:25:58 CEST; 11min ago
     Docs: man:bluetoothd(8)
 Main PID: 869 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─869 /usr/libexec/bluetooth/bluetoothd

Oct 26 18:25:58 vostro3300 systemd[1]: Starting Bluetooth service...
Oct 26 18:25:58 vostro3300 bluetoothd[869]: Bluetooth daemon 5.10
Oct 26 18:25:58 vostro3300 systemd[1]: Started Bluetooth service.
Oct 26 18:25:58 vostro3300 bluetoothd[869]: Starting SDP server
Oct 26 18:25:58 vostro3300 bluetoothd[869]: Bluetooth management interface 1.3 initialized

And yet, my bluetooth adapter seems unknown in the bluetooth entry of the settings. Same if I use hcitool :

$ hcitool dev  
Devices:

I'm all ears if you have any idea!

Edit : after booting on Ubuntu GNOME 3.10 were my adapter is working, I have noticed one more line when running lsusb:

ubuntu-gnome@ubuntu-gnome:~$ lsusb
Bus 001 Device 008: ID 413c:8160 Dell Computer Corp. Wireless 365 Bluetooth
Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)

I thought it deserved a bug report.

edit retag flag offensive close merge delete

Comments

It's inside the laptop actually. Do you think it might be a hardware failure?

remjg gravatar imageremjg ( 2013-10-26 11:41:22 -0500 )edit
1

Install some other operating systems to find out.

yanglifu90 gravatar imageyanglifu90 ( 2013-10-26 11:49:12 -0500 )edit

I've tried Ubuntu GNOME 13.10, it's working well. There must be something missing on my Fedora installation.

remjg gravatar imageremjg ( 2013-10-26 12:36:34 -0500 )edit

8 Answers

Sort by » oldest newest most voted
0

answered 2013-12-17 02:07:28 -0500

remjg gravatar image

The problem is solved for me after a recent update (maybe from yesterday). Here are the versions installed for my packages:

bluez-5.12-1
kernel-3.11.10-301

Well good news for those who are going to install Fedora 20 which has been released... today !

edit flag offensive delete link more

Comments

Mine doesn't work and this is what I have installed!

Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)

[root@localhost dhoch]# rpm -qa | grep bluez bluez-libs-5.13-1.fc20.x86_64 bluez-cups-5.13-1.fc20.x86_64 pybluez-0.18-7.fc20.x86_64 bluez-5.13-1.fc20.x86_64 bluez-hid2hci-5.13-1.fc20.x86_64

So it's not just a matter of upgrading, this problem has been going on for years on all versions of Fedora as far back as I can see in the google searches. This post is why I decided to try upgrading to Fedora 20 but no different than 19

sktr gravatar imagesktr ( 2014-01-16 09:28:20 -0500 )edit

You said it wasn't working in Fedora 19 but I didn't have any issue with this version... Have you tried another distribution or booting on windows to be sure it's not a hardware issue ? Because we seem to have exactly the same device.

remjg gravatar imageremjg ( 2014-01-17 00:55:13 -0500 )edit

I have not re-installed windows and don't have windows available to boot with, however I did boot with the Dell diagnostics disc and ran the hardware tests which all passed. It showed the Dell wireless 370 bluetooth devices ( 413c:8157 keyboard & 413c:8158 mousepad also shown seperately as those devices) as a subsystem under the bcm2046b1 hub (0a5c:4500)which was shown in the lsusb output. It also showed a seperate device for Dell wireless 370 bluetooth minicard with tests for led,usb interface, antenna, which all passed, but it showed no device ID number, other than 0a5c:4500,Dell usb BIST.

sktr gravatar imagesktr ( 2014-01-17 09:32:28 -0500 )edit

Here is what I get with lsusb: Bus 001 Device 009: ID 413c:8160 Dell Computer Corp. Wireless 365 Bluetooth

We don't actually have the same device: I have a Dell 365 device, whereas you have a Dell 370.

remjg gravatar imageremjg ( 2014-01-18 09:34:00 -0500 )edit
1

answered 2013-10-29 05:44:11 -0500

gfdsa gravatar image

After some googling

yum install bluez-hid2hci

Solved the mistery for me on FC18. Apparently something has changed between FC16 (worked OOTB) and FC18

Running Transaction
  Installing : bluez-hid2hci-4.101-6.fc18.x86_64                                                                         1/1 
  Verifying  : bluez-hid2hci-4.101-6.fc18.x86_64                                                                         1/1 

Installed:
  bluez-hid2hci.x86_64 0:4.101-6.fc18                                                                                        

Complete!
[root@xps ~]# rpm -ql bluez-hid2hci
/lib/udev/rules.d/97-bluetooth-hid2hci.rules
/usr/lib/udev/hid2hci
/usr/share/man/man8/hid2hci.8.gz
[root@xps ~]# dmesg | tail
[91631.303259] vboxnetflt: dropped 1 out of 1095 packets
[91631.310164] vboxnetflt: dropped 0 out of 0 packets
[92127.212331] usb 2-1.6.3: new full-speed USB device number 12 using ehci-pci
[92127.301863] usb 2-1.6.3: New USB device found, idVendor=413c, idProduct=8156
[92127.301868] usb 2-1.6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[92127.301870] usb 2-1.6.3: Product: Dell Wireless 370 Bluetooth Mini-card
[92127.301872] usb 2-1.6.3: Manufacturer: Dell Computer Corp
[92127.367266] Bluetooth: RFCOMM TTY layer initialized
[92127.367287] Bluetooth: RFCOMM socket layer initialized
[92127.367291] Bluetooth: RFCOMM ver 1.11
edit flag offensive delete link more

Comments

Thanks, @gfdsa! That did it for me too, on Vostro 3500. It worked after installing bluez-hid2hci on Fedora 20 64bit.

Cheers

camypaj gravatar imagecamypaj ( 2014-04-05 17:39:05 -0500 )edit

Thanks! it works for DELL XT2. Fedora 20 (KDE)

S.Adrian gravatar imageS.Adrian ( 2014-08-11 01:33:27 -0500 )edit

I too followed the above instructions for Fedora 19 with a new Asus-BT400 Bluetooth 4.0 adapter. Using the Gnome version. Things appear to be OK with a wireless speaker. I use a home built PC--pretty barebones :-(

geralan gravatar imagegeralan ( 2014-12-13 19:02:09 -0500 )edit

Thanks @gfdsa, it works fine on Dell Studio 1558. (Fedora 21)

evillagr gravatar imageevillagr ( 2014-12-20 20:24:04 -0500 )edit

Me too It works for DELL INSPIRON N5010 . Fedora 21 Gnome

Thank You.

Samer gravatar imageSamer ( 2015-01-21 02:38:58 -0500 )edit
1

answered 2013-10-26 20:04:27 -0500

skytux gravatar image

updated 2013-10-26 20:07:48 -0500

I have a Dell Vosto 3500 and it has the same adapter as yours.

In my case, the only way to make the bluetooth work is using Bluetooth Manager:

# yum install blueman

HTH,

Germán.

edit flag offensive delete link more

Comments

Well, no luck on Fedora 20 :( Package blueman-1.23-7.fc20.x86_64 is obsoleted by bluez-5.10-2.fc20.x86_64 which is already installed Nothing to do I have read before that in version 3.10: "shell has been ported to use the latest bluetooth protocol stack BlueZ 5".

remjg gravatar imageremjg ( 2013-10-27 04:05:35 -0500 )edit

Thank you @remjg for reporting the bug! I have voted up your question :)

skytux gravatar imageskytux ( 2013-10-27 12:07:20 -0500 )edit

Nice, that means my karma is enough high to post links... I found this restriction quite annoying today ;-)

remjg gravatar imageremjg ( 2013-10-27 12:26:27 -0500 )edit

That was the intention :-D

skytux gravatar imageskytux ( 2013-10-27 12:32:07 -0500 )edit
0

answered 2013-10-26 11:37:42 -0500

yanglifu90 gravatar image

It is an usb-like device? Does it work on other devices?

edit flag offensive delete link more
0

answered 2013-10-27 10:49:17 -0500

skytux gravatar image

You are right, I forgot about that. But just remember that Fedora 20 is in an Alpha state, so it is not complete yet. I think that you should file a bug report.

edit flag offensive delete link more
0

answered 2014-01-17 09:33:42 -0500

sktr gravatar image

+remjg what did you working system show for the device ID of the Dell 370 device?

edit flag offensive delete link more
0

answered 2014-01-16 09:23:29 -0500

sktr gravatar image

updated 2014-01-18 14:55:19 -0500

skytux gravatar image

I just upgraded to Fedora 20 and still doesn't find my BCM2046B1 device or even show the Dell device in lsusb?

[root@localhost dhoch]# lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 046d:c51b Logitech, Inc. V220 Cordless Optical Mouse for Notebooks
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0c45:63f8 Microdia Sonix Integrated Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / Trackstick
Bus 003 Device 003: ID 413c:8157 Dell Computer Corp. Integrated Keyboard
Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[root@localhost dhoch]# hciconfig -a
[root@localhost dhoch]# rpm -qa | grep bluez
bluez-libs-5.13-1.fc20.x86_64
bluez-cups-5.13-1.fc20.x86_64
pybluez-0.18-7.fc20.x86_64
bluez-5.13-1.fc20.x86_64
bluez-hid2hci-5.13-1.fc20.x86_64
edit flag offensive delete link more
0

answered 2013-10-27 11:27:09 -0500

remjg gravatar image

I have filled a bug report in the mean time: https://bugzilla.redhat.com/show_bug.cgi?id=1023720 I hope that will help! And yeah, I can't resist switching a bit earlier to discover the new features ^^

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2013-10-26 11:17:39 -0500

Seen: 23,588 times

Last updated: Apr 05 '14