Ask Your Question
2

fedora19 bluetooth problem, adapter not found

asked 2013-08-05 07:06:06 -0500

pnadk gravatar image

updated 2013-08-25 15:34:06 -0500

On my desktop PC I have a USB Bluetooth adapter. It works on Fedora17 and in Windows 7, but not on Fedora 19. All the relevant blue* packages are installed. The Bluetooth control panel in KDE as well as in Gnome say "no adapter found".

The following commands are what I have tried to get some information about what is wrong, but none of it seems out of order.

I hope someone has an idea. All Google searches for this issue seem to come up with either "restart bluetooth service" or "problem disappeared after a kernel update" none of which worked for me.

uname -a 

Linux localhost.localdomain  3.10.3-300.fc19.x86_64 #1 SMP Fri Jul 26 00:00:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

lsusb 

...
Bus 001 Device 005: ID 0a5c:2100 Broadcom Corp. Bluetooth 2.0+eDR dongle

dmesg | grep -i blue 

[    8.285325] Bluetooth: Core ver 2.16 
[    8.285364] Bluetooth: HCI device and connection manager initialized 
[    8.285380] Bluetooth: HCI socket layer initialized 
[    8.285383] Bluetooth: L2CAP socket layer initialized 
[    8.285391] Bluetooth: SCO socket layer initialized
[   33.076981] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 
[   33.076985] Bluetooth: BNEP filters: protocol multicast
[   33.076998] Bluetooth: BNEP socket layer initialized 
[  834.206412] Bluetooth: RFCOMM TTY layer initialized 
[  834.206430] Bluetooth: RFCOMM socket layer initialized 
[  834.206431] Bluetooth: RFCOMM ver 1.11 
[ 1752.307480] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 
[ 1752.307496] Bluetooth: HIDP socket layer initialized

rfkill list

 0: hci0: Bluetooth
         Soft blocked: no
         Hard blocked: no

hciconfig  
 hci0:   Type: BR/EDR  Bus: USB
         BD Address: 00:19:86:00:21:8F  ACL MTU: 1017:8  SCO MTU: 64:0
         DOWN 
         RX bytes:1852 acl:0 sco:0 events:68 errors:0
         TX bytes:284 acl:0 sco:0 commands:68 errors:0

hcitool dev 

 Devices:

yes, bluez-hid2hci is also installed. Here is what what the /var/log/messages shows when I unplug and replug the adapter:

Aug  6 19:13:29 localhost kernel: [  570.953058] usb 5-2: USB disconnect, device number 3
Aug  6 19:13:29 localhost systemd[1]: Service bluetooth.target is not needed anymore. Stopping.
Aug  6 19:13:29 localhost systemd[1]: Stopping Bluetooth.
Aug  6 19:13:29 localhost systemd[1]: Stopped target Bluetooth.
Aug  6 19:13:41 localhost kernel: [  583.804033] usb 5-2: new full-speed USB device number 4 using uhci_hcd
Aug  6 19:13:42 localhost kernel: [  584.044059] usb 5-2: New USB device found, idVendor=0a5c, idProduct=2100
Aug  6 19:13:42 localhost kernel: [  584.044067] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug  6 19:13:42 localhost kernel: [  584.044072] usb 5-2: Product: Broadcom BCM2045 dongle
Aug  6 19:13:42 localhost kernel: [  584.044076] usb 5-2: Manufacturer: Broadcom
Aug  6 19:13:42 localhost systemd[1]: Starting Bluetooth.
Aug  6 19:13:42 localhost systemd[1]: Reached target Bluetooth.

Edit 2013-08-25: moved my previous answer here so I could write a new ... (more)

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
0

answered 2013-08-07 12:49:13 -0500

pnadk gravatar image

updated 2013-08-25 15:45:31 -0500

Update / answer:

I gave up! I went and bought a new USB Bluetooth adapter, and now my mouse and headset work. So the short answer is, the Broadcom device is not supported.

Just for comparison, here are the output from the same commands as in the original post:

