Intel AX201 Bluetooth Issues connecting to logitech products on Linux OS

[mccurly]

Hi.

I am using this dual intel wireless/bluetooth network card:

inxi -E                                                                                                                     
Bluetooth:
  Device-1: Intel AX201 Bluetooth driver: btusb type: USB
  Report: hciconfig ID: hci0 state: up address: aa:bb:cc:dd:ee:ff (redacted) bt-v: 5.2

 in my up-to-date Arch Linux System:

uname -a                                                                                                                     
Linux (system name, redacted) 6.4.11-zen2-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Sat, 19 Aug 2023 15:38:10 +0000 x86_64 GNU/Linux

Problem (detected since a few days ago with the first logitech product that I inserted on my system, a bluetooth mouse) is that when I put these logitech devices in "pairing" mode, they do not get detected by my host system with the aforementioned Intel device.

If I try to do the same process on another computer that I own, with a different bluetooth device, and basically the same OS version and bluetooth software installed, on that second pc, the pairing and connection procedures and usage works as expected.

The same Intel AX201 card works well with other devices such as bluetooth speakers/headphones and the like.

This is the first time that I've had issues related to the bluetooth card.

Can anyone shed some light into this please?

[mccurly]

Hello again.

There is a news update:

I've installed and booted up LTS kernel, and all seems to work as expected.

I am going to report this on the Arch Linux user forum as well.

For now I sort of settle with this workaround.

Thanks to all who leaned over and took a peek at this post of mine.

Hope that Intel or Arch or anybody else that might contribute to solving this issue in a more decisive manner would consider doing so.

Thank you.

This is the post I've just made in Arch Linux Forums 

[Jocelyn_Intel]

Hello, @mccurly  

Thank you for posting on the Intel® communities. I will gladly assist you here. 

I appreciate the information provided, however, please provide us with the following information: 

1. Is the Intel® Wi-Fi 6 AX201 the pre-installed wireless card in your motherboard or is it an integration (upgrade/ not the original card)? 
2. What is the specific model of your system? If you have a Desktop PC, please provide the model of your motherboard. 
3. What is the Logitech device model you are trying to connect to? Does this happen with other Logitech devices apart from your mouse? 
4. Was it working before? 

Best regards,  

Jocelyn M.   

Intel Customer Support Technician. 

[mccurly]

Hello @Jocelyn_Intel , thank you for your time:

---

Is the Intel® Wi-Fi 6 AX201 the pre-installed wireless card in your motherboard or is it an integration (upgrade/ not the original card)?

Yes. It is the original one, not an upgrade.

What is the specific model of your system? If you have a Desktop PC, please provide the model of your motherboard. 

Yes of course, here it is:

sudo inxi -M
Machine:
  Type: Desktop System: ASUSTeK product: MINIPC PB62 v: N/A
    serial: (REDACTED)
  Mobo: ASUSTeK model: PB62 serial: N/A UEFI: ASUSTeK v: 0221
    date: 09/06/2022​

What is the Logitech device model you are trying to connect to? Does this happen with other Logitech devices apart from your mouse? 


Yes the same happens with the Logitech Keyboard (these are the devices, that are seen in LTS Kernel) :

bluetoothctl                                                                                  
Agent registered
# devices
Device aa:bb:cc:dd:ee:ff (redacted) M720 Triathlon
Device aa:bb:cc:dd:ee:ff (redacted) MX Keys
Device aa:bb:cc:dd:ee:ff (redacted) JBL (headphones)
​

Was it working before? 

