The hardware is present:
$ lspci | grep Centrino 04:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
And the Bluetooth, iwlwifi, and iwldvm modules get loaded:
$ lsmod | egrep 'iwl|blue' iwldvm 232285 0 mac80211 626557 1 iwldvm iwlwifi 169932 1 iwldvm bluetooth 395423 10 bnep,rfcomm cfg80211 484040 3 iwlwifi,mac80211,iwldvm
Indeed, there's bluetooth output in my startup log:
$ dmesg | egrep -i 'iwl|blue' [ 2.598945] Bluetooth: Core ver 2.17 [ 2.598994] Bluetooth: HCI device and connection manager initialized [ 2.599006] Bluetooth: HCI socket layer initialized [ 2.599010] Bluetooth: L2CAP socket layer initialized [ 2.599016] Bluetooth: SCO socket layer initialized [ 2.637552] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 2.637557] Bluetooth: BNEP filters: protocol multicast [ 2.637570] Bluetooth: BNEP socket layer initialized [ 2.683477] Bluetooth: RFCOMM TTY layer initialized [ 2.683493] Bluetooth: RFCOMM socket layer initialized [ 2.683501] Bluetooth: RFCOMM ver 1.11 [ 2.802024] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002) [ 2.802106] iwlwifi 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control [ 2.802169] iwlwifi 0000:04:00.0: irq 106 for MSI/MSI-X [ 2.829897] iwlwifi 0000:04:00.0: loaded firmware version 184.108.40.206 op_mode iwldvm [ 2.981631] iwlwifi 0000:04:00.0: CONFIG_IWLWIFI_DEBUG disabled [ 2.981638] iwlwifi 0000:04:00.0: CONFIG_IWLWIFI_DEBUGFS enabled [ 2.981640] iwlwifi 0000:04:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled [ 2.981644] iwlwifi 0000:04:00.0: Detected Intel(R) Centrino(R) Advanced-N 6235 AGN, REV=0xB0 [ 2.981921] iwlwifi 0000:04:00.0: L1 Disabled; Enabling L0S [ 3.054692] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
And the wifi portion of the card is working great! However, the bluetooth device isn't coming up at all— doesn't show up for hcitool, hciconfig, or rfkill, eg:
$ hcitool dev Devices: $ sudo rfkill list all 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no
I'm on a 64-bit machine, running a headless minimal Ubuntu 14.04:
$ lsb_release -r Release: 14.04 $ uname -a Linux test 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
I briefly tried the 3.14 kernel, which seemed no different. I also tried removing and reinserting the the iwlwifi and bluetooth modules. I've also confirmed the same behaviour as above in the 14.04 live desktop.
Would appreciate additional thoughts or pointers, thanks.
One additional piece of data is syslog output related to bluetoothd:
$ sudo cat /var/log/syslog | grep -i bluetoothd Jun 26 15:09:54 jackal2 bluetoothd: DIS cannot start: GATT is disabled Jun 26 15:09:54 jackal2 bluetoothd: Failed to init deviceinfo plugin Jun 26 15:09:54 jackal2 bluetoothd: Failed to init proximity plugin Jun 26 15:09:54 jackal2 bluetoothd: Failed to init time plugin Jun 26 15:09:54 jackal2 bluetoothd: Failed to init alert plugin Jun 26 15:09:54 jackal2 bluetoothd: Failed to init thermometer plugin Jun 26 15:09:54 jackal2 bluetoothd: Failed to init gatt_example plugin Jun 26 15:09:54 jackal2 bluetoothd: Bluetooth Management interface initialized
Are these plugin failures something to investigate? What is GATT?
I have determined now that this radio and driver work fine with wifi and bluetooth on a different motherboard, so I'm assuming it's a hardware conflict with something on the particular motherboard (a Gigabyte J1800N-D2H).
Curiously, the same problem persists on a different J1900 motherboard, leading to suspicion that this is a chipset conflict. This time the dmesg log is showing a firmware crash on startup, which I don't recall seeing previously. The log and lshw output are in a gist here: