Title: Bluetooth 5.4 Adapter (Ugreen CM749) Not Functioning on Ubuntu 20.04 with Kernel 6.x Description: The Bluetooth 5.4 adapter Ugreen CM749 is not functioning on Ubuntu 20.04 with Kernel 6.x. The adapter is detected by the system but fails to initialize, showing a "Connection timed out (110)" error when attempting to bring up the interface. The Bluetooth 5.0 dongle works without issues on the same system. Steps to Reproduce: 1. Plugged in the Ugreen CM749 Bluetooth 5.4 adapter. 2. Ran `hciconfig hci0 up` to bring up the Bluetooth interface. 3. Observed the error "Connection timed out (110)" in the terminal. 4. Checked the dmesg logs and found repeated Bluetooth errors. Expected Behavior: The Bluetooth 5.4 adapter should initialize correctly, allowing for Bluetooth functionality such as pairing and connecting devices. Actual Behavior: The Bluetooth 5.4 adapter fails to initialize, with the interface staying down and connection attempts timing out. Additional Information: - Kernel Version: 6.10.2-061002-generic - Ubuntu Version: 20.04 - Hardware Information: *-network:1 description: Bluetooth device product: Realtek Bluetooth Adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: usb@1:1 version: 1.00 - dmesg Output: [12345.6789] Bluetooth: hci0: Opcode 0x1005 failed: -110 - hciconfig Output: hci0: Type: Primary Bus: USB BD Address: 00:A7:45:28:00:B3 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:171 acl:0 sco:0 events:10 errors:0 TX bytes:276 acl:0 sco:0 commands:11 errors:0

Bug #2076407 reported by maestrom4
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

Title: Bluetooth 5.4 Adapter (Ugreen CM749) Not Functioning on Ubuntu 20.04 with Kernel 6.x

Description:
The Bluetooth 5.4 adapter Ugreen CM749 is not functioning on Ubuntu 20.04 with Kernel 6.x. The adapter is detected by the system but fails to initialize, showing a "Connection timed out (110)" error when attempting to bring up the interface. The Bluetooth 5.0 dongle works without issues on the same system.

Steps to Reproduce:
1. Plugged in the Ugreen CM749 Bluetooth 5.4 adapter.
2. Ran `hciconfig hci0 up` to bring up the Bluetooth interface.
3. Observed the error "Connection timed out (110)" in the terminal.
4. Checked the dmesg logs and found repeated Bluetooth errors.

Expected Behavior:
The Bluetooth 5.4 adapter should initialize correctly, allowing for Bluetooth functionality such as pairing and connecting devices.

Actual Behavior:
The Bluetooth 5.4 adapter fails to initialize, with the interface staying down and connection attempts timing out.

Additional Information:
- Kernel Version: 6.10.2-061002-generic
- Ubuntu Version: 20.04
- Hardware Information:
  *-network:1
       description: Bluetooth device
       product: Realtek Bluetooth Adapter
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: usb@1:1
       version: 1.00
- dmesg Output:
  [12345.6789] Bluetooth: hci0: Opcode 0x1005 failed: -110
- hciconfig Output:
  hci0: Type: Primary Bus: USB
  BD Address: 00:A7:45:28:00:B3 ACL MTU: 0:0 SCO MTU: 0:0
  DOWN
  RX bytes:171 acl:0 sco:0 events:10 errors:0
  TX bytes:276 acl:0 sco:0 commands:11 errors:0

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: bluez 5.72-0ubuntu5
Uname: Linux 6.10.2-061002-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 9 17:05:31 2024
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Micro-Star International Co., Ltd. MS-7C51
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.10.2-061002-generic root=UUID=b4f23699-fafb-4f32-8572-eb30ac62d1dc ro quiet splash btusb.enable_autosuspend=0 usbcore.autosuspend=-1 vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to noble on 2024-07-30 (10 days ago)
dmi.bios.date: 07/20/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.71
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A320M-A PRO (MS-7C51)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.71:bd07/20/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnA320M-APRO(MS-7C51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C51
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
hciconfig:
 hci0: Type: Primary Bus: USB
  BD Address: 00:A7:45:28:00:B3 ACL MTU: 0:0 SCO MTU: 0:0
  DOWN
  RX bytes:165 acl:0 sco:0 events:9 errors:0
  TX bytes:273 acl:0 sco:0 commands:10 errors:0
rfkill:
 2: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

Revision history for this message
maestrom4 (dnlmts96) wrote :
Revision history for this message
maestrom4 (dnlmts96) wrote :

lsusb
Bus 001 Device 002: ID 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio
Bus 001 Device 002: ID 0bda:8771 Realtek Semiconductor Corp.
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.10
  bDeviceClass 224 Wireless
  bDeviceSubClass 1 Radio Frequency
  bDeviceProtocol 1 Bluetooth
  bMaxPacketSize0 64
  idVendor 0x0bda Realtek Semiconductor Corp.
  idProduct 0x8771
  bcdDevice 0.02
  iManufacturer 1 Realtek
  iProduct 2 Bluetooth Radio
  iSerial 3 00A7452800B3
  bNumConfigurations 1

[12345.6789] Bluetooth: hci0: Opcode 0x1005 failed: -110
hci0: Type: Primary Bus: USB
BD Address: 00:A7:45:28:00:B3 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:171 acl:0 sco:0 events:10 errors:0
TX bytes:276 acl:0 sco:0 commands:11 errors:0

affects: bluez (Ubuntu) → linux (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.