linux-kernel - Re: [regression] Bug 216753 - 6e 6 ghz bands are disabled since 5.16 on intel ax211

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMfi-DQfuro4c_VUrFHBTv8sPnwuV8XhTV_W7qswGeCC2t-wzg@mail.gmail.com>
Date:   Fri, 2 Dec 2022 11:18:03 -0600
From:   Dave Chiluk <chiluk@...ntu.com>
To:     Marcel Holtmann <marcel@...tmann.org>
Cc:     Thorsten Leemhuis <regressions@...mhuis.info>,
        "Coelho, Luciano" <luciano.coelho@...el.com>,
        "Greenman, Gregory" <gregory.greenman@...el.com>,
        "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
        Johannes Berg <johannes@...solutions.net>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [regression] Bug 216753 - 6e 6 ghz bands are disabled since 5.16
 on intel ax211

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.

Thanks,

On Fri, Dec 2, 2022 at 10:46 AM Marcel Holtmann <marcel@...tmann.org> wrote:
>
> Hi Thorsten,
>
> >> The other possibility is that this is actually a bios bug, as the DSM
> >> is being read out of ACPI.  In which case that would be Dell's fault.
> >
> > Yes and no, but no:
> >
> > A kernel change exposed this problem, hence it doesn't matter if the
> > BIOS is faulty: it's makes it a kernel regression and those are not
> > allowed. For more on this see
> > https://docs.kernel.org/admin-guide/reporting-issues.html
> >
> > That at least would be the normal approach. But the thing is: the legal
> > implications when it comes to things like wifi make this somewhat
> > trickier. :-/
>
> so you need to set your country code first before any of the regulatory
> enabled channels on 6Ghz get used. Otherwise you are stuck in the world
> domain that doesn’t allow 6Ghz at all.
>
> Two choices, either you run iwd and just set Country=DE where this than
> would be persistent; see iwd.config(5). Or you do this via iw reg set DE
> manually. wpa_supplicant has a set_country wrapper, but I don’t see it
> being used anywhere, so I assume you have to do this manually when using
> wpa_supplicant.
>
> And of course tools like crda etc. need to be fully functional to load
> the appropriate regulatory information. Since any 6Ghz operation is
> blocked by default.
>
> Regards
>
> Marcel
>