Wireless
Participate in insightful discussions regarding issues related to Intel® Wireless Adapters and technologies
Announcements
All support for Intel NUC 7 - 13 systems has transitioned to ASUS. Read latest update.
7310 Discussions

intel AX211 Bluetooth stopped connecting to some devices. Linux

alinelena
Novice
3,240 Views
I have a bt keyboard (using a xiao ble nrf52840 controller). this
worked fine on the current computer with tumbleweed till beginning of
september(may be red herring). when i decided to remove the old bt
profiles and repair all my devices..
headphones, mice and keyboard. headphones and mice work as expected no
issues.. the only one is the keyboard that refuses to connect or pair.

there is nothing wrong with the keyboard since I can pair it without
issues on another xps laptop (different bt adapter) or my android
phone.

trying to debug but kind of hit a wall since I have little experience
with bt errors.
in logs i see
[  367.758074] Bluetooth: hci0: unexpected SMP command 0x0b from
e8:77:fb:f9:41:5a
the bt adapter is integrated in the wifi as far as I can say
00:14.3 Network controller [0280]: Intel Corporation Alder Lake-P PCH
CNVi WiFi [8086:51f0] (rev 01)
       Subsystem: Intel Corporation Wi-Fi 6E AX211 160MHz [8086:4090]
       Kernel driver in use: iwlwifi

the computer itself is an XPS 9320

I also attach a btmon log when I try to pair the keyboard. I see a
timeout event.

kernel is Linux abbaton 6.5.4-1-vanilla #1 SMP PREEMPT_DYNAMIC Wed Sep
20 05:07:04 UTC 2023 (fdd7e9e) x86_64 x86_64 x86_64 GNU/Linux
but on default I get the same behaviour. attached also the full dmesg

for record the working computer is  XPS 13 9370 and the adapter
02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac
Wireless Network Adapter [168c:003e] (rev 32)
       Subsystem: Rivet Networks Killer 1435 Wireless-AC [1a56:143a]
       Kernel driver in use: ath10k_pci
       Kernel modules: ath10k_pci

workaround: replace ibt-0040-0041.ddc  ibt-0040-0041.sfi from kernel-firmware-bluetooth(both default tw and from kernel head)...
from kernel-firmware-bluetooth-20230320-150500.1.1.noarch.rpm and
seems to work without any issues.
17 Replies
DeividA_Intel
Moderator
3,226 Views

Hello alinelena,  

  

Thank you for posting on the Intel® communities. I want to understand what happened just as much as you do. 


To have a better view of this issue, I would like to confirm the following:


1. Is this the original adapter that came pre-installed on your computer or did you change/install the adapter to this one?  

2. Is the Wi-Fi working?  

3. What is the BIOS version installed?

4. Was the Intel® Wi-Fi 6E AX211 working before?

5. Did you try to connect the keyboard without the other components connected?

6. Run the Intel® System Support Utility (Intel® SSU) to gather more details about the system.  


Regards,  

Deivid A. 

Intel Customer Support Technician


0 Kudos
alinelena
Novice
3,217 Views

Hi,

 

answers in line below

 

1. Is this the original adapter that came pre-installed on your computer or did you change/install the adapter to this one?  

this is the original that came with the computer.

2. Is the Wi-Fi working?  

yes

3.What is the BIOS version installed?

latest,         BIOS Revision: 2.5

4. Was the Intel® Wi-Fi 6E AX211 working before?

yes, it worked before, and works after I downgraded the kernel firmware as described below.

5. Did you try to connect the keyboard without the other components connected?

if you mean other bt devices, answer is yes.

6. 

I will be able to do it only at weekend, but I will do it... I suspect you wanted run on the non working version of the firmware?

0 Kudos
DeividA_Intel
Moderator
3,203 Views

Hello alinelena, 


Thanks for your response. I would appreciate it if you run the Intel® System Support Utility (Intel® SSU) with the latest firmware and I understand that you will gather this information during the weekend.


Also, I will need the outcome from the following commands:

- hciconfig -a -> check the details 

- hciconfig -i <interface name> up -> Enable the adapter if hciconfig shows that adapter is down 

- lsusb | grep 8087 -> check if the system is identifying adapter 

- modinfo btintel -> check if bluetooth drivers are loaded 

- dmesg | grep Bluetooth -> check the firmware version 

- grep Bluetooth /var/log/syslog | grep -i -e "Firmware revision" -e "ibt" -> If the firmware version is not available in dmesg, then check in syslog 


Please visit here for the latest firmware - https://www.intel.com/content/www/us/en/download/18895/intel-system-support-utility-for-the-linux-operating-system.html 


