Build for Netgear R7800

cursedZeroX · October 25, 2021, 2:47pm

After upgrading to r17842-b428f187f0-20211024, my R7800 2.4Ghz and 5Ghz wifi stopped working and the Luci wireless page shows Generic 802.11bg for both radios. I am using the ath10k drivers and from a bit of research, I came across a patch which seems to address the recent issue https://patchwork.kernel.org/project/linux-wireless/patch/20211020075054.23061-1-kvalo@codeaurora.org/.

This is what I see in my logs:

[   14.166486] ath10k_pci 0000:01:00.0: assign IRQ: got 43
[   14.167052] ath10k_pci 0000:01:00.0: enabling device (0140 -> 0142)
[   14.167148] ath10k_pci 0000:01:00.0: enabling bus mastering
[   14.167732] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[   15.140001] ath10k_pci 0000:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
[   15.140218] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[   15.155530] ath10k_pci 0000:01:00.0: firmware ver 10.4-3.9.0.2-00131 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 23bd9e43
[   17.426888] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id 0:1 crc32 85498734
[   21.085387] ath10k_pci 0000:01:00.0: failed to copy target iram contents: -12
[   21.172940] ath10k_pci 0000:01:00.0: could not init core (-12)
[   21.173569] ath10k_pci 0000:01:00.0: could not probe fw (-12)
[   21.178236] ath10k_pci 0001:01:00.0: assign IRQ: got 45
[   21.179906] ath10k_pci 0001:01:00.0: enabling device (0140 -> 0142)
[   21.183740] ath10k_pci 0001:01:00.0: enabling bus mastering
[   21.184702] ath10k_pci 0001:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[   21.396114] ath10k_pci 0001:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
[   21.396149] ath10k_pci 0001:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[   21.407102] ath10k_pci 0001:01:00.0: firmware ver 10.4-3.9.0.2-00131 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 23bd9e43
[   23.686963] ath10k_pci 0001:01:00.0: board_file api 2 bmi_id 0:2 crc32 85498734
[   27.354454] ath10k_pci 0001:01:00.0: failed to copy target iram contents: -12
[   27.443524] ath10k_pci 0001:01:00.0: could not init core (-12)
[   27.444154] ath10k_pci 0001:01:00.0: could not probe fw (-12)

hnyman · October 25, 2021, 5:04pm

With r17842-b428f187f0-20211024 I have clients connected to both 2.4 and 5 GHz networks, with the default ath10k-ct wifi driver.

I haven't really looked into the mainline ath10k.

Ps. you might highlight that upstream patch to @hauke who just merged the newest batch of the upstream mac80211 wifi backports. As the fix was apparently accepted by upstream, the fix will trickle down to us at some point.

hnyman · October 25, 2021, 5:31pm

I made an updated DSA test build, as most of the qca8k switch config has now been merged, and the current PR is mostly about toggling the device DTSs.

Test-DSA-master-r17855-a1939e7e37-20211025

(Based on PR 4036 from @Ansuel . Possible feedback to there...)

hnyman · October 26, 2021, 2:43pm

owrt2102-r16327-a77ea2f05f-20211026
Equivalent to the soon-to-be-released 21.02.1

The relevant recent 21.02 change is the new ath10k-ct version with the VHT160 fix. It has been officially backported to 21.02 before the maintenance release 21.02.1 was tagged (My previous 21.02 build already contained it.)

(Not applicable to my build with openssl, but the 21.02.1 will also have the wolfssl fix for the Letsencrypt certs.)

immi803 · October 27, 2021, 10:21pm

@hnyman
Thanks for awesome latest build

I'm getting following error, any help would be highly appreciated

Thu Oct 28 02:55:24 2021 daemon.err nlbwmon[2428]: Netlink receive failure: Out of memory
Thu Oct 28 02:55:24 2021 daemon.err nlbwmon[2428]: Unable to dump conntrack: No buffer space available

Having total 18 buffer size shortage in Logs in 11 hour active time

Heaviest service I've in my opinion is samba v4
As kernel doesn't support light ksmbd

Secondly, is there any chance i can get compatibility of following module in upcoming releases

hnyman · October 30, 2021, 7:33pm

The upstream patch for the mainline ath10k got merged a few minutes ago.

See

jedthe3rd · November 7, 2021, 11:59pm

What is the difference between this build and the one in the wiki?:

I see you included some additional software to enable similar functionality as the stock firmware. Is there anything else non obvious you have done?

slh · November 8, 2021, 12:14am

How about reading the very first post of this thread?

Ansuel · November 8, 2021, 12:15am

BIG LOL ahahahhaha

steom · November 8, 2021, 1:01am

Absolutely nothing....

Oh yes... That you cannot be able to install many software and any kernel module!

This version is not suitable for any type of advanced use tailored to your needs.

It's a very old story...
I'm here from 2017 and I see that this thing it's still the same.

The answer is that him have no plans to add kmod etc etc that this is him strictly personal build only etc etc because him have no need for it etc etc and for every questions or problems other than his build you are kindly invited to write in another thread etc etc as like if his build has ever had who knows what improvements and changes etc etc instead it is simply like the official build.

I am amazed how this strictly personal thread concerning only his strictly private build is still open.

Fortunately, since 2019 exists the Kong build.

You would be much better off using the Kong build which has a proper software repository support.

Ansuel · November 8, 2021, 1:03am

I smell random flame from new user.... BAD....

anon50098793 · November 8, 2021, 2:42am

fwiw... I went down that route with the rpi4 ( fortunately does not really have space/ram constraints )...

