Bug 210279
| Summary: | Bluetooth regression in kernel 5.9.x for Realtek RTL8822CE | ||
|---|---|---|---|
| Product: | Networking | Reporter: | Mike Cloaked (mike.cloaked) |
| Component: | Wireless | Assignee: | networking_wireless (networking_wireless) |
| Status: | NEW --- | ||
| Severity: | normal | CC: | andy, arsphl, forum.viennet, funtoos, pabs3 |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 5.9.9-arch1-1 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: | Journal log with realtek rtl8822ce bluetooth fail | ||
Created attachment 293781 [details]
Journal log with realtek rtl8822ce bluetooth fail
I saw that another user built a current kernel with the patch at https://marc.info/?l=linux-bluetooth&m=160378222632366&w=2 and has the same Realtek chip now working for bluetooth. Is it known which version of upcoming kernel will have this patch included? Also same issue on recent HP AMD laptop with this chipset, working on 5.8, broken on 5.9 through at least 5.10-rc4 (tried last week) on Fedora. The patch on comment #2 was posted on linux-bluetooth end Oct and didn't seem to get any attention / replies on the ml. One arch linux user has applied the patch in comment #2 and rebuilt his kernel which seems to have fixed it. See https://bbs.archlinux.org/viewtopic.php?pid=1939186#p1939186 so hopefully this patch will get into mainline before long since the bluetooth radio is completely inoperative until the kernel is patched for this chipset. This patch has not been applied to bluetooth next tree - https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/ Thanks for the tip... let's hope we don't have too long to wait... really it needs to go on kernel -stable too since it's broken all through 5.9 and to date on 5.10-rc It got into bluetooth-next: https://marc.info/?l=linux-bluetooth&m=160631527001950&w=2 https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=7c66018139629bfd16fe09b982916cc6c814c8d6 I have a kernel built with the patch included to test my Realtek rtl8822ce radio. [mike@ryzen1 ~]$ uname -r 5.9.11-2-stable Tested bluetooth with this kernel that includes the patch: [mike@ryzen1 ~]$ sudo systemctl start bluetooth [mike@ryzen1 ~]$ bluetoothctl Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# power on [CHG] Controller xx:xx:xx:xx:xx:xx Class: 0x003c0000 Changing power on succeeded [CHG] Controller xx:xx:xx:xx:xx:xx Powered: yes [bluetooth]# So the BT radio now powers on, where previously it would not. After that I was able to pair and connect the bluetooth ear buds, and they work normally with audio. If the patch was included in arch kernel builds until it reaches the upstream released kernel tree, that would help all users running the same chipset to have bluetooth working much earlier. Hopefully the patch will have a short journey from bluetooth-next into mainline. Can someone who has applied the patch and has this adapter working, please suspend and resume, and see if the adapter disappears after resume? I am running into this after applying the patch: https://bugzilla.kernel.org/show_bug.cgi?id=210141 I had the same problem but on rtl8822cu device reported here https://bugzilla.kernel.org/show_bug.cgi?id=210453 I compiled 5.10 kernel downloaded here git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git and applied the patch given here https://marc.info/?l=linux-bluetooth&m=160378222632366&w=2. I works perfectly on my rtl8822cu device, with suspend and resume too. Please add the patch to next kernel. The fix that got into bluetooth-next got into Linxu mainline: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a31489d2a368d2f9225ed6a6f595c63bc7d10de8 Looks like 5.11 will be the first release containing the commit, unless someone requests adding it to stable. Solved in 5.11.0-rc2 Sudip Mukherjee requested inclusion in stable, so it will likely get into v5.10.6 Sudip mentioned it has been queued for Linux v5.10.6 too. Solved in 5.10.6 (installed and tried today). Bug can be marked as solved. *** Bug 210453 has been marked as a duplicate of this bug. *** I have the same issue with v5.11.11 uname -r 5.11.11-100.fc32.x86_64 bluetoothctl Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# power on No default controller available [bluetooth]# exit sudo lspci -knn | grep Net -A3 04:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] Subsystem: Lenovo Device [17aa:b024] Kernel driver in use: rtw_8822be Kernel modules: rtw88_8822be |
Running arch linux, Bluetooth no longer works for the dual wireless/BT card: 01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter DeviceName: WLAN Subsystem: Hewlett-Packard Company Device 85f7 Kernel driver in use: rtw_8822ce Kernel modules: rtw88_8822ce $ sudo systemctl start bluetooth [mike@ryzen1 ~]$ sudo systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: disabled) Active: active (running) since Fri 2020-11-20 12:40:17 GMT; 8s ago Docs: man:bluetoothd(8) Main PID: 4049 (bluetoothd) Status: "Running" Tasks: 1 (limit: 18427) Memory: 1.8M CGroup: /system.slice/bluetooth.service └─4049 /usr/lib/bluetooth/bluetoothd Nov 20 12:40:17 ryzen1 bluetoothd[4049]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowAdvMonitor” in group “Controller” Nov 20 12:40:17 ryzen1 bluetoothd[4049]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalConnect” in group “Controller” Nov 20 12:40:17 ryzen1 bluetoothd[4049]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowConnect” in group “Controller” Nov 20 12:40:17 ryzen1 bluetoothd[4049]: src/main.c:parse_controller_config() Key file does not have key “LEMinConnectionInterval” in group “Controller” Nov 20 12:40:17 ryzen1 bluetoothd[4049]: src/main.c:parse_controller_config() Key file does not have key “LEMaxConnectionInterval” in group “Controller” Nov 20 12:40:17 ryzen1 bluetoothd[4049]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionLatency” in group “Controller” Nov 20 12:40:17 ryzen1 bluetoothd[4049]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionSupervisionTimeout” in group “Controller” Nov 20 12:40:17 ryzen1 bluetoothd[4049]: src/main.c:parse_controller_config() Key file does not have key “LEAutoconnecttimeout” in group “Controller” Nov 20 12:40:17 ryzen1 bluetoothd[4049]: Starting SDP server Nov 20 12:40:17 ryzen1 bluetoothd[4049]: Bluetooth management interface 1.18 initialized $ bluetoothctl Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# power on No default controller available $ lspci -knn | grep Net -A3 01:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter [10ec:c822] DeviceName: WLAN Subsystem: Hewlett-Packard Company Device [103c:85f7] Kernel driver in use: rtw_8822ce There is no apparent way to work around this in order to connect bluetooth devices. and from lspci -knn 01:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter [10ec:c822] DeviceName: WLAN Subsystem: Hewlett-Packard Company Device [103c:85f7] Kernel driver in use: rtw_8822ce Kernel modules: rtw88_8822ce