[RESPONDED] Does anyone have wifi 6e working in linux with the AX210?

Framework Laptop 13 Linux
21

Dredging this one back up.

@Matt_Hartley - apologies for bringing this back up, but are you willing to try to test this out on both? I lack a 12th gen on which to test. Happy to test it out if anyone wants to chuck a 12th gen my way. Saving up and holding out for the 16" for now, but still interested in getting Wifi 6E working on my 11th gen machines with the AX210. The MediaTek card apparently works, but at half the bandwidth. I haven’t been able to dig up if the RZ616 will work with Intel CPUs, but it appears that the RZ608 is a rebadged Mediatek card, so fingers crossed that it might, so I may order one to test once they are available.

22

RZ608 absolutely works with Intel (11th gen in my case). I see no reason why RZ616 wouldn’t. Drivers are under heavy and continuous development, so be sure to get the latest Mediatek firmware bin files.

Instructions here:

23

Thanks @D.H! I just ordered a mt7921k from Amazon, may fiddle with it this weekend. If all goes well I will look into upgrading to the rz616 when it is out. If I’m reading the information in various threads correctly, something changed after one of the 5.x kernels that deactivated the 6e bands. On the 12th gen systems, the firmware passes a value that tells the system to enable them, but on the 11th gen that does not happen. I may not be wording that exactly correctly, but I believe that is the gist. I’d like to make use of the 6e band on my router, but I think that I’m stuck unless this change makes it into the firmware. Thus my foray into the mediatek/amd cards. I held out for a bit as the 7921k is not as fast as the ax210, but finally decided to test it.

24

I do not believe that is the case for the RZ6**. 6GHz bands are marked no-IR on my arch machine running 6.2 kernel, but the RZ608 happily connects to 6GHz APs that are available for me.

25

@D.H - installed and firmware updated. Connects on 6e bands in windows. They show up in iw list. But unable to connect in linux, and in fact the network usually only shows up momentarily when I make a change on the router and it has come back online.

Striking out on what to try. Suggestions or snarky comments welcome.

26

Okay let’s try an easy troubleshooting step first:

What’s the output of iw reg get ?

27

@D.H - thanks for the reply. I thought that I recalled two sections when I had the AX210 in there. This is the output with the MT7921K:

global
country US: DFS-FCC
	(902 - 904 @ 2), (N/A, 30), (N/A)
	(904 - 920 @ 16), (N/A, 30), (N/A)
	(920 - 928 @ 8), (N/A, 30), (N/A)
	(2400 - 2472 @ 40), (N/A, 30), (N/A)
	(5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
	(5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
	(5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS
	(5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
	(5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
	(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
	(57240 - 71000 @ 2160), (N/A, 40), (N/A)

iw list has lines like this:

			* 6935 MHz [197] (12.0 dBm) (no IR)
			* 6955 MHz [201] (12.0 dBm) (no IR)
			* 6975 MHz [205] (12.0 dBm) (no IR)

so it seems that the bands are no longer disabled

28

Now working. Dug around a bit more, tried setting my router to use a static control channel rather than auto, and voila. The suggestion was in this thread on the github that you linked: WiFi 6 vs WiFi 6e · morrownr/USB-WiFi · Discussion #63 · GitHub.

Thanks again for the input and help!

3 Likes
29

Glad you figured it out.

That GitHub is a gold mine of information on bleeding edge and old stable adapters alike…

1 Like
30

Sorry for the delay @lbkNhubert

I have the AX210 on my 12th gen. I am seeing this on Fedora 37 kernel 6.2.9-200.

frequencies
frequencies1325×1241 210 KB

This is one of our officially supported distros.

31

Thank You @Matt_Hartley. Here’s the output from an 11th gen machine with an AX210, running a Fedora live iso:

[liveuser@localhost-live ~]$ uname \-a
Linux localhost-live 6.2.9-300.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Mar 30 22:32:58 UTC 2023 x86_64 GNU/Linux

[liveuser@localhost-live ~]$ iw reg get
global
country 00: DFS-UNSET
	(755 - 928 @ 2), (N/A, 20), (N/A), PASSIVE-SCAN
	(2402 - 2472 @ 40), (N/A, 20), (N/A)
	(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
	(2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
	(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
	(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
	(5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
	(5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
	(57240 - 63720 @ 2160), (N/A, 0), (N/A)

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

[liveuser@localhost-live ~]$ iw list
.
.
.
		Frequencies:
			* 5955 MHz [1] (disabled)
			* 5975 MHz [5] (disabled)
			* 5995 MHz [9] (disabled)
			* 6015 MHz [13] (disabled)
			* 6035 MHz [17] (disabled)
			* 6055 MHz [21] (disabled)
			* 6075 MHz [25] (disabled)
			* 6095 MHz [29] (disabled)
			* 6115 MHz [33] (disabled)
			* 6135 MHz [37] (disabled)
			* 6155 MHz [41] (disabled)
			* 6175 MHz [45] (disabled)
			* 6195 MHz [49] (disabled)
			* 6215 MHz [53] (disabled)
			* 6235 MHz [57] (disabled)
			* 6255 MHz [61] (disabled)
			* 6275 MHz [65] (disabled)
			* 6295 MHz [69] (disabled)
			* 6315 MHz [73] (disabled)
			* 6335 MHz [77] (disabled)
			* 6355 MHz [81] (disabled)
			* 6375 MHz [85] (disabled)
			* 6395 MHz [89] (disabled)
			* 6415 MHz [93] (disabled)
			* 6435 MHz [97] (disabled)
			* 6455 MHz [101] (disabled)
			* 6475 MHz [105] (disabled)
			* 6495 MHz [109] (disabled)
			* 6515 MHz [113] (disabled)
			* 6535 MHz [117] (disabled)
			* 6555 MHz [121] (disabled)
			* 6575 MHz [125] (disabled)
			* 6595 MHz [129] (disabled)
			* 6615 MHz [133] (disabled)
			* 6635 MHz [137] (disabled)
			* 6655 MHz [141] (disabled)
			* 6675 MHz [145] (disabled)
			* 6695 MHz [149] (disabled)
			* 6715 MHz [153] (disabled)
			* 6735 MHz [157] (disabled)
			* 6755 MHz [161] (disabled)
			* 6775 MHz [165] (disabled)
			* 6795 MHz [169] (disabled)
			* 6815 MHz [173] (disabled)
			* 6835 MHz [177] (disabled)
			* 6855 MHz [181] (disabled)
			* 6875 MHz [185] (disabled)
			* 6895 MHz [189] (disabled)
			* 6915 MHz [193] (disabled)
			* 6935 MHz [197] (disabled)
			* 6955 MHz [201] (disabled)
			* 6975 MHz [205] (disabled)
			* 6995 MHz [209] (disabled)
			* 7015 MHz [213] (disabled)
			* 7035 MHz [217] (disabled)
			* 7055 MHz [221] (disabled)
			* 7075 MHz [225] (disabled)
			* 7095 MHz [229] (disabled)
			* 7115 MHz [233] (disabled)
.
.
.
32

Just confirmed, same card on 12th gen is compatible, same card on 11th shows disabled. Tested this myself. Image of my 11th gen, same card.

disabled
disabled1090×1366 348 KB

Ubuntu 22.04 kernel 6.1 on 11th gen.

1 Like
33

So this would seem to me to be a difference in the firmware on the 11th vs the 12th gen, where the 12th gen is passing a flag that enables the 6e bands while the 11th gen does not pass that flag? To be clear, that was pointed out by others far more skilled in tracking this down, so credit to them.

1 Like
34

@Matt_Hartley Wow, good detective work! That looks like a UEFI/firmware issue? Is this still actively being worked on, and do you think it might be fixed in this quarter or the next? (I’m debating returning my new Wifi 6E mesh access points :sweat_smile: )

35

Happy to help. I don’t see this being changed on 11th gen as we’re already using 13th gen boards. So I’d keep the mesh APs and when you’re ready to board swap at a later date and find the 11th gen board a new home (CoolerMaster case for example), you’ll be able to enjoy the Wifi 6E-ness in all it’s shining glory. :slight_smile:

36

@Matt_Hartley since this WiFi issue depends on a firmware change (just a flag, it seems), I had assumed that a fix was still on the roadmap, even if not “soon”. Also the 11gen firmware still has the Intel ME open issue. Is the firmware EOL?

5 Likes
37

OOH. This solved it for me too with my AX210 and Ubiquiti access point. I’ve been struggling that ArchLinux wouldn’t connect to 6Ghz.

2 Likes
38

Fantastic to hear!

39

Without getting too far into the weeds on what will be and won’t be, the team is aware folks would like to see something happening here. I do not have updates as to this right now. I will say this is not a matter of a simple flag. There are other considerations (including but not limited to) staffing, hours spent and other related considerations.

11th gen just received a beta release of the 3.19 BIOS. It continues to be actively supported. Feature requests are seen and heard. But no changes to this at this time.

3 Likes
40

@Matt_Hartley this issue appears to be occurring in the amd 7040s laptops on ubuntu as well.

On my AP I had band steering on, then it forced me on 5ghz.

Turned that off, I was able to connect on 6ghz.

Now for the bad news. I can confirm I am close to the AP, -62dbm.

The connection drops constantly on 6ghz and it is unusable right now. Pinging 1.1.1.1 drops out and I cant even make a speed test because connection goes in and out.

Then I manually kicked it off the network from my router so it would reconnect, did this a few times, eventually settled on channel 37 on the 6ghz band, and now its not reconnecting, works okay, although still surprised because the pixel speed test is a few hundred megabits faster.

Maybe this early firmware is just buggy.