Thanks. And, it's still broken. When i flashed Kong's build couple of days ago, same issue. The commit says it was fixed on Sep 7 and I guess the latest build on 09/08 (R7800-owrt1907-r10505) doesn't include that commit?
That is right: the build of fixed base-files just showed a few minutes ago, so the image builder should build an upgradable image. Custom builds will pick it up at their own pace.
1 Like
Thank you for the info. I had to reset with a PIN and tftp two times in the last two days. I guess this is a warning for others so that they don't have to go through the pain like I did.
Not a big deal but I thought @hnyman mentioned that he always tests the firmware before publishing it. I guess he didn't catch it or was an automated build?
1 Like
I actually tested flashing master, downgrading that to 19.07, sysupgrading to 19.07, and sysupgrading to master...
I got hit earlier a few days ago by the sysupgrading trouble with 19.07, but as that happens every now and then, I was just happy that newer testing worked ok.
Also note that with sysupgrade routines, you usually notice the trouble when you are sysupgrading from the faulty build to the next build.
(I believe that the fault was in the procd backports into 19.07, which got then fixed by a more recent procd backport a day later)
1 Like
Wonderful and thanks.
So, now I have your latest build (R7800-owrt1907-r10505) and it has the fix? So, if I flash your next firmware or Kongs (to test it as I want to check how QOS works on his build), shouldn't be a problem now?
Thanks hnyman fpr your awesome build!
It works great and I havent any troubles.
But I have one Question:
Is it correct, that when I´m updateing my router with your build, that I will lost all additional installed packages? And will I lost de Config for these packages too?
The reason is, that i want user DNS over TLS or maybe DNS over HTTPS.
And if I am right, that I will lost the required packages (and maybe the config too), do you think its possible to integrate this functionallity directliy into your build?
I think your users would like this option for more privacy.
Whats your thoughts about this?
Thnakks!
s3m
@hnyman, I was in your latest build and today I flashed Kong's build to test bufferbloat. I didn't see much difference and flashed your build back as yours have a small footprint and easy on memory.
My question is what happens to the configs between your build and Kong's? Would there be any discrepancy between the builds as his builds are a bit bigger with lot more packages. Would there be any conflicts although both of your builds are based on OpenWrt 19.07 branch?
And, Kong's build says squashfs. Just wondering whether I need to reset settings and start from scratch or not needed?
Yes. Like with all normal OpenWrt builds, sysupgrade does not take care of the packages installed by the user. You need to reinstall those after sysupgrading. Normal config in /etc/config will survive even for those packages.
You can use opkg to install those extra packages that you want. It should work for normal user-space packages, but will not work for kernel related stuff like kmods.
1 Like
I don't know why i'm getting super high processor usage by the netmonitor nlbw. Anyone else with same issues?
Same here after few weeks, but as already said, this is not related to this build, so it's not the correct place to debate.
1 Like
master-r11070-c5b10c8282-20190920-ath10k-crashes ("old" ath10k)
Sorry if I've not been following: the latest master build mentions 'crashes' with the official 'old' ath10k firmware, what 'crashes' exactly?
The discussion has been going on since early August...
The old mainline ath10k driver spams the kernel log with " SWBA overrun on vdev 0, skipped old beacon " errors when there is wifi traffic. Sooner or later the router crashes and reboots.
More details at FS#2480
Currently the "ath10k-ct" is clearly more usable.
For the old mainline ath10k, the last working version is from July, before major wifi driver updates.
1 Like
FWIW, I'm on R7800-master-r10443-ea4e1dac71-20190708-1054 (old ath10k), paired with firmware-5.bin_10.4-3.10-00047, uptime 26 days. Newer builds last only a few minutes for me before reboot.
I jinxed it, it just had a random reboot.
This worked. Up time 2d no issue no such log error ms
Any ideas on these random reboots after a month of uptime? Does something build up, like a memory leak (though it didn't look like it, I look at stats frequently) and then it explodes or is it more like some edge case, certain unfortunate sequence of events that trigger it? It's done this before where it didn't make it past the month mark. The last reboot happened at around 5am when there shouldn't have been much traffic. Somehow in the past reboots also occurred in the early hours. I don't think I've experienced them during the day with more traffic, except when the firmware clearly has issues and it doesn't last long.
My guess is some edge case, like the already suspected jumbo frame case (that hurts at least kernel 4.14 and below).
There was some talk at some point about UDP packet fragmentation also causing issues? Is this the same as the jumbo frame? I do use VPN over UDP for work but it's on almost all the time so I'd expect to see these crashes more often.
No idea. I am talking about this:
https://forum.openwrt.org/search?q=ipq806x-gmac-dwmac%20larger%20than%20size
@hnyman, Is there a way to know whenever a new build is in your dropbox? I check manually once in a while and was wondering whether it's possible to get notified or even a comment on this thread that a new build is available would be great. Thanks again for all your builds and much appreciate it.