I’ve got a update for atheros-firmware(I think that all atheros and QCA) on Fedora last night and it seems a bit better on 5GHz (W6) and a lot worse on 6GHz(6E) did not tryed a W7 AP yet.
5GHz seems to be limited to 80MHz still.
I’ll try to test booting a rawhide live image and check if I see any difference. Maybe the new firmware does not play nice with the 6.11.7 kernel module.
Great news, everyone! I’ve identified the issue causing Bluetooth audio problems and my patch will be eventually pushed into bluetooth-next to fix that.
https://patchwork.kernel.org/project/bluetooth/patch/20241121180742.156230-1-greyxor@protonmail.com/
Thank you for your efforts!
Fantastic!
Can anyone confirm if AP mode works on 2.4GHz, 5GHz bands and 6GHz bands?
I’m still not getting those kinds of speeds in Fedora. On 6.11.8 and still getting only 400 Mbps.
In Windows I am able to get 1.1 Gbps.
I’m on a WIFI7 AP (TP-Link EAP773).
You should write this in the ath12k mailing list
Great work! I’ve looked at the patch and noticed that my own QCNCM865 has yet another VID / PID value: 0x2C7C:0x0130. Looks like I’ll have to look into compiling my own kernel for testing…
T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=03 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=2c7c ProdID=0130 Rev= 0.01
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
[...]
Edit: Alright, I hadn’t tested BT audio on this card for a while and I’ve noticed that even without the kernel patch, my audio devices now seem to work without issue on Fedora 41 with kernel 6.11.8-300.fc41.x86_64 while they did not work when I last tested them. Looking at dmesg output still shows a lot of the following error:
Bluetooth: hci0: ACL packet for unknown connection handle 3805
Running a 6.12.1 kernel patched to include my VID/PID fixes that error showing up, but seems to make no functional difference to how the audio works (i.e. fine).
I’m not familiar with how to do that.
In addition to @csp my card also has an other PID.
It has VID: 0x0489 and PID: 0xe10d.
T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0489 ProdID=e10d Rev= 0.01
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
After adding those to your patch and building my own kernel bluetooth audio is now working perfect! 
I’m not that talented creating a pull request for bluetooth-next…maybe you can do this?
The problem is that Qualcomm seems to be having a lot of fun creating 50 different ProdIDs. And I don’t know why they’re doing it. I’ll do an email to explain the situation
Thank you!
…maybe you can post the link to the mailinglist thread/Bugreport afterwards?
just got this message from quic_zijuhu
will up-steam updated more BT firmwares
and add batch of IDs in btusb.c
but it may take some times to complete.
we will up-stream more BT firmwares and Added serial IDs.
Sooo, I suppose it’s matter of Wait & See.
I have this chipset on my MSI Tomahawk MAG x870 motherboard. I have 6.9.3 kernel with 22.04 jammy and ath12k driver. My card works when the computer is booted, however after about 20-60 minutes it suddenly stops working. Any ideas on what’s wrong?
I already have power management off.
$ iwconfig
...
wlp6s0 IEEE 802.11 ESSID:"RankedChoiceVoting"
Mode:Managed Frequency:5.24 GHz Access Point: 80:B9:7A:CF:FD:48
Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=70/70 Signal level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:178 Invalid misc:175 Missed beacon:0
...
You really want and need a newer kernel, try 6.12
I used mainline to update my kernel in my pop-os! Do I need to do anything else? I’m gonna wait for a few hours and see if the WiFi drops again:
❯ uname -mrs
Linux 6.12.1-061201-generic x86_64
No that should be enough, how is it ?
I was gonna post here afterwards. I updated kernel using mainline and everything is working great. The wifi has been stable and working great for the last 6 hours, and it has never gone this long without failing. Thank you!
Thanks for posting your submitted patch. Based on it, I created a patch for my own kernel linux-zen-dori/qcnm_btusb_ids.patch at main · Doridian/linux-zen-dori · GitHub
Was it easy to upstream your change? Anything I should keep in mind other?
I’m obviously interested in doing that as well now that I confirmed this has indeed fixed BT audio for me on my FW16.
Yes it was easy and no I don’t think you need anything else. Now we wait for upstream to merge it and/or qualcomm to upgrade the ID and firmware : [GUIDE] Successful Wi-Fi 7 (802.11be) on Framework 13 AMD with Qualcomm QCNCM865 and Arch Linux - #176 by GreyXor