* Re: [ISSUE] [CLOSED] Enable CONFIG_BT_HCIBTUSB_MTK in package linux5.x
2021-12-15 10:52 [ISSUE] Enable CONFIG_BT_HCIBTUSB_MTK in package linux5.x rubin55
@ 2021-12-16 17:16 ` leahneukirchen
2021-12-20 19:08 ` rubin55
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: leahneukirchen @ 2021-12-16 17:16 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
Closed issue by rubin55 on void-packages repository
https://github.com/void-linux/void-packages/issues/34554
Description:
### System
* xuname:
`Void 5.15.7_1 x86_64 AuthenticAMD notuptodate rF`
* package:
`linux5.15-5.15.7_1`
### Expected behavior
```
cat /boot/config-5.15.7_1 | grep CONFIG_BT_HCIBTUSB_MTK
CONFIG_BT_HCIBTUSB_MTK=m
```
### Actual behavior
```
cat /boot/config-5.15.7_1 | grep CONFIG_BT_HCIBTUSB_MTK
# CONFIG_BT_HCIBTUSB_MTK is not set
```
### Steps to reproduce the behavior
See above. This is simply a feature-request to enable `CONFIG_BT_HCIBTUSB_MTK` so that MediaTek based HCI bluetooth USB controllers start working (encountered this particular controller on my new AMD Ryzen 5850U based ThinkPad P14s).
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Enable CONFIG_BT_HCIBTUSB_MTK in package linux5.x
2021-12-15 10:52 [ISSUE] Enable CONFIG_BT_HCIBTUSB_MTK in package linux5.x rubin55
2021-12-16 17:16 ` [ISSUE] [CLOSED] " leahneukirchen
@ 2021-12-20 19:08 ` rubin55
2021-12-20 19:11 ` leahneukirchen
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: rubin55 @ 2021-12-20 19:08 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
New comment by rubin55 on void-packages repository
https://github.com/void-linux/void-packages/issues/34554#issuecomment-998196430
Comment:
@leahneukirchen Is it possible to enable this also for the older kernels? Specifically I'm thinking about whichever version would have introduced the CONFIG_BT_HCIBTUSB_MTK flag, but at least 5.12, 5.13 and 5.14?
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Enable CONFIG_BT_HCIBTUSB_MTK in package linux5.x
2021-12-15 10:52 [ISSUE] Enable CONFIG_BT_HCIBTUSB_MTK in package linux5.x rubin55
2021-12-16 17:16 ` [ISSUE] [CLOSED] " leahneukirchen
2021-12-20 19:08 ` rubin55
@ 2021-12-20 19:11 ` leahneukirchen
2021-12-20 19:40 ` ericonr
2021-12-22 10:57 ` rubin55
4 siblings, 0 replies; 6+ messages in thread
From: leahneukirchen @ 2021-12-20 19:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 181 bytes --]
New comment by leahneukirchen on void-packages repository
https://github.com/void-linux/void-packages/issues/34554#issuecomment-998198335
Comment:
I wont bump EOL kernels, sorry.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Enable CONFIG_BT_HCIBTUSB_MTK in package linux5.x
2021-12-15 10:52 [ISSUE] Enable CONFIG_BT_HCIBTUSB_MTK in package linux5.x rubin55
` (2 preceding siblings ...)
2021-12-20 19:11 ` leahneukirchen
@ 2021-12-20 19:40 ` ericonr
2021-12-22 10:57 ` rubin55
4 siblings, 0 replies; 6+ messages in thread
From: ericonr @ 2021-12-20 19:40 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 241 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/34554#issuecomment-998216894
Comment:
linux5.12 has already been removed from source repos, and linux5.13 and 5.14 will soon be removed.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Enable CONFIG_BT_HCIBTUSB_MTK in package linux5.x
2021-12-15 10:52 [ISSUE] Enable CONFIG_BT_HCIBTUSB_MTK in package linux5.x rubin55
` (3 preceding siblings ...)
2021-12-20 19:40 ` ericonr
@ 2021-12-22 10:57 ` rubin55
4 siblings, 0 replies; 6+ messages in thread
From: rubin55 @ 2021-12-22 10:57 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
New comment by rubin55 on void-packages repository
https://github.com/void-linux/void-packages/issues/34554#issuecomment-999481844
Comment:
Ok fair enough. For posterity, I ran into an issue when both Bluetooth and Wi-Fi were enabled and thought it was a recent regression in the Linux kernel, hence the wish to have it available in older kernel versions.
Turns out this issue exists on older kernel versions equally. I wrote about the issue here: https://www.reddit.com/r/thinkpad/comments/rkvggg/thinkpad_p14s_gen2_amd_linux_515_mediatek_7961/
TL;DR; if you come here and think you have an issue with `mt7921e` and/or with `btusb`, check your wireless band with `iwconfig wlan0`. If its in the ~2.4Ghz range, you will find that it is very likely conflicting with your bluetooth stack which is also operating within the same range. Quick workaround: make sure you have a Wi-Fi router that can do ~5Ghz and connect your Wi-Fi on the ~5Ghz band, which avoids conflict with your bluetooth stack.
Other drivers (i.e., `iwl2200`) have a `bt_coex` option that seems to avoid this issue. `mt7921e` does not have this option (yet?). I emailed Sean Wang, who is one of the developers at MediaTek who works on `mt7921e` to share my experiences.
^ permalink raw reply [flat|nested] 6+ messages in thread