Regards,  

Deivid A. 

Intel Customer Support Technician 


0 Kudos
Me11
Beginner
3,195 Views

I am having the exact same issue on Win 10/22H 64, but only with my Arteck keyboards (one at a time for testing purposes). All the sudden, no matter what I do, my Arteck bluetooth keyboard will not even connect. It cannot even be found. It does not stay on to be found for me, but I tried it on my son's computer; no problem. I made the mistake of updating all the Intel drivers, including the BIOS driver. I think now that I will never again update drivers on a system that was working fine. 

 

I did this around end-of-September, because of an UbiSoft game that kept hanging and freezing up the entire system. Don't buy Assassin's Creed Odyssey. There is a 4-year old issue of freezing that cannot be resolved.

 

Attached is my Intel SSU report. When I choose to submit them to customer support in the SSU application, the website cannot be opened. Anyhow since I've had my components, the Bluetooth radio has never installed correctly. It installs a generic driver, and that has non-stop issues. However, in spite of this, my keyboard worked fine - always. I even tried a different Arteck bluetooth keyboard. Neither work on my system; they both work on my son's system. I used the Intel Driver Assistant, then deleted it off of my system. I do not need to clog-up my system with an app that opens a website, and especially when updating the drivers makes my system worse, not better.

 

The issue actually began with the keyboard randomly typing the letters a variable number of times. The imaginary setting to control how long to hold a key in Win 10 didn't exist, so that was not a solution. After uninstalling all of the HID keyboards, I updated the drivers. I have again deleted all HID keyboards a couple of times, but it has not helped.

 

Most frustrating is that it is impossible to have NO other bluetooth connections. The bluetooth connects even my mouse and keyboard that are NOT wireless! Let alone my monitors that are also not wireless! My wired mouse disappears while trying to connect bluetooth devices. Something is VERY wrong with the bluetooth technology that Intel has provided. It should NEVER affect my wired devices, and those wired devices should not be appearing in the bluetooth section, as if they are bluetooth connected, when the devices don't even support bluetooth. It's like the bluetooth is interrupting the wired input in windows.

 

My Arteck keyboards cannot be found (tested one after the other). Yes, the Artecks are fully-charged. Yes, the Artecks are turned on, only one at a time to see if it is the keyboard itself. The Artecks do not stay on, and cannot be found, as I wrote above. They behave exactly the same. The other bluetooth keyboard can be connected. Sadly, it has some permanent something that makes using the FN keys useless, as well as the ALT/CTRL etc, and the FN key is where the CTRL key should be, making the Assassin's Creed games unplayable with it.

 

I have already deleted all HID keyboards. When they re-install, it does not fix the problem, and for some reason, there are 7 of them, whereas I have only 2 keyboards connected typically: One bluetooth and one mini-gaming keyboard, which in spite of having a wire is also shown as being connected through the bluetooth.

 

Thank you for your attention to this issue.

0 Kudos
Me11
Beginner
3,179 Views

I was finally able to connect the keyboard after much screwing around. It typed a random number of extra characters again - sometimes lines and lines of one character that you had pressed in the middle of typing at over 50 words a minute speed. This was where I was after updating all of my NVidia and Intel drivers a couple of days ago. This issue has cost me days out of my precious life of trouble-shooting and attempting to fix.

 

This turns out to be an issue with the Bluetooth Enumerator. When I looked in the events for the driver, it said it was not fully migrated, due to a conflict with the bluetooth enumerator. I reset my entire windows system. 

 

Please do not put out drivers that do not work. Please fix the current "newest drivers", so that this is no longer a problem. The Arteck bluetooth keyboards use a default windows driver, so Intel and Microsoft need to work together to fix these issues with the bluetooth, and other Intel products. Thank you.

0 Kudos
DeividA_Intel
Moderator
3,106 Views

Hello alinelena, 

 

I am following up with you to confirm if you had the time to collect the out from the commands asked or if you need additional to gather them. I will be waiting for your response.

 

@Me11, thanks for your report, I recommend you open a new thread so we can have a better view of this issue and its impact on the community.

 

Thanks for your comprehension.

 

Regards,  

Deivid A.  

Intel Customer Support Technician

 

0 Kudos
Me11
Beginner
3,070 Views

Feel free to copy the information so you can find out how many other people are having this problem, or just search the internet.

Meanwhile, I forced my PC back to Win 10 21H1 and disabled the updates in the services, which means I cannot get any drivers installed properly, because MS wants to force me to use 22H2, where my bluetooth constantly quit working; even my bt headphones. This is actually your problem now, because I have tried absolutely everything I could find everywhere in the internet. I'm considering rolling my system down to Win 8, which is at least stable. The bluetooth is still crashing my system now, but there is nothing I can do without allowing MS to FORCE their piece-of-junk Win 10 22H2 onto me. 

 

