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
*** Bug 216533 has been marked as a duplicate of this bug. ***
Please attach dmesg. Would be great if you elucidated the steps to reproduce in an easy to understand form. If you don't know English well enough, please use deepl.com
What don't you understand in this following procedure ? At the PC, after pairing, disconnect the smartphone. Wait 5 minutes or more At the PC, connect the smartphone. Connection fails.
There is no dmesg log file in/var/log/ . I put forward the problem. It's not a problem with chipset intel AX210 (Bluetooth 5.3). There is no problem between a Bluetooth 5.0 tablet (Blackview Tab 8) 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.
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
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
At the PC, I connect the smartphone bluetoothctl connect 90:06:28:B6:B1:B6 Attempting to connect to 90:06:28:B6:B1:B6 Failed to connect: org.bluez.Error.Failed le-connection-abort-by-local
Created attachment 301903 [details] trace
I forgot pipewire 3.58
Steven G. (Intel Customer Support Technician) said ******************************************************************************** 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. ******************************************************************************** I don't understand the Intel support. The card is equipped with an Intel AX210 chipset and if I understand well, Linux uses the Intel wifi/bluetooth driver of the AX210. No ?
Created attachment 301936 [details] dmesg -H I tried several times to connect the smartphone.
There is some progress. with the kernel 5.19.12, at the PC i can connect the smartphone