lsusb
Bus 001 Device 011: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth

dmesg | grep -i blue
[    7.992924] Bluetooth: Core ver 2.16
[    7.992947] Bluetooth: HCI device and connection manager initialized
[    7.992957] Bluetooth: HCI socket layer initialized
[    7.992960] Bluetooth: L2CAP socket layer initialized
[    7.992966] Bluetooth: SCO socket layer initialized
[   13.581292] Bluetooth: Can't change to loading configuration err
[   36.106025] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   36.106030] Bluetooth: BNEP filters: protocol multicast
[   36.106042] Bluetooth: BNEP socket layer initialized
[  125.903328] Bluetooth: RFCOMM TTY layer initialized
[  125.903346] Bluetooth: RFCOMM socket layer initialized
[  125.903347] Bluetooth: RFCOMM ver 1.11
[  126.564991] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[  126.565030] Bluetooth: HIDP socket layer initialized
[  131.501745] input: Logitech Bluetooth Mouse M555b as /devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2.1/1-2.1:1.0/bluetooth/hci0/hci0:21/input16
[  131.502928] hid-generic 0005:046D:B009.0005: input,hidraw4: BLUETOOTH HID v4.19 Mouse [Logitech Bluetooth Mouse M555b] on 00:02:72:36:15:2a

rfkill list
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

hcitool dev
Devices:
        hci0    00:02:72:36:15:2A

and finally hcidump did not show any error messages when I ran hciconfig hci0 up

edit flag offensive delete link more
1

answered 2013-08-06 02:22:55 -0500

FranciscoD_ gravatar image

Mine didn't show up either after a clean install. Installing the bluez-hid2hci package fixed it. This package isn't installed by default in Fedora 19. Since your device is already detected, this may not be the answer, but it's worth a try.

[asinha@localhost  ~]$ rpm -qi bluez-hid2hci
Name        : bluez-hid2hci
Version     : 4.101
Release     : 9.fc19
Architecture: x86_64
Install Date: Sat 27 Jul 2013 05:22:53 PM EST
Group       : System Environment/Daemons
Size        : 18065
License     : GPLv2+
Signature   : RSA/SHA256, Wed 24 Jul 2013 03:11:53 AM EST, Key ID 07477e65fb4b18e6
Source RPM  : bluez-4.101-9.fc19.src.rpm
Build Date  : Wed 24 Jul 2013 01:36:23 AM EST
Build Host  : buildvm-11.phx2.fedoraproject.org
Relocations : (not relocatable)
Packager    : Fedora Project
Vendor      : Fedora Project
URL         : http://www.bluez.org/
Summary     : Put HID proxying bluetooth HCI's into HCI mode
Description :
Most allinone PC's and bluetooth keyboard / mouse sets which include a
bluetooth dongle, ship with a so called HID proxying bluetooth HCI.
The HID proxying makes the keyboard / mouse show up as regular USB HID
devices (after connecting using the connect button on the device + keyboard),
which makes them work without requiring any manual configuration.

The bluez-hid2hci package contains the hid2hci utility and udev rules to
automatically switch supported Bluetooth devices into regular HCI mode.

Install this package if you want to use the bluetooth function of the HCI
with other bluetooth devices like for example a mobile phone.

Note that after installing this package you will first need to pair your
bluetooth keyboard and mouse with the bluetooth adapter before you can use
them again. Since you cannot use your bluetooth keyboard and mouse until
they are paired, this will require the use of a regular (wired) USB keyboard
and mouse.
[asinha@localhost  ~]$
edit flag offensive delete link more

Comments

FranciscoD > yes that package is installed and I even tried reinstalling it. Also added more log information to original post.

pnadk gravatar imagepnadk ( 2013-08-06 12:21:54 -0500 )edit

Thank you good sir, this has solved my problem.

LeoUfimtsev gravatar imageLeoUfimtsev ( 2014-12-19 10:04:43 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2013-08-05 07:06:06 -0500

Seen: 8,523 times

Last updated: Aug 25 '13