Guess I am glad it still works then, was not looking forward to switching all my devices or making a special fast 5ghz network or something.
Gonna have to do it eventually but that’ll probably be when there are cheap be APs that support openwrt become available and that’ll probably be a while. Until then Wifi6 is really good XD.
Just adding a note that it appears the ath12k driver currently has some issues with multicast. Couldn’t discover/interact with Chromecast and others until I swapped back to my old wifi card. I only tried with iwd.
Interesting, by any chances did you report it to mailing list ? or there’s a kernel issue about it ?
Still chasing wifi nirvana as well. Picked up a Herald to pull one of these from. RZ616 is stable-ish with too many latency spikes for streaming workstations and the work wifi hates it. AX210 with ax off and US regdom works with nice low latency, but still will see an occasional full system reset like a power trip. Considered trying a 717 but grabbed one of these instead. Worth the hassle yet or is it still unstable?
Have you ruled out Multicast is working from one ESSID/Frequency to the other? This is a common issue on many chipsets on the AP side. It my first culprit to check as this has always been the source (Or not having IGMP snooping enabled consistently) of multicast issues in my experience - of which avahi/bonjour/zeroconf makes use of ; not showing up . i.e Chromecast connected on 2.4ghz (or distinct essid) to that of the Client 5ghz/6ghz - different essid.
For what is is worth I’ve put my QCM865 back into a testing SBC - it was barely useable on the 6.14 kernel series; and it doen’t play nice with mediatek AP’s at all (that’s partially mediateks fault, but also the Ath12k). Mostly on the 7840u FW13 tho it would cause kernel lockups during s2idle tho or wouldn’t be visible unless PXE Netboot was set as first boot option (which forces the chipset to init the card prior to stage1 kernel). Which in the framework settings ; doesn’t auto fall back and requires a keypress to acknowledge - which a bios bug IMO.
Hello! I was having an issue with the WiFi adapter not working in Linux for a while (due to bad Linux/atheros firmware packages.)
I installed kernel 6.16.1 and found a built version of Linux-firmware 202508, and after installing all of the dependencies and the included atheros firmware, I’m happy to report that the WiFi adapter is seen and functional on the more up-to-date firmware packages.
I have also noticed this (I build ath-next branch), I am not able to send wake-on-lan with this chip.
Level1Techs says that the AMD RZ series chips work well on Linux in his experience, but ONLY as of kernel version 6.14.3 released in April 2025. The backported fixes in his experience are still hit or miss, and he agrees it was pretty disappointing before that.
https://youtu.be/L-xgMQ-7lW0?si=fOVnl9l-YMQDHqI1&t=325 (I guess he only mentions RZ717 in this review, but I am fairly certain I remember him saying similar stuff about the whole RZ series in other videos).
Wake-on-LAN now seems to work with the master branch of the ath repo:
And works great with my unifi 6e (don’t have a wifi7 router to test… yet.
Has anyone had any success getting these cards to run at reasonable (non-wireless G) speeds?
I got a card in for myself however it’s hard capped at around 20 Mbps. I think i’ve narrowed down the problem to the card having the incorrect country code internally ( as shown by iw reg get ) shows phy#0 (self-managed) to always be in country 00 regardless of whatever the global reg domain is, and as far as I can tell there’s no way to change it.
Anyone have any ideas?
My kernel version is 6.16.9-200.fc42.x86_64 and linux-firmware package is linux-firmware-20250917-2.fc42.noarch
I get about 1.3G to another computer on my lan, but mine is set to US on both sections. What does yours show?
Seems like the reg dom decided to work today, weird.
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-ETSI
(2402 - 2482 @ 40), (N/A, 20), (N/A), NO-80MHZ, NO-160MHZ, NO-320MHZ
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW, NO-320MHZ
(5250 - 5330 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS, AUTO-BW, NO-320MHZ
(5490 - 5590 @ 80), (N/A, 30), (0 ms), DFS, AUTO-BW, NO-320MHZ
(5590 - 5650 @ 40), (N/A, 30), (600000 ms), DFS, AUTO-BW, NO-320MHZ
(5650 - 5730 @ 80), (N/A, 30), (0 ms), DFS, AUTO-BW, NO-320MHZ
(5735 - 5875 @ 80), (N/A, 14), (N/A), AUTO-BW, NO-320MHZ
(5855 - 5875 @ 20), (N/A, 14), (N/A), AUTO-BW, NO-320MHZ
(5945 - 6425 @ 320), (N/A, 24), (N/A), NO-OUTDOOR, AUTO-BW
However, the speed is still really poor. For reference, the original mediatek card:
user@host:~$ speedtest-cli --secure
Retrieving speedtest.net configuration…
Testing from toob (xx.xx.xx.xx)…
Retrieving speedtest.net server list…
Selecting best server based on ping…
Hosted by Orbital Net (London) [111.02 km]: 9.794 ms
Testing download speed…
Download: 321.72 Mbit/s
Testing upload speed…
Upload: 547.96 Mbit/s
user@host:~$ speedtest-cli --secure
Retrieving speedtest.net configuration…
Testing from toob (xx.xx.xx.xx)…
Retrieving speedtest.net server list…
Selecting best server based on ping…
Hosted by BRSK (London) [111.02 km]: 12.141 ms
Testing download speed…
Download: 350.97 Mbit/s
Testing upload speed…
Upload: 423.65 Mbit/s
and the Qualcomm card, connected to the same AP from the same location in the room:
user@host:~$ speedtest-cli --secure
Retrieving speedtest.net configuration…
Testing from toob (xx.xx.xx.xx)…
Retrieving speedtest.net server list…
Selecting best server based on ping…
Hosted by toob Ltd (London) [111.02 km]: 102.413 ms
Testing download speed…
Download: 25.65 Mbit/s
Testing upload speed…
Upload: 77.91 Mbit/s
crystalyne@trudeautop:~$ speedtest-cli --secure
Retrieving speedtest.net configuration…
Testing from toob (xx.xx.xx.xx)…
Retrieving speedtest.net server list…
Selecting best server based on ping…
Hosted by Orbital Net (London) [111.02 km]: 50.998 ms
Testing download speed…
Download: 36.30 Mbit/s
Testing upload speed…
Upload: 71.18 Mbit/santennas swapped:
user@host:~$ speedtest-cli --secure
Retrieving speedtest.net configuration…
Testing from toob (xx.xx.xx.xx)…
Retrieving speedtest.net server list…
Selecting best server based on ping…
Hosted by YouFibre (London) [111.02 km]: 86.255 ms
Testing download speed…
Download: 58.68 Mbit/s
Testing upload speed…
Upload: 76.21 Mbit/s
user@host:~$ speedtest-cli --secure
Retrieving speedtest.net configuration…
Testing from toob (xx.xx.xx.xx)…
Retrieving speedtest.net server list…
Selecting best server based on ping…
Hosted by YouFibre (London) [111.02 km]: 66.967 ms
Testing download speed…
Download: 51.12 Mbit/s
Testing upload speed…
Upload: 81.86 Mbit/s
Antenna swapped test was done as the Qualcomm card doesn’t mark which port is which, unlike the original Mediatek card, so testing in both configurations to be sure it’s not an antenna issue.
Other info:
Qualcomm:
user@host:~$ sudo iw dev
phy#0
Unnamed/non-netdev interface
wdev 0x2
addr mac
type P2P-device
Interface wlp4s0
ifindex 3
wdev 0x1
addr mac
ssid MyAP
type managed
channel 36 (5180 MHz), width: 80 MHz, center1: 5210 MHz
txpower 17.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 0 0 0 0 0 0 0
user@host:~$ nmcli dev wifi
IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY
mac MyAP Infra 10 270 Mbit/s 100 ▂▄▆█ WPA3* mac MyAP Infra 36 270 Mbit/s 83 ▂▄▆█ WPA3
Mediatek:
user@host:~$ nmcli dev wifi
IN-USE BSSID SSID MODE CHAN RATE SIGNAL BARS SECURITY
mac MyAP Infra 10 270 Mbit/s 100 ▂▄▆█ WPA3* mac MyAP Infra 36 270 Mbit/s 72 ▂▄▆_ WPA3
user@host:~$ sudo iw dev
Place your right index finger on the fingerprint reader
phy#0
Unnamed/non-netdev interface
wdev 0x2
addr mac
type P2P-device
txpower 3.00 dBm
Interface wlp4s0
ifindex 2
wdev 0x1
addr mac
ssid MyAP
type managed
channel 36 (5180 MHz), width: 80 MHz, center1: 5210 MHz
txpower 3.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 0 0 0 0 0 0 0
Think i’m just going to return the card I have. Nothing is wrong with my setup as far as I know, but the performance on this Qualcomm card is truly awful. Back to the Mediatek for me.
I’ve tested kernel 6.16 and 6.17 and the card is broken on both. DO NOT BUY THIS CARD - IT DOES NOT WORK (properly) WITH LINUX.
I use my Qualcomm card on Linux (Fedora 42) without issues. 2gig+ on 320MHz channel on 6GHz.
I see that you have your WiFI on Channel 36 ( you should avoid it at all costs), that is the most crowded one.
Also check your atheros-firmware version, mismatched version (with the kernel module) does make a lot of issues.
The OS being used for the above tests is Fedora Silverblue 42, and I have checked that the versions of the kernel and firmware modules match.
WiFi channel is irrelevant here as adaptors from other vendors (Mediatek and Intel) have speeds orders of magnitude higher and lower pings than this Qualcomm adaptor. I have tried other channels, with the same results.
Good evening. What issues are you having with the Qualcomm card? It works flawlessly for me (6.17.2 kernel & 20251011 linux-firmware)
6.17.1 was having issues with WPA3, But since moving up to 6.17.2 it has been a non-issue.
See this post:
This adapter suffers from low speeds, high (and inconsistent) ping times, neither of which are problems which affect any other adaptors I have tried.
This issue is present on all kernel versions I have tried, 6.16, 6.17 and 6.18
Yeah Qualcomm drivers on linux are kind of all over the place. The mediatek driver on linux has gotten in a much better state over the past two years. I experience no problems with the mt7925 that came with my system on Arch Linux.
Idk how is in the UK, but in the EU there are some channels after the DFS range, but not all APs allow you to do. Sometimes is worth to try a smaller channel BW in the DFS range to avoid radars.
