Hello! I have AC8260 device in my laptop, and I'm trying to use it for my experiments with wifi. I live in Russia, and accordingly to regulatory database, I should have access to 80Mhz channels and to 5170-5330 and 5650-5730 channels: country RU: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW (5650 - 5730 @ 80), (N/A, 30), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 30), (N/A) (57000 - 66000 @ 2160), (N/A, 40), (N/A) But when I'm starting wpa_supplicant (to set MCC to RU), FW don' allow cannot 80Mhz channels: [ 356.728188] iwlwifi 0000:04:00.0: U iwl_mvm_get_regdomain Getting regdomain data for RU from FW [ 356.728189] iwlwifi 0000:04:00.0: U iwl_mvm_update_mcc send MCC update to FW with 'RU' src = 5 [ 356.728974] iwlwifi 0000:04:00.0: U iwl_mvm_update_mcc MCC response status: 0x0. new MCC: 0x5255 ('RU') change: 1 n_chans: 51 [ 356.728977] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info building regdom for 51 channels [ 356.728979] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 2412 [2.4GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x34b): Ad-Hoc supported [ 356.728981] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 2417 [2.4GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x34b): Ad-Hoc supported [ 356.728982] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 2422 [2.4GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x34b): Ad-Hoc supported [ 356.728984] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 2427 [2.4GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x34b): Ad-Hoc supported [ 356.728985] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 2432 [2.4GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x34b): Ad-Hoc supported [ 356.728986] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 2437 [2.4GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x34b): Ad-Hoc supported [ 356.728987] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 2442 [2.4GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x34b): Ad-Hoc supported [ 356.728989] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 2447 [2.4GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x34b): Ad-Hoc supported [ 356.728990] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 2452 [2.4GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x34b): Ad-Hoc supported [ 356.728991] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 2457 [2.4GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x34b): Ad-Hoc supported [ 356.728993] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 2462 [2.4GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x34b): Ad-Hoc supported [ 356.728994] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 2467 [2.4GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x34b): Ad-Hoc supported [ 356.728995] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 2472 [2.4GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x34b): Ad-Hoc supported [ 356.728997] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 14 Flags 0 [2.4GHz] - No traffic [ 356.728999] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5180 [5.2GHz] VALID WIDE 40MHZ INDOOR_ONLY GO_CONCURRENT (0x3e1): Ad-Hoc not supported [ 356.729001] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5200 [5.2GHz] VALID WIDE 40MHZ INDOOR_ONLY GO_CONCURRENT (0x3e1): Ad-Hoc not supported [ 356.729003] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5220 [5.2GHz] VALID WIDE 40MHZ INDOOR_ONLY GO_CONCURRENT (0x3e1): Ad-Hoc not supported [ 356.729004] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5240 [5.2GHz] VALID WIDE 40MHZ INDOOR_ONLY GO_CONCURRENT (0x3e1): Ad-Hoc not supported [ 356.729005] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5260 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729007] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5280 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729008] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5300 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729009] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5320 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729010] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 68 Flags 0 [5.2GHz] - No traffic [ 356.729011] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 72 Flags 0 [5.2GHz] - No traffic [ 356.729012] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 76 Flags 0 [5.2GHz] - No traffic [ 356.729013] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 80 Flags 0 [5.2GHz] - No traffic [ 356.729014] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 84 Flags 0 [5.2GHz] - No traffic [ 356.729016] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 88 Flags 0 [5.2GHz] - No traffic [ 356.729017] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 92 Flags 0 [5.2GHz] - No traffic [ 356.729017] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 96 Flags 0 [5.2GHz] - No traffic [ 356.729019] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5500 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729020] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5520 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729021] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5540 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729023] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5560 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729024] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5580 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729025] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5600 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729026] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5620 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729028] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5640 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729029] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5660 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729030] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5680 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729031] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5700 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729033] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5720 [5.2GHz] VALID RADAR WIDE 40MHZ (0x311): Ad-Hoc not supported [ 356.729034] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5745 [5.2GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x3cb): Ad-Hoc supported [ 356.729035] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5765 [5.2GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x3cb): Ad-Hoc supported [ 356.729037] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5785 [5.2GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x3cb): Ad-Hoc supported [ 356.729038] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5805 [5.2GHz] VALID ACTIVE WIDE 40MHZ GO_CONCURRENT (0x3cb): Ad-Hoc supported [ 356.729040] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 5825 [5.2GHz] VALID ACTIVE WIDE GO_CONCURRENT (0x1cb): Ad-Hoc supported [ 356.729041] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 169 Flags 0 [5.2GHz] - No traffic [ 356.729042] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 173 Flags 0 [5.2GHz] - No traffic [ 356.729043] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 177 Flags 0 [5.2GHz] - No traffic [ 356.729044] iwlwifi 0000:04:00.0: U iwl_parse_nvm_mcc_info Ch. 181 Flags 0 [5.2GHz] - No traffic [ 356.729046] iwlwifi 0000:04:00.0: U iwl_mvm_get_regdomain setting alpha2 from FW to RU (0x52, 0x55) src=5 [ 1522.856159] cfg80211: Updating information on frequency 2412 MHz with regulatory rule: [ 1522.856160] cfg80211: (2402000 KHz - 2482000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856161] cfg80211: Updating information on frequency 2417 MHz with regulatory rule: [ 1522.856161] cfg80211: (2402000 KHz - 2482000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856162] cfg80211: Updating information on frequency 2422 MHz with regulatory rule: [ 1522.856162] cfg80211: (2402000 KHz - 2482000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856163] cfg80211: Updating information on frequency 2427 MHz with regulatory rule: [ 1522.856164] cfg80211: (2402000 KHz - 2482000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856164] cfg80211: Updating information on frequency 2432 MHz with regulatory rule: [ 1522.856165] cfg80211: (2402000 KHz - 2482000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856166] cfg80211: Updating information on frequency 2437 MHz with regulatory rule: [ 1522.856166] cfg80211: (2402000 KHz - 2482000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856167] cfg80211: Updating information on frequency 2442 MHz with regulatory rule: [ 1522.856167] cfg80211: (2402000 KHz - 2482000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856168] cfg80211: Updating information on frequency 2447 MHz with regulatory rule: [ 1522.856169] cfg80211: (2402000 KHz - 2482000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856169] cfg80211: Updating information on frequency 2452 MHz with regulatory rule: [ 1522.856170] cfg80211: (2402000 KHz - 2482000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856171] cfg80211: Updating information on frequency 2457 MHz with regulatory rule: [ 1522.856171] cfg80211: (2402000 KHz - 2482000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856172] cfg80211: Updating information on frequency 2462 MHz with regulatory rule: [ 1522.856172] cfg80211: (2402000 KHz - 2482000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856173] cfg80211: Updating information on frequency 2467 MHz with regulatory rule: [ 1522.856174] cfg80211: (2402000 KHz - 2482000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856174] cfg80211: Updating information on frequency 2472 MHz with regulatory rule: [ 1522.856175] cfg80211: (2402000 KHz - 2482000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856175] cfg80211: Disabling freq 2484 MHz as custom regd has no rule that fits it [ 1522.856176] cfg80211: Updating information on frequency 5180 MHz with regulatory rule: [ 1522.856177] cfg80211: (5170000 KHz - 5250000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856177] cfg80211: Updating information on frequency 5200 MHz with regulatory rule: [ 1522.856178] cfg80211: (5170000 KHz - 5250000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856179] cfg80211: Updating information on frequency 5220 MHz with regulatory rule: [ 1522.856179] cfg80211: (5170000 KHz - 5250000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856180] cfg80211: Updating information on frequency 5240 MHz with regulatory rule: [ 1522.856180] cfg80211: (5170000 KHz - 5250000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856181] cfg80211: Updating information on frequency 5260 MHz with regulatory rule: [ 1522.856182] cfg80211: (5250000 KHz - 5330000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856183] cfg80211: Updating information on frequency 5280 MHz with regulatory rule: [ 1522.856183] cfg80211: (5250000 KHz - 5330000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856184] cfg80211: Updating information on frequency 5300 MHz with regulatory rule: [ 1522.856184] cfg80211: (5250000 KHz - 5330000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856185] cfg80211: Updating information on frequency 5320 MHz with regulatory rule: [ 1522.856186] cfg80211: (5250000 KHz - 5330000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856186] cfg80211: Disabling freq 5340 MHz as custom regd has no rule that fits it [ 1522.856187] cfg80211: Disabling freq 5360 MHz as custom regd has no rule that fits it [ 1522.856187] cfg80211: Disabling freq 5380 MHz as custom regd has no rule that fits it [ 1522.856188] cfg80211: Disabling freq 5400 MHz as custom regd has no rule that fits it [ 1522.856188] cfg80211: Disabling freq 5420 MHz as custom regd has no rule that fits it [ 1522.856189] cfg80211: Disabling freq 5440 MHz as custom regd has no rule that fits it [ 1522.856189] cfg80211: Disabling freq 5460 MHz as custom regd has no rule that fits it [ 1522.856190] cfg80211: Disabling freq 5480 MHz as custom regd has no rule that fits it [ 1522.856190] cfg80211: Updating information on frequency 5500 MHz with regulatory rule: [ 1522.856191] cfg80211: (5490000 KHz - 5730000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856192] cfg80211: Updating information on frequency 5520 MHz with regulatory rule: [ 1522.856192] cfg80211: (5490000 KHz - 5730000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856193] cfg80211: Updating information on frequency 5540 MHz with regulatory rule: [ 1522.856193] cfg80211: (5490000 KHz - 5730000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856195] cfg80211: Updating information on frequency 5560 MHz with regulatory rule: [ 1522.856195] cfg80211: (5490000 KHz - 5730000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856196] cfg80211: Updating information on frequency 5580 MHz with regulatory rule: [ 1522.856197] cfg80211: (5490000 KHz - 5730000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856197] cfg80211: Updating information on frequency 5600 MHz with regulatory rule: [ 1522.856198] cfg80211: (5490000 KHz - 5730000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856198] cfg80211: Updating information on frequency 5620 MHz with regulatory rule: [ 1522.856199] cfg80211: (5490000 KHz - 5730000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856200] cfg80211: Updating information on frequency 5640 MHz with regulatory rule: [ 1522.856200] cfg80211: (5490000 KHz - 5730000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856201] cfg80211: Updating information on frequency 5660 MHz with regulatory rule: [ 1522.856201] cfg80211: (5490000 KHz - 5730000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856202] cfg80211: Updating information on frequency 5680 MHz with regulatory rule: [ 1522.856203] cfg80211: (5490000 KHz - 5730000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856203] cfg80211: Updating information on frequency 5700 MHz with regulatory rule: [ 1522.856204] cfg80211: (5490000 KHz - 5730000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856204] cfg80211: Updating information on frequency 5720 MHz with regulatory rule: [ 1522.856205] cfg80211: (5490000 KHz - 5730000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856206] cfg80211: Updating information on frequency 5745 MHz with regulatory rule: [ 1522.856206] cfg80211: (5735000 KHz - 5815000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856207] cfg80211: Updating information on frequency 5765 MHz with regulatory rule: [ 1522.856207] cfg80211: (5735000 KHz - 5815000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856208] cfg80211: Updating information on frequency 5785 MHz with regulatory rule: [ 1522.856209] cfg80211: (5735000 KHz - 5815000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856209] cfg80211: Updating information on frequency 5805 MHz with regulatory rule: [ 1522.856210] cfg80211: (5735000 KHz - 5815000 KHz @ 0 KHz, 40000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856211] cfg80211: Updating information on frequency 5825 MHz with regulatory rule: [ 1522.856211] cfg80211: (5815000 KHz - 5835000 KHz @ 0 KHz, 20000 KHz AUTO), (600 mBi, 2200 mBm) [ 1522.856212] cfg80211: Disabling freq 5845 MHz as custom regd has no rule that fits it [ 1522.856212] cfg80211: Disabling freq 5865 MHz as custom regd has no rule that fits it [ 1522.856213] cfg80211: Disabling freq 5885 MHz as custom regd has no rule that fits it [ 1522.856213] cfg80211: Disabling freq 5905 MHz as custom regd has no rule that fits it [ 1582.926542] cfg80211: Verifying active interfaces after reg change iw reg get: phy#2 (self-managed) country RU: DFS-UNSET (2402 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ (5170 - 5250 @ 40), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, PASSIVE-SCAN (5250 - 5330 @ 40), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, PASSIVE-SCAN (5490 - 5730 @ 40), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, PASSIVE-SCAN (5735 - 5815 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ (5815 - 5835 @ 20), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-HT40PLUS, NO-80MHZ, NO-160MHZ Here is what hostapd could get from kernel: Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=20 dBm Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=20 dBm Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=20 dBm Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=20 dBm Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=20 dBm Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=20 dBm Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=20 dBm Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=20 dBm Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=20 dBm Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=20 dBm Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=20 dBm Allowed channel: mode=1 chan=12 freq=2467 MHz max_tx_power=20 dBm Allowed channel: mode=1 chan=13 freq=2472 MHz max_tx_power=20 dBm Allowed channel: mode=2 chan=52 freq=5260 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=56 freq=5280 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=60 freq=5300 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=64 freq=5320 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=100 freq=5500 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=104 freq=5520 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=108 freq=5540 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=112 freq=5560 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=116 freq=5580 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=120 freq=5600 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=124 freq=5620 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=128 freq=5640 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=132 freq=5660 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=136 freq=5680 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=140 freq=5700 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=144 freq=5720 MHz max_tx_power=20 dBm (DFS state = usable) Allowed channel: mode=2 chan=149 freq=5745 MHz max_tx_power=20 dBm Allowed channel: mode=2 chan=153 freq=5765 MHz max_tx_power=20 dBm Allowed channel: mode=2 chan=157 freq=5785 MHz max_tx_power=20 dBm Allowed channel: mode=2 chan=161 freq=5805 MHz max_tx_power=20 dBm Allowed channel: mode=2 chan=165 freq=5825 MHz max_tx_power=20 dBm But I cannot use DFS-usable channels for hostapd, because of DFS-UNSET check in the kernel. When I disabled this check, another error in hostapd appears: wlp4s0: DFS-CAC-START freq=5660 chan=132 sec_chan=1, width=0, seg0=0, seg1=0, cac_time=60s nl80211: Start radar detection (CAC) 5660 MHz (ht_enabled=1, vht_enabled=0, bandwidth=40 MHz, cf1=5670 MHz, cf2=0 MHz) * freq=5660 * vht_enabled=0 * ht_enabled=1 * sec_channel_offset=1 * channel_type=3 nl80211: Failed to start radar detection: -16 (Device or resource busy) Probably this error could be caused by PASSIVE-SCAN status of channel. So, I could use 4 40Mhz channels and one 20Mhz in the whole 5GHz band and I cannot use 80Hz width at all. I have kernel 4.5.0 and fw version 21.302800.0 (I've backported commit from 4.6 to support ucode-21) and here is adapter: [ 60.099012] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
I am confused. You are trying to connect to an AP using those channels, or to make 8260 work in AP mode?
Oh, sorry for this confusion. Actually, it's another problem - this chip is using Dynamic Regulatory, so I cannot set up regulatory using hostapd/iw reg, so I need to start wpa_supplicant first - FM will get the regulatory from other WiFi network (as I understand from "iwl_mvm_update_mcc send MCC update to FW with 'RU' src = 5" line, where 5 is MCC_SOURCE_WIFI). Only after that I could start hostapd. If I don't start wpa_supplicant first, FW will use '00' region, which completely disables 5GHz band. My main interest is AP mode, though.
I am not sure that you should get an update with WIFI source in this case. I'd need to check. I don't know that code very well. Are you actually able to set an AP in 40MHz on A band? Do you achieve this by associating to another AP on the same channel?
I'm able to use AP mode with 149 channel and 40Mhz width. I don't need to associate on the same channel first - actually, I only need to associate once before starting hostapd, to set correct MCC in FW. Here is excerpt from hostapd log for 40MHz on 149 channel: hw vht capab: 0x38071b0, conf vht capab: 0x0 wlp4s0: interface state COUNTRY_UPDATE->HT_SCAN Scan for neighboring BSSes prior to enabling 40 MHz channel 40 MHz affected channel range: [5735,5775] MHz wlp4s0: nl80211: scan request nl80211: Scan frequency 5745 MHz nl80211: Scan frequency 5765 MHz Scan requested (ret=0) - scan timeout 10 seconds Interface initialization will be completed in a callback nl80211: Event message available nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for wlp4s0 wlp4s0: nl80211: Scan trigger wlp4s0: Event SCAN_STARTED (47) received Unknown event 47 nl80211: Event message available nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlp4s0 wlp4s0: nl80211: New scan results available nl80211: Scan included frequencies: 5745 5765 wlp4s0: Event SCAN_RESULTS (3) received nl80211: Received scan results (0 BSSes) HT40: control channel: 149 secondary channel: 153 Completing interface initialization Mode: IEEE 802.11a Channel: 149 Frequency: 5745 MHz DFS 0 channels required radar detection nl80211: Set freq 5745 (ht_enabled=1, vht_enabled=0, bandwidth=40 MHz, cf1=5755 MHz, cf2=0 MHz) * freq=5745 * vht_enabled=0 * ht_enabled=1 * sec_channel_offset=1 * channel_type=3 RATE[0] rate=60 flags=0x1 RATE[1] rate=90 flags=0x0 RATE[2] rate=120 flags=0x1 RATE[3] rate=180 flags=0x0 RATE[4] rate=240 flags=0x1 RATE[5] rate=360 flags=0x0 RATE[6] rate=480 flags=0x0 RATE[7] rate=540 flags=0x0 hostapd_setup_bss(hapd=0x17d5eb0 (wlp4s0), first=1) And here is a iw dev: phy#2 Interface wlp4s0 ifindex 5 wdev 0x200000001 addr a4:34:d9:c2:06:4b ssid test type AP channel 149 (5745 MHz), width: 40 MHz, center1: 5755 MHz So yeah, seems that I could use HT40+ on 149 and 157 channels (even if no neighbour networks support 5GHz)
The same part of log, but for 52 channel, 40MHz (after disabling kernel check for DFS-UNSET): hw vht capab: 0x38071b0, conf vht capab: 0x0 wlp4s0: interface state COUNTRY_UPDATE->HT_SCAN Scan for neighboring BSSes prior to enabling 40 MHz channel 40 MHz affected channel range: [5250,5290] MHz wlp4s0: nl80211: scan request nl80211: Scan frequency 5260 MHz nl80211: Scan frequency 5280 MHz Scan requested (ret=0) - scan timeout 10 seconds Interface initialization will be completed in a callback nl80211: Event message available nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for wlp4s0 wlp4s0: nl80211: Scan trigger wlp4s0: Event SCAN_STARTED (47) received Unknown event 47 nl80211: Event message available nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlp4s0 wlp4s0: nl80211: New scan results available nl80211: Scan included frequencies: 5260 5280 wlp4s0: Event SCAN_RESULTS (3) received nl80211: Received scan results (0 BSSes) HT40: control channel: 52 secondary channel: 56 Completing interface initialization Mode: IEEE 802.11a Channel: 52 Frequency: 5260 MHz DFS 2 channels required radar detection DFS all channels available, (SKIP CAC): no DFS 0 chans unavailable - choose other channel: no wlp4s0: interface state HT_SCAN->DFS DFS start CAC on 5260 MHz wlp4s0: DFS-CAC-START freq=5260 chan=52 sec_chan=1, width=0, seg0=0, seg1=0, cac_time=60s nl80211: Start radar detection (CAC) 5260 MHz (ht_enabled=1, vht_enabled=0, bandwidth=40 MHz, cf1=5270 MHz, cf2=0 MHz) * freq=5260 * vht_enabled=0 * ht_enabled=1 * sec_channel_offset=1 * channel_type=3 nl80211: Failed to start radar detection: -16 (Device or resource busy)
And the same part of logs if I try to use 80Mhz on 149 channel: hw vht capab: 0x38071b0, conf vht capab: 0x10b0 wlp4s0: interface state COUNTRY_UPDATE->HT_SCAN Scan for neighboring BSSes prior to enabling 40 MHz channel 40 MHz affected channel range: [5735,5775] MHz wlp4s0: nl80211: scan request nl80211: Scan frequency 5745 MHz nl80211: Scan frequency 5765 MHz Scan requested (ret=0) - scan timeout 10 seconds Interface initialization will be completed in a callback nl80211: Event message available nl80211: Drv Event 33 (NL80211_CMD_TRIGGER_SCAN) received for wlp4s0 wlp4s0: nl80211: Scan trigger wlp4s0: Event SCAN_STARTED (47) received Unknown event 47 nl80211: Event message available nl80211: Drv Event 34 (NL80211_CMD_NEW_SCAN_RESULTS) received for wlp4s0 wlp4s0: nl80211: New scan results available nl80211: Scan included frequencies: 5745 5765 wlp4s0: Event SCAN_RESULTS (3) received nl80211: Received scan results (0 BSSes) HT40: control channel: 149 secondary channel: 153 Completing interface initialization Mode: IEEE 802.11a Channel: 149 Frequency: 5745 MHz DFS 0 channels required radar detection nl80211: Set freq 5745 (ht_enabled=1, vht_enabled=1, bandwidth=80 MHz, cf1=5775 MHz, cf2=0 MHz) * freq=5745 * vht_enabled=1 * ht_enabled=1 * bandwidth=80 * channel_width=3 * center_freq1=5775 * center_freq2=0 nl80211: Failed to set channel (freq=5745): -22 (Invalid argument) But this one is definitely caused by wrong HW regulatory
Oh, BTW, should I create another bug for inability to set regulatory via iw reg set/hostapd?
After a few inquiries. 80MHz is not supported by our device in Russia. This is hardcoded in the device. Note that we don't support A band operation in AP mode. Closing this bug as invalid.
So, just for clarify things, is 80MHz not supported even for 'managed' mode?
It surely is. But not in AP mode.
Oh, glad to hear, because I started to think how to return my laptop :) Thank you for researching this! One more thing - how this country auto-detect (aka DRS) is working? I suspect that it is using 802.11d, but what if no APs nearby will support this? Or what if I go to USA, where 802.11d is prohibited by FCC?
Sent from my ASUS -------- Original Message -------- From:bugzilla-daemon@bugzilla.kernel.org Sent:Sun, 17 Apr 2016 12:36:20 +0300 To:linuxwifi Subject:[linuxwifi] [Bug 116231] Intel AC-8260 with iwlwifi cannot use 80Mhz channels and DFS in Russia. https://bugzilla.kernel.org/show_bug.cgi?id=116231 --- Comment #11 from Yaroslav Isakov <yaroslav.isakov@gmail.com> --- Oh, glad to hear, because I started to think how to return my laptop :) Thank you for researching this! One more thing - how this country auto-detect (aka DRS) is working? I suspect that it is using 802.11d, but what if no APs nearby will support this? Or what if I go to USA, where 802.11d is prohibited by FCC? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ------------------------------------- linuxwifi@eclists.intel.com https://eclists.intel.com/sympa/info/linuxwifi Unsubscribe by sending email to sympa@eclists.intel.com with subject "Unsubscribe linuxwifi"
Hello, Does this hold for US also? I mean configuring 8260 or 8265 as AP in 5GHz band? Thanks
We don't support AP mode in the 5GHz band, because we don't have a way to detect radar transmissions in order to evacuate the channels...
Luca, what about few channels without DFS? e.g, according to Intel's regulatory for Russia: (2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ (2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ (2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ (5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5735 - 5755 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5755 - 5775 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5775 - 5795 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5795 - 5815 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5815 - 5835 @ 20), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, PASSIVE-SCAN Could you, please, allow to use these channels? I've tested them on some old FW, and it worked perfectly with hostapd
It's the IR-CONCURRENT flag that disallows AP mode in those channels. :( This means that we can only transmit in those channels as GO or in TDLS if we are at the same time connected as a station to an AP in that channel. This is not allowed for AP mode. APs can only transmit in those channels if they are able to detect other irradiation in that channel, which is not the case of our devices. I have no idea how you got it to work with an old FW. This should have never been allowed. This is a regulatory issue so please do *not* try to bypass it by using an old firmware or in any other way. If you do, the liability is yours.
I was not aware of this issue, that's why I used AP on these channels, and I wondered why it stopped working after FW update... and this is the reason :) Thank you a lot for a clarification!