i'm now at probably over 100 extra kmods... which chew up maybe;

100M or extra ram...
23M extra space

these things cost alot from the person providing these;

time (hour+ every build)
storage space (think TB over months)
hosting space (think many GBs)

putting a dollar factor on it... charging very low labor hours... you are looking at someone spending $700+(AUD) every year to provide such support

so if you want to do or suggest this go ahead... just know and be realistic about what it takes... choice is probably alot less than half of the equation...

and nobody has provided more builds for more time than hnyman... so $700 x 5 years would have cost him over $3500(AUD)~$2500(US) off his own back...

not a nice expectation at all for a 'volunteer' take on...

hnyman · November 8, 2021, 6:38am

Well, you might be even more surprised, as this is the second-most read thread in the forum history...
https://forum.openwrt.org/latest?order=views

Measured by the reply count this is "only" the 4th:
https://forum.openwrt.org/latest?order=posts

steom · November 8, 2021, 7:53am

here some of the pearls who do not question a single one of my statements:

Do yourself a favor, it would be much better for you to use Kong build which has an adequate repository and with which you can use all software and kernel modules for a full and complete openwrt experience.

if you didn't know it and you haven't done it yet..you've lost at least three years..don't waste any more time!

jedthe3rd · November 8, 2021, 8:03am

I am new to OpenWRT so I am still trying to learn, but after reading the first post I posted my question because I didn't have an answer.
Is what I linked to the "Official" or some other build a user made that got added to the wiki. I am trying to understand why I would use this build over the "Official" build, or some other build.

jedthe3rd · November 8, 2021, 8:17am

Ya, it is a bit confusing when I am doing research and I see people say install this build, but it's from 2016 but there is a recent update. Then I have 100 questions about what's the difference between this build, the official build, and now the Kong build. I am probably just going to stick with the Official build and install software I need as I go.

jedthe3rd · November 8, 2021, 8:58am

When you say -

Does that mean the Official build doesn't have all the kernel modules for a full OpenWRT experience (what's that mean?)? I don't really care if it doesn't have all the software because I can download and install that. But if it doesn't have all the kernel modules that would require me to rebuild the firmware with the needed kernel modules, which I would rather not have to do every time I need a specific feature.

Does Kong have a forum thread talking about his build? There seems to be a discussion thread about it. Why should I trust the Kong build?

To give some perspective:
This is my journey so far -
I was buying a wifi router, I see that there is open source options for software that runs on a wifi router.
I look up what's the best wifi router to get that is compatible with the opensource firmware.
I buy that wifi router, knowing I will need more flexibility in the future.
I haven't needed features more advanced than what the stock firmware provided so I don't upgrade the firmware.
I now need more advanced features like VLAN's and LAG.
I flash the Official firmware. I see I can do VLAN's but LAG I will have to do using linux ip routing commands.
I go look and see if there are any other builds with LAG packages.
I see this one and ask what exactly is the difference between this one and the Official.

Maybe I need to spend more time in the docs to get a more holistic view of the landscape before I go and ask questions...

castiel652 · November 8, 2021, 9:58am

If you install the official build then you can simply use opkg to install everything you need until there's a new release

D43m0n · November 8, 2021, 1:44pm

No it doesn't, the official build has all the kernel modules. On community builds like these from hnyman and KONG for instance it depends on what the volunteer in question has available in time and resources to provide and maintain all kernel modules for a specific build, or just the build itself.

Exactly, if you're in the experimenting phase to find out what you exactly need, an official build might be easier get started with experimenting. However community builds like the ones from @hnyman, @KONG or @ACwifidude for instance are more tailored to the specific device, but there are slight differences which they all explain clearly in their first post in their topic, and during the topic as well.

Yes there is: KONG pro. You have to decide for yourself what you trust. Most volunteers/contributors for community builds in open source software have a reputation. They built that over the years. The ones I mentioned are very active and seem very knowledgeable. I have no reason to distrust them, but is that the same as that I trust them? A general rule I mostly use; is the source provided with a description or some sort of explanation how I can use the source and make my own modifications as I see fit? Then I see no reason for distrust. You could turn that around and say: "that means you trust the builds" but that's for everyone to decide by themselves.

This looks like the journey of 95% of the alternative firmware users I guess.

OpenWRT does VLAN's out of the box. Link aggregation is something different. I consider link aggregation for OpenWRT a niche. It's possible, because Linux has support for it, but it's not a standard functionality. One might wonder how setting up a LAG would actually be of any benefit for a device like the R7800. You would need at least 2 ports of the integrated switch of the R7800 to set up a link aggregation to another device. This means you only have 2 other ports left, besides WiFi. WiFi will not ever saturate this aggregation. You haven't mentioned what you want to achieve with a link aggregation so I'm assuming you want to create one for speed with a NAS?

Time in the docs means gathering knowledge but it may get overwhelming sometimes. Bonding has been done before on OpenWRT, but I don't know it's current state.

You could create a topic in Installing and using OpenWRT with a clear description of what you want to achieve with VLAN's and link aggregation. People will likely respond and give you an idea what's a start. Link aggregation is usually used for 3 reason's:

Increased throughput
redundancy
both

Now I'd like to add that I'm getting off topic here, this thread is about hnymans build, you asked questions, I gave some answers. I'd advise to create a topic in Installing and using OpenWRT with a clear description of what you want to achieve.

rawd · November 13, 2021, 1:39pm

I removed the DDNS support and I'd like to put it back in. What are the pre installed Hnyman DDNS packages? Thx in advance