F17 bluetooth adapter not found

[HansV]

I am trying to get bluetooth working on an Asus N73SV.
When I open system settings and go to bluetooth all options are grayed out and "No bluetooth adapter found" is displayed.

Output from bluetoothd -nd:

hans@boson:~$ sudo bluetoothd -nd
bluetoothd[4444]: Bluetooth daemon 4.99
bluetoothd[4444]: src/main.c:parse_config() parsing main.conf
bluetoothd[4444]: src/main.c:parse_config() discovto=0
bluetoothd[4444]: src/main.c:parse_config() pairto=0
bluetoothd[4444]: src/main.c:parse_config() pageto=8192
bluetoothd[4444]: src/main.c:parse_config() auto_to=60
bluetoothd[4444]: src/main.c:parse_config() name=%h-%d
bluetoothd[4444]: src/main.c:parse_config() class=0x000100
bluetoothd[4444]: src/main.c:parse_config() discov_interval=30
bluetoothd[4444]: src/main.c:parse_config() Key file does not have key 'DeviceID'
D-Bus setup failed: Name already in use
bluetoothd[4444]: Unable to get on D-Bus

Output from lsusb:

hans@boson:~$ sudo lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 002: ID 1b1c:1a03  
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 13d3:5205 IMC Networks

dmesg:

hans@boson:~$ dmesg | grep -i bluetooth
[   23.424380] Bluetooth: Core ver 2.16
[   23.424464] Bluetooth: HCI device and connection manager initialized
[   23.424466] Bluetooth: HCI socket layer initialized
[   23.424468] Bluetooth: L2CAP socket layer initialized
[   23.424474] Bluetooth: SCO socket layer initialized
[   23.464593] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   23.464596] Bluetooth: BNEP filters: protocol multicast
[   82.074850] Bluetooth: RFCOMM TTY layer initialized
[   82.074854] Bluetooth: RFCOMM socket layer initialized
[   82.074855] Bluetooth: RFCOMM ver 1.11

lsmod:

hans@boson:~$ lsmod | grep -i bluetooth
bluetooth             298929  10 bnep,rfcomm
rfkill                 21384  7 cfg80211,bluetooth,asus_wmi

Linux version:

hans@boson:~$ uname -a
Linux boson.localdomain 3.5.4-1.fc17.x86_64 #1 SMP Mon Sep 17 15:03:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

I've been searching the web but didn't find a solution.

[weitjong]

Is your Bluetooth service started or enabled in systemd?

[HansV]

Originally Posted by weitjong

Is your Bluetooth service started or enabled in systemd?

Yes, it is. I tried to restart it but that doesn't help.

hans@boson:~$ sudo systemctl status bluetooth.service
[sudo] password for hans: 
bluetooth.service - Bluetooth Manager
          Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
          Active: active (running) since Sun, 23 Sep 2012 12:45:43 +0200; 23min ago
        Main PID: 888 (bluetoothd)
          CGroup: name=systemd:/system/bluetooth.service
                  └ 888 /usr/sbin/bluetoothd -n

Sep 23 12:45:42 boson.localdomain bluetoothd[888]: bluetoothd[888]: Bluetooth daemo...9
Sep 23 12:45:42 boson.localdomain bluetoothd[888]: Bluetooth daemon 4.99
Sep 23 12:45:42 boson.localdomain bluetoothd[888]: Starting SDP server
Sep 23 12:45:42 boson.localdomain bluetoothd[888]: bluetoothd[888]: Starting SDP server
Sep 23 12:45:43 boson.localdomain bluetoothd[888]: bluetoothd[888]: Parsing /etc/bl...y
Sep 23 12:45:43 boson.localdomain bluetoothd[888]: bluetoothd[888]: Parsing /etc/bl...y
Sep 23 12:45:43 boson.localdomain bluetoothd[888]: Parsing /etc/bluetooth/input.con...y
Sep 23 12:45:43 boson.localdomain bluetoothd[888]: Parsing /etc/bluetooth/audio.con...y
hans@boson:~$

[weitjong]

I have a ASUS motherboard with built-in bluetooth adapter which I believe uses the Atheros AR30xx chip. I believe your notebook too, in a way. A quick search on the internet shows that your notebook uses Atheros AR9004WB-1NG which combines WIFI (AR9485) and bluetooth (AR3012) into one chip. Perhaps, Linux kernel (or just Fedora) fails to recognize that and does not automatically load the Atheros kernel module on boot up.

Below is the lsmod output from my system.

[weitjong@igloo ~]$ lsmod |grep -i bluetooth
bluetooth             298929  26 bnep,hidp,ath3k,btusb,rfcomm
rfkill                 21384  4 bluetooth,asus_wmi

No promise but you may want to try to manually load the ath3k (and hidp) kernel modules to see if it fixes your problem.

[HansV]

Originally Posted by weitjong

No promise but you may want to try to manually load the ath3k (and hidp) kernel modules to see if it fixes your problem.

I tried loading them and restarted bluetooth.service. Still same problem.

hans@boson:~$ lsmod | grep -i bluetooth
bluetooth             298929  13 bnep,hidp,ath3k,btusb,rfcomm
rfkill                 21384  7 cfg80211,bluetooth,asus_wmi

[weitjong]

I am sorry to hear that. Probably the current version of ath3k really does not recognize your chip yet. Perhaps your AR3012 has different vendor ID & product ID from its current supported list. See the supported list in here.

And just for a comparison, my system's dmesg output has a recognizable Atheros chip. In my case it is a AR3011, the first in the list in the above c source code.

Sep 25 16:11:34 igloo kernel: [    2.256450] usb 2-1.7: new full-speed USB device number 5 using ehci_hcd
Sep 25 16:11:34 igloo kernel: [    2.341771] usb 2-1.7: New USB device found, idVendor=0cf3, idProduct=3000
Sep 25 16:11:34 igloo kernel: [    2.341773] usb 2-1.7: New USB device strings: Mfr=0, Product=0, SerialNumber=0

I don't know how comfortable are you with compiling c source code, but from the past git commits it appears it is rather trivial to modify the list to add new vendor/product id. I am sorry to say you are on your own as I have never done that myself. May be it is easier just to submit the request to kernel developer to add that for you .