We live in a society, where we pay for products, then have junk forced on us, and companies "updating" things, until those things no longer work. Until I upgraded to MS Win 10 22H2 and simultaneously updated all of my drivers, my system was completely stable. I was just trying to fix issues with an UbiSoft game; now my system is complete junk. The bluetooth locks up the entire system multiple times a day, and still my bluetooth keyboards do not work. Now, the bluetooth locks up my wired technology, too, because someone thought it would be cool to force my wired technology to be bluetooth dependent. I have a 1200W power supply and have disabled the the power management everywhere I could find it. The system is performance optimized to the max.

 

Please work with MS to fix these issues. There is some problem between your bluetooth and MS Win 10 22H2, if not other builds of Windows. I do not have any desire to waste precious time from my life messing around checking and writing and trying. I will just roll everything down to Win 8 before I do that.

0 Kudos
DeividA_Intel
Moderator
3,079 Views

Hello alinelena,  


I was checking your thread and noticed that we have not heard back from you. I’m going to close your post, but if you need further assistance, please do not hesitate to create a new thread. 


Regards,  

Deivid A.  

Intel Customer Support Technician  


0 Kudos
alinelena
Novice
3,067 Views

I did not have the chance to collect the stuff with the tool indicated... mainly cause the suggested instructions do not seem to work for linux... 

I have tested the new kernel-bluetooth-firmware release and is not working... same issues... go back to march firmware and is working perfectly fine.

 

lsusb | grep 8087                                                                                                                                                                         12/10/23 21:35:45
Bus 003 Device 007: ID 8087:0033 Intel Corp.


dmesg | grep Bluetooth                                                                                                                                                                1 ⨯ 12/10/23 21:41:23
[    5.003050] Bluetooth: Core ver 2.22
[    5.003082] Bluetooth: HCI device and connection manager initialized
[    5.003088] Bluetooth: HCI socket layer initialized
[    5.003091] Bluetooth: L2CAP socket layer initialized
[    5.003093] Bluetooth: SCO socket layer initialized
[    5.013230] Bluetooth: hci0: Device revision is 0
[    5.013236] Bluetooth: hci0: Secure boot is enabled
[    5.013237] Bluetooth: hci0: OTP lock is enabled
[    5.013239] Bluetooth: hci0: API lock is enabled
[    5.013239] Bluetooth: hci0: Debug lock is disabled
[    5.013241] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    5.013243] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[    5.013954] Bluetooth: hci0: DSM reset method type: 0x00
[    5.082017] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.082021] Bluetooth: BNEP filters: protocol multicast
[    5.082027] Bluetooth: BNEP socket layer initialized
[    5.118600] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[    5.118622] Bluetooth: hci0: Boot Address: 0x100800
[    5.118624] Bluetooth: hci0: Firmware Version: 64-35.23
[    6.634942] Bluetooth: hci0: Waiting for firmware download to complete
[    6.635310] Bluetooth: hci0: Firmware loaded in 1481156 usecs
[    6.635408] Bluetooth: hci0: Waiting for device to boot
[    6.652338] Bluetooth: hci0: Device booted in 16602 usecs
[    6.652349] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[    6.652884] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc
[    6.655425] Bluetooth: hci0: Applying Intel DDC parameters completed
[    6.658445] Bluetooth: hci0: Firmware timestamp 2023.35 buildtype 1 build 70976
[    6.732486] Bluetooth: MGMT ver 1.22
[    6.957364] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[    6.957424] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[    6.957440] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   42.508361] Bluetooth: hci0: Opcode 0x200e failed: -16
[   42.508647] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   42.508757] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   42.508798] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   54.519930] Bluetooth: RFCOMM TTY layer initialized
[   54.519944] Bluetooth: RFCOMM socket layer initialized
[   54.519949] Bluetooth: RFCOMM ver 1.11
[   58.161311] Bluetooth: hci0: Opcode 0x200e failed: -16
[ 1055.160788] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 1055.160797] Bluetooth: HIDP socket layer initialized

