Intel Wireless-AC 3165 [8086:3166] Subsystem [8086:4210] Bluetooth (ideapad_bluetooth) disabled every time on startup

[Hafiz]

[Policy]
AutoEnable=true

not working

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
Uname: Linux 5.10.0-051000-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Sun Jan 24 19:49:49 2021
InstallationDate: Installed on 2021-01-24 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:0a2a Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
     |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
     |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
MachineType: LENOVO 81CG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-051000-generic root=UUID=0281b4fb-589a-46ed-b8ee-896d3505e7bd ro
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/10/2019
dmi.bios.release: 1.39
dmi.bios.vendor: LENOVO
dmi.bios.version: 6NCN39WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40688 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 32
dmi.chassis.vendor: LENOVO
dmi.chassis.version: MIIX 520-12IKB
dmi.ec.firmware.release: 1.39
dmi.modalias: dmi:bvnLENOVO:bvr6NCN39WW:bd10/10/2019:br1.39:efr1.39:svnLENOVO:pn81CG:pvrMIIX520-12IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct32:cvrMIIX520-12IKB:
dmi.product.family: MIIX 520-12IKB
dmi.product.name: 81CG
dmi.product.sku: LENOVO_MT_81CG_BU_idea_FM_MIIX 520-12IKB
dmi.product.version: MIIX 520-12IKB
dmi.sys.vendor: LENOVO
hciconfig:
 hci0: Type: Primary Bus: USB
  BD Address: 3C:6A:A7:BB:B7:63 ACL MTU: 1021:5 SCO MTU: 96:6
  UP RUNNING PSCAN ISCAN
  RX bytes:213889 acl:13940 sco:0 events:310 errors:0
  TX bytes:40352 acl:45 sco:0 commands:249 errors:0

[Daniel van Vugt (vanvugt)]

Thanks for the bug report.

1. Do you mean Bluetooth is disabled in Gnome Shell on startup, or the controllers are disabled in bluetoothctl?

2. Please reboot and then in a Terminal window run:

   rfkill > newrfkill.txt

   and attach the resulting text file here.

[Hafiz (myphnix)]

Hi Daniel,

Sorry for the late reply

I need to let bluetooth enabled by default during the restart but it seems
not work to me..here's the rfkill attachment as per request.

Thank you.

On Mon, Jan 25, 2021 at 3:15 PM Daniel van Vugt <email address hidden>
wrote:

> Thanks for the bug report.
>
> 1. Do you mean Bluetooth is disabled in Gnome Shell on startup, or the
> controllers are disabled in bluetoothctl?
>
> 2. Please reboot and then in a Terminal window run:
>
> rfkill > newrfkill.txt
>
> and attach the resulting text file here.
>
>
> ** Changed in: bluez (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1912940
>
> Title:
> disabled everytime startup
>
> Status in bluez package in Ubuntu:
> Incomplete
>
> Bug description:
> [Policy]
> AutoEnable=true
>
>
> not working
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: bluez 5.53-0ubuntu3
> Uname: Linux 5.10.0-051000-generic x86_64
> ApportVersion: 2.20.11-0ubuntu27.14
> Architecture: amd64
> CasperMD5CheckResult: skip
> CurrentDesktop: ubuntu:GNOME
> CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg:
> read kernel buffer failed: Operation not permitted
> Date: Sun Jan 24 19:49:49 2021
> InstallationDate: Installed on 2021-01-24 (0 days ago)
> InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
> (20200731)
> InterestingModules: rfcomm bnep btusb bluetooth
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 002: ID 8087:0a2a Intel Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Lsusb-t:
> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
> |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
> |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
> MachineType: LENOVO 81CG
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-051000-generic
> root=UUID=0281b4fb-589a-46ed-b8ee-896d3505e7bd ro
> SourcePackage: bluez
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 10/10/2019
> dmi.bios.release: 1.39
> dmi.bios.vendor: LENOVO
> dmi.bios.version: 6NCN39WW
> dmi.board.asset.tag: NO Asset Tag
> dmi.board.name: LNVNB161216
> dmi.board.vendor: LENOVO
> dmi.board.version: SDK0J40688 WIN
> dmi.chassis.asset.tag: NO Asset Tag
> dmi.chassis.type: 32
> dmi.chassis.vendor: LENOVO
> dmi.chassis.version: MIIX 520-12IKB
> dmi.ec.firmware.release: 1.39
> dmi.modalias:
> dmi:bvnLENOVO:bvr6NCN39WW:bd10/10/2019:br1.39:efr1.39:svnLENOVO:pn81CG:pvrMIIX520-12IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct32:cvrMIIX520-12IKB:
> dmi.product.family: MIIX 520-12IKB
> dmi.product.name: 81CG
> dmi.product.sku: LENOVO_MT_81CG_BU_idea_FM_MIIX 520-12IKB
> dmi.product.version: MIIX 520-12IKB
> dmi.sys.vendor: LENOVO
> hciconfig:
> hci0: Type: Primary Bus: USB
> BD Address: 3C:6A:A7:BB:B7:63 ACL MTU: 1021:5 ...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Karol (wasowski02)]

