You have a source problem on your side. The qca-nss-gmac package has a different path. Check which branch your sources are from.
Anyone else getting inconsistent type errors building luci-base or is my beta-fedora-42 glibc causing problems
edit: scratch that, it doesn't like gcc 15 and the makefile is ignoring my override to gcc-14 because of course it is
R7800-24.10-nss
Check your sources again because the NSS packages are not in the feeds location.
There is something wrong with these sources, I did everything exactly as on the other source (which works) and as I have done dozens of other times for Flint 2 with the original vanilla repos
I've compiled from the updated repo main-NSS but for the first time R7800 was bricked. R7800 no longer boots. Maybe anyone else tried that build too.
I've had to recover it via U-Boot debricking and it's up again with my old build. Really strange it compiled just fine.
Ha, same. Unfortunate.
I don't have my earlier factory image either (I didn't build it) so, uh, unless @sqter still has that repo floating around or someone knows how to convert a sysupgrade image to a factory one, I'm a bit stuck for the moment
1 Like
Take the non NSS OpenWrt official factory image and flash it then use your old sysupgrade.
1 Like
oh, duh, lmfao
now let's play "do i have a configuration backup lying around anywhere"
October. we take those.
Yes, I’m bricked now and just tftp to official img.
btw I’ve kept the previous version of build.
Edit:
Lucky, I just fall-back to 3-25 build with 3-24 config.
1 Like
I also bricked today building from k6.x branch and reverted to a previous version
1 Like
With your r7800's they went brick it makes me give up on flashing my c2600
Should I try it anyway?
In the meantime I re-downloaded the sources, but I noticed that now some NSS stuff is missing, like CONFIG_NSS_DRV_DTLS_ENABLE and CONFIG_NSS_DRV_MAPT_ENABLE for example, it has now passed the compilation of nss-gmac which before failed, but now it fails on ath10k-ct, error 1
I would recommend against it unless youre comfortable debricking.
Updated my last release from 09-04-25 with factory img. Might come handy 
It's from the same build but didn't upload.
Anyone want to check this out? Maybe this is the solution to the last problem.
3 Likes
Let's hope it is the solution.
@asvio can you sync again, thanks.
@sqter By the way bellow error seems to be from the banIP package.
1 Like
Updated, tested and it works
3 Likes
I built with the updated sources and now it worked without errors, as soon as I get my hands on the c2600 I'll try it
It's indirectly related to banip but with NFT itself when loading large sets. Does it still happen on you upon boot and with banip?
1 Like