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.
7299 Discussions

openSUSE Tumbleweed, AX210, bluetooth, connection fails

promeneur
Beginner
1,498 Views

MB Asus B250M

Wi-Fi/Bluetooth card : EDUP LOVE EP-9651GS (chipset Intel AX210), Bluetooth 5.3

Samsung S7, android 8.0, Bluetooth 4

 

openSUSE Tumbleweed

kernel 5.19.10

Firmware date : 20220902 (date of the package "firmware all")

 

I don't use Wi-Fi. Just for a backup solution. I checked Wi-Fi works well.

 

At the PC, just disconnect the smartphone after pairing.

Wait 5 mn or more.

At the PC, connect the smartphone. The connection fails.

 

I did some experiments with Clearlinux and Fedora. With the two OS, I can reproduce the problem.

 

More info :

At the smartphone, I connect the PC. The connection succeeds.

At the PC, I disconnect then reconnect the smartphone. The connection succeeds.

At the PC disconnect the smartphone.

Wait for 5 mn or more.

At the PC connect the smartphone. The connection fails.

 

Thanks in advance

0 Kudos
12 Replies
Steven_Intel
Moderator
1,464 Views

Hello promeneur,


Thank you for posting on the Intel® communities.


In order to better assist you, please provide the following information:


  • What driver version are you using for the wireless adapter, and where are you downloading it?
  • Did the issue start after any hardware upgrade or driver/OS update?


Best regards,


Steven G.

Intel Customer Support Technician.


0 Kudos
promeneur
Beginner
1,459 Views

>>  where are you downloading it?

 

I downloaded nothing. The driver is installed by the OS openSUSE Tumbleweed.

 

>> What driver version are you using for the wireless adapter ?

 

In the file boot.msg I found this

 

<6>[ 6.840275] Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi
<6>[ 6.840359] Bluetooth: hci0: Boot Address: 0x100800
<6>[ 6.840360] Bluetooth: hci0: Firmware Version: 129-28.22

 

I found this :

 

<6>[ 6.801315] Bluetooth: hci0: Device revision is 0
<6>[ 6.801319] Bluetooth: hci0: Secure boot is enabled
<6>[ 6.801319] Bluetooth: hci0: OTP lock is enabled
<6>[ 6.801320] Bluetooth: hci0: API lock is enabled

 

I found this :

 

<4>[ 6.865334] iwlwifi 0000:04:00.0: api flags index 2 larger than supported by driver
<6>[ 6.865349] iwlwifi 0000:04:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36
<6>[ 6.865587] iwlwifi 0000:04:00.0: loaded firmware version 71.058653f6.0 ty-a0-gf-a0-71.ucode op_mode iwlmvm
<6>[ 6.801321] Bluetooth: hci0: Debug lock is disabled
<6>[ 6.801322] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
<6>[ 6.801323] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38

0 Kudos
promeneur
Beginner
1,458 Views

Since yesterday, I have put forward.

 

 

It's not a problem with chipset intel AX210 (Bluetooth 5.3).

There is no problem between a Bluetooth 5.0 tablet (Blackview Tab  and a PC equipped with Bluetooth 5.3.

There is a problem between a Bluetooth 4.2 smartphone (Samsung S7) and a PC equipped with Bluetooth 5.3. 
You can't connect the smartphone from the PC.
You can only connect the PC from the smartphone then immediately disconnect/reconnect the smartphone
from the PC to get all the protocols, HSP and A2DP.

 

What do you think ?

 

0 Kudos
Steven_Intel
Moderator
1,422 Views

Thank you for all the information provided.


I am going to research about this, based on the information provided. As soon as I have an update, I will let you know.


Best regards,


Steven G.

Intel Customer Support Technician.


0 Kudos
promeneur
Beginner
1,409 Views

bluetoothctl show
Controller F0:B6:1E:FE:FB:F4 (public)
Name: grincheux
Alias: grincheux
Class: 0x007c0104
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x000000b4
Pairable: yes
UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0541
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x0c (12)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded

0 Kudos
promeneur
Beginner
1,409 Views

bluetoothctl info 90:06:28:B6:B1:B6
Device 90:06:28:B6:B1:B6 (public)
Name: Samsung Galaxy S7 Argent
Alias: Samsung Galaxy S7 Argent
Class: 0x005a020c
Icon: phone
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb)
UUID: PANU (00001115-0000-1000-8000-00805f9b34fb)
UUID: NAP (00001116-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: SIM Access (0000112d-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (a23d00bc-217c-123b-9c00-fc44577136ee)
Modalias: bluetooth:v0075p0100d0201
Affected by Policy: no

0 Kudos
promeneur
Beginner
1,409 Views

At the PC, i connect the smartphone. the connection fails.

0 Kudos
promeneur
Beginner
1,409 Views

At the PC, I connect the smartphone. The connection fails.

See the dump.snoop file

0 Kudos
promeneur
Beginner
1,409 Views

Sorry, I fail to attach the dump.snoop or the dump.snoop.txt file

0 Kudos
promeneur
Beginner
1,403 Views

You can get the dump.snoop file here

 

https://github.com/bluez/bluez/issues/401#issuecomment-1263235497

 

 

0 Kudos
Steven_Intel
Moderator
1,393 Views

Hello promeneur,


Due to the fact that you are using a wireless card designed by a third-party manufacturer, and none of our drivers are being used, our best recommendation is to contact EDUP support for further assistance.


Please keep in mind that this thread will no longer be monitored by Intel. Thank you for your understanding.  


Best regards,


Steven G.

Intel Customer Support Technician.


0 Kudos
promeneur
Beginner
1,387 Views

How do you no it is not an intel driver which is used.

iwlwifi is an intel driver. no ?

 

Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi

 

ibt-0041-0041.sfi is an intel driver. No ?

0 Kudos
Reply