2255

If you use the vanilla ath10k version, make sure you manually upgrade it to the latest ath10k firmware. The original ath10k firmware from OpenWrt builds is quite old (around 3 years) and truly CRAPPY.

I've been using 20220709-Stable2203NSS with updated ath10k firmware for a few days and it seems pretty good for me so far.

If you use schedutil and ondemand governor, try to set the minimum scaling frequency to 800 MHz as it may help with the stability a bit (less chance of spontaneous rebooting).

1 Like
2256

The builds from this thread seem to use recent ath10k, mine is versioned 20211216-1. I've been using 1000mhz minimum frequency.

2257

My $0.02 is this cache coherency issue with running the CPU too slow needs to be moved away from oral-tradition / ad-hoc advice and to an official patch for this CPU that sets the min freq to the only minimum frequency that works.

This will help cut problems in half (at least) by eliminating one issue that seems to be currently handled effectively by word-of-mouth (keyboard) - make it a certainty.

edit - an openwrt-hosted, mainline, backported patch for all routers with this cpu.

2258

@Mpilon

I never said setting a certain minimum frequency would help get rid of the random reboot with IPQ806x devices. I just said "a bit" more stable based on my own experience and others that setting the minimum frequency at 800 MHz seems to prolong the interval between random reboots to some extent (a few weeks to 2-3 months, instead of every day or every other day etc.). I also tried other minimum frequency settings but none of them fully got rid of the random reboots either. As for the performance governor, a few people have extolled its "virtue" for long uptime but I did not try it long enough on my router. I'm a "tree-hugger" and have kept messing with my devices so I don't care too much about more than several weeks of uptime. For IPQ806x, I just believe it's a hardware bug in terms of its frequency scaling design.

2259

I did a check on the vanilla ath10k firmware included in the 20220709-Stable2203NSS build last week. It was the same as firmware-5.bin_10.4-3.9.0.2-00131. Can you please paste the md5sum checksum of ath10k firmware file on your device.

Only the master snapshot may have the newer vanilla ath10k firmware. I don't think OpenWrt people committed the newer vanilla ath10k firmware to 22.03 (yet).

2260

not 100% sure if I got the right file here, but firmware-5.bin located in /lib/firmware/ath10k/QCA9984/hw1.0 has an md5sum of: 3364807dea5b2db08504d99fd37cb702

I should make note that I directly flashed using sysupgrade from 22.03 to master to 22.03 to 21.03, using the same config for all. So far no reboots with performance governor at 22hr uptime.

2261

I was right :slight_smile: The vanilla ath10k firmware in 22.03.x or 21.03.x is the old version 131 from several years ago. Master snapshot was only recently updated with the newer version 156.

md5sum firmware-5.bin_10.4-3.9.0.2-00131
3364807dea5b2db08504d99fd37cb702 <== same md5sum as yours

And btw, the old firmware may be crappy for my WIFI clients but may be just fine for yours, so to each his own.

I have built my own images with custom (newer) firmware image and other files added so I don't have to manually transfer the newer image to the device after each firmware upgrade.

2262

wait-so on the july 22.03rc5 build, how exactly is fqcodel supposed to be activated? Waveform bufferbloat is acting as if there is no mitigation and running the commands in my rc.local manually (tc qdisc etc) doesn't run anything. Is there any reason that tc isn't included in the image by default?

2263

Besides using a md5sum you can also use a ‘head -1’ on the firmware file. The first line shows you the exact version number.

1 Like
2264

quick update: it does seem to be shaping now, but i'm getting similar errors to @ka2107 in my syslog

2265

ACwifidude removed the sqm-related packages and that prevented "make defconfig" from including the tc-tiny package (and its dependencies). Without tc, you cannot configure NSS fq-codel script. Manually installing tc-tiny package requires installing some kmod-sched-core package that does not seem to work using his kmod packages due to some kernel version conflict. You have to build your own image and include them.

@ACwifidude does not need to remove the sqm-related package (aka luci-app-sqm in his diffconfig). He should only need to remove the physdev packages because the qca-nss-ecm script is no longer needed. LUCI's Firewall status page will no longer complain about legacy ipables rules caused by these physdev rules.

1 Like
2266

Yeah, that's the thing. Between my two posts I installed the dependencies and I'm still getting errors from tc.

2267

Just wait for his next release. I'm sure he will include them in the next build.

The next build will definitely have the multicast-induced latency bug fix for WIFI as well. This is important for people using uPnP or multicast stuff in their network.

1 Like
2268

@ACwifidude Would it be possible to provide the kmods and target specific packages in a place (other than github) which can be added as a repo location in opkg.conf.

Right now opkg does not seem to be able to download packages direct from github, even if I add the raw github path. I have to wget the packages manually onto /tmp and then do "opkg install *.ipk". Thanks in advance.

2269

@ka2107

Since @ACwifidude frequently releases new builds, I don't think it's a good idea to ask him to upload packages to a separate storage location. "Good and free" (and adware/malware-free) storage sites are rare nowadays.

You just need to add some script lines in /etc/rc.local to check for an existing installed package. If it does not exist (e.g. after an upgrade), use wget to download the wanted packages and opkg install *.ipk them. That easily solves the problem for you and saves the trouble for ACwifidude.

1 Like
2270

Silly question, where did you find this section of script so that I can delete it? For some reason I can't find it. :upside_down_face:

config include 'qcanssecm'
        option type 'script'
        option path '/etc/firewall.d/qca-nss-ecm'
        option family 'any'  
        option reload '1'
2271

It's in /etc/config/firewall.

I think the process of building/adding qca-nss related packages during the build process might have added such config to /etc/config/firewall by default.

If that's the case, you may have to use the custom files method to overwrite it : build_root/files/etc/config/firewall

2272

There are some UCI commands in qca-nss-ecm/files/qca-nss-ecm.defaults, it looks like this gets installed to uci-defaults, so the firewall configuration is appended to /etc/config/firewall on first boot. It should just be a simple case of removing the appropriate line from the qca-nss-ecm Makefile...

2 Likes
2273

Switched to the 20220709-Stable2102NSS ath10k-ct build and I still get a reboot once a day on the performance governor, so it doesn't seem to be schedutil governor that's causing it for me, just something added to the recent builds

2274

Are you using NSS fq-codel for SQM?