Followup: Eventually speed of CT drivers matched my previous speed on 23.05.
I updated my XR500 to 24.10 - the later 20241110 driver worked at full speed for me.
Router: R7800
Firmware: KONG 24 r28237-4b4f319931
I switched to the latest Kong build from the firmware selector RC4 build, in the hope that I would stop seeing the following errors in the log:
Wed Jan 1 13:42:09 2025 kern.warn kernel: [ 6317.103398] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 17 tid 0
Wed Jan 1 13:42:09 2025 kern.warn kernel: [ 6317.103449] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 17 tid 0
Wed Jan 1 13:42:09 2025 kern.warn kernel: [ 6317.109591] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 17 tid 0
Wed Jan 1 13:42:09 2025 kern.warn kernel: [ 6317.116730] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 17 tid 0
Wed Jan 1 13:42:09 2025 kern.warn kernel: [ 6317.124360] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 17 tid 0
Wed Jan 1 13:42:09 2025 kern.warn kernel: [ 6317.131202] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 17 tid 0
Wed Jan 1 13:42:09 2025 kern.warn kernel: [ 6317.138409] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 17 tid 0
Wed Jan 1 13:42:09 2025 kern.warn kernel: [ 6317.145551] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 17 tid 0
Wed Jan 1 13:42:09 2025 kern.warn kernel: [ 6317.152812] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 17 tid 0
Wed Jan 1 13:42:09 2025 kern.warn kernel: [ 6317.160037] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 17 tid 0
Well they also exist on the Kong build.. Does anybody know what they are referring to? and is there any way to correct this?
Edit: Probably Important to mention that I swapped the default "-ct" drivers on the previous rc4 build with none-ct drivers, so the same as the Kong build:
ath10k-board-qca9984 - 20241110-r1
ath10k-firmware-qca9984 - 20241110-r1
kmod-ath10k - 6.6.67.6.11.2-r1
I created a thread on these log entries, but more likely to get a response here, as in theory everybody with an R7800 router should be getting the same errors on their logs..
This does not make sense between 20230804-1 and 20241110-r1 nothing changed for this hw:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/ath10k/QCA9984
To see which firmware is used you should run this command:
dmesg | grep firmware
Not look at the package date of ath10k-firmware.
The XR500 had no issues with the latest 24.10 wifi firmware.
20230804-1 and 20241110-r1 both gave 100Mbps.
The EA8500 only went to 40Mbps with the latest 24.10 firmware.
When I swapped to drivers for the CT versions (2020.11.08-r1), the EA8500 speed increased to 100Mbps.
Hello,
Do you know if the build for the R7500v2 can be used on a R7500v1 ?
I know that they have different HW for the 5Ghz radio, and that the • Quantenna QT3840BC + QT2518B of the R7500v1 is not supported... but I believe the rest of the hardware is similar between the two versions (CPU Qualcomm Atheros IPQ8064, Switch Qualcomm Atheros QCA8337, 2..4 Ghz wifi Qualcomm Atheros QCA9880), thus I was hoping to benefit from the NSS acceleration at least for the Ethernet part of the router...
Or am I missing something?
You are missing a lot, the hardware is not at all as similar as you'd like it to be.
'Somehow' force-flashing the R7500v2 image on a R7500v1 is guaranteed to brick it, probably for good.
When I renew wan6, tcpdump is like this, vltime:86400 (24 hours), my question is why the router cannot renew the prefix time before this time expires.
root@R7800:~# tcpdump -i pppoe-wan -n -vv udp port 547
tcpdump: listening on pppoe-wan, link-type LINUX_SLL (Linux cooked v1), snapshot length 262144 bytes
04:41:26.525667 IP6 (flowlabel 0x188ec, hlim 1, next-header UDP (17) payload length: 137) fe80::dd96:a173:718e:575f.546 > ff02::1:2.547: [udp sum ok] dhcp6 solicit (xid=8aedc (elapsed-time 0) (option-request SIP-servers-domain SIP-servers-address DNS-server DNS-search-list SNTP-servers NTP-server AFTR-Name opt_67 opt_94 opt_95 opt_96 opt_82) (client-ID hwaddr type 1 b0b98a7357a0) (reconfigure-accept) (Client-FQDN) (IA_NA IAID:1 T1:0 T2:0) (IA_PD IAID:1 T1:0 T2:0 (IA_PD-prefix ::/64 pltime:0 vltime:0)))
04:41:26.544429 IP6 (flowlabel 0x1aef2, hlim 64, next-header UDP (17) payload length: 112) fe80::b098:7707:f2:67e1.547 > fe80::dd96:a173:718e:575f.546: [udp sum ok] dhcp6 advertise (xid=8aedc (client-ID hwaddr type 1 b0b98a7357a0) (server-ID hwaddr type 1 18fd747f43ae) (IA_NA IAID:1 T1:43200 T2:69120 (status-code NoAddrsAvail)) (preference 255) (IA_PD IAID:1 T1:43200 T2:69120 (IA_PD-prefix 2a03:hidden:little:monkey::/64 pltime:77760 vltime:86400)))
04:41:26.762722 IP6 (flowlabel 0x188ec, hlim 1, next-header UDP (17) payload length: 121) fe80::dd96:a173:718e:575f.546 > ff02::1:2.547: [udp sum ok] dhcp6 solicit (xid=4e8d4f (elapsed-time 0) (option-request SIP-servers-domain SIP-servers-address DNS-server DNS-search-list SNTP-servers NTP-server AFTR-Name opt_67 opt_94 opt_95 opt_96 opt_82) (client-ID hwaddr type 1 b0b98a7357a0) (reconfigure-accept) (Client-FQDN) (IA_PD IAID:1 T1:0 T2:0 (IA_PD-prefix ::/64 pltime:0 vltime:0)))
04:41:26.782383 IP6 (flowlabel 0x1aef2, hlim 64, next-header UDP (17) payload length: 90) fe80::b098:7707:f2:67e1.547 > fe80::dd96:a173:718e:575f.546: [udp sum ok] dhcp6 advertise (xid=4e8d4f (client-ID hwaddr type 1 b0b98a7357a0) (server-ID hwaddr type 1 18fd747f43ae) (preference 255) (IA_PD IAID:1 T1:43200 T2:69120 (IA_PD-prefix 2a03:hidden:little:monkey::/64 pltime:77760 vltime:86400)))
04:41:26.873453 IP6 (flowlabel 0x188ec, hlim 1, next-header UDP (17) payload length: 133) fe80::dd96:a173:718e:575f.546 > ff02::1:2.547: [udp sum ok] dhcp6 request (xid=4521ba (elapsed-time 0) (option-request SIP-servers-domain SIP-servers-address DNS-server DNS-search-list SNTP-servers NTP-server AFTR-Name opt_67 opt_94 opt_95 opt_96) (client-ID hwaddr type 1 b0b98a7357a0) (server-ID hwaddr type 1 18fd747f43ae) (reconfigure-accept) (Client-FQDN) (IA_PD IAID:1 T1:0 T2:0 (IA_PD-prefix 2a03:hidden:little:monkey::/64 pltime:77760 vltime:86400)))
04:41:26.892606 IP6 (flowlabel 0x1aef2, hlim 64, next-header UDP (17) payload length: 85) fe80::b098:7707:f2:67e1.547 > fe80::dd96:a173:718e:575f.546: [udp sum ok] dhcp6 reply (xid=4521ba (client-ID hwaddr type 1 b0b98a7357a0) (server-ID hwaddr type 1 18fd747f43ae) (IA_PD IAID:1 T1:43200 T2:69120 (IA_PD-prefix 2a03:hidden:little:monkey::/64 pltime:77760 vltime:86400)))
Where can I get information.