filename:       /usr/lib/modules/6.6.0-rc5-2.gd26c540-default/kernel/drivers/bluetooth/btintel.ko.zst
firmware:       intel/ibt-12-16.ddc
firmware:       intel/ibt-12-16.sfi
firmware:       intel/ibt-11-5.ddc
firmware:       intel/ibt-11-5.sfi
license:        GPL
version:        0.1
description:    Bluetooth support for Intel devices ver 0.1
author:         Marcel Holtmann <marcel@holtmann.org>
suserelease:    openSUSE Tumbleweed
srcversion:     6850F65AEED3D3A5FE15B61
depends:        bluetooth
retpoline:      Y
intree:         Y
name:           btintel
vermagic:       6.6.0-rc5-2.gd26c540-default SMP preempt mod_unload modversions  
sig_id:         PKCS#7
signer:         Kernel OBS Project
sig_key:        BC:B2:07:5D:92:88:1E:7C
sig_hashalgo:   sha256
signature:      8D:9B:CC:23:B0:3F:EE:68:69:62:CD:F3:06:08:8B:69:9D:6A:7E:51:
               64:D7:5E:A0:AD:9B:44:F5:B5:2C:81:74:CF:1E:F5:95:43:C6:FC:52:
               E3:A1:64:AB:D3:94:FB:2A:95:C5:D1:4B:1E:2D:F6:3B:0D:D2:81:9E:
               40:65:52:12:10:A5:5C:30:81:D7:DF:4E:18:76:4E:8D:CF:B9:BC:86:
               59:E6:59:0F:75:57:93:99:21:C7:0D:84:D7:F2:DB:E7:53:14:1E:9F:
               02:E3:C7:D1:17:94:D0:A9:EB:67:5C:9C:DE:06:EF:CB:6F:C6:87:2E:
               D3:8E:78:CF:76:5C:BD:1A:67:01:C8:1C:29:31:5A:E3:14:56:89:ED:
               32:75:A5:56:19:38:66:38:9D:C2:9F:10:FA:2F:8F:64:DE:79:DF:24:
               BD:83:3A:43:F0:48:B5:E8:0D:09:87:EA:6B:EB:E0:2B:A0:B2:EF:A5:
               1A:D9:A3:79:64:C6:44:51:C7:37:53:68:90:B9:7E:0B:3C:F6:D7:D5:
               6E:2C:01:8B:21:CC:A6:E4:46:15:D4:B9:E2:F9:D7:FA:8B:38:41:03:
               39:D8:15:8C:83:C9:AF:CC:94:F0:44:F7:A6:E8:C3:8B:DB:53:6A:46:
               16:C0:F4:B0:32:88:71:B2:6A:B1:CE:A6:C1:DF:0D:60

also, I hope you realise you suggest users to install deprecated tools... like hciconfig... 

https://www.spinics.net/lists/linux-bluetooth/msg70489.html

 

also note than the original post already reported some of these.

alderlake22
Beginner
2,492 Views

Hi, it looks like I'm having the same problems. I have the same intel/ibt-0040-0041.sfi firmware on my logs. Do you mine telling me the steps on how you fixed this?

0 Kudos
alinelena
Novice
2,485 Views

i extracted that files from an old rpm of the kernel firmware, and replaced them. then rebooted.

however this is not a long term solution

0 Kudos
alderlake22
Beginner
2,446 Views

Are you using a ZMK keyboard by any chance? Can you provide the Kernel release with the working ibt firmware?

0 Kudos
alinelena
Novice
2,356 Views

yes is a xiao seeduino one... but probably same for other nrf52840 chips

 

i extracted from this kernel-firmware-bluetooth-20230320-150500.1.1.noarch.rpm this is opensuse rpm but probably similar firmware packages on other distros too

0 Kudos
vbaskoff
Beginner
2,381 Views

Hi All,

 