We've been discussing rfkill on the duplicate bug (#1922338). The rfkill output from just after boot was:
ID TYPE DEVICE SOFT HARD
 0 wlan ideapad_wlan unblocked unblocked
 1 bluetooth ideapad_bluetooth blocked unblocked
 2 wlan phy0 unblocked unblocked
 4 bluetooth hci0 blocked unblocked

And we've come to the conclusion that the GUI does not run rfkill unblock, however I've checked today and after flicking the GUI switch it does indeed unblock the device:
ID TYPE DEVICE SOFT HARD
 0 wlan ideapad_wlan unblocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 2 wlan phy0 unblocked unblocked
 4 bluetooth hci0 unblocked unblocked

It still doesn't work of course. I can also manually run rfkill unblock 1 (and 3), but that doesn't work either. Bluetooth starts working only after unblocking and then restarting bluetooth.service

[Daniel van Vugt (vanvugt)]

Interesting these bug reports are all from kernel 5.10 and later, and all related to ideapad_bluetooth. This sounds like a kernel regression in that area. Can anyone test some older/newer kernels?

https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

[Karol (wasowski02)]

I've tested a few versions:
1) Working fine:
5.8.0-48 (official repo)
5.9.16
5.10.0
5.10.14
5.10.27 (last build of 5.10)

2) The issue first appears on 5.11.0-051100. I haven't tested release candidates.

[Daniel van Vugt (vanvugt)]

Thanks Karol. That's good news you have found the point of regression was 5.11.0 but also strange because this bug suggests it was broken in 5.10.0 also.

[Karol (wasowski02)]

Seems that both #1912940 (this issue - kernel 5.10) and #1922338 (kernel 5.11) use the same network controller as suggested by lspci:
Network controller [0280]: Intel Corporation Dual Band Wireless-AC 3165 Plus Bluetooth [8086:3166] (rev 99)

I can't find any bluetooth controller on #1922536. The only network controller is:
Network controller [0280]: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) [8086:34f0] (rev 30)

Maybe the third issue is different from the first two, though it still doesn't explain the difference in the first two.

[Karol (wasowski02)]

Oh, seems that the Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter does support bluetooth it's just not mentioned in lspci.

[You-Sheng Yang (vicamo)]

Intel WiFi/Bluetooth Dual chips always have WiFi in `lspci` and Bluetooth in `lsusb`. For PCI part its PCI ID _and_ subsystem ID is critical for identifying them, USB VID/PID is not so useful as they can be even identical across different models.

Anyway, this one has 3165 as updated in bug title.

[Karol (wasowski02)]

The bug went away today when I ran an upgrade. In the updateHistory.log are the packages I updated this morning so I expect that it has something to do with systemd.

[Daniel van Vugt (vanvugt)]

I'm not sure it was appropriate to make this bug specific to the 3165 when bug 1922536 uses something different. But rather than argue that point, we can now declare this fixed in hirsute for "Intel Wireless-AC 3165".

Bug 1922536 will be separated...