Make 6 GHz / Wi-Fi 6E and the upper 5 GHz channels visible again
The cause is accurate and I confirmed it from the primary data rather than memory. In wireless-regdb's db.txt, country 00: has no 6 GHz range at all and every 5 GHz range carries NO-IR, exactly as claimed. country US: does have a 6 GHz range. The self-managed claim is right too. iw reg get on this Intel machine prints a global block followed by a separate phy#0 (self-managed) block, precisely the shape the record describes. wireless-regdb really does own /etc/conf.d/wireless-regdom and /usr/lib/udev/rules.d/85-regulatory.rules (which RUNs /usr/bin/set-wireless-regdom on cfg80211 module add), so the sed and the reboot advice are sound. linux-firmware-intel is a real Arch package and does contain /usr/lib/firmware/intel/iwlwifi (390 files), so that is not a fabricated package name. pacman -S --needed wireless-regdb after omarchy update is safe: I read /usr/bin/omarchy-update-pacman-guard and it only aborts when BOTH sync and sysupgrade are present, so a plain -S is not blocked. TWO DEFECTS. (1) The country= line in /etc/wpa_supplicant/wpa_supplicant.conf is inert on Omarchy: Arch's wpa_supplicant.service runs /usr/bin/wpa_supplicant -u -s -O /run/wpa_supplicant with no -c, so under NetworkManager that file is never read. Telling a user to edit it sends them chasing a no-op. (2) The verify criteria are wrong on two counts I checked live. regulatory.db supplies only a max-EIRP figure, so a country-set global block prints (N/A, 23) style entries. (6, 22) only ever appears in the self-managed Intel block, so "real EIRP figures such as (6, 22)" will never be satisfied by setting a country. And with country US set on this machine the 5925 to 7125 MHz range still shows NO-OUTDOOR, PASSIVE-SCAN, because that is what US 6 GHz client rules are. A user following the stated verify would conclude the fix failed when it worked.
Setting a regulatory domain other than the country you are actually in is illegal in most jurisdictions and can interfere with radar, aviation and licensed services on DFS and 6 GHz channels. Set your real country. Note also that software can only ever add restrictions on top of what the card's EEPROM/firmware allows. A device with a CN EEPROM will not transmit at US power levels no matter what you set.
Symptom
A Wi-Fi 6E or Wi-Fi 7 card sees the 2.4 GHz and lower 5 GHz SSIDs but never the 6 GHz one, even though a phone standing next to it connects to it. Or 5 GHz networks are visible but will not associate. The log shows send auth to xx:xx (try 1/3), authenticated, associated, then immediately deauthenticating ... by local choice (Reason: 3=DEAUTH_LEAVING). iw reg get reports global / country 00: DFS-UNSET with every band tagged PASSIVE-SCAN, and iw list shows the channels as no IR.
Cause
Country 00 is the world regulatory domain: a lowest-common-denominator ruleset in which nearly every 5 GHz range is passive-scan / no-IR (no initiating radiation) and the whole 6 GHz band is simply absent. The card may legally listen but not transmit, so it can beacon-scan and never associate, and 6 GHz channels it is not permitted to use are never even enumerated. The kernel only leaves country 00 if wireless-regdb is installed and something actually sets a country. Intel cards muddy this: they are *self-managed* (Location Aware Regulatory), carry their own table in firmware, and are unaffected by iw reg set on the global domain. iw reg get prints a separate phy#0 (self-managed) block for them.
Fix
Diagnose first. The two blocks in this output mean different things:
iw reg get
# 'global / country 00: DFS-UNSET' with NO-IR / PASSIVE-SCAN everywhere = unset
# a trailing 'phy#0 (self-managed)' block = Intel-style LAR, the global domain is not what governs that card
iw list | grep -A 40 'Frequencies:' | grep -i 'no IR\|disabled\|5955\|6135'
journalctl -kb | grep -i 'regulatory\|regdb\|cfg80211'
# 'cfg80211: failed to load regulatory.db' means wireless-regdb is missing
Install the database and set your country persistently. (wireless-regdb is already in Omarchy's base package set, so normally it is present, but check before assuming it is the problem.)
# Omarchy: go through the wrapper, direct pacman -Syu is blocked by the update guard
omarchy update
sudo pacman -S --needed wireless-regdb
sudo sed -i 's/^#WIRELESS_REGDOM="US"/WIRELESS_REGDOM="US"/' /etc/conf.d/wireless-regdom
Uncomment exactly one line in /etc/conf.d/wireless-regdom, matching where you physically are. That file is read by /usr/bin/set-wireless-regdom, which udev runs from /usr/lib/udev/rules.d/85-regulatory.rules when the cfg80211 module appears, i.e. at boot. Apply it now without rebooting:
sudo /usr/bin/set-wireless-regdom # reads the file you just edited
iw reg get
Do **not** bother putting country= in /etc/wpa_supplicant/wpa_supplicant.conf on Omarchy. NetworkManager starts the supplicant as wpa_supplicant -u -s -O /run/wpa_supplicant with no -c, so that file is never read. It only applies if you run wpa_supplicant@<iface>.service yourself instead of NetworkManager.
If iw reg get shows a (self-managed) phy (Intel AX210/AX211/BE200 and similar), the global setting is cosmetic for that card. Its domain comes from firmware plus the country IE in nearby beacons, so make sure the firmware is current and let it associate to a 2.4/5 GHz SSID from the same AP once:
sudo pacman -S --needed linux-firmware-intel
journalctl -kb | grep -i iwlwifi | head -20
Two further things block 6 GHz specifically even with a correct regdomain:
- The card must genuinely be 6E/7. An AX200 is Wi-Fi 6 (2.4/5 GHz only) and will never see 6 GHz no matter what you set. Check with
lspci -knn | grep -i networkand confirm the exact part number. - 6 GHz mandates WPA3-SAE with PMF required. A profile saved as WPA2-PSK will not join the 6 GHz SSID. See the WPA3/SAE record and set
802-11-wireless-security.key-mgmt saeand.pmf 3.
To confirm the band opened up:
iw list | grep -E '59[0-9]{2}|6[0-9]{3}\.0 MHz' | head
nmcli device wifi list --rescan yes
**What success actually looks like. Read this before deciding it failed.** iw reg get should show country US: DFS-FCC (or your country) instead of country 00: DFS-UNSET, and the 5 GHz ranges should lose their NO-IR flag. The power figures will still print as (N/A, 23): regulatory.db carries only a max-EIRP number and never a max antenna gain, so the first field is always N/A in the global block. A pair like (6, 22) appears only in a (self-managed) phy block and is not something setting a country can produce. The US 6 GHz range 5925 - 7125 legitimately keeps NO-OUTDOOR, PASSIVE-SCAN even when everything is correct. That is the US client rule, and the channel is unblocked once the card hears the AP's beacon or discovers it out-of-band from the 2.4/5 GHz SSID. The real end-to-end check is that nmcli device wifi list --rescan yes now shows the 6 GHz SSID and the profile associates.
Verify
iw reg get shows country XX (not 00) with real EIRP figures such as (6, 22) instead of (N/A, 20), and the previously blocked ranges no longer carry PASSIVE-SCAN. iw list lists frequencies in the 5955 to 7115 MHz range without no IR. nmcli device wifi list then shows the 6 GHz SSID.