[GUIDE] Successful Wi-Fi 7 (802.11be) on Framework 13 AMD with Qualcomm QCNCM865 and Arch Linux

My patch made it in, too, for people with that USB ID. And supposedly just got pulled in for the 6.13 cycle I assume with all those other IDs as well. So I suspect the next 6.13 patch release might contain all the new IDs.

2 Likes

Nope, I got 6.13.1-zen1 rn and bluetooth isn’t working at all, device doesn’t even show up for bluetooth (Wi-Fi works fine).

1 Like

Got another PCID not in that list unfortunately
23:00.0 Network controller [0280]: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] [17cb:1107] (rev 01)

1 Like

Wondering if you have seen any changes? I think I got the same card as you, at least my lspci output looks the same. Hoping my limited speed is related to the PCID differences being discussed.

On my side seeing speeds max out at ~550 Mbs as opposed to my ax210 card which can is doing ~900Mbs on my network.

No changes on my end unfortunately, just realized I don’t even have Bluetooth working under Windows 11, kinda worried I have a broken card :confused:

If you have this card working could you try putting it into monitor mode and see if you can capture packets?

For my Framework 13 7840 running Fedora 41:

I just got some updates today. My bluetooth audio device started working where it would previously be visible, but refuse to connect.

For my TP-Link EAP773 wifi 7 access point, I can connect to 2.4G and 5G bands, but 6G is not visible. An update to atheros-firmware-20250311-1 came in which I believe is one prerequisite to getting it to work. My understanding is that it would work if these patches were merged (related to the WCN7850):

Currently the country is na:

iw reg get
global
country CA: DFS-FCC
	(2402 - 2472 @ 40), (N/A, 30), (N/A)
	(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
	(5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
	(5470 - 5600 @ 80), (N/A, 24), (0 ms), DFS
	(5650 - 5730 @ 80), (N/A, 24), (0 ms), DFS
	(5735 - 5835 @ 80), (N/A, 30), (N/A)
	(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR

phy#0 (self-managed)
country na: DFS-UNSET
	(2402 - 2472 @ 40), (N/A, 20), (N/A)
	(2457 - 2482 @ 20), (N/A, 20), (N/A), PASSIVE-SCAN
	(5170 - 5330 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
	(5490 - 5730 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
	(5735 - 5895 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
	(5945 - 7125 @ 320), (N/A, 30), (N/A), AUTO-BW, PASSIVE-SCAN
1 Like

I just picked up an affordable Gigabyte branded GC-WIFI7 off Amazon, swapped the mini card from it for my RZ616. The FW wifi works in the PCIe card, and the ath12k works perfectly in my AMD FW13. Thanks to everyone who has been troubleshooting and writing patches/requesting changes, wifi7 and BT5.3 are working perfectly for me on Arch with kernel 6.13.7.

1 Like

Got a link for which card you bought? I’d like to upgrade this crappy ā€œMEDIATEK Corp. MT7922ā€ that I’m very disappointed Framework sold to us. Wife’s Asus has the same card and they both randomly disconnect and have to reload the module (or reboot) to get them to come back. Utter junk.

I was expecting to get my FW LAN adapter out, but the mainline Arch kernel and firmware was ready to go. It resumes smoothly from sleep, no regulatory domain nonsense, it’s quite lovely.

Edit: Hmmm. Only just noticed, I ordered one used, about 30$ US, it’s only showing new for 45$ now. Used works fine, since we’re just stripping out the M.2 card anyways.

1 Like

The Gigabyte GC-WIFI7 currently comes in 3 versions: 1.0, 1.1, 1.2. Each version uses a completely different chip.
1.2 is intel
1.1 is mediatek
1.0 is qualcomm

So it may not be clear which one you’re getting when you buy it, and may not be the ncm865.

Good thing Amazon return policy is pretty good. I ordered one, will see when I get it.

bluetooth fix is merged for linux 6.15

5 Likes

Thanks. I got a used one for $36 or so. Installed it over the weekend.
I’m on arch linux, using kernel 6.12.21-1-lts and it connected to wifi faster than the crappy Framework mediatek card ever did. Connected to my wifi7 AP just fine, but is not using 6gh, only 5gh, and throughput is much slower than the mediatek was. So I suspect it’s not utilizing any wifi7 or even 6e features. However, I experienced no dieing wifi all weekend so I consider that a win.

Bluetooth on the other hand is a mess. Keyboard works and that’s the most important. Game controller seems to connect just fine, but does not work at all. Bluetooth headphones sometimes connect, most the time fail, and never work either.

Of note, my Wife’s Asus gaming laptop also had that same mediatek card and experienced the same dieing wifi. But in her case she uses Windows 11 and has to reboot the whole machine to bring her wifi back. We installed one of these qualcomm cards in her laptop at the same time (good time to teach her how to change her own components :D), sourced from a different vendor, but using the same Gigabyte drivers to make it work in Windows and much improved there as well. At least she hasn’t complained yet.

You may need to tell Linux where you are in the world, before it will attempt to use the 6GHz band. I had to use this tweak before it would work under Ubuntu 24.04.

1 Like

I am horrified, but not surprised. The one I ordered was the ath12k/qualcomm. I would have settled for a Mediatek for 30$, but I guess I got lucky. Thanks for the heads up.

Thanks for the pointer, I didn’t think about that. And in fact it was NOT set correctly. Got it to set by adding the modprobe config for cfg80211 set to US. It’s using 6Ghz now.

2 Likes

Just installed mine and it seems to be working out of the box, including bluetooth audio/mouse on arch 6.13.8. The only thing that irritates me a little is that connection info shows this:

while I’m in fact on 5GHz and using WPA2/WPA3:

weird, what’s your wifi manager ?
on iwd + networkmanager I got the correct infos

Exactly that, iwd+network manager, running KDE Plasma. I even completely deleted my saved network and re-authenticated, still the same. Is the workaround from the first post still necessary? Not that I suspect that’s the culprit but you can never know.

Interestingly, iwd itself shows the proper info:

[iwd]# station wlan0 show
                                 Station: wlan0                                
--------------------------------------------------------------------------------
  Settable  Property              Value                                          
--------------------------------------------------------------------------------
            Scanning              no                                               
            State                 connected                                        
            Connected network     Skynet                                           
            IPv4 address          192.168.1.88                                     
            ConnectedBss          f6:e2:c6:9e:3e:cd                                
            Frequency             5560                                             
            Channel               112                                              
            Security              WPA3-Personal + FT                               
            RSSI                  0 dBm                                            
            RxMode                802.11ax                                         
            RxMCS                 5                                                
            RxBitrate             576400 Kbit/s 

So it’s something about network manager, I guess.

edit: yep, see last post of this NetworkManager bug report