From: rubin55 <rubin55@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Enable CONFIG_BT_HCIBTUSB_MTK in package linux5.x
Date: Wed, 22 Dec 2021 11:57:39 +0100 [thread overview]
Message-ID: <20211222105739.9PEZiijr32GvyIjjECJuuveR5h5XD2LYcpzNlcgxVwg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34554@inbox.vuxu.org>
[-- 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.
prev parent reply other threads:[~2021-12-22 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 10:52 [ISSUE] " 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 [this message]
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=20211222105739.9PEZiijr32GvyIjjECJuuveR5h5XD2LYcpzNlcgxVwg@z \
--to=rubin55@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).