Bluetooth does not work but WiFi does on Intel 7265 with both Ubuntu 16.04 and 16.10

Bug #1643455 reported by Mike
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux-firmware (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On an Acer V3-574-7481 with built-in stock Intel 7265 wireless hardware, WiFi works perfectly but Bluetooth does not. The System Settings applet reports "No Bluetooth adapters found" and the option to enable Bluetooth is grayed out. However, Bluetooth hardware is reported by "dmesg" and a firmware patch file is applied automatically during boot.

*Bluetooth works on this same machine booted into Windows 10.* The machine is dual-boot from separate partitions.

# uname -a
Linux galois-l 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

# head -6 /etc/os-release
NAME="Ubuntu"
VERSION="16.10 (Yakkety Yak)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.10"
VERSION_ID="16.10"

# rfkill list
1: acer-wireless: Wireless LAN
    Soft blocked: no
    Hard blocked: no
2: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

# lspci -knn | grep -A3 Net
03:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] (rev 59)
    Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5010]
    Kernel driver in use: iwlwifi
    Kernel modules: iwlwifi

# lsusb
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 002 Device 003: ID 04f2:b526 Chicony Electronics Co., Ltd
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

# hcitool dev
Devices:

# hcitool scan
Device is not available: No such device

# dmesg | grep -i bluetooth
[ 26.310459] Bluetooth: Core ver 2.21
[ 26.310476] Bluetooth: HCI device and connection manager initialized
[ 26.310478] Bluetooth: HCI socket layer initialized
[ 26.310480] Bluetooth: L2CAP socket layer initialized
[ 26.310483] Bluetooth: SCO socket layer initialized
[ 26.514833] Bluetooth: hci0: read Intel version: 370810011003110e00
[ 26.794565] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[ 26.987853] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated
[ 39.604402] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 39.604404] Bluetooth: BNEP filters: protocol multicast
[ 39.604407] Bluetooth: BNEP socket layer initialized

# locate ibt-hw
/lib/firmware/intel/ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq
/lib/firmware/intel/ibt-hw-37.7.10-fw-1.0.2.3.d.bseq
/lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
/lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
/lib/firmware/intel/ibt-hw-37.7.bseq
/lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.2.27.d.bseq
/lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
/lib/firmware/intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq
/lib/firmware/intel/ibt-hw-37.8.bseq

# dpkg -S /lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
linux-firmware: /lib/firmware/intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq

# dpkg -s linux-firmware | grep Version
Version: 1.161

This behavior was identical first under Ubuntu 16.04 and then under 16.10 after upgrade. Command and response examples above are under 16.10 after upgrade.
---
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: GNOME
Dependencies:

DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2016-09-20 (293 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Package: linux-firmware 1.164.1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Tags: zesty
Uname: Linux 4.10.0-26-generic x86_64
UpgradeStatus: Upgraded to zesty on 2017-04-14 (86 days ago)
UserGroups: adm audio cdrom dialout dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc6

Revision history for this message
Mike (mikebw) wrote :

The bug is replicated with the mainline kernel:

# uname -a
Linux galois-l 4.10.10-041010-generic #201704120813 SMP Wed Apr 12 12:15:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

# hcitool dev
Devices:

# hcitool scan
Device is not available: No such device

# hciconfig all
Can't get device info: No such device

This bug also still exists on Ubuntu 17.04 with kernel 4.10.

# uname -a
Linux galois-l 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

# dpkg -s linux-firmware | grep Version
Version: 1.164

tags: added: kernel-bug-exists-upstream
Changed in linux-firmware (Ubuntu):
status: New → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please try version >= v4.11-rc2, it has two more seems related commits:

5ffa572a431ff3fd6175419656603519fa471c27 platform/x86: acer-wmi: add another KEY_WLAN keycode
280642c3c8dda79da39e056fd5480d1c3942524e platform/x86: acer-wmi: Inform firmware that RF Button Driver is active

Revision history for this message
Mike (mikebw) wrote :

No improvement.

# uname -a
Linux galois-l 4.11.0-041100rc7-generic #201704161731 SMP Sun Apr 16 21:32:58 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

# hcitool dev
Devices:

# hcitool scan
Device is not available: No such device

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Does airplane hotkey work? Does it work after v4.11-rc2?

Revision history for this message
Mike (mikebw) wrote :

As explained, I tested using mainline kernel 4.11-rc7 and Bluetooth still did not work.

There is no "airplane hotkey," although Fn-F3 toggles WiFi. There are generally no dedicated hotkeys: for example, Fn-F7 toggles the touchpad and Fn-F9 toggles the keyboard backlight.

Bluetooth works correctly booted to Windows 10, so the hardware is good.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you run 'apport-collect 1643455'?

Revision history for this message
Mike (mikebw) wrote : JournalErrors.txt

apport information

tags: added: apport-collected zesty
description: updated
Revision history for this message
Mike (mikebw) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Mike (mikebw) wrote : ProcEnviron.txt

apport information

Revision history for this message
Mike (mikebw) wrote :

Note that the above data from "apport-collect" was with a third-party Bluetooth USB dongle installed, which is how I've been working around the kernel's failure to support the built-in Bluetooth hardware.

$ lsusb -d 0a12:0001
Bus 002 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

I can rerun the test with the third-party dongle removed if necessary.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

There are several logs are missing. I think you can collect the log with WiFi, additional bluetooth dongle is unnecessary.

Revision history for this message
dino99 (9d9) wrote :
Changed in linux-firmware (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.