# Any WiFi 6E support recently?

**URL:** <https://community.frame.work/t/any-wifi-6e-support-recently/74373>\
**Category:** Linux\
**Tags:** debian, fedora, ubuntu\
**Created:** [August 21, 2025, 4:44pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373 "2025-08-21T16:44:35Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\
**Post date:** [August 21, 2025, 4:44pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/1 "2025-08-21T16:44:35Z")

</div>

Which Linux distro are you using? Debian, Fedora, Ubuntu, …

Which release version? latest each

Which kernel are you using? various of the 6.x branch

Which BIOS version are you using? 3.05

Which Framework Laptop 16 model are you using? (AMD Ryzen™ 7040 Series)

Has anybody “recently” (within the past like 6 months or so) any success seeing, let alone connecting to any 6 GHz WiFi signals? I know it has been possible in the past, but for quite a while now, neither on Debian (Testing/Trixie), Fedora (41 and 42), Ubuntu (25.04) or even Windows (24h2 to go) I have been able to see 6 GHz networks on either the original MTK module or the Intel AX210.

The issue with testing merely is, I only have a phone that can create 6 GHz hotspots, I haven’t encountered any other 6 GHz devices yet. The trick of setting your country with `iw` doesn’t help either. I’ve recently read there where issues in the BIOS on FW 13 models that prevented it from properly working. So I wonder if it is even supposed to work currently. `iw list` says for the frequencies from 5955 MHz to 6415 MHz “no IR”, frequencies above that are disabled. For all I know there is no legal reason 6 GHz should be disabled in my country (europe), and if it was, that option would be greyed out in Android too. So I’m a bit out of ideas what’s wrong.

---

<div class="post-metadata">

**Author:** ![Nickolas\_Grigoriadis](https://avatars.discourse-cdn.com/v4/letter/n/858c86/32.png) [@Nickolas\_Grigoriadis](https://community.frame.work/u/Nickolas_Grigoriadis)\
**Post date:** [August 21, 2025, 10:36pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/2 "2025-08-21T22:36:38Z")

</div>

I have 6ghz working reliably with an Intel AX210 module in a Batch1 FW16 using Fedora 42.

The reason from changing out from the MTK was because I would suffer throughput stutters (we think when the radio was doing signal scanning), and I tested it with an AX210 I had. It resolved the stutters for me. But both were working just fine on 6Ghz.

---

<div class="post-metadata">

**Author:** ![Conor](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/conor/32/29835_2.png) [@Conor](https://community.frame.work/u/Conor)\
**Post date:** [August 22, 2025, 4:06am UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/3 "2025-08-22T04:06:01Z")

</div>

I’ve got a the AX210 installed in my FW16 too and it’s worked beautifully. I noticed a bit of lag with the RZ616, purchased the AX210 through Amazon, put it in, and haven’t seen a problem since.

---

<div class="post-metadata">

**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\
**Post date:** [August 22, 2025, 6:18am UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/4 "2025-08-22T06:18:43Z")

</div>

Very odd. I mean I’ve replaced the MTK module a long time ago, the drivers were just terrible and bigger downloads would constantly stall because the download rate kept dropping to 0 for a few seconds repeatedly, but I’m not sure if I ever used 6 GHz on the Intel module. But I just tried it out again, I even installed the driver bundle from Framework and the Wi-Fi drivers from Intel’s website on Windows, no success. But also both Linux and Windows lack the ability to create 6 GHz hotspots to see if any errors pop up and if my phone sees that.

What does iw list say for the both of you about the 6 GHz channels? I’m not sure what the “no IR” is supposed to mean, but at least about half the channels aren’t explicitly labeled as disabled. But no software that I know of can even scan on the 6 GHz channels for a signal.

---

<div class="post-metadata">

**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\
**Post date:** [August 22, 2025, 4:19pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/5 "2025-08-22T16:19:34Z")

</div>

@Nickolas_Grigoriadis @Conor how does `iw reg get` display your reason? For whatever reason, for me it only shows the generic “country EU: DFS-UNSET” for phy#0 (self-managed), which may be the cause for issues. Setting the country code myself has sadly no effect whatsoever.

---

<div class="post-metadata">

**Author:** ![Nickolas\_Grigoriadis](https://avatars.discourse-cdn.com/v4/letter/n/858c86/32.png) [@Nickolas\_Grigoriadis](https://community.frame.work/u/Nickolas_Grigoriadis)\
**Post date:** [August 24, 2025, 8:07am UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/6 "2025-08-24T08:07:52Z")

</div>

Mine is setup, get both `GB: DFS-ETSI` and `GB: DFS-UNSET` . I think the unset is the frequency ranges that are not approved here?

```auto
$ iw reg get
global
country GB: 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 - 5730 @ 160), (N/A, 26), (0 ms), DFS
        (5725 - 5850 @ 80), (N/A, 23), (N/A), NO-OUTDOOR
        (5925 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR
        (57000 - 71000 @ 2160), (N/A, 40), (N/A)

phy#0 (self-managed)
country GB: 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
        (5170 - 5190 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
        (5190 - 5210 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
        (5210 - 5230 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
        (5230 - 5250 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
        (5250 - 5270 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
        (5270 - 5290 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
        (5290 - 5310 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
        (5310 - 5330 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
        (5490 - 5510 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
        (5510 - 5530 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
        (5530 - 5550 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
        (5550 - 5570 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
        (5570 - 5590 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
        (5590 - 5610 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
        (5610 - 5630 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
        (5630 - 5650 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
        (5650 - 5670 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
        (5670 - 5690 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
        (5690 - 5710 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
        (5735 - 5755 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ
        (5755 - 5775 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ
        (5775 - 5795 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ
        (5795 - 5815 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ
        (5815 - 5835 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ, NO-320MHZ
        (5835 - 5855 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, NO-320MHZ
        (5855 - 5875 @ 20), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, NO-320MHZ
        (5945 - 6425 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-320MHZ, PASSIVE-SCAN

```

As I understand the region is got from the network and should be configured on your router.

---

<div class="post-metadata">

**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\
**Post date:** [August 24, 2025, 9:58am UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/7 "2025-08-24T09:58:44Z")

</div>

Interesting. I don’t know what changed, as for the longest time I had `country 00: DFS-UNSET` in global, which is now showing the correct country code, but also with DFS-ETSI. For `phy#0 `though I still get `country EU: DFS-UNSET`.

```auto
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
	(57000 - 66000 @ 2160), (N/A, 40), (N/A)

phy#0 (self-managed)
country EU: 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
	(5170 - 5190 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5190 - 5210 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5210 - 5230 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5230 - 5250 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5250 - 5270 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5270 - 5290 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5290 - 5310 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5310 - 5330 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5490 - 5510 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5510 - 5530 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5530 - 5550 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5550 - 5570 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5570 - 5590 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5590 - 5610 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5610 - 5630 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5630 - 5650 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5650 - 5670 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5670 - 5690 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5690 - 5710 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5735 - 5755 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ
	(5755 - 5775 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ
	(5775 - 5795 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ
	(5795 - 5815 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ
	(5815 - 5835 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ, NO-320MHZ
	(5835 - 5855 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, NO-320MHZ
	(5855 - 5875 @ 20), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, NO-320MHZ
	(5945 - 6425 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-320MHZ, PASSIVE-SCAN

```

My guess is this could be caused by wpa\_supplicant, but even setting `country=DE` in its config doesn’t seem to help:

```auto
wpa_supplicant[1037]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=EU

```

---

<div class="post-metadata">

**Author:** ![Adrian\_Joachim](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/adrian_joachim/32/9949_2.png) [@Adrian\_Joachim](https://community.frame.work/u/Adrian_Joachim)\
**Post date:** [August 27, 2025, 1:07pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/8 "2025-08-27T13:07:27Z")

</div>

The ax210 figures out the country itself.

Do you have the firmware (according to a google search it would be the ‘iwlwifi-mvm-firmware’ package in fedora)?

---

<div class="post-metadata">

**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\
**Post date:** [August 27, 2025, 1:33pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/9 "2025-08-27T13:33:25Z")

</div>

Well, it’s supposed to do so, yes. But it clearly doesn’t. And yes, all firmware is present as long as it has been upstreamed. I’ve just copied the whole firmware git to /usr/lib/firmware. Also, if it where a firmware issue, it would be working on Windows, which it doesn’t.

---

<div class="post-metadata">

**Author:** ![Adrian\_Joachim](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/adrian_joachim/32/9949_2.png) [@Adrian\_Joachim](https://community.frame.work/u/Adrian_Joachim)\
**Post date:** [August 27, 2025, 1:47pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/10 "2025-08-27T13:47:57Z")

</div>

> [@Richard](#):
>
> Also, if it where a firmware issue, it would be working on Windows, which it doesn’t.

Not necessarily but it points away from this direction.

I am assuming there are other APs in the area, if I understand it right the intel firmware determines the regulatory domain based on the information coming from the surounding aps so if most of those somehow don’t have reg domain configured right or even worse there are multiple different ones it may not be able to select the right one.

---

<div class="post-metadata">

**Author:** ![Nickolas\_Grigoriadis](https://avatars.discourse-cdn.com/v4/letter/n/858c86/32.png) [@Nickolas\_Grigoriadis](https://community.frame.work/u/Nickolas_Grigoriadis)\
**Post date:** [August 27, 2025, 1:59pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/11 "2025-08-27T13:59:09Z")

</div>

The AP’s in the area should broadcast the region, so I imagine this can happen because there is at least one AP in the are that isn’t saying EU, and since it’s getting confusing messages it might just decide that no region applies. This is done inside the radio module and is not something can touch.

The region in local config doesn’t apply for Intel AX cards or newer. It’s a red herring.

Take your notebook somewhere else and do the same kind of scan and see if it changes?  
If it does, then your wifi network (or a neighbours) is potentially the cause

---

<div class="post-metadata">

**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\
**Post date:** [August 27, 2025, 2:36pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/12 "2025-08-27T14:36:23Z")

</div>

> [@Adrian\_Joachim](#):
>
> Not necessarily but it points away from this direction.

Uhm…necessarily. Sure, if I didn’t install the Intel drivers that may be true, but I expect them to also install the firmware. And for testing the MTK module, I installed FW’s driver bundle. Both with reboot (as in contrast to Linux Live ISOs, Windows to go is persistent).

---

<div class="post-metadata">

**Author:** ![Adrian\_Joachim](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/adrian_joachim/32/9949_2.png) [@Adrian\_Joachim](https://community.frame.work/u/Adrian_Joachim)\
**Post date:** [August 27, 2025, 2:40pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/13 "2025-08-27T14:40:30Z")

</div>

> [@Richard](#):
>
> Uhm…necessarily. Sure, if I didn’t install the Intel drivers that may be true, but I expect them to also install the firmware.

Assuming they were the right drivers and borked windows drivers are not unheard of.

> [@Richard](#):
>
> (as in contrast to Linux Live ISOs, Windows to go is persistent)

Well windows 2 go isn’t a live iso, if you install linux to an usb drive it’s also persistent XD

---

<div class="post-metadata">

**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\
**Post date:** [August 27, 2025, 2:41pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/14 "2025-08-27T14:41:17Z")

</div>

> [@Nickolas\_Grigoriadis](#):
>
> The AP’s in the area should broadcast the region, so I imagine this can happen because there is at least one AP in the are that isn’t saying EU

Rather at least one is falsely broadcasting the EU regdomain instead of the proper country domain. Also, I can’t tell if my router is even capable of sending it, and I don’t know of a method to tell which AP is sending what regdomain. But I’ve got some news: I just tried `iw reg get` in a different place, now it shows

```auto
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 @ 320), (N/A, 23), (N/A), NO-OUTDOOR
	(57000 - 66000 @ 2160), (N/A, 40), (N/A)

phy#0 (self-managed)
country DE: 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
	(5170 - 5190 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5190 - 5210 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5210 - 5230 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5230 - 5250 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5250 - 5270 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5270 - 5290 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5290 - 5310 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5310 - 5330 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5490 - 5510 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5510 - 5530 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5530 - 5550 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5550 - 5570 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5570 - 5590 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5590 - 5610 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5610 - 5630 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-320MHZ, PASSIVE-SCAN
	(5630 - 5650 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-320MHZ, PASSIVE-SCAN
	(5650 - 5670 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5670 - 5690 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5690 - 5710 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5735 - 5755 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ
	(5755 - 5775 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ
	(5775 - 5795 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ
	(5795 - 5815 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ
	(5815 - 5835 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ, NO-320MHZ
	(5835 - 5855 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, NO-320MHZ
	(5855 - 5875 @ 20), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, NO-320MHZ
	(5945 - 6425 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-320MHZ, PASSIVE-SCAN

```

So while that’s correct now, it still doesn’t see any 6 GHz signals. The output iw `iw list` seems to be the same.

---

<div class="post-metadata">

**Author:** ![Adrian\_Joachim](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/adrian_joachim/32/9949_2.png) [@Adrian\_Joachim](https://community.frame.work/u/Adrian_Joachim)\
**Post date:** [August 27, 2025, 3:07pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/15 "2025-08-27T15:07:58Z")

</div>

Just to make sure you aren’t making the same mistake I did a while ago where I was ripping out my hair about iw reg get not showing 6GHz channels, chan you make sure it actually is an ax210 and not something else (lspci will probably do)?

My dumb ass accidentally mixed up some wifi cards and I ended up installing an older intel card instead of the ax210 and was wondering why I didn’t get any 6ghz channels showing up.

---

<div class="post-metadata">

**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\
**Post date:** [August 27, 2025, 8:34pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/16 "2025-08-27T20:34:29Z")

</div>

As you can see, `iw reg get` is showing the 6 GHz channels just as well as `iw list`. And yes, both the sticker and lspci say AX210. And even in the unlikely event someone made that good of a fake, as mentioned, I still have the original MTK module that my FW shipped with, which is a WiFi 6E module, and it shows the exact same symptoms (although I haven’t cross-checked the output of iw).

---

<div class="post-metadata">

**Author:** ![Conor](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/conor/32/29835_2.png) [@Conor](https://community.frame.work/u/Conor)\
**Post date:** [August 28, 2025, 12:41am UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/17 "2025-08-28T00:41:26Z")

</div>

PROBABLY not a helpful question as it doesn’t explain why you would see the same issue with the MTK module (although those are problematic modules regardless of your currently-reported error…

Are you using the non-vPro AX210? I’d imagine the AX210 vPro with an AMD mainboard would have more issues than just an inability to access 6Ghz signals, but I don’t know that for certain.

---

<div class="post-metadata">

**Author:** ![Richard](https://avatars.discourse-cdn.com/v4/letter/r/f0a364/32.png) [@Richard](https://community.frame.work/u/Richard)\
**Post date:** [August 28, 2025, 8:36pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/18 "2025-08-28T20:36:33Z")

</div>

The invoice says non-vPro, the PCI ID is 8086:2725, which to my knowledge is the non-vPro version.

---

<div class="post-metadata">

**Author:** ![Conor](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/conor/32/29835_2.png) [@Conor](https://community.frame.work/u/Conor)\
**Post date:** [August 28, 2025, 9:12pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/19 "2025-08-28T21:12:56Z")

</div>

I’d probably trust that invoice. Dang!

I THINK the vPro and non-vPro share the same PCI ID (8086 is Intel’s vendor ID, 2725 is the device ID). I see a lot of people online saying that you have to look at the module’s label to differentiate if you don’t have a vPro-enabled CPU, but that seems pretty bogus if true.

vPro PN: 5W10V2578 **3**  
non-vPro PN: 5W10V2578 **4**

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/1X/64c81a89f963ddb07633887baceb642a4b056046.png) [@system](https://community.frame.work/u/system)\
**Post date:** [February 24, 2026, 9:13pm UTC](https://community.frame.work/t/any-wifi-6e-support-recently/74373/20 "2026-02-24T21:13:48Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.