* [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce
@ 2020-08-19 20:53 bugzilla-daemon
2020-10-04 13:41 ` [Bug 208965] " bugzilla-daemon
` (32 more replies)
0 siblings, 33 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-08-19 20:53 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
Bug ID: 208965
Summary: not working bluetooth mouse low energy rtl8822ce
Product: Drivers
Version: 2.5
Kernel Version: 5.8.1-arch1-1
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: fakecop@yandex.ru
Regression: No
Created attachment 292031
--> https://bugzilla.kernel.org/attachment.cgi?id=292031&action=edit
journalctl
I'm use huawei matebook 13 amd (2020), this is notebook use combo module
wifi+bluetooth: Realtek 8822CE. I am trying to connect huawei mouse and i get
error (in attachments)
Systemctl log:
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor
preset: disabled)
Active: active (running) since Tue 2020-08-04 16:36:29 MSK; 1min 4s ago
Docs: man:bluetoothd(8)
Main PID: 2110 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 17907)
Memory: 1.7M
CGroup: /system.slice/bluetooth.service
└─2110 /usr/lib/bluetooth/bluetoothd -d
авг 04 16:37:14 Anton bluetoothd[2110]: src/agent.c:agent_unref()
0x55720e940a70: ref=1
авг 04 16:37:14 Anton bluetoothd[2110]: src/adapter.c:resume_discovery()
авг 04 16:37:14 Anton bluetoothd[2110]: src/adapter.c:pair_device_complete()
Failed (0x03)
авг 04 16:37:14 Anton bluetoothd[2110]:
src/adapter.c:bonding_attempt_complete() hci0 bdaddr FE:FD:2D:11:26:FD type 2
status 0x3
авг 04 16:37:14 Anton bluetoothd[2110]: src/device.c:device_bonding_complete()
bonding (nil) status 0x03
авг 04 16:37:14 Anton bluetoothd[2110]: src/device.c:device_bonding_failed()
status 3
авг 04 16:37:14 Anton bluetoothd[2110]: src/adapter.c:resume_discovery()
авг 04 16:37:16 Anton bluetoothd[2110]: src/agent.c:agent_disconnect() Agent
:1.118 disconnected
авг 04 16:37:16 Anton bluetoothd[2110]: src/agent.c:agent_destroy() agent
:1.118
авг 04 16:37:16 Anton bluetoothd[2110]: src/agent.c:agent_unref()
0x55720e940a70: ref=0
bluetoothctl:
Agent registered
[bluetooth]# select 1C:BF:C0:1A:8E:3C
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller 1C:BF:C0:1A:8E:3C Discovering: yes
[NEW] Device FE:FD:2D:11:26:FD HUAWEI Mouse
[bluetooth]# agent on
Agent is already registered
[bluetooth]# scan off
Discovery stopped
[CHG] Controller 1C:BF:C0:1A:8E:3C Discovering: no
[CHG] Device FE:FD:2D:11:26:FD RSSI is nil
[bluetooth]# pair FE:FD:2D:11:26:FD
Attempting to pair with FE:FD:2D:11:26:FD
[CHG] Device FE:FD:2D:11:26:FD Connected: yes
[CHG] Device FE:FD:2D:11:26:FD Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
[bluetooth]# connect FE:FD:2D:11:26:FD
Attempting to connect to FE:FD:2D:11:26:FD
[CHG] Device FE:FD:2D:11:26:FD Connected: yes
[CHG] Device FE:FD:2D:11:26:FD Connected: no
Failed to connect: org.bluez.Error.Failed
[bluetooth]#
btmon log:
Bluetooth monitor ver 5.54
= Note: Linux version 5.7.12-arch1-1 (x86_64)
0.859592
= Note: Bluetooth subsystem version 2.22
0.859597
= New Index: 1C:BF:C0:1A:8E:3C (Primary,USB,hci0)
[hci0] 0.859598
= Open Index: 1C:BF:C0:1A:8E:3C
[hci0] 0.859599
= Index Info: 1C:BF:C0:1A:8E:3C (Realtek Semiconductor Corporation)
[hci0] 0.859601
@ MGMT Open: bluetoothd (privileged) version 1.16
{0x0001} 0.859602
@ MGMT Open: btmon (privileged) version 1.16
{0x0002} 0.859625
@ MGMT Command: Start Discovery (0x0023) plen 1
{0x0001} [hci0] 5.188846
Address type: 0x07
BR/EDR
LE Public
LE Random
< HCI Command: LE Set Random Address (0x08|0x0005) plen 6
#1 [hci0] 5.188925
Address: 3E:88:2E:4E:58:6D (Non-Resolvable)
> HCI Event: Command Complete (0x0e) plen 4
> #2 [hci0] 5.302358
LE Set Random Address (0x08|0x0005) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#3 [hci0] 5.302395
Own address type: Random (0x01)
Filter policy: Accept all advertisement (0x00)
PHYs: 0x01
Entry 0: LE 1M
Type: Active (0x01)
Interval: 11.250 msec (0x0012)
Window: 11.250 msec (0x0012)
> HCI Event: Command Complete (0x0e) plen 4
> #4 [hci0] 5.307380
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#5 [hci0] 5.307438
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4
> #6 [hci0] 5.310369
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
@ MGMT Event: Command Complete (0x0001) plen 4
{0x0001} [hci0] 5.310427
Start Discovery (0x0023) plen 1
Status: Success (0x00)
Address type: 0x07
BR/EDR
LE Public
LE Random
@ MGMT Event: Discovering (0x0013) plen 2
{0x0002} [hci0] 5.310439
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Enabled (0x01)
@ MGMT Event: Discovering (0x0013) plen 2
{0x0001} [hci0] 5.310439
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Enabled (0x01)
> HCI Event: LE Meta Event (0x3e) plen 54
> #7 [hci0] 6.257392
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0010
Props: 0x0010
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_NONCONN_IND (0x0010)
Address type: Public (0x00)
Address: 00:C3:F4:13:15:07 (Samsung Electronics Co.,Ltd)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -72 dBm (0xb8)
Periodic advertising invteral: 0.00 msec (0x0000)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1c
1b ff 75 00 42 04 01 80 60 00 c3 f4 13 15 07 02 ..u.B...`.......
c3 f4 13 15 06 01 00 00 00 00 00 00 ............
@ MGMT Event: Device Found (0x0012) plen 42
{0x0002} [hci0] 6.257457
LE Address: 00:C3:F4:13:15:07 (Samsung Electronics Co.,Ltd)
RSSI: -72 dBm (0xb8)
Flags: 0x00000004
Not Connectable
Data length: 28
Company: Samsung Electronics Co. Ltd. (117)
Data: 420401806000c3f413150702c3f413150601000000000000
@ MGMT Event: Device Found (0x0012) plen 42
{0x0001} [hci0] 6.257457
LE Address: 00:C3:F4:13:15:07 (Samsung Electronics Co.,Ltd)
RSSI: -72 dBm (0xb8)
Flags: 0x00000004
Not Connectable
Data length: 28
Company: Samsung Electronics Co. Ltd. (117)
Data: 420401806000c3f413150702c3f413150601000000000000
> HCI Event: LE Meta Event (0x3e) plen 52
> #8 [hci0] 9.000403
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: FE:FD:2D:11:26:FD (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -24 dBm (0xe8)
Periodic advertising invteral: 0.00 msec (0x0000)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
0e 09 48 55 41 57 45 49 20 20 4d 6f 75 73 65 03 ..HUAWEI Mouse.
19 c2 03 02 01 05 03 03 12 18 ..........
> HCI Event: LE Meta Event (0x3e) plen 52
> #9 [hci0] 9.147398
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: FE:FD:2D:11:26:FD (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -16 dBm (0xf0)
Periodic advertising invteral: 0.00 msec (0x0000)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
0e 09 48 55 41 57 45 49 20 20 4d 6f 75 73 65 03 ..HUAWEI Mouse.
19 c2 03 02 01 05 03 03 12 18 ..........
> HCI Event: LE Meta Event (0x3e) plen 52
> #10 [hci0] 9.357399
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: FE:FD:2D:11:26:FD (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -14 dBm (0xf2)
Periodic advertising invteral: 0.00 msec (0x0000)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
0e 09 48 55 41 57 45 49 20 20 4d 6f 75 73 65 03 ..HUAWEI Mouse.
19 c2 03 02 01 05 03 03 12 18 ..........
> HCI Event: LE Meta Event (0x3e) plen 52
> #11 [hci0] 9.567397
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: FE:FD:2D:11:26:FD (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -16 dBm (0xf0)
Periodic advertising invteral: 0.00 msec (0x0000)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
0e 09 48 55 41 57 45 49 20 20 4d 6f 75 73 65 03 ..HUAWEI Mouse.
19 c2 03 02 01 05 03 03 12 18 ..........
> HCI Event: LE Meta Event (0x3e) plen 52
> #12 [hci0] 9.777398
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: FE:FD:2D:11:26:FD (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -10 dBm (0xf6)
Periodic advertising invteral: 0.00 msec (0x0000)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
0e 09 48 55 41 57 45 49 20 20 4d 6f 75 73 65 03 ..HUAWEI Mouse.
19 c2 03 02 01 05 03 03 12 18 ..........
> HCI Event: LE Meta Event (0x3e) plen 52
> #13 [hci0] 9.987376
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: FE:FD:2D:11:26:FD (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -8 dBm (0xf8)
Periodic advertising invteral: 0.00 msec (0x0000)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
0e 09 48 55 41 57 45 49 20 20 4d 6f 75 73 65 03 ..HUAWEI Mouse.
19 c2 03 02 01 05 03 03 12 18 ..........
> HCI Event: LE Meta Event (0x3e) plen 52
> #14 [hci0] 10.197401
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: FE:FD:2D:11:26:FD (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -14 dBm (0xf2)
Periodic advertising invteral: 0.00 msec (0x0000)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
0e 09 48 55 41 57 45 49 20 20 4d 6f 75 73 65 03 ..HUAWEI Mouse.
19 c2 03 02 01 05 03 03 12 18 ..........
> HCI Event: LE Meta Event (0x3e) plen 52
> #15 [hci0] 10.407402
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: FE:FD:2D:11:26:FD (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -12 dBm (0xf4)
Periodic advertising invteral: 0.00 msec (0x0000)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
0e 09 48 55 41 57 45 49 20 20 4d 6f 75 73 65 03 ..HUAWEI Mouse.
19 c2 03 02 01 05 03 03 12 18 ..........
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#16 [hci0] 10.525798
Extended scan: Disabled (0x00)
Filter duplicates: Disabled (0x00)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4
> #17 [hci0] 10.527420
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
@ MGMT Event: Device Found (0x0012) plen 40
{0x0002} [hci0] 10.527479
LE Address: FE:FD:2D:11:26:FD (Static)
RSSI: -12 dBm (0xf4)
Flags: 0x00000000
Data length: 26
Name (complete): HUAWEI Mouse
Appearance: Mouse (0x03c2)
Flags: 0x05
LE Limited Discoverable Mode
BR/EDR Not Supported
16-bit Service UUIDs (complete): 1 entry
Human Interface Device (0x1812)
@ MGMT Event: Device Found (0x0012) plen 40
{0x0001} [hci0] 10.527479
LE Address: FE:FD:2D:11:26:FD (Static)
RSSI: -12 dBm (0xf4)
Flags: 0x00000000
Data length: 26
Name (complete): HUAWEI Mouse
Appearance: Mouse (0x03c2)
Flags: 0x05
LE Limited Discoverable Mode
BR/EDR Not Supported
16-bit Service UUIDs (complete): 1 entry
Human Interface Device (0x1812)
< HCI Command: Inquiry (0x01|0x0001) plen 5
#18 [hci0] 10.527581
Access code: 0x9e8b33 (General Inquiry)
Length: 5.12s (0x04)
Num responses: 0
> HCI Event: Command Status (0x0f) plen 4
> #19 [hci0] 10.530407
Inquiry (0x01|0x0001) ncmd 2
Status: Success (0x00)
> HCI Event: Inquiry Complete (0x01) plen 1
> #20 [hci0] 15.713404
Status: Success (0x00)
@ MGMT Event: Discovering (0x0013) plen 2
{0x0002} [hci0] 15.713434
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Disabled (0x00)
@ MGMT Event: Discovering (0x0013) plen 2
{0x0001} [hci0] 15.713434
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Disabled (0x00)
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 15.737736
LE Address: FE:FD:2D:11:26:FD (Static)
Capability: DisplayYesNo (0x01)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#21 [hci0] 15.737806
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
> #22 [hci0] 15.739428
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#23 [hci0] 15.739490
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4
> #24 [hci0] 15.742444
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
> #25 [hci0] 15.847438
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: FE:FD:2D:11:26:FD (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -40 dBm (0xd8)
Periodic advertising invteral: 0.00 msec (0x0000)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
0e 09 48 55 41 57 45 49 20 20 4d 6f 75 73 65 03 ..HUAWEI Mouse.
19 c2 03 02 01 05 03 03 12 18 ..........
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#26 [hci0] 15.847520
Extended scan: Disabled (0x00)
Filter duplicates: Disabled (0x00)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4
> #27 [hci0] 15.849412
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
< HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26
#28 [hci0] 15.849470
Filter policy: White list is not used (0x00)
Own address type: Public (0x00)
Peer address type: Random (0x01)
Peer address: FE:FD:2D:11:26:FD (Static)
Initiating PHYs: 0x01
Entry 0: LE 1M
Scan interval: 60.000 msec (0x0060)
Scan window: 60.000 msec (0x0060)
Min connection interval: 30.00 msec (0x0018)
Max connection interval: 50.00 msec (0x0028)
Connection latency: 0 (0x0000)
Supervision timeout: 420 msec (0x002a)
Min connection length: 0.000 msec (0x0000)
Max connection length: 0.000 msec (0x0000)
> HCI Event: Command Status (0x0f) plen 4
> #29 [hci0] 15.852531
LE Extended Create Connection (0x08|0x0043) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 31
> #30 [hci0] 16.036426
LE Enhanced Connection Complete (0x0a)
Status: Success (0x00)
Handle: 16
Role: Master (0x00)
Peer address type: Random (0x01)
Peer address: FE:FD:2D:11:26:FD (Static)
Local resolvable private address: 00:00:00:00:00:00 (Non-Resolvable)
Peer resolvable private address: 00:00:00:00:00:00 (Non-Resolvable)
Connection interval: 45.00 msec (0x0024)
Connection latency: 0 (0x0000)
Supervision timeout: 420 msec (0x002a)
Master clock accuracy: 0x00
@ MGMT Event: Device Connected (0x000b) plen 39
{0x0002} [hci0] 16.036500
LE Address: FE:FD:2D:11:26:FD (Static)
Flags: 0x00000000
Data length: 26
Name (complete): HUAWEI Mouse
Appearance: Mouse (0x03c2)
Flags: 0x05
LE Limited Discoverable Mode
BR/EDR Not Supported
16-bit Service UUIDs (complete): 1 entry
Human Interface Device (0x1812)
@ MGMT Event: Device Connected (0x000b) plen 39
{0x0001} [hci0] 16.036500
LE Address: FE:FD:2D:11:26:FD (Static)
Flags: 0x00000000
Data length: 26
Name (complete): HUAWEI Mouse
Appearance: Mouse (0x03c2)
Flags: 0x05
LE Limited Discoverable Mode
BR/EDR Not Supported
16-bit Service UUIDs (complete): 1 entry
Human Interface Device (0x1812)
< HCI Command: LE Read Remote Used Features (0x08|0x0016) plen 2
#31 [hci0] 16.036597
Handle: 16
> HCI Event: Command Status (0x0f) plen 4
> #32 [hci0] 16.038415
LE Read Remote Used Features (0x08|0x0016) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 4
> #33 [hci0] 16.059417
LE Channel Selection Algorithm (0x14)
Handle: 16
Algorithm: #1 (0x00)
> HCI Event: Disconnect Complete (0x05) plen 4
> #34 [hci0] 16.284578
Status: Success (0x00)
Handle: 16
Reason: Connection Failed to be Established (0x3e)
@ MGMT Event: Device Disconnected (0x000c) plen 8
{0x0002} [hci0] 16.284608
LE Address: FE:FD:2D:11:26:FD (Static)
Reason: Unspecified (0x00)
@ MGMT Event: Device Disconnected (0x000c) plen 8
{0x0001} [hci0] 16.284608
LE Address: FE:FD:2D:11:26:FD (Static)
Reason: Unspecified (0x00)
@ MGMT Event: Command Complete (0x0001) plen 10
{0x0001} [hci0] 16.284627
Pair Device (0x0019) plen 7
Status: Failed (0x03)
LE Address: FE:FD:2D:11:26:FD (Static)
@ MGMT Command: Start Discovery (0x0023) plen 1
{0x0001} [hci0] 18.178861
Address type: 0x07
BR/EDR
LE Public
LE Random
< HCI Command: LE Set Random Address (0x08|0x0005) plen 6
#35 [hci0] 18.178943
Address: 19:76:BC:0F:FA:10 (Non-Resolvable)
> HCI Event: Command Complete (0x0e) plen 4
> #36 [hci0] 18.180482
LE Set Random Address (0x08|0x0005) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#37 [hci0] 18.180539
Own address type: Random (0x01)
Filter policy: Accept all advertisement (0x00)
PHYs: 0x01
Entry 0: LE 1M
Type: Active (0x01)
Interval: 11.250 msec (0x0012)
Window: 11.250 msec (0x0012)
> HCI Event: Command Complete (0x0e) plen 4
> #38 [hci0] 18.183465
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#39 [hci0] 18.183520
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4
> #40 [hci0] 18.186452
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
@ MGMT Event: Command Complete (0x0001) plen 4
{0x0001} [hci0] 18.186538
Start Discovery (0x0023) plen 1
Status: Success (0x00)
Address type: 0x07
BR/EDR
LE Public
LE Random
@ MGMT Event: Discovering (0x0013) plen 2
{0x0002} [hci0] 18.186547
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Enabled (0x01)
@ MGMT Event: Discovering (0x0013) plen 2
{0x0001} [hci0] 18.186547
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Enabled (0x01)
@ MGMT Command: Stop Discovery (0x0024) plen 1
{0x0001} [hci0] 19.465795
Address type: 0x07
BR/EDR
LE Public
LE Random
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#41 [hci0] 19.465838
Extended scan: Disabled (0x00)
Filter duplicates: Disabled (0x00)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4
> #42 [hci0] 19.467439
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
@ MGMT Event: Command Complete (0x0001) plen 4
{0x0001} [hci0] 19.467508
Stop Discovery (0x0024) plen 1
Status: Success (0x00)
Address type: 0x07
BR/EDR
LE Public
LE Random
@ MGMT Event: Discovering (0x0013) plen 2
{0x0002} [hci0] 19.467526
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Disabled (0x00)
@ MGMT Event: Discovering (0x0013) plen 2
{0x0001} [hci0] 19.467526
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Disabled (0x00)
@ MGMT Command: Stop Discovery (0x0024) plen 1
{0x0001} [hci0] 19.467699
Address type: 0x07
BR/EDR
LE Public
LE Random
@ MGMT Event: Command Complete (0x0001) plen 4
{0x0001} [hci0] 19.467709
Stop Discovery (0x0024) plen 1
Status: Rejected (0x0b)
Address type: 0x07
BR/EDR
LE Public
LE Random
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 19.467757
LE Address: FE:FD:2D:11:26:FD (Static)
Capability: DisplayYesNo (0x01)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#43 [hci0] 19.467802
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
> #44 [hci0] 19.470445
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#45 [hci0] 19.470513
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4
> #46 [hci0] 19.473434
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
> #47 [hci0] 19.587457
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: FE:FD:2D:11:26:FD (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -44 dBm (0xd4)
Periodic advertising invteral: 0.00 msec (0x0000)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
0e 09 48 55 41 57 45 49 20 20 4d 6f 75 73 65 03 ..HUAWEI Mouse.
19 c2 03 02 01 05 03 03 12 18 ..........
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#48 [hci0] 19.587536
Extended scan: Disabled (0x00)
Filter duplicates: Disabled (0x00)
Duration: 0 msec (0x0000)
Period: 0.00 sec (0x0000)
> HCI Event: Command Complete (0x0e) plen 4
> #49 [hci0] 19.589453
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
< HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26
#50 [hci0] 19.589492
Filter policy: White list is not used (0x00)
Own address type: Public (0x00)
Peer address type: Random (0x01)
Peer address: FE:FD:2D:11:26:FD (Static)
Initiating PHYs: 0x01
Entry 0: LE 1M
Scan interval: 60.000 msec (0x0060)
Scan window: 60.000 msec (0x0060)
Min connection interval: 30.00 msec (0x0018)
Max connection interval: 50.00 msec (0x0028)
Connection latency: 0 (0x0000)
Supervision timeout: 420 msec (0x002a)
Min connection length: 0.000 msec (0x0000)
Max connection length: 0.000 msec (0x0000)
> HCI Event: Command Status (0x0f) plen 4
> #51 [hci0] 19.592524
LE Extended Create Connection (0x08|0x0043) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 31
> #52 [hci0] 19.798455
LE Enhanced Connection Complete (0x0a)
Status: Success (0x00)
Handle: 16
Role: Master (0x00)
Peer address type: Random (0x01)
Peer address: FE:FD:2D:11:26:FD (Static)
Local resolvable private address: 00:00:00:00:00:00 (Non-Resolvable)
Peer resolvable private address: 00:00:00:00:00:00 (Non-Resolvable)
Connection interval: 45.00 msec (0x0024)
Connection latency: 0 (0x0000)
Supervision timeout: 420 msec (0x002a)
Master clock accuracy: 0x00
@ MGMT Event: Device Connected (0x000b) plen 39
{0x0002} [hci0] 19.798500
LE Address: FE:FD:2D:11:26:FD (Static)
Flags: 0x00000000
Data length: 26
Name (complete): HUAWEI Mouse
Appearance: Mouse (0x03c2)
Flags: 0x05
LE Limited Discoverable Mode
BR/EDR Not Supported
16-bit Service UUIDs (complete): 1 entry
Human Interface Device (0x1812)
@ MGMT Event: Device Connected (0x000b) plen 39
{0x0001} [hci0] 19.798500
LE Address: FE:FD:2D:11:26:FD (Static)
Flags: 0x00000000
Data length: 26
Name (complete): HUAWEI Mouse
Appearance: Mouse (0x03c2)
Flags: 0x05
LE Limited Discoverable Mode
BR/EDR Not Supported
16-bit Service UUIDs (complete): 1 entry
Human Interface Device (0x1812)
< HCI Command: LE Read Remote Used Features (0x08|0x0016) plen 2
#53 [hci0] 19.798601
Handle: 16
> HCI Event: Command Status (0x0f) plen 4
> #54 [hci0] 19.800437
LE Read Remote Used Features (0x08|0x0016) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 4
> #55 [hci0] 19.826470
LE Channel Selection Algorithm (0x14)
Handle: 16
Algorithm: #1 (0x00)
> HCI Event: Disconnect Complete (0x05) plen 4
> #56 [hci0] 20.051518
Status: Success (0x00)
Handle: 16
Reason: Connection Failed to be Established (0x3e)
@ MGMT Event: Device Disconnected (0x000c) plen 8
{0x0002} [hci0] 20.051576
LE Address: FE:FD:2D:11:26:FD (Static)
Reason: Unspecified (0x00)
@ MGMT Event: Device Disconnected (0x000c) plen 8
{0x0001} [hci0] 20.051576
LE Address: FE:FD:2D:11:26:FD (Static)
Reason: Unspecified (0x00)
@ MGMT Event: Command Complete (0x0001) plen 10
{0x0001} [hci0] 20.051594
Pair Device (0x0019) plen 7
Status: Failed (0x03)
LE Address: FE:FD:2D:11:26:FD (Static)
P.S.: Please help and fix it! Mouse used bluetooth 4.0 low energy
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
@ 2020-10-04 13:41 ` bugzilla-daemon
2020-10-11 6:51 ` bugzilla-daemon
` (31 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-04 13:41 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
julian@blk9.net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |julian@blk9.net
--- Comment #3 from julian@blk9.net ---
This problem is affecting multiple users on ubuntu:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887968
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
2020-10-04 13:41 ` [Bug 208965] " bugzilla-daemon
@ 2020-10-11 6:51 ` bugzilla-daemon
2020-10-21 18:14 ` bugzilla-daemon
` (30 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-11 6:51 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #4 from Jonathan L. Komar (komar.jonathan@gmail.com) ---
Huawei Matebook 13 2020 AMD running the 5.8.13-zen1-2-zen kernel on Arch Linux.
Same problem. I added myself to the mailing list.
RTL8822CE 802.11ac PCIe Wireless Network Adapter
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
2020-10-04 13:41 ` [Bug 208965] " bugzilla-daemon
2020-10-11 6:51 ` bugzilla-daemon
@ 2020-10-21 18:14 ` bugzilla-daemon
2020-10-23 9:50 ` bugzilla-daemon
` (29 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-21 18:14 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
david.zakarias@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |david.zakarias@gmail.com
--- Comment #6 from david.zakarias@gmail.com ---
Same problem here on Redmibook 16, RTL8822CE, with Microsoft Modern Mobile
Mouse.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (2 preceding siblings ...)
2020-10-21 18:14 ` bugzilla-daemon
@ 2020-10-23 9:50 ` bugzilla-daemon
2020-10-23 9:52 ` bugzilla-daemon
` (28 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-23 9:50 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #7 from julian@blk9.net ---
On my machine (Huawei Matebook 13 2020 AMD), the btrtl driver does not seem to
be used at all (btusb is used instead). The bluetooth device seem to use the
1358:c123 USB identifiers which are not listed in the blacklist table of
drivers/bluetooth/btusb.c. Could this be the problem ?
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (3 preceding siblings ...)
2020-10-23 9:50 ` bugzilla-daemon
@ 2020-10-23 9:52 ` bugzilla-daemon
2020-10-23 22:00 ` bugzilla-daemon
` (27 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-23 9:52 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #8 from julian@blk9.net ---
Note that other RTL8822CE devices with different USB vendor/device IDs are
present in the blacklist table.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (4 preceding siblings ...)
2020-10-23 9:52 ` bugzilla-daemon
@ 2020-10-23 22:00 ` bugzilla-daemon
2020-10-24 7:49 ` bugzilla-daemon
` (26 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-23 22:00 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #9 from julian@blk9.net ---
I've patched my kernel to add the missing USB identifier and that seem to have
solved the issue. I can now properly pair with a bluetooth mouse.
My dmesg now shows firmware files being loaded for the device:
[ 5.909847] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000c
lmp_ver=0
a lmp_subver=8822
[ 5.912751] Bluetooth: hci0: RTL: rom_version status=0 version=3
[ 5.912754] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_fw.bin
[ 5.918147] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_config.bin
[ 5.918282] Bluetooth: hci0: RTL: cfg_sz 6, total sz 31422
What's the right way to go about this ? Should I submit my patch upstream ?
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (5 preceding siblings ...)
2020-10-23 22:00 ` bugzilla-daemon
@ 2020-10-24 7:49 ` bugzilla-daemon
2020-10-24 9:02 ` bugzilla-daemon
` (25 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-24 7:49 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #10 from david.zakarias@gmail.com ---
My device ID as shown by lsusb:
Bus 001 Device 002: ID 0cb5:c547 Realtek Bluetooth Radio
Both btusb and btrtl is loaded but I do not see the rtl8822 firmware being
loaded in the dmesg output.
The wifi part of the chip works fine.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (6 preceding siblings ...)
2020-10-24 7:49 ` bugzilla-daemon
@ 2020-10-24 9:02 ` bugzilla-daemon
2020-10-24 17:34 ` bugzilla-daemon
` (24 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-24 9:02 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #11 from julian@blk9.net ---
I’ve submitted this patch to the linux-bluetooth mailing list:
https://patchwork.kernel.org/project/bluetooth/patch/20201023231748.56519-1-julian@pidancet.net/
David, i suggest you try to apply the same patch to your system, changing the
USB IDs to what you’re seeing, and see if that solves your issue.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (7 preceding siblings ...)
2020-10-24 9:02 ` bugzilla-daemon
@ 2020-10-24 17:34 ` bugzilla-daemon
2020-10-25 12:47 ` bugzilla-daemon
` (23 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-24 17:34 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #12 from Vladislav Smirnov (beluckydaf@gmail.com) ---
(In reply to julian from comment #11)
> I’ve submitted this patch to the linux-bluetooth mailing list:
> https://patchwork.kernel.org/project/bluetooth/patch/20201023231748.56519-1-
> julian@pidancet.net/
>
> David, i suggest you try to apply the same patch to your system, changing
> the USB IDs to what you’re seeing, and see if that solves your issue.
This is indeed the solution. Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (8 preceding siblings ...)
2020-10-24 17:34 ` bugzilla-daemon
@ 2020-10-25 12:47 ` bugzilla-daemon
2020-10-25 14:11 ` bugzilla-daemon
` (22 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-25 12:47 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #13 from david.zakarias@gmail.com ---
I tried what Julian did, but things do not work.
hciconfig hci0 shows:
hci0: Type: Primary Bus: USB
BD Address: 80:30:49:1B:82:2C ACL MTU: 1021:6 SCO MTU: 255:12
DOWN
RX bytes:2068 acl:0 sco:0 events:189 errors:0
TX bytes:32660 acl:0 sco:0 commands:189 errors:0
If I start btmon, and do sudo hciconfig hci0 up, there's a huge amount of
output, and an error at the end:
< HCI Command: LE Clear White List (0x08|0x0010) plen 0 #59 [hci0] 38.597768
> HCI Event: Command Complete (0x0e) plen 4 #60 [hci0] 38.599898
LE Clear White List (0x08|0x0010) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Resolvable P.. (0x08|0x002e) plen 2 #61 [hci0] 38.600001
Timeout: 900 seconds
> HCI Event: Command Complete (0x0e) plen 4 #62 [hci0] 38.601954
LE Set Resolvable Private Address Timeout (0x08|0x002e) ncmd 2
Status: Unsupported Remote Feature / Unsupported LMP Feature (0x1a)
I'm stuck, any ideas?
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (9 preceding siblings ...)
2020-10-25 12:47 ` bugzilla-daemon
@ 2020-10-25 14:11 ` bugzilla-daemon
2020-10-25 17:02 ` bugzilla-daemon
` (21 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-25 14:11 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #16 from david.zakarias@gmail.com ---
Also, in a sense the patch worked, as the firmware is now loaded on boot. But
that's the only positive thing about it, as no (remote) devices are visible and
it's impossible to bring hci0 up because of the error above.
Without the patch, the firmware is not loaded, remote devices ARE visible, but
when I try connecting, it disconnects instantly, same
org.bluez.Error.AuthenticationCanceled error as what OP is seeing.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (10 preceding siblings ...)
2020-10-25 14:11 ` bugzilla-daemon
@ 2020-10-25 17:02 ` bugzilla-daemon
2020-10-26 8:37 ` bugzilla-daemon
` (20 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-25 17:02 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #17 from fakecop (fakecop@yandex.ru) ---
(In reply to julian from comment #11)
> I’ve submitted this patch to the linux-bluetooth mailing list:
> https://patchwork.kernel.org/project/bluetooth/patch/20201023231748.56519-1-
> julian@pidancet.net/
>
> David, i suggest you try to apply the same patch to your system, changing
> the USB IDs to what you’re seeing, and see if that solves your issue.
Hi, Julian, help me pls, how to apply your patch?
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (11 preceding siblings ...)
2020-10-25 17:02 ` bugzilla-daemon
@ 2020-10-26 8:37 ` bugzilla-daemon
2020-10-27 8:34 ` bugzilla-daemon
` (19 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-26 8:37 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #19 from Niklas Frank (niklas97.nf@googlemail.com) ---
(In reply to david.zakarias from comment #13)
> I tried what Julian did, but things do not work.
>
> hciconfig hci0 shows:
>
> hci0: Type: Primary Bus: USB
> BD Address: 80:30:49:1B:82:2C ACL MTU: 1021:6 SCO MTU: 255:12
> DOWN
> RX bytes:2068 acl:0 sco:0 events:189 errors:0
> TX bytes:32660 acl:0 sco:0 commands:189 errors:0
>
> If I start btmon, and do sudo hciconfig hci0 up, there's a huge amount of
> output, and an error at the end:
>
> < HCI Command: LE Clear White List (0x08|0x0010) plen 0 #59 [hci0]
> 38.597768
> > HCI Event: Command Complete (0x0e) plen 4 #60 [hci0]
> 38.599898
> LE Clear White List (0x08|0x0010) ncmd 2
> Status: Success (0x00)
> < HCI Command: LE Set Resolvable P.. (0x08|0x002e) plen 2 #61 [hci0]
> 38.600001
> Timeout: 900 seconds
> > HCI Event: Command Complete (0x0e) plen 4 #62 [hci0]
> 38.601954
> LE Set Resolvable Private Address Timeout (0x08|0x002e) ncmd 2
> Status: Unsupported Remote Feature / Unsupported LMP Feature (0x1a)
>
>
> I'm stuck, any ideas?
Hi,
I got a similar error.
I have a Huawei Matebook 14 2020 with Ryzen 4600H and the same RTL8822CE.
lsusb shows the following:
Bus 003 Device 002: ID 1358:c123 Realtek Bluetooth Radio
I applied Julians Kernel patch and can see that the firmware is loaded during
boot, but bluez does not detect the controller.
dmesg | grep -i bluetooth:
[ 1.720939] usb 3-3: Product: Bluetooth Radio
[ 3.962354] Bluetooth: Core ver 2.22
[ 3.962376] Bluetooth: HCI device and connection manager initialized
[ 3.962380] Bluetooth: HCI socket layer initialized
[ 3.962382] Bluetooth: L2CAP socket layer initialized
[ 3.962385] Bluetooth: SCO socket layer initialized
[ 4.091974] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000c
lmp_ver=0a lmp_subver=8822
[ 4.093982] Bluetooth: hci0: RTL: rom_version status=0 version=3
[ 4.093985] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_fw.bin
[ 4.094858] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_config.bin
[ 4.094926] Bluetooth: hci0: RTL: cfg_sz 6, total sz 31422
[ 4.196048] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 4.196051] Bluetooth: BNEP filters: protocol multicast
[ 4.196057] Bluetooth: BNEP socket layer initialized
[ 4.371968] Bluetooth: hci0: RTL: fw version 0x09993aa1
Trying to bring the device up via 'hciconfig hci0 up' gives me the following
error message:
Can't init device hci0: Protocol not supported (93)`
Does anyone have any Ideas what I can do to get this working?
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (12 preceding siblings ...)
2020-10-26 8:37 ` bugzilla-daemon
@ 2020-10-27 8:34 ` bugzilla-daemon
2020-10-27 8:58 ` bugzilla-daemon
` (18 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-27 8:34 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #23 from Niklas Frank (niklas97.nf@googlemail.com) ---
Too bad..
As you, Julian, are the one who has been able to fix the problem for at least
some people, do you have any Idea what David and I might try out to get
Bluetooth working for our devices as well?
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (13 preceding siblings ...)
2020-10-27 8:34 ` bugzilla-daemon
@ 2020-10-27 8:58 ` bugzilla-daemon
2020-10-27 16:39 ` bugzilla-daemon
` (17 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-27 8:58 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #24 from julian@blk9.net ---
I must admit I am clueless...
We should probably start by comparing Laptop models and distro used to see if a
pattern emerges.
I’m running Ubuntu 20.04 on a Huawei Matebook 13 AMD 2020 laptop. I’ve applied
my patch on top of the 5.4.0 Ubuntu kernel
(linux-image-unsigned-5.4.0-52-generic). I’m happy to share the .deb files if
someone wants to give it a try.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (14 preceding siblings ...)
2020-10-27 8:58 ` bugzilla-daemon
@ 2020-10-27 16:39 ` bugzilla-daemon
2020-10-28 12:56 ` bugzilla-daemon
` (16 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-27 16:39 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
Edward Vear (edwardvear@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |edwardvear@gmail.com
--- Comment #25 from Edward Vear (edwardvear@gmail.com) ---
(In reply to david.zakarias from comment #20)
> Is it possible that a newer firmware fixes the problem? I also have version
> 0x09993aa1.
> Julian what version do you have?
Hi David,
I ran into the same Set Resolvable Private Address error with my adapter, an
rtl8761b. I submitted a patch here with my understanding of the issue:
https://marc.info/?l=linux-bluetooth&m=160378222632366&w=2. Could you check to
see if that patch helps?
I don't believe it is related to the original issue seen in this thread though.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (15 preceding siblings ...)
2020-10-27 16:39 ` bugzilla-daemon
@ 2020-10-28 12:56 ` bugzilla-daemon
2020-10-28 14:47 ` bugzilla-daemon
` (15 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-28 12:56 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #28 from waffen03@gmail.com ---
(In reply to Edward Vear from comment #25)
> (In reply to david.zakarias from comment #20)
> > Is it possible that a newer firmware fixes the problem? I also have version
> > 0x09993aa1.
> > Julian what version do you have?
>
> Hi David,
>
> I ran into the same Set Resolvable Private Address error with my adapter, an
> rtl8761b. I submitted a patch here with my understanding of the issue:
> https://marc.info/?l=linux-bluetooth&m=160378222632366&w=2. Could you check
> to see if that patch helps?
>
> I don't believe it is related to the original issue seen in this thread
> though.
I had the same problem, patch worked for me. Thank you! Can confirm it now
works on 5.9.1.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (16 preceding siblings ...)
2020-10-28 12:56 ` bugzilla-daemon
@ 2020-10-28 14:47 ` bugzilla-daemon
2020-10-28 20:37 ` bugzilla-daemon
` (14 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-28 14:47 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #29 from Niklas Frank (niklas97.nf@googlemail.com) ---
(In reply to Edward Vear from comment #25)
> (In reply to david.zakarias from comment #20)
> > Is it possible that a newer firmware fixes the problem? I also have version
> > 0x09993aa1.
> > Julian what version do you have?
>
> Hi David,
>
> I ran into the same Set Resolvable Private Address error with my adapter, an
> rtl8761b. I submitted a patch here with my understanding of the issue:
> https://marc.info/?l=linux-bluetooth&m=160378222632366&w=2. Could you check
> to see if that patch helps?
>
> I don't believe it is related to the original issue seen in this thread
> though.
Thanks alot! I am now able to connect to my Bluetooth mouse!
Although I notice that the bluetooth adapter still behaves weird. It sometimes
simply stops working and I have to unload and load the `btusb` kernel module to
get the adapter working again.
As for Distro/Kernel Version: I am using Manjaro and I have applied the patches
on top of Kernel 5.9.3
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (17 preceding siblings ...)
2020-10-28 14:47 ` bugzilla-daemon
@ 2020-10-28 20:37 ` bugzilla-daemon
2020-10-28 21:56 ` bugzilla-daemon
` (13 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-28 20:37 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #30 from fakecop (fakecop@yandex.ru) ---
(In reply to Niklas Frank from comment #29)
> (In reply to Edward Vear from comment #25)
> > (In reply to david.zakarias from comment #20)
> > > Is it possible that a newer firmware fixes the problem? I also have
> version
> > > 0x09993aa1.
> > > Julian what version do you have?
> >
> > Hi David,
> >
> > I ran into the same Set Resolvable Private Address error with my adapter,
> an
> > rtl8761b. I submitted a patch here with my understanding of the issue:
> > https://marc.info/?l=linux-bluetooth&m=160378222632366&w=2. Could you check
> > to see if that patch helps?
> >
> > I don't believe it is related to the original issue seen in this thread
> > though.
>
> Thanks alot! I am now able to connect to my Bluetooth mouse!
>
> Although I notice that the bluetooth adapter still behaves weird. It
> sometimes simply stops working and I have to unload and load the `btusb`
> kernel module to get the adapter working again.
>
> As for Distro/Kernel Version: I am using Manjaro and I have applied the
> patches on top of Kernel 5.9.3
Hi, please tell me how you managed to apply the patch??
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (18 preceding siblings ...)
2020-10-28 20:37 ` bugzilla-daemon
@ 2020-10-28 21:56 ` bugzilla-daemon
2020-10-29 7:16 ` bugzilla-daemon
` (12 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-28 21:56 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #31 from waffen03@gmail.com ---
(In reply to fakecop from comment #30)
> (In reply to Niklas Frank from comment #29)
> > (In reply to Edward Vear from comment #25)
> > > (In reply to david.zakarias from comment #20)
> > > > Is it possible that a newer firmware fixes the problem? I also have
> > version
> > > > 0x09993aa1.
> > > > Julian what version do you have?
> > >
> > > Hi David,
> > >
> > > I ran into the same Set Resolvable Private Address error with my adapter,
> > an
> > > rtl8761b. I submitted a patch here with my understanding of the issue:
> > > https://marc.info/?l=linux-bluetooth&m=160378222632366&w=2. Could you
> check
> > > to see if that patch helps?
> > >
> > > I don't believe it is related to the original issue seen in this thread
> > > though.
> >
> > Thanks alot! I am now able to connect to my Bluetooth mouse!
> >
> > Although I notice that the bluetooth adapter still behaves weird. It
> > sometimes simply stops working and I have to unload and load the `btusb`
> > kernel module to get the adapter working again.
> >
> > As for Distro/Kernel Version: I am using Manjaro and I have applied the
> > patches on top of Kernel 5.9.3
>
> Hi, please tell me how you managed to apply the patch??
> Thanks
You need the source code to compile a modified kernel. If you have it you could
just go in and edit the file in question manually (net/bluetooth/hci_core.c) or
apply the patch with the patch command if you find it easier.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (19 preceding siblings ...)
2020-10-28 21:56 ` bugzilla-daemon
@ 2020-10-29 7:16 ` bugzilla-daemon
2020-11-09 16:55 ` bugzilla-daemon
` (11 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-10-29 7:16 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #32 from Niklas Frank (niklas97.nf@googlemail.com) ---
(In reply to fakecop from comment #30)
> (In reply to Niklas Frank from comment #29)
> > (In reply to Edward Vear from comment #25)
> > > (In reply to david.zakarias from comment #20)
> > > > Is it possible that a newer firmware fixes the problem? I also have
> > version
> > > > 0x09993aa1.
> > > > Julian what version do you have?
> > >
> > > Hi David,
> > >
> > > I ran into the same Set Resolvable Private Address error with my adapter,
> > an
> > > rtl8761b. I submitted a patch here with my understanding of the issue:
> > > https://marc.info/?l=linux-bluetooth&m=160378222632366&w=2. Could you
> check
> > > to see if that patch helps?
> > >
> > > I don't believe it is related to the original issue seen in this thread
> > > though.
> >
> > Thanks alot! I am now able to connect to my Bluetooth mouse!
> >
> > Although I notice that the bluetooth adapter still behaves weird. It
> > sometimes simply stops working and I have to unload and load the `btusb`
> > kernel module to get the adapter working again.
> >
> > As for Distro/Kernel Version: I am using Manjaro and I have applied the
> > patches on top of Kernel 5.9.3
>
> Hi, please tell me how you managed to apply the patch??
> Thanks
Hi,
are you on Manjaro as well?
As Julian already said, there is information available online on how to compile
your specific distros kernel. Just do a quick google search, read the
instructions, make sure you understand what the commands are doing, and follow
the steps.
If you are on manjaro as well, have a look at the following forum post:
https://forum.manjaro.org/t/how-to-compile-patch-kernel-with-custom-alsa-driver/20326
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (20 preceding siblings ...)
2020-10-29 7:16 ` bugzilla-daemon
@ 2020-11-09 16:55 ` bugzilla-daemon
2020-11-21 15:18 ` bugzilla-daemon
` (10 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-11-09 16:55 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #34 from fakecop (fakecop@yandex.ru) ---
Thanks very match, sorry my bad English.
I am used arch linux and my mouse work now!!
1). I'm download source code linux (version 5.9.6)
2). Insert in PKGBUILD two patchs: onw from julian and two from Edward (thanks
guys, good job)
3). Build kernel and install.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (21 preceding siblings ...)
2020-11-09 16:55 ` bugzilla-daemon
@ 2020-11-21 15:18 ` bugzilla-daemon
2020-11-26 18:44 ` bugzilla-daemon
` (9 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-11-21 15:18 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
Francois B (Makoto) (francois@makotonoblog.be) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |francois@makotonoblog.be
--- Comment #38 from Francois B (Makoto) (francois@makotonoblog.be) ---
(In reply to julian from comment #24)
> I must admit I am clueless...
>
> We should probably start by comparing Laptop models and distro used to see
> if a pattern emerges.
>
> I’m running Ubuntu 20.04 on a Huawei Matebook 13 AMD 2020 laptop. I’ve
> applied my patch on top of the 5.4.0 Ubuntu kernel
> (linux-image-unsigned-5.4.0-52-generic). I’m happy to share the .deb files
> if someone wants to give it a try.
It could be great if you can share your deb file. Thanks a lot :)
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (22 preceding siblings ...)
2020-11-21 15:18 ` bugzilla-daemon
@ 2020-11-26 18:44 ` bugzilla-daemon
2020-11-28 18:59 ` bugzilla-daemon
` (8 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-11-26 18:44 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
Steeve McCauley (steeve.mccauley@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |steeve.mccauley@gmail.com
--- Comment #39 from Steeve McCauley (steeve.mccauley@gmail.com) ---
Also confirming that the patch works for the realtek 8761b usb bluetooth
adaptor, on all 5.9.x kernels I've patched and tested, including some fedora
kernels,
cd
~/rpmbuild/BUILD/kernel-5.9.fc32/linux-5.9.8-100.fc32.x86_64/net/bluetooth/
$ diff -u hci_core.c~ hci_core.c
--- hci_core.c~ 2020-11-17 16:36:11.387834274 -0500
+++ hci_core.c 2020-11-26 06:35:22.422411928 -0500
@@ -763,7 +763,7 @@
hci_req_add(req, HCI_OP_LE_CLEAR_RESOLV_LIST, 0, NULL);
}
- if (hdev->commands[35] & 0x40) {
+ if (hdev->commands[35] & 0x04) {
__le16 rpa_timeout = cpu_to_le16(hdev->rpa_timeout);
/* Set RPA timeout */
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (23 preceding siblings ...)
2020-11-26 18:44 ` bugzilla-daemon
@ 2020-11-28 18:59 ` bugzilla-daemon
2020-12-02 14:05 ` bugzilla-daemon
` (7 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-11-28 18:59 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #40 from devsk (funtoos@yahoo.com) ---
(In reply to Steeve McCauley from comment #39)
> Also confirming that the patch works for the realtek 8761b usb bluetooth
> adaptor, on all 5.9.x kernels I've patched and tested, including some fedora
> kernels,
>
> cd
> ~/rpmbuild/BUILD/kernel-5.9.fc32/linux-5.9.8-100.fc32.x86_64/net/bluetooth/
> $ diff -u hci_core.c~ hci_core.c
> --- hci_core.c~ 2020-11-17 16:36:11.387834274 -0500
> +++ hci_core.c 2020-11-26 06:35:22.422411928 -0500
> @@ -763,7 +763,7 @@
> hci_req_add(req, HCI_OP_LE_CLEAR_RESOLV_LIST, 0, NULL);
> }
>
> - if (hdev->commands[35] & 0x40) {
> + if (hdev->commands[35] & 0x04) {
> __le16 rpa_timeout = cpu_to_le16(hdev->rpa_timeout);
>
> /* Set RPA timeout */
This patch does not resolve the issue of suspend/resume cycle leading to
disconnected USB device and hence requiring reboot to get the bluetooth adapter
back. https://bugzilla.kernel.org/show_bug.cgi?id=210141
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (24 preceding siblings ...)
2020-11-28 18:59 ` bugzilla-daemon
@ 2020-12-02 14:05 ` bugzilla-daemon
2020-12-11 12:00 ` bugzilla-daemon
` (6 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-12-02 14:05 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
Olivier V (forum.viennet@free.fr) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |forum.viennet@free.fr
--- Comment #41 from Olivier V (forum.viennet@free.fr) ---
Bug affects rtl8822cu too (and not only rtl8822ce)
meloli@Asus-A17:~$ lsusb
Bus 005 Device 002: ID 13d3:3548 IMC Networks Bluetooth Radio
Bug report for this device here :
https://bugzilla.kernel.org/show_bug.cgi?id=210453
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (25 preceding siblings ...)
2020-12-02 14:05 ` bugzilla-daemon
@ 2020-12-11 12:00 ` bugzilla-daemon
2020-12-11 18:44 ` bugzilla-daemon
` (5 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-12-11 12:00 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #43 from Maksim Moskalik (gravelandmp3@yandex.ru) ---
I checked on kernel 5.9.12 Ubuntu 20.04 Huawei amd D13, problem not solved
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (26 preceding siblings ...)
2020-12-11 12:00 ` bugzilla-daemon
@ 2020-12-11 18:44 ` bugzilla-daemon
2020-12-12 1:00 ` bugzilla-daemon
` (4 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-12-11 18:44 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #44 from Olivier V (forum.viennet@free.fr) ---
I'm happy for you and your rtl8822ce firmware...
But still bluetooth not working for rtl8822cu in 5.9.12.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (27 preceding siblings ...)
2020-12-11 18:44 ` bugzilla-daemon
@ 2020-12-12 1:00 ` bugzilla-daemon
2020-12-12 6:24 ` bugzilla-daemon
` (3 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-12-12 1:00 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
Luis (lcarmona@openpartner.cl) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lcarmona@openpartner.cl
--- Comment #45 from Luis (lcarmona@openpartner.cl) ---
Confirmed that worked mixing julian@blk9.net and Edward Vear patches.
I have a Matebook D15 with Elementary OS and kernel 5.9.12 (now patched).
Thanks a lot for all the efforts. Spent several days searching for the
solution.
Regards,
LC
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (28 preceding siblings ...)
2020-12-12 1:00 ` bugzilla-daemon
@ 2020-12-12 6:24 ` bugzilla-daemon
2020-12-12 8:10 ` bugzilla-daemon
` (2 subsequent siblings)
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-12-12 6:24 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #46 from devsk (funtoos@yahoo.com) ---
@Luis: do the patches make it work with suspend-resume cycle? Are you able to
see your bluetooth devices after resuming from suspend?
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (29 preceding siblings ...)
2020-12-12 6:24 ` bugzilla-daemon
@ 2020-12-12 8:10 ` bugzilla-daemon
2020-12-19 19:59 ` bugzilla-daemon
2021-01-11 18:29 ` bugzilla-daemon
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-12-12 8:10 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #47 from Olivier V (forum.viennet@free.fr) ---
Is it necessary to apply the patch myself ?
How to do this (exact steeps) ?
Thank you?
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (30 preceding siblings ...)
2020-12-12 8:10 ` bugzilla-daemon
@ 2020-12-19 19:59 ` bugzilla-daemon
2021-01-11 18:29 ` bugzilla-daemon
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2020-12-19 19:59 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #48 from Olivier V (forum.viennet@free.fr) ---
I bisected the bug on the rtl8822ce here :
https://bugzilla.kernel.org/show_bug.cgi?id=210453
It seems to bee the same problem linked to "rpa".
meloli@Asus-A17:~/Bureau/meloli/GITBISECT/linux$ git bisect bad
b2cc23398e8166b38f8715026273503b081c2a7a is the first bad commit
commit b2cc23398e8166b38f8715026273503b081c2a7a
Author: Sathish Narasimman <nsathish41@gmail.com>
Date: Thu Jul 23 18:09:02 2020 +0530
Bluetooth: Enable RPA Timeout
Enable RPA timeout during bluetooth initialization.
The RPA timeout value is used from hdev, which initialized from
debug_fs
Signed-off-by: Sathish Narasimman <sathish.narasimman@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
include/net/bluetooth/hci.h | 2 ++
net/bluetooth/hci_core.c | 8 ++++++++
2 files changed, 10 insertions(+)
$ git checkout b2cc23398e8166b38f8715026273503b081c2a7a
# give a bad kernel
$ git checkout b2cc23398e8166b38f8715026273503b081c2a7a^
# give a good kernel
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
* [Bug 208965] not working bluetooth mouse low energy rtl8822ce
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
` (31 preceding siblings ...)
2020-12-19 19:59 ` bugzilla-daemon
@ 2021-01-11 18:29 ` bugzilla-daemon
32 siblings, 0 replies; 34+ messages in thread
From: bugzilla-daemon @ 2021-01-11 18:29 UTC (permalink / raw)
To: linux-bluetooth
https://bugzilla.kernel.org/show_bug.cgi?id=208965
--- Comment #58 from Olivier V (forum.viennet@free.fr) ---
Here https://bugzilla.kernel.org/show_bug.cgi?id=210279#c14
Paul Wise said : "Sudip Mukherjee requested inclusion in stable, so it will
likely get into v5.10.6".
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 34+ messages in thread
end of thread, other threads:[~2021-01-11 18:31 UTC | newest]
Thread overview: 34+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-19 20:53 [Bug 208965] New: not working bluetooth mouse low energy rtl8822ce bugzilla-daemon
2020-10-04 13:41 ` [Bug 208965] " bugzilla-daemon
2020-10-11 6:51 ` bugzilla-daemon
2020-10-21 18:14 ` bugzilla-daemon
2020-10-23 9:50 ` bugzilla-daemon
2020-10-23 9:52 ` bugzilla-daemon
2020-10-23 22:00 ` bugzilla-daemon
2020-10-24 7:49 ` bugzilla-daemon
2020-10-24 9:02 ` bugzilla-daemon
2020-10-24 17:34 ` bugzilla-daemon
2020-10-25 12:47 ` bugzilla-daemon
2020-10-25 14:11 ` bugzilla-daemon
2020-10-25 17:02 ` bugzilla-daemon
2020-10-26 8:37 ` bugzilla-daemon
2020-10-27 8:34 ` bugzilla-daemon
2020-10-27 8:58 ` bugzilla-daemon
2020-10-27 16:39 ` bugzilla-daemon
2020-10-28 12:56 ` bugzilla-daemon
2020-10-28 14:47 ` bugzilla-daemon
2020-10-28 20:37 ` bugzilla-daemon
2020-10-28 21:56 ` bugzilla-daemon
2020-10-29 7:16 ` bugzilla-daemon
2020-11-09 16:55 ` bugzilla-daemon
2020-11-21 15:18 ` bugzilla-daemon
2020-11-26 18:44 ` bugzilla-daemon
2020-11-28 18:59 ` bugzilla-daemon
2020-12-02 14:05 ` bugzilla-daemon
2020-12-11 12:00 ` bugzilla-daemon
2020-12-11 18:44 ` bugzilla-daemon
2020-12-12 1:00 ` bugzilla-daemon
2020-12-12 6:24 ` bugzilla-daemon
2020-12-12 8:10 ` bugzilla-daemon
2020-12-19 19:59 ` bugzilla-daemon
2021-01-11 18:29 ` bugzilla-daemon
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.