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?
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
--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com
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
>
On 1/30/21 9:09 AM, Ben Greear wrote:
> 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?
Ok, I think I see the pattern now.
You have to admin-up the station and start scanning before it will show the
6E channels in 'iw reg get'. And that makes the 'band 4' frequencies become
usable as well, as seen in 'iw phy foo info'.
So, a bit confusing for me, but I guess it works as intended.
This is with 5.11-rc5+ kernel and latest ax210 FW that I can find.
Thanks,
Ben
>
> 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
>>
>