Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
mac80211: add missing config for third 160MHz width for 5GHz radio
Without this configuration it is not possible to run the radio using HE160 on channels 149-177. Fixes: #14906 Signed-off-by: Paweł Owoc <frut3k7@gmail.com>
- Loading branch information
a91b79f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried out this commit on my Xiaomi Redmi AX6000 with
MT7976AN
Unfortunately it doesn't come up at the kernel level. "Could not set channel for kernel driver"
a91b79f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@taylorkline You can try to run every single channel (149, 153, 157, 161, 165, 169, 173 and 177) using
HE20
option and see which one is not supported.a91b79f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@testuser7
169
and above do not show up in LUCI, and setting viauci
and restarting the interface fails:a91b79f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So your adapter probably do not support these frequencies. You can verify this using
iw reg get
command.a91b79f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For
mt76
, support for channels above 165 has not been backported yet: https://patchwork.kernel.org/project/linux-wireless/list/?series=788955&state=*a91b79f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. I'm imagining that hypothetically, I could download
https://patchwork.kernel.org/series/788955/mbox/
And apply to my local build? But I'm not confident enough to risk a brick.
a91b79f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I'm not following. It looks like the series you linked to is merged into openwrt/mt76, e.g.: openwrt/mt76@4a0f839
a91b79f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I forgot that the mt76 driver used is from a separate repository and the changes I mentioned are already applied.
In your case, the problem is probably the
NO-IR
flag. Discussion on this topic: https://forum.openwrt.org/t/new-indoor-5-ghz-channels/156942a91b79f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@testuser7 you seem to be correct, I get better output after setting my
country3
to the indoor flag, as it is an indoor AP:If you don't mind me asking, what is your usecase that allows you to use your device on these channels? You have a non-OpenWrt AP and your OpenWrt device is a client?
a91b79f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@taylorkline
ath11k
based devices use internal regdb and there channels 169-177 are not restricted (bug?):This is what the channels look like for
ath10k
where an external regdb is used:a91b79f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Solid. Thanks!