Bug 194101 - Intel bluetooth device 8087:0a2a not recognized by kernel
Summary: Intel bluetooth device 8087:0a2a not recognized by kernel
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: All Linux
: P1 high
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-06 14:59 UTC by iliyabo
Modified: 2017-03-22 17:10 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.9.6
Subsystem:
Regression: No
Bisected commit-id:


Attachments
lsusb output (270 bytes, text/plain)
2017-02-06 14:59 UTC, iliyabo
Details
dmesg output (146.06 KB, text/plain)
2017-02-06 14:59 UTC, iliyabo
Details
powertop output (1.80 KB, text/plain)
2017-02-06 15:03 UTC, iliyabo
Details

Description iliyabo 2017-02-06 14:59:14 UTC
Created attachment 254261 [details]
lsusb output

I recently got Lenovo yoga 510. I installed linux, but noticed that some of the device drivers are not working(mainly bluetooth). This results in inability to disable bluetooth and save power(at least according to powertop). I attach the output of lsusb and dmesg, please tell me if I need to give anything else.
Comment 1 iliyabo 2017-02-06 14:59:40 UTC
Created attachment 254271 [details]
dmesg output
Comment 2 iliyabo 2017-02-06 15:03:08 UTC
Created attachment 254281 [details]
powertop output

This is the output from powertop, it shows that this device is using 1.5W of power, although bluetooth is disabled in settings. I don't know what else to do.
Comment 3 Martin 2017-03-22 17:10:59 UTC
I can confirm the finding. I added lots of BT_INFO calls to the driver to trace the proper initialization and firmware loading (no errors). Still, no device is shown by "hcitool dev". 

I don't know the BT drivers very well, but I wonder why the device appears in the "blacklist" vector? It seems that all those devices need some extra firmware?

It would be great if this could be fixed. I have two machines with the device, ready to test fixes as needed. I haven't figured out how the driver goes from being loaded to actually create the hci0 device, else I could report more details.

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