appears to be like tackle lar_disable functionality modified into once removed as of 5.5 kernel as a technique to fix the firmware break area with iwlwifi, is that lawful? if i boot with 4.19 or 5.3 im able to make use of lar_diable but booting on 5.5 no longer even lists it as a iwlwifi module choice.
without lar_disable all my 5ghz channels gain disabled for the rationale that regulatory area will get detected as shown by `iw reg gain` as both "nation US: DFS-FCC" which is correct (im in the US) and "nation ID: DFS-UNSET" (Indonesia)which then disables all 5ghz channels excluding for 149-163 and easiest at 20mhz. the connection trudge is decrease than 1/10th of what it needs to be. as a replace of the 360mbps i on the total gain, im barely able to gain 9mbps when the usage of these 5ghz channels. (exact rapid.com trudge take a look at numbers, not link trudge)
i've tried replacing the wifi adapter but this occurs on intel wi-fi-ac 3165, 8265, and 9260 dual band 160Mhz (presently establish in adapter). i need to mute add that this occurs on both dwelling windows and linux but as a minimum on linux i had a technique of disabling LAR so my regulatory area will get detected effectively and your entire wifi channels/widths works as they need to mute.
on all 5.3 and earlier kernels, the usage of lar_disable=1 all my channels work and i gain a full 1733mbps link trudge (5ghz ch.36 at 160mhz)as shown here
relevant outputs from 5.3 kernel:
[code]
~ >>> uname -r
5.3.13-zen1-1-zen
~ >>> iw reg gain
world
nation US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
~ >>> iw phy0 channels
Band 1:
2412 MHz [1]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40+
2417 MHz [2]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40+
2422 MHz [3]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40+
2427 MHz [4]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40+
2432 MHz [5]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40- HT40+
2437 MHz [6]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40- HT40+
2442 MHz [7]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40- HT40+
2447 MHz [8]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40-
2452 MHz [9]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40-
2457 MHz [10]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40-
2462 MHz [11]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40-
2467 MHz [12] (disabled)
2472 MHz [13] (disabled)
Band 2:
5180 MHz [36]
Maximum TX energy: 22.0 dBm
No IR
Channel widths: 20MHz HT40+ VHT80 VHT160
5200 MHz [40]
Maximum TX energy: 22.0 dBm
No IR
Channel widths: 20MHz HT40- HT40+ VHT80 VHT160
5220 MHz [44]
Maximum TX energy: 22.0 dBm
No IR
Channel widths: 20MHz HT40- HT40+ VHT80 VHT160
5240 MHz [48]
Maximum TX energy: 22.0 dBm
No IR
Channel widths: 20MHz HT40- HT40+ VHT80 VHT160
5260 MHz [52]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- HT40+ VHT80 VHT160
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5280 MHz [56]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- HT40+ VHT80 VHT160
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5300 MHz [60]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- HT40+ VHT80 VHT160
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5320 MHz [64]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- VHT80 VHT160
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5500 MHz [100]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40+ VHT80 VHT160
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5520 MHz [104]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- HT40+ VHT80 VHT160
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5540 MHz [108]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- HT40+ VHT80 VHT160
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5560 MHz [112]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- HT40+ VHT80 VHT160
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5580 MHz [116]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- HT40+ VHT80 VHT160
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5600 MHz [120]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- HT40+ VHT80 VHT160
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5620 MHz [124]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- HT40+ VHT80 VHT160
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5640 MHz [128]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- HT40+ VHT80 VHT160
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5660 MHz [132]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- HT40+ VHT80
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5680 MHz [136]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- HT40+ VHT80
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5700 MHz [140]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- HT40+ VHT80
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5720 MHz [144]
Maximum TX energy: 22.0 dBm
No IR
Radar detection
Channel widths: 20MHz HT40- VHT80
DFS remark: usable (for 155 sec)
DFS CAC time: 60000 ms
5745 MHz [149]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40+ VHT80
5765 MHz [153]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40- HT40+ VHT80
5785 MHz [157]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40- HT40+ VHT80
5805 MHz [161]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40- VHT80
5825 MHz [165]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz
~ >>>
~ >>> iw wlan0 information
Interface wlan0
ifindex 3
wdev 0x1
addr 24:ee:9a: 88: 66: 84
ssid wrt5-160
model managed
wiphy 0
channel 36 (5180 MHz), width: 160 MHz, center1: 5250 MHz
txpower 22.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 0 0 0 0 0 0 0
~ >>>
[/code]
and the same outputs from 5.5 kernel (lar_disable not an choice)
[code]
~ >>> uname -r
5.5.1-arch1-1
~ >>> iw reg gain
world
nation US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0 (self-managed)
nation ID: DFS-UNSET
(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
(5735 - 5815 @ 20), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
~ >>> iw phy0 channels
Band 1:
2412 MHz [1]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40+
2417 MHz [2]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40+
2422 MHz [3]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40+
2427 MHz [4]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40+
2432 MHz [5]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40- HT40+
2437 MHz [6]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40- HT40+
2442 MHz [7]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40- HT40+
2447 MHz [8]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40- HT40+
2452 MHz [9]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40- HT40+
2457 MHz [10]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40-
2462 MHz [11]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40-
2467 MHz [12]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40-
2472 MHz [13]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz HT40-
2484 MHz [14] (disabled)
Band 2:
5180 MHz [36] (disabled)
5200 MHz [40] (disabled)
5220 MHz [44] (disabled)
5240 MHz [48] (disabled)
5260 MHz [52] (disabled)
5280 MHz [56] (disabled)
5300 MHz [60] (disabled)
5320 MHz [64] (disabled)
5340 MHz [68] (disabled)
5360 MHz [72] (disabled)
5380 MHz [76] (disabled)
5400 MHz [80] (disabled)
5420 MHz [84] (disabled)
5440 MHz [88] (disabled)
5460 MHz [92] (disabled)
5480 MHz [96] (disabled)
5500 MHz [100] (disabled)
5520 MHz [104] (disabled)
5540 MHz [108] (disabled)
5560 MHz [112] (disabled)
5580 MHz [116] (disabled)
5600 MHz [120] (disabled)
5620 MHz [124] (disabled)
5640 MHz [128] (disabled)
5660 MHz [132] (disabled)
5680 MHz [136] (disabled)
5700 MHz [140] (disabled)
5720 MHz [144] (disabled)
5745 MHz [149]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz
5765 MHz [153]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz
5785 MHz [157]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz
5805 MHz [161]
Maximum TX energy: 22.0 dBm
Channel widths: 20MHz
5825 MHz [165] (disabled)
5845 MHz [169] (disabled)
5865 MHz [173] (disabled)
5885 MHz [177] (disabled)
5905 MHz [181] (disabled)
~ >>>
~ >>> iw wlan0 information
Interface wlan0
ifindex 4
wdev 0x100000001
addr 24:ee:9a: 88: 66: 84
ssid HOME_2.4
model managed
wiphy 1
channel 11 (2462 MHz), width: 40 MHz, center1: 2452 MHz
txpower 22.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 0 0 0 0 0 0 0
[/code]
when LAR fails, a technique to disable it seems doubtlessly the most efficient workaround and i train this after many hours over many months attempting to identify why. every kernel version ive examined (4.14 to 5.5) all behave the same if lar_disable=1 just is not very historical.
sorry, i wasnt certain on how code boxes are historical here.
assorted that it's likely you'll presumably well presumably mediate of causes i examined whereas attempting to figure this out and made no contrast.
- replaced router.
- replaced wifi adapter.
- reset bios multiple times and flashed with 3 assorted bios variations.
- rolled encourage linux-firmware and tried every version since jan 2019 to unique.
- removed unique drives, and tried both a intellectual linux install and additionally a intellectual dwelling windows install (every individually, not dual boot and with a novel bios flash in between)
- powered down every assorted wifi machine excluding for this computer with the reasoning that LAR works by picking up on assorted machine's regdom (cant safe documentation for LAR so im not certain).
- made certain every machine together with router is determined to a US locale.
this area started about 4-6 months ago on my dell inspiron 15-7559 and it be now began to occur on an msi gf63-8rd (both possess intel wifi adapters). please let me know if extra information is well-known, thanks for your time.
Additionally area for me, can't gain the wifi card to work in AP mode on 5Ghz band, attributable to it doesn't recognize iw reg situation and in overall disables all channels:
$ iw reg gain
world
nation 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, AUTO-BW
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#0 (self-managed)
nation 00: DFS-UNSET
...
$ iw list
...
Frequencies:
5180 MHz [36] (22.0 dBm) (no IR)
5200 MHz [40] (22.0 dBm) (no IR)
5220 MHz [44] (22.0 dBm) (no IR)
5240 MHz [48] (22.0 dBm) (no IR)
5260 MHz [52] (22.0 dBm) (no IR, radar detection)
5280 MHz [56] (22.0 dBm) (no IR, radar detection)
5300 MHz [60] (22.0 dBm) (no IR, radar detection)
5320 MHz [64] (22.0 dBm) (no IR, radar detection)
5340 MHz [68] (disabled)
5360 MHz [72] (disabled)
5380 MHz [76] (disabled)
5400 MHz [80] (disabled)
5420 MHz [84] (disabled)
5440 MHz [88] (disabled)
5460 MHz [92] (disabled)
5480 MHz [96] (disabled)
5500 MHz [100] (22.0 dBm) (no IR, radar detection)
5520 MHz [104] (22.0 dBm) (no IR, radar detection)
5540 MHz [108] (22.0 dBm) (no IR, radar detection)
5560 MHz [112] (22.0 dBm) (no IR, radar detection)
5580 MHz [116] (22.0 dBm) (no IR, radar detection)
5600 MHz [120] (22.0 dBm) (no IR, radar detection)
5620 MHz [124] (22.0 dBm) (no IR, radar detection)
5640 MHz [128] (22.0 dBm) (no IR, radar detection)
5660 MHz [132] (22.0 dBm) (no IR, radar detection)
5680 MHz [136] (22.0 dBm) (no IR, radar detection)
5700 MHz [140] (22.0 dBm) (no IR, radar detection)
5720 MHz [144] (22.0 dBm) (no IR, radar detection)
5745 MHz [149] (22.0 dBm) (no IR)
5765 MHz [153] (22.0 dBm) (no IR)
5785 MHz [157] (22.0 dBm) (no IR)
5805 MHz [161] (22.0 dBm) (no IR)
5825 MHz [165] (22.0 dBm) (no IR)
5845 MHz [169] (disabled)
5865 MHz [173] (disabled)
5885 MHz [177] (disabled)
5905 MHz [181] (disabled)
Real same area here.
On Intel ax210ngw all 5ghz channels are disabled and can't be historical to transmit
+1, an identical ax210 hardware at hand.
On my AX200 i correct gain "nation 00: DFS-UNSET" and i will't use AP mode on any channel.
How am i alleged to situation up a 5GHz network in a basement when there clearly is no assorted APs to listen to to down here for the retarded-firmware to search out which nation it's miles in??
Am i alleged to purchase one other wise wifi card, host a 5GHz AP on that so the AX200 sees it after which allows me to make use of AP on that. What a shaggy dog narrative.
I appear to possess found a reputedly official partial workaround for when the nation is 00.
I first initiate AP mode in 2.4GHz on ap0 which for some reason straight away sets the nation to DE for me, which remains to be inferior but as a minimum it's miles one other EU nation which i will work with. This allows me to make use of 5GHz channels 149-165:
iw list
5745 MHz [149] (22.0 dBm)
5765 MHz [153] (22.0 dBm)
5785 MHz [157] (22.0 dBm)
5805 MHz [161] (22.0 dBm)
5825 MHz [165] (22.0 dBm)
Nonetheless for the nation DE to not be reset i possess to attend the ap0 unique till the 5GHz ap1 is operating. So i correct down the ap0, initiate up 5GHz on ap1 ch 149 80Mhz after which i will take dangle of away the 2.4GHz ap0. This leaves me with a working 5GHz AP.
I in actuality possess automated this the usage of create_ap from https://github.com/dlenski/create_ap:
echo "# Starting 2.4 GHz on ap0 #"
echo "# Starting 2.4 GHz #" > /var/log/wifi2
create_ap --config /and loads others/create_ap2.conf --daemon --logfile /var/log/wifi2
sleep 2
cat /var/log/wifi2
echo "# Downing 2.4 GHz ap0 #"
ip link situation down ap0
echo "# Starting 5 GHz on ap1 #"
echo "# Starting 5 GHz #" > /var/log/wifi
create_ap --config /and loads others/create_ap5.conf --daemon --logfile /var/log/wifi
sleep 2
create_ap --pause ap0
tail -f /var/log/wifi
# cat /and loads others/create_ap2.conf
# AP
SSID=take a look at
PASSPHRASE=password
USE_PSK=0
HIDDEN=0
# Inernet sharing
WIFI_IFACE=wifi
INTERNET_IFACE=br0
SHARE_METHOD=bridge
GATEWAY=192.168.9.1
IPV6=1
ISOLATE_CLIENTS=0
# Wireless
FREQ_BAND=2.4
CHANNEL=1
COUNTRY=
WPA_VERSION=2
WPS=0
IEEE80211N=1
IEEE80211AC=1
HT_CAPAB=[HT40+][SHORT-GI-20][SHORT-GI-40]
VHT_CAPAB=[RXLDPC][TX-STBC-2BY1][RX-STBC-1]
BEACON_INTERVAL=100
DTIM_PERIOD=2
# Community
DHCP_DNS=gateway
ETC_HOSTS=0
NO_DNS=0
NO_DNSMASQ=0
MAC_FILTER=0
MAC_FILTER_ACCEPT=/and loads others/hostapd/hostapd.gain
NEW_MACADDR=
# Misc
DRIVER=nl80211
DAEMONIZE=0
NO_VIRT=0
NO_HAVEGED=0
DAEMON_PIDFILE=
DAEMON_LOGFILE=/var/log/wifi
# cat /and loads others/create_ap5.conf
# AP
SSID=take a look at
PASSPHRASE=password
USE_PSK=0
HIDDEN=0
# Inernet sharing
WIFI_IFACE=wifi
INTERNET_IFACE=br0
SHARE_METHOD=bridge
GATEWAY=192.168.9.1
IPV6=1
ISOLATE_CLIENTS=0
# Wireless
FREQ_BAND=5
CHANNEL=149
COUNTRY=
WPA_VERSION=2
WPS=0
IEEE80211N=1
IEEE80211AC=1
HT_CAPAB=[HT40+][SHORT-GI-20][SHORT-GI-40]
VHT_CAPAB=[VHT80][RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1]
# for 80MHz and up it's likely you'll presumably well presumably need gotten with the intention to add:
# vht_oper_chwidth=1
# vht_oper_centr_freq=seg0_idx=155 (for ch 149)
# to the create_ap script at line 1804 in piece "# hostapd config".
BEACON_INTERVAL=100
DTIM_PERIOD=2
# Community
DHCP_DNS=gateway
ETC_HOSTS=0
NO_DNS=0
NO_DNSMASQ=0
MAC_FILTER=0
MAC_FILTER_ACCEPT=/and loads others/hostapd/hostapd.gain
NEW_MACADDR=
# Misc
DRIVER=nl80211
DAEMONIZE=0
NO_VIRT=0
NO_HAVEGED=0
DAEMON_PIDFILE=
DAEMON_LOGFILE=/var/log/wifi
I correct wonder what Intel engineers concept whereas masterminding their LAR implementation...
I could expose you a secret - the rationale on the encourage of LAR is in actuality nonsensual. Will possess to you situation up an AP that skill that you can situation any regulatory area you want (there are a amount of such units), your modules will discuss with it anyway. Regardless if the frequency and energy is stunning at that plot. LAR the truth is did not cure the rest - it be alibism in it be purest create.
So now to push some exact solution forward:
What would you point out as a replace guys? One thing with modems from Qualcomm, Broadcom or Realtek? Attain it's likely you'll presumably well presumably need gotten stunning abilities with any unique M.2 modules? i.e. from Sparklan?
Thanks!
My unique emotional remark is: very irritated
I could presumably well realize LAR if it the truth is worked, lawful now it be merely very very inferior and there seems no official or unofficial approach to correct it. Here's very clearly buggy and unless mounted by Intel, the elimination of the module choice needs to be reverted. Why need to mute of us must endure crippled hardware?
Subsequent up Intel screws up their implementation of machine-enabled silicon and by probability disables half of of the cores and it be correct saved?
I'm going thru a an identical area on an Intel 9560.
LAR doesn't work, I in actuality possess one other AP lawful next to it, broadcasting two indicators on channel 100 (5500 MHz), I even connect the Intel 9560 to them in AC mode, with the intent of forcing LAR to compute the station, but it by no methodology changes and continues to be
...
phy#0 (self-managed)
nation 00: DFS-UNSET
...
which effectively disables 5ghz channels in AP mode, making it pointless.
Additionally, mediate that workaround needs to be there!
Guys, i battled a entire day to build a intel 3165 chip work in AP mode 5Ghz. Pulled nearly all hair from my head. Specially attributable to it already worked in 2.4Ghz. Nonetheless i can't use it, as it interferes with assorted 2.4Ghz stuff.
So, this methodology it could well perhaps presumably well not work with ANY intel wifi chip? I modified into once about to drag the situation off on a AX210 m.2 module...
No approach to situation the nation manually? Is it that it's likely you'll presumably well presumably mediate of to make use of a older version of the motive force to disable LAR?
Somebody know of a stunning USB wifi adapter that works AP mode in 5Ghz?
How one can edit the motive force code and rebuild it?
Procure the kernel source code, from kernel.org or your distro, attain what you want and collect.
Additionally area for me, can't gain the wifi card to work in AP mode on 5Ghz band, attributable to it doesn't recognize iw reg situation and in overall disables all channels: $ iw reg gain world nation 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, AUTO-BW (57000 - 66000 @ 2160), (N/A, 40), (N/A) phy#0 (self-managed) nation 00: DFS-UNSET ... $ iw list ... Frequencies: 5180 MHz [36] (22.0 dBm) (no IR) 5200 MHz [40] (22.0 dBm) (no IR) 5220 MHz [44] (22.0 dBm) (no IR) 5240 MHz [48] (22.0 dBm) (no IR) 5260 MHz [52] (22.0 dBm) (no IR, radar detection) 5280 MHz [56] (22.0 dBm) (no IR, radar detection) 5300 MHz [60] (22.0 dBm) (no IR, radar detection) 5320 MHz [64] (22.0 dBm) (no IR, radar detection) 5340 MHz [68] (disabled) 5360 MHz [72] (disabled) 5380 MHz [76] (disabled) 5400 MHz [80] (disabled) 5420 MHz [84] (disabled) 5440 MHz [88] (disabled) 5460 MHz [92] (disabled) 5480 MHz [96] (disabled) 5500 MHz [100] (22.0 dBm) (no IR, radar detection) 5520 MHz [104] (22.0 dBm) (no IR, radar detection) 5540 MHz [108] (22.0 dBm) (no IR, radar detection) 5560 MHz [112] (22.0 dBm) (no IR, radar detection) 5580 MHz [116] (22.0 dBm) (no IR, radar detection) 5600 MHz [120] (22.0 dBm) (no IR, radar detection) 5620 MHz [124] (22.0 dBm) (no IR, radar detection) 5640 MHz [128] (22.0 dBm) (no IR, radar detection) 5660 MHz [132] (22.0 dBm) (no IR, radar detection) 5680 MHz [136] (22.0 dBm) (no IR, radar detection) 5700 MHz [140] (22.0 dBm) (no IR, radar detection) 5720 MHz [144] (22.0 dBm) (no IR, radar detection) 5745 MHz [149] (22.0 dBm) (no IR) 5765 MHz [153] (22.0 dBm) (no IR) 5785 MHz [157] (22.0 dBm) (no IR) 5805 MHz [161] (22.0 dBm) (no IR) 5825 MHz [165] (22.0 dBm) (no IR) 5845 MHz [169] (disabled) 5865 MHz [173] (disabled) 5885 MHz [177] (disabled) 5905 MHz [181] (disabled)Add Observation