Use non `-ct` driver for R7800

Feature Requests
1

After extensive testing, I see a significant performance improvement for using the packages ath10k-firmware-qca9984 and kmod-ath10k on NETGEAR Nighthawk X4S R7800. The 2.4 GHz wifi download speeds are approximately 8x as fast on the environment I tested in.

Currently, the standard build for this device uses the drivers from Candela Technologies: ath10k-firmware-qca9984-ct and kmod-ath10k-ct.

My experiments are independently corroborated by others, for example:

Therefore, I suggest using the non -ct drivers in the standard build. This would provide a significant speed increase on the 2.4 GHz band to R7800 users, with no effort on their part.

(PS: I talked about this on another thread, but I think this category is the appropriate one for a request like this)

2

When I tried the non ct drivers on linksys ea8300 2.4ghz stops working. What could be the problem?

3

I'm using non-ct drivers on a MR8300 and 2.4 GHz is working perfectly. Delete wireless file and reconstruct it.

4

How to Delete wireless file and reconstruct?

5

Enter SSH than this. This will force wifi to reconstruct with correct devices id and default values. Than customize at will.
https://openwrt.org/docs/guide-user/network/wifi/basic#regenerate_configuration

1 Like
6

Is this correct

opkg remove kmod-ath10k-ct
opkg install ath10k-firmware-qca9888
opkg install kmod-ath10k
type or paste code here
7

You'll also need opkg update before.
Do not remove the firmware package, just kmod-ath10k-ct. Than install the non-ct.
Despite this will work, flashing a custom image rather than removing/installing packages is considered a better practice.
Last but not least, I have decided to switch to the ct drivers for better performances with WDS (read in another thread). I suggest you try both drivers and evaluate which one fits better your case.

8

After changing to non ct I cant connect 2.4ghz.maybe I'll just stick to ct drivers. Thanks

2 Likes
9

And the 4019 fw for 2.4 should not stay on ct either.

10

@Painnance Remove the ath10k-firmware-qca4019-ct, ath10k-firmware-qca9888-ct, kmod-ath10k-ct packages and add ath10k-firmware-qca4019, ath10k-firmware-qca9888 and kmod-ath10k.

2 Likes
11

Sorry for the off-topic, but is there a reason CT firmware is still being used? I can't find any recent comments about it, except for people reporting issues.

12

Last time I tried, 802.11r wasn't supported by non -ct firmware. As a matter of fact, regular version always gave me worse performance (range and speed) in addition to missing features.
But sure, it's been at least a couple years since I tested the regular version so I might give it another try.

13

switched to non -ct version long time ago, using a standalone compex card.
better speeds, no weird disconnects and less battery drain on android devices.

14

I suggested switching to non -ct about a year ago.
Throughout the next releases and up to 24.10 (4 days ago), the -ct driver is still the one used.

I don't know if the devs did not take my suggestion because they disagreed with it, or because they are not aware of it.

As far as I know, this forum "feature requests" is the right avenue? :thinking:

1 Like
15

There's a GitHub issues that's been open for a while now:

16

Interesting. Hopefully it will be picked up at some point.

To be fair though, it's not particularly hard to adapt the non -ct version, with a simple customized install packages.

17

I think it is worth making individual PR-s where -ct experiences problems, at least its introduction was justified by some devices not working at all with mainline driver+fw.

1 Like
18

@badulesia please check if you still have the CT firmware installed. I made this mistake too and debugged for two days.... No comment on that.

1 Like
19

On my build procedure, I don't have the CT version. I'm using directly the firmlware selector. This is for 23.05

ath10k-board-qca4019 ath10k-firmware-qca4019 ath10k-firmware-qca9888 base-files busybox ca-bundle dnsmasq dropbear firewall4 fstools kmod-ath10k kmod-gpio-button-hotplug kmod-leds-gpio kmod-nft-offload kmod-usb-dwc3 kmod-usb-dwc3-qcom kmod-usb-ledtrig-usbport kmod-usb3 libc libgcc libustream-mbedtls logd luci mtd netifd nftables odhcp6c odhcpd-ipv6only opkg procd procd-seccomp procd-ujail uboot-envtools uci uclient-fetch urandom-seed urngd wpad-basic-mbedtls luci luci-theme-material luci-app-advanced-reboot

20

And this is needed, and it does not conflict with ath10k-firmware-qca4019? Just want to double check; I don't know your target...