I am also face issue when AX211 based laptop (HP Elitebook 1040 G10) at some point starts to refuse (even can't find while scanning) pair bt keyboard and mice (tested with Logitech MX Keys, MX Keys Mini, MX Master 3, MX Anywhere 3S ). All these BT keyborads and mices are work perfectly previously and works as expected at my Lenovo Thinkpad X270.

 

Please help.

 

My environment is the following:

 

 

 

[$]> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.3 LTS
Release:        22.04
Codename:       jammy

[$]> uname -a
Linux XXXX 6.5.0-1008-oem #8-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 10 13:08:33 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

[$]> modinfo btintel
filename:       /lib/modules/6.5.0-1008-oem/kernel/drivers/bluetooth/btintel.ko
firmware:       intel/ibt-12-16.ddc
firmware:       intel/ibt-12-16.sfi
firmware:       intel/ibt-11-5.ddc
firmware:       intel/ibt-11-5.sfi
license:        GPL
version:        0.1
description:    Bluetooth support for Intel devices ver 0.1
author:         Marcel Holtmann <marcel@holtmann.org>
srcversion:     FDF2221B8ED4B01F8EADF85
depends:        bluetooth
retpoline:      Y
intree:         Y
name:           btintel
vermagic:       6.5.0-1008-oem SMP preempt mod_unload modversions 
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        14:D5:74:C6:2D:0F:A0:F7:55:6E:CF:93:9D:18:BE:D9:19:27:23:97
sig_hashalgo:   sha512
signature:      82:6D:90:...


[$]> sudo dmesg | grep -i bluetooth
[   10.482749] Bluetooth: Core ver 2.22
[   10.482769] NET: Registered PF_BLUETOOTH protocol family
[   10.482771] Bluetooth: HCI device and connection manager initialized
[   10.482774] Bluetooth: HCI socket layer initialized
[   10.482777] Bluetooth: L2CAP socket layer initialized
[   10.482781] Bluetooth: SCO socket layer initialized
[   10.659595] Bluetooth: hci0: Device revision is 0
[   10.659600] Bluetooth: hci0: Secure boot is enabled
[   10.659601] Bluetooth: hci0: OTP lock is enabled
[   10.659602] Bluetooth: hci0: API lock is enabled
[   10.659603] Bluetooth: hci0: Debug lock is disabled
[   10.659604] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   10.659606] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[   10.665789] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
[   10.665848] Bluetooth: hci0: Boot Address: 0x100800
[   10.665850] Bluetooth: hci0: Firmware Version: 107-51.22
[   11.716274] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   11.716277] Bluetooth: BNEP filters: protocol multicast
[   11.716282] Bluetooth: BNEP socket layer initialized
[   12.240934] Bluetooth: hci0: Waiting for firmware download to complete
[   12.241584] Bluetooth: hci0: Firmware loaded in 1538857 usecs
[   12.241635] Bluetooth: hci0: Waiting for device to boot
[   12.257582] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[   12.257598] Bluetooth: hci0: Device booted in 15620 usecs
[   12.257717] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc
[   12.260596] Bluetooth: hci0: Applying Intel DDC parameters completed
[   12.263617] Bluetooth: hci0: Firmware timestamp 2022.51 buildtype 1 build 56683
[   12.333644] Bluetooth: MGMT ver 1.22
[   14.259423] Bluetooth: RFCOMM TTY layer initialized
[   14.259436] Bluetooth: RFCOMM socket layer initialized
[   14.259443] Bluetooth: RFCOMM ver 1.11
[$]> hciconfig -a
hci0:   Type: Primary  Bus: USB
        BD Address: 70:D8:23:BE:FD:6A  ACL MTU: 1021:4  SCO MTU: 96:6
        UP RUNNING PSCAN 
        RX bytes:20635 acl:0 sco:0 events:3237 errors:0
        TX bytes:790253 acl:0 sco:0 commands:3231 errors:0
        Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH SNIFF 
        Link mode: PERIPHERAL ACCEPT 
        Name: 'XXXX'
        Class: 0x7c010c
        Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony
        Device Class: Computer, Laptop
        HCI Version:  (0xc)  Revision: 0x356b
        LMP Version:  (0xc)  Subversion: 0x356b
        Manufacturer: Intel Corp. (2)


[$]> sudo hciconfig hci0 up 

        
[$]> lsusb | grep 8087
Bus 001 Device 005: ID 8087:0033 Intel Corp. 

 

 

 

I have also tried latest Intel SSU tool, report is attached

 

 

 

[$]> sudo ./ssu.sh 
This product is not supported on this operating system.
     Would you like to try to scan? (y/n) y

 

 

 

 

0 Kudos
neyb
Beginner
1,975 Views

Any news on this ?

 

@alinelena your btmon.log seems to indicate your timeout seems to occure after a PHY 2M upgrade. it seems last version of the intel firmware for linux are buggy on PHY 2M. (I suspect the same problem on windows btw...). if you use a mkinitcpio based init process (pop os, arch...) you can revert to the old firmware, ... or disable PHY 2M in zmk (CONFIG_BT_CTLR_PHY_2M=n).

 

@DeividA_Intel : has bt PHY 2M be tested on last ax211 family firmware ?

FearlessSpiff
Beginner
1,453 Views

I just created an account to confirm that setting 'CONFIG_BT_CTLR_PHY_2M=n' fixed my connection problem on ZMK with an AX211 intel card and newest linux stuff from arch on a Surface Pro 9. Thanks for that temporary fix!

0 Kudos
alinelena
Novice
274 Views

@neyb @FearlessSpiff  sorry for late reply I missed the messages... 

I can confirm that your workaround works... and I can also confirm the bug is still present in ernel 6.8.0-rc3

0 Kudos
Reply