Since I only purchased these Logitech devices recently, I can only say that they do not work with Linux ZEN, on the aforementioned setup. As opposed to another laptop that I own (that ran the same Linux ZEN) but had no issues. (That is why I turned up here in Intel's Forums for help)

---

Thank you.

[Jocelyn_Intel]

Hello, @mccurly  

Thank you very much for the information provided. 

Please try the following commands to make sure everything is okay and attach the logs, if applicable: 

1. Make sure the BT adapter is enabled by running #hciconfig -i <interface name> up. 
2. Type # modinfo btintel to make sure the driver is loaded. 
3. Type the #dmesg | grep Bluetooth” to check if you have the latest Firmware, you need to check here for supported FW. 
4. If the issue persists after this debugging, please attach the dmesg logs, please type # dmesg > dmesg.log. If there are any replication steps, please specify them as well. 

Best regards,  

Jocelyn M.   

Intel Customer Support Technician. 

[mccurly]

Hello again @Jocelyn_Intel , and (again, as well), thank you very much for your time and attention.

Well, the problem, now, having booted up this kernel doesn't manifest any longer:

uname -r :
6.4.11-zen2-1-zen

 (I mean after having paired the devices MX Keys and M720 Triathlon under LTS kernel, verifying it works on that kernel, I rebooted, but without powering off the computer, to Zen kernel, and here, the issue is not apparent).

Nevertheless, I ran the suggested commands (all but the dmesg buffer capture that you have suggested) and here are the outputs:

(root-prompt) hciconfig hci0 up

(does not yield anything in the terminal so I suppose the command returned successfully)

(root-prompt) modinfo btintel:

filename:       /lib/modules/6.4.11-zen2-1-zen/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>
srcversion:     6E15B16D7DCE127A97A0FFA
depends:        bluetooth
retpoline:      Y
intree:         Y
name:           btintel
vermagic:       6.4.11-zen2-1-zen SMP preempt mod_unload 
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        58:E4:FB:21:BC:B5:46:79:7F:6B:A6:7F:E1:04:1E:22:4C:BE:1E:AF
sig_hashalgo:   sha512
signature:      30:64:02:30:26:86:DE:69:E4:9F:D0:F4:5D:B6:C2:15:2D:8E:26:81:
                75:6D:80:8D:73:3E:48:10:F6:CD:ED:C4:0E:AF:23:83:ED:18:87:57:
                85:82:84:EE:A2:C8:5D:D5:24:A5:D1:7C:02:30:73:43:0F:E8:66:4F:
                75:13:BD:EA:46:D0:F8:8D:45:70:47:C4:BD:B7:CB:34:6B:DC:A0:FD:
                A9:52:D5:43:E0:EC:E0:1D:77:56:89:14:3F:F5:26:5B:58:AA:6A:06:
                1C:A6

(root-prompt) dmesg | grep Bluetooth:

[    3.549412] Bluetooth: Core ver 2.22
[    3.549429] Bluetooth: HCI device and connection manager initialized
[    3.549431] Bluetooth: HCI socket layer initialized
[    3.549432] Bluetooth: L2CAP socket layer initialized
[    3.549435] Bluetooth: SCO socket layer initialized
[    3.629661] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
[    3.630619] Bluetooth: hci0: Device revision is 2
[    3.630620] Bluetooth: hci0: Secure boot is enabled
[    3.630621] Bluetooth: hci0: OTP lock is enabled
[    3.630621] Bluetooth: hci0: API lock is enabled
[    3.630622] Bluetooth: hci0: Debug lock is disabled
[    3.630622] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    3.783854] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
[    3.783878] Bluetooth: hci0: Boot Address: 0x24800
[    3.783879] Bluetooth: hci0: Firmware Version: 206-22.23
[    3.807151] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    3.807153] Bluetooth: BNEP filters: protocol multicast
[    3.807155] Bluetooth: BNEP socket layer initialized
[    5.519750] Bluetooth: hci0: Waiting for firmware download to complete
[    5.520592] Bluetooth: hci0: Firmware loaded in 1696030 usecs
[    5.520653] Bluetooth: hci0: Waiting for device to boot
[    5.535574] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[    5.535574] Bluetooth: hci0: Device booted in 14615 usecs
[    5.535816] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
[    5.537646] Bluetooth: hci0: Applying Intel DDC parameters completed
[    5.538586] Bluetooth: hci0: Firmware revision 0.4 build 206 week 22 2023
[    5.605687] Bluetooth: MGMT ver 1.22
[    5.711266] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   28.237052] Bluetooth: RFCOMM TTY layer initialized
[   28.237060] Bluetooth: RFCOMM socket layer initialized
[   28.237061] Bluetooth: RFCOMM ver 1.11

And for the sake of consistency, I am going to try to unpair/"forget" the devices from booted Zen kernel, and repeat the whole process to see if it keeps connecting with this setup:

(And, to my regret, it falls through, does not connect, as expected).

So, summing up: These devices do not pair (and subsequently connect) with zen kernel (and possibly with main kernel as well, but I haven't tried so I can only speculate at the moment).

I am going to reboot and be right back with the updates for this situation in the main kernel.

See you soon.

[mccurly]

Hello again @Jocelyn_Intel , and thank you very much for your support.

I will try those commands (I think that you are referring to both of the involved kernels, which are LTS and "vanilla") flavors and post back the proceedings.

(I am not at that computer right now).

I think I will have the opportunity to issue those commands soon, though, and as I said I will post back the resulting information.

Thank you again for your time and patience.

See you soon.

[Jocelyn_Intel]

Hello, @mccurly  

Thank you for your reply. 

Sure, no worries. I will follow up on this thread to see if there are any updates. 

Have a nice day. 

Best regards,  

Jocelyn M.   

Intel Customer Support Technician. 

[mccurly]

Hello again @Jocelyn_Intel ,

I attached the answers to your questions in the subsequent text files.

I have not noticed much in particular. As expected, the hardware works well if paired under the LTS kernel.

In the proceedings files you will notice that the only clearly differing aspect is the src version of the btintel module.

Which is, for LTS:

28058858CBC79161EF62BD9

And for Main and Zen kernel:

6E15B16D7DCE127A97A0FFA

Can you please, @Jocelyn_Intel , specify what might have changed between these versions?

Thank you.

[Jocelyn_Intel]

Hello, @mccurly  

Thank you for your reply and the information provided. 

Can you please provide me the dmesg logs (# dmesg > dmesg.log ) so we can onvestigate this issue further? 

Best regards,  

Jocelyn M.   

Intel Customer Support Technician. 

[mccurly]

Hi, sorry for this late reply.

Ok I'll be happy to provide those logs.

From which kernel should I gather them? LTS? Mainline? Both?

Also, is there any need to anonymize that information?

How?

Is there any channel where I could deliver you these logs without the need for anonymizing them, if that need seems fair?

Thank you.

See you soon.

[Jocelyn_Intel]

Hello, @mccurly  

Thank you for your reply. Sure, I totally comprehend.

For the dmesg logs, type # dmesg > dmesg.log and send the output in a txt file. 

You can send it via Communities DM or I can send an email to the email address associated to your Profile, in case you feel uncomfortable attaching it to the thread.  As for the kernel, please use the kernel you have issues with..

Best regards,  

Jocelyn M.   

Intel Customer Support Technician. 

[Jocelyn_Intel]

Hello, @mccurly    

I am checking this thread and I would like to know if you were able to review our previous post.

Best regards,  

Jocelyn M.   

Intel Customer Support Technician. 

[Jocelyn_Intel]

Hello, @mccurly         

As we have not heard back from you, we will proceed to close this thread now. If you need any additional assistance, please feel free to contact us back and submit a new question as this thread will no longer be monitored.  

Best regards,  

Jocelyn M.   

Intel Customer Support Technician.