Hey guys,
has anybody managed to get 6 GHz WiFi signal to show up on Linux when replacing that MTK-garbage WiFi chip with the AX210? Sadly the only device I can test that with is my Pixel 9, which can force its WiFi Hotspot to use 6 GHz only - unless the phone is connected to a 5 GHz WiFi signal at the same time, but I already reported that bug. For all I can gather, it should work, no regulation should prohibit it. Sadly, Intel’s community people want to rather blame this on Framework instead of looking properly into the issue.
One thing I found out together with them though is that one firmware file, iwlwifi-ty-a0-gf-a0.pnvm is present ony my system and was claimed by Intel to be important, as I’m running the firmware directly from upstream, but nothing seems to be loading that. grep’ing dmesg for pnvm only finds
[ 11.893405] iwlwifi 0000:01:00.0: loaded PNVM version 581d4936
Has anybody else have more success?
After replacing the wifi card that ships with the FW16 with a wifi 7 one (a different one than yours), I had the same problem. The solution that worked for me is described here, as well as in many other entries on this site.
Thanks, I’ll try that out. Just to make sure, is it still options cfg80211 ieee80211_regdom= for Intel chips or do you need another option?
Pretty sure it’s the same for all wifi chips.
Sadly this doesn’t do the trick for me. I did make sure that I set the country code the same way it’s in the regdb (though I don’t know what exact patches Debian applies, as together with the regulatory.db-upstream they also ship a regulatory.db-debian), and that my Pixel 9 doesn’t grey out the 6 GHz only option proves to me that it can’t be a regulatory issue, yet it still doesn’t show up.
Pretty sure the ax210 does it’s own reg stuff you can’t normally override.
If you run iw reg get it should show you what it came up with.
It shows both
global
country 00: DFS-UNSET
and
phy#0 (self-managed)
country DE: DFS-UNSET
So no clue what that’s supposed to mean.
The self managed bit looks normal and it seems to think you are in germany.
As it should. So what exactly is the issue now?
Not having the wrong regulatory domain I suppose.
Unfortunately I don’t have any 6ghz aps to test myself.
iw list shows the 6ghz bands right?
It’s the right one though.
It does. These are activated, everything higher is marked as deactivated:
* 5955.0 MHz [1] (22.0 dBm) (no IR)
* 5975.0 MHz [5] (22.0 dBm) (no IR)
* 5995.0 MHz [9] (22.0 dBm) (no IR)
* 6015.0 MHz [13] (22.0 dBm) (no IR)
* 6035.0 MHz [17] (22.0 dBm) (no IR)
* 6055.0 MHz [21] (22.0 dBm) (no IR)
* 6075.0 MHz [25] (22.0 dBm) (no IR)
* 6095.0 MHz [29] (22.0 dBm) (no IR)
* 6115.0 MHz [33] (22.0 dBm) (no IR)
* 6135.0 MHz [37] (22.0 dBm) (no IR)
* 6155.0 MHz [41] (22.0 dBm) (no IR)
* 6175.0 MHz [45] (22.0 dBm) (no IR)
* 6195.0 MHz [49] (22.0 dBm) (no IR)
* 6215.0 MHz [53] (22.0 dBm) (no IR)
* 6235.0 MHz [57] (22.0 dBm) (no IR)
* 6255.0 MHz [61] (22.0 dBm) (no IR)
* 6275.0 MHz [65] (22.0 dBm) (no IR)
* 6295.0 MHz [69] (22.0 dBm) (no IR)
* 6315.0 MHz [73] (22.0 dBm) (no IR)
* 6335.0 MHz [77] (22.0 dBm) (no IR)
* 6355.0 MHz [81] (22.0 dBm) (no IR)
* 6375.0 MHz [85] (22.0 dBm) (no IR)
* 6395.0 MHz [89] (22.0 dBm) (no IR)
* 6415.0 MHz [93] (22.0 dBm) (no IR)
Which is why that is probably not the problem.
And your ap is on what channel?
I fear that’s impossible to tell. As originally stated, the only 6 GHz AP I have is my Pixel 9, and Android can’t show that information for its hotspots afaik. And apps running on the phone that could tell can’t show the WiFi signal sent out by the device. And since my FW16 doesn’t show that WiFi, I can’t use it to tell either. And I’m not sure if any Linux programm running e.g. in Termux on my phone could tell that.
And you are sure the ap on the pixel actually works?
I think this’ll be hard to diagnose without a known working 6ghz ap.
You could try booting a windows to go stick and see if it works there to confirm the ap part works then it can be narrowed down to a linux speciffic issue.
Impossible to tell, but also I have no reason to believe it doesn’t. For that to be a thing it would have to have been broken for like half a year, and I’d probably read about that somewhere.
That’s (still) a thing? I remember Windows 8 was able of that. I’ll have to look into how to create one.
EDIT: aaand I’ll have to get a 64 GB USB stick first, as Windows is such a bloated sow…
Rufus, though I am not sure how you could run that on linux. What a dilemma, you need running windows to make windows to go XD
I could swear one of my windows to go sticks is 32gb but going with 64+ (and a reasonably fast one) isn’t a bad idea.
I’ve got a VM (I’d have to look into how to pass through a USB Stick) and I have an ancient Win10 desktop PC that I barely ever touch, so thankfully I’m good to go.