All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 208965] not working bluetooth mouse low energy rtl8822ce
Date: Mon, 26 Oct 2020 08:37:31 +0000	[thread overview]
Message-ID: <bug-208965-62941-kohn0aEqr5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208965-62941@https.bugzilla.kernel.org/>

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.

  parent reply	other threads:[~2020-10-26  8:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-208965-62941-kohn0aEqr5@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.