Build for Netgear R7800

How to revert to orginal firmware once we are in lEDE if things dont go well.

Using the OEM TFTP recovery mode is the easy way to revert to Netgear firmware.

Hnyman,

Thanks. Just wanted few more before i flash. the stock works fine but when i upgrade to V4 database of qos it get crashed. Voxel believes it could be V4 database problem or Hardware problem.

I dont know which is causing the crash. But the router works perfectly fine when it is in V2.0 database.

I dont know if the LEDE support such QOS.

I am having 100/5 Mbps connection download and upload.

I do wanted to know if there is similar qos . Is there any traffic analayzer package available which keep additional traffic data like individual devices data consumption.

Does LEDE also support secure Remote web management and VPN as a client or server for home access.

It would be great in near future the LEDE have a mobile app to access and control both locally and remotely.

Was this normal default stock r7800 partition of flash layout.

You are again hijacking this build-specific thread for generic questions.
Never heard about QoS v4 database...
Your questions are related to general LEDE features. Just browse the forum and wiki and you will find suitable packages.
SQM, openvpn, vnstat, luci-statistics ...

I have been losing wifi access lately.
I am not sure when it started but since the last builds it happens within 24 hours.

The only thing in my kernel log is this:
[46645.621937] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead.
[101198.237888] ath10k_pci 0001:01:00.0: rx ring became corrupted: -5

the ap isnt visible to any device.
I am on LEDE Reboot SNAPSHOT r4173-5d48dc1146
i reset the settings to default to rule out any old settings causing it.

I just toggled wifi on and off and i got this log:

https://pastebin.com/kqMpHJHn

the entire wifi stack crashed a bit later, here is the log

https://pastebin.com/5KA7tBWu

I have not seen similar wifi crashes. If it continues, please file a bug in https://bugs.lede-project.org

The "nf_conntrack: default automatic helper" message is normal. Rather similar warning has been there for years, but the wording changed recently when Linux kernel / netfilter developers really turned the automatic helpers off.

Hi @hnyman

Thanks for making the binaries available. I TFTPed you latest build into a newly bought R7800 and am facing some issues.

Basically, my device does not boot (keeps blinking white power-up led) if I have any of the ethernet cables attached to it (lan or wan). The only way to boot my device (with your binaries) seems to be to detach all cables and then power-up. After that I can connect the cables and things work well till the next power up cycle. Since I power down the router every evening, this is not a practically workable situation for me.

Is it the normal behavior that my R7800 is showing? Can it be changed by some configuration so that power up can be done with cables in place.

Thanks

  • Puneet

[quote="puneet, post:170, topic:316"]
Basically, my device does not boot (keeps blinking white power-up led) if I have any of the ethernet cables attached to it (lan or wan).
...
Is it the normal behavior that my R7800 is showing?
[/quote]Sounds strange.
Never heard about similar problem with R7800 before.

i opened a bug report here https://bugs.lede-project.org/index.php?do=details&task_id=801

What if you delete the patch that decreases buffers

If @hnyman can kindly make a build with that removed i can test it


Config.seed and manifest are inside of it
Built off https://github.com/dissent1/r7800/commits/sta34

hnyman I managed to use your build environment and make the DTS file changes (that you and Wally discussed) to get 76.42MB of space for packages and added MiniDLNA, OpenVPN and Samba in the build menu. First time compiling and it went well thanks to all you guys here. One thing I noticed after the DTS edit is that the root filesystem is read only and any post install changes like replacing the pci-calibration files have to be made via the /overlay folder, which is not a major issue.

Also just out of curiosity is there a reason the QCA9884 wireless firmware is also installed along side the QCA9984 in your 17.01 builds, I took out the former, when compiling.

1 Like

I think that you have just discoveres the standard LEDE/Openwrt feature that enables easy reset to post-flash conditions (with "firstboot" command). All changes are done to /overlay while /rom remains untouched. And overlayfs shows them together seamlessy as a combined /.

As you can see from my changes & config, it is not my selection. For this kind of general questions, please look at the source code changes in LEDE & packages... The reason is the earlier bulky handling of ath10k firmwares, which was polished in March (after 17.01 had already been branched off, so the error is still in 17.01).
https://git.lede-project.org/?p=source.git;a=commit;h=e3c88f49648c92e83cb0075ee3d2f744700ff511

1 Like

Like I already commented this is in the main source. But it looks like a valid change done for master that should be backported also to 17.01. The official 17.01.2 will likely be released in 1-2 weeks, so I proposed to @jow that this change could be backported to 17.01 branch before the release:
https://www.mail-archive.com/lede-dev@lists.infradead.org/msg07699.html

I already did the change manually in my own 17.01 build.
Thanks for bringing this to my attention.

Thanks for the information and all your all help so far. :slight_smile:

@hnyman @dissent1

I flashed dissent1's build to test, I should have the results in 24 hours.

I noticed however that my kernel bootup log is full of errors and warnings. Are these normal?
See paste here: https://pastebin.com/yThmTtJN

At the first glance I spot nothing special.

If you are trying different builds, you should copy and save kernel logs and system logs from the different builds, so that you can compare them by yourself.