Bug 206469
Summary: | LAR (location aware regulatory) fails, removal of lar_disable module option breaks workaround. | ||
---|---|---|---|
Product: | Drivers | Reporter: | dglt (dglt) |
Component: | network-wireless-intel | Assignee: | Default virtual assignee for network-wireless-intel (drivers_network-wireless-intel) |
Status: | NEW --- | ||
Severity: | normal | CC: | alex.dafoita, andrej.gelenberg, andrey.vihrov, avamander, berend.de.schouwer, exuvo, garyvdm, gruzija, hamad12a, hkz85825915, jlp.bugs, jm, kronenpj, ladislav.furman, leho, leledumbo_cool, lilydjwg, lu_zero, marcomartins86, mseifert, philipp+Kernel, teslan223, yuya.kusakabe |
Priority: | P1 | ||
Hardware: | Intel | ||
OS: | Linux | ||
Kernel Version: | 5.5 kernels | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
dglt
2020-02-08 16:14:21 UTC
sorry, i wasnt sure on how code boxes are used here. other possible causes i tested while trying to figure this out and made no difference. - replaced router. - replaced wifi adapter. - reset bios multiple times and flashed with 3 different bios versions. - rolled back linux-firmware and tried every version since jan 2019 to current. - removed current drives, and tried both a clean linux install and also a clean windows install (each separately, not dual boot and with a fresh bios flash in between) - powered down every other wifi device except for this laptop with the reasoning that LAR works by picking up on other device's regdom (cant find documentation for LAR so im not sure). - made sure every device including router is set to a US locale. this issue started about 4-6 months ago on my dell inspiron 15-7559 and it's now started to happen on an msi gf63-8rd (both have intel wifi adapters). please let me know if further info is needed, thanks for your time. Also issue for me, can't get the wifi card to work in AP mode on 5Ghz band, because it doesn't respect iw reg set and basically disables all channels: $ iw reg get global country 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) country 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) Exact same issue here. On Intel ax210ngw all 5ghz channels are disabled and cannot be used to transmit Same issue, for me especially regarding 6 GHz operation, this might be linked to this: https://bugzilla.kernel.org/show_bug.cgi?id=215043 +1, similar ax210 hardware at hand. On my AX200 i just get "country 00: DFS-UNSET" and i can't use AP mode on any channel. How am i supposed to set up a 5GHz network in a basement when there obviously is no other APs to listen to down here for the retarded-firmware to find which country it is in?? Am i supposed to buy another sensible wifi card, host a 5GHz AP on that so the AX200 sees it and then allows me to use AP on that. What a joke. I seem to have found a seemingly reliable partial workaround for when the country is 00. I first start AP mode in 2.4GHz on ap0 which for some reason immediately sets the country to DE for me, which is still wrong but at least it is another EU country which i can work with. This allows me to use 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) But for the country DE to not be reset i have to keep the ap0 existing until the 5GHz ap1 is running. So i just down the ap0, start up 5GHz on ap1 ch 149 80Mhz and then i can remove the 2.4GHz ap0. This leaves me with a working 5GHz AP. I have automated this using 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 /etc/create_ap2.conf --daemon --logfile /var/log/wifi2 sleep 2 cat /var/log/wifi2 echo "# Downing 2.4 GHz ap0 #" ip link set down ap0 echo "# Starting 5 GHz on ap1 #" echo "# Starting 5 GHz #" > /var/log/wifi create_ap --config /etc/create_ap5.conf --daemon --logfile /var/log/wifi sleep 2 create_ap --stop ap0 tail -f /var/log/wifi # cat /etc/create_ap2.conf # AP SSID=test 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 # Network DHCP_DNS=gateway ETC_HOSTS=0 NO_DNS=0 NO_DNSMASQ=0 MAC_FILTER=0 MAC_FILTER_ACCEPT=/etc/hostapd/hostapd.accept NEW_MACADDR= # Misc DRIVER=nl80211 DAEMONIZE=0 NO_VIRT=0 NO_HAVEGED=0 DAEMON_PIDFILE= DAEMON_LOGFILE=/var/log/wifi # cat /etc/create_ap5.conf # AP SSID=test 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 you need 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 section "# hostapd config". BEACON_INTERVAL=100 DTIM_PERIOD=2 # Network DHCP_DNS=gateway ETC_HOSTS=0 NO_DNS=0 NO_DNSMASQ=0 MAC_FILTER=0 MAC_FILTER_ACCEPT=/etc/hostapd/hostapd.accept NEW_MACADDR= # Misc DRIVER=nl80211 DAEMONIZE=0 NO_VIRT=0 NO_HAVEGED=0 DAEMON_PIDFILE= DAEMON_LOGFILE=/var/log/wifi I just wonder what Intel engineers thought while masterminding their LAR implementation... I'll tell you a secret - the rationale behind LAR is absolutely nonsensual. If you set up an AP that allows you to set any regulatory domain you want (there are many such devices), your modules will communicate with it anyway. Regardless if the frequency and power is legal at that location. LAR actually did not solve anything - it's alibism in it's purest form. So now to push some real solution forward: What would you recommend instead guys? Something with modems from Qualcomm, Broadcom or Realtek? Do you have good experience with any existing M.2 modules? i.e. from Sparklan? Thanks! My current emotional state is: very annoyed I'd understand LAR if it actually worked, right now it's simply very very wrong and there seems to be no official or unofficial way to correct it. This is very clearly buggy and unless fixed by Intel, the removal of the module option should be reverted. Why should people have to endure crippled hardware? Next up Intel screws up their implementation of software-enabled silicon and accidentally disables half of the cores and it's just kept? I am facing a similar issue on an Intel 9560. LAR doesn't work, I have another AP right next to it, broadcasting two signals 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 region, but it never changes and continues to be ... phy#0 (self-managed) country 00: DFS-UNSET ... which effectively disables 5ghz channels in AP mode, making it useless. Also, think that workaround should be there! Guys, i battled an entire day to make a intel 3165 chip work in AP mode 5Ghz. Pulled almost all hair from my head. Specially because it already worked in 2.4Ghz. But i can't use it, as it interferes with other 2.4Ghz stuff. So, this means it won't work with ANY intel wifi chip? I was about to pull the trigger on a AX210 m.2 module... No way to set the country manually? Is it possible to use a older version of the driver to disable LAR? Anyone know of a good USB wifi adapter that works AP mode in 5Ghz? How to edit the driver code and rebuild it? Download the kernel source code, from kernel.org or your distro, do what you want and compile. |