Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: ax210: Why no 6E channels valid in regdom?
From:   Ben Greear <greearb@candelatech.com>
To:     "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
References: <3b3b53f6-a974-601f-f136-d685c4841647@candelatech.com>
Organization: Candela Technologies
Message-ID: <ee8074e5-dbc9-e70f-1d51-934de9ccdcf1@candelatech.com>
Date:   Sat, 30 Jan 2021 09:09:59 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <3b3b53f6-a974-601f-f136-d685c4841647@candelatech.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-MW
Content-Transfer-Encoding: 8bit
Precedence: bulk

On 1/29/21 2:31 PM, Ben Greear wrote:
> I cannot figure out why my ax210 won't show any 6E channels.  It worked for a bit a few days
> ago, but now it does not..and not sure why.  Looks like it uses some internal regdom.
> 
> Any idea from these logs what is going on?

Is that 'mcc' logic actually able to read the cellular network?  I am near enough to Canada
that sometimes my mobile phone will pick up those towers...could the ax210 possibly be
hearing the same and forcing itself to OO regdom, which would cause it to disable all 6E
channels?

Thanks,
Ben

> 
>   kernel: iwlwifi 0000:0f:00.0: In iwl-mvm-init-mcc, nvm-type: 1  NVM_EXT: 1
>   kernel: iwlwifi 0000:0f:00.0: init-fw-regd: r: 0000000000000000
>   kernel: iwlwifi 0000:0f:00.0: Getting regdomain data for ZZ from FW
>   kernel: iwlwifi 0000:0f:00.0: send MCC update to FW with 'ZZ' src = 16
>   kernel: iwlwifi 0000:0f:00.0: MCC response status: 0x1. new MCC: 0x3030 ('00') n_chans: 110
>   kernel: iwlwifi 0000:0f:00.0: MCC update response version: 6
>   kernel: iwlwifi 0000:0f:00.0: setting alpha2 from FW to 00 (0x30, 0x30) src=7
>   kernel: iwlwifi 0000:0f:00.0: Get current regdom: 000000001caad6b5  mcc-supported: 1
>   kernel: cfg80211: d8:f8:83:35:e9:f9: Disabling freq 2484.000 MHz as custom regd has no rule that fits it
> ....
>   kernel: cfg80211: d8:f8:83:35:e9:f9: Disabling freq 5955.000 MHz as custom regd has no rule that fits it
>   kernel: cfg80211: d8:f8:83:35:e9:f9: Disabling freq 5975.000 MHz as custom regd has no rule that fits it
>   kernel: cfg80211: d8:f8:83:35:e9:f9: Disabling freq 5995.000 MHz as custom regd has no rule that fits it
>   kernel: cfg80211: d8:f8:83:35:e9:f9: Disabling freq 6015.000 MHz as custom regd has no rule that fits it
>   kernel: cfg80211: d8:f8:83:35:e9:f9: Disabling freq 6035.000 MHz as custom regd has no rule that fits it
>   kernel: cfg80211: d8:f8:83:35:e9:f9: Disabling freq 6055.000 MHz as custom regd has no rule that fits it
> 
> Thanks,
> Ben
>