linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Dave Chiluk <chiluk@ubuntu.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	"Coelho, Luciano" <luciano.coelho@intel.com>,
	"Greenman, Gregory" <gregory.greenman@intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [regression] Bug 216753 - 6e 6 ghz bands are disabled since 5.16 on intel ax211
Date: Fri, 2 Dec 2022 18:46:38 +0100	[thread overview]
Message-ID: <457D8649-B855-43BB-B3AD-334E166FED31@holtmann.org> (raw)
In-Reply-To: <CAMfi-DQfuro4c_VUrFHBTv8sPnwuV8XhTV_W7qswGeCC2t-wzg@mail.gmail.com>

Hi Dave,

> Running
> $ iw reg set US
> or
> $ iw reg set DE
> do not result in the bands becoming enabled.  I should have included
> that in the initial bug report.   Additionally shouldn't the country
> code should be getting gathered through 802.11d from the broadcast APs
> within region?
> 
> Also crda is now disabled in both debian and Ubuntu.
> https://bugs.debian.org/1003903
> https://bugs.launchpad.net/ubuntu/jammy/+source/crda/+bug/1958918
> 
> I'm specifically on 22.04, and the 6ghz band works on the 5.15 ubuntu
> kernel and the 5.15.79 linux-stable kernel.
> The 6ghz band becomes disabled as soon as I upgrade to the 5.16+
> linux-stable kernels. So from a user perspective this really is a case
> of a kernel upgrade breaking user-space.  This is what led me down
> this rabbit hole here.
> 
> If there's something that needs to be done differently from a
> userspace perspective I'm all ears, but this seems as if it's a hard
> disable by the above mentioned commit.

can you run iwd and set Country=DE (or US) in its main.conf. I think
most distros have a 2.0 package of iwd available. With iwd we have
implemented all the handling and re-scanning to make sure we actually
get to use 6Ghz is available.

Btw. you can run iwd from its source tree. No need to install it if
You don’t want to mess up your system. Just make sure to disable
wpa_supplicant so it doesn’t interfere.

I have this working on 6.0 kernel (not with ax211 hardware though) and
it needed some help to get the regdom loaded correctly. I think the key
part was to install crda on Fedora.

$ iw reg get
global
country DE: DFS-ETSI
	(2400 - 2483 @ 40), (N/A, 20), (N/A)
	(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
	(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
	(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
	(5725 - 5875 @ 80), (N/A, 13), (N/A)
	(5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
	(57000 - 66000 @ 2160), (N/A, 40), (N/A)

Unless you see it available in iw reg get, then it is also not available,
but I remember that you also have per PHY regdom and other fun stuff. As
I said, it was a breath to get it running with iwd once you set your
country code in the config file.

On a note, you could run iwmon and see what nl80211 related calls to
regdom handling actually happen.

Regards

Marcel


  parent reply	other threads:[~2022-12-02 17:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01 10:14 [regression] Bug 216753 - 6e 6 ghz bands are disabled since 5.16 on intel ax211 Thorsten Leemhuis
2022-12-01 11:33 ` Coelho, Luciano
2022-12-02 15:37   ` Dave Chiluk
2022-12-02 16:02     ` Thorsten Leemhuis
2022-12-02 16:46       ` Marcel Holtmann
2022-12-02 17:18         ` Dave Chiluk
2022-12-02 17:42           ` Maxime Bizon
2022-12-04  9:37             ` Thorsten Leemhuis
2022-12-20 13:16               ` Maxime Bizon
2023-01-03 19:48               ` Dave Chiluk
2022-12-02 17:46           ` Marcel Holtmann [this message]
2022-12-05 16:35             ` Dave Chiluk
2023-01-03 17:37   ` Dave Chiluk
2023-01-04  8:50     ` Coelho, Luciano
2023-01-05  6:15     ` Greenman, Gregory
2023-01-06 15:37       ` Dave Chiluk
2023-01-19 14:09         ` Greenman, Gregory

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=457D8649-B855-43BB-B3AD-334E166FED31@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=chiluk@ubuntu.com \
    --cc=gregory.greenman@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@intel.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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).