Build for Netgear R7800

you need to wait for this..

Just saw the commits have been ,merged. :slight_smile:
On average how long before new commits are included in builds on main opkg repo?

A few hours. Buildbot does all targets on round robin fashion.

Next arm_cortex-a15_neon-vfpv4 build should have it.

https://phase2.builds.lede-project.org/grid

1 Like

thanks :slight_smile:

lede1701-r3918-aaecfecdcd-20180707-large-flash

I made a "large-flash" version of the 17.01 build. It has the same partition structure as 18.06 and master builds (i.e. 4 MB kernel and large ubi utilising also old "netgear"), so flashing master or 18.06 can be done via sysupgrade from this 17.01 build. But naturally flashing this large flash 17.01 requires TFTP if you are still running an old 17.01 build.

This is mostly for fun, as there is no practical reason to use 17.01 with R7800 any more. 18.06 builds should be used instead.

Ps. 18.06 rc1 still had "small flash" partitions, while rc2 and final will already have the "large flash".

1 Like

OpenWrt SNAPSHOT r7427
Wireless died, had to restart both 5Ghz and 2.4Ghz.

my 7800 has been unstable off and on since the move to 4.14. sometimes it's fine for days and days, others it just randomly reboots after a few hours. it seems to come and go either with minor upgrades (everytime hnyman releases a new build). i figure there are probably some niggles still. i run the master builds.

Master has been quite stable for myself. No surprising reboots etc. that I am aware of.

A month ago I had problems with LAN speed with the build master-r7136-987e10af07-20180607-large-flash. After that I'm back to the latest build 17.01 of @hnyman. What about the new builds? Is the LAN speed ok again?

Has anyone measured the speed with iperf?

Read the R7800 exploration thread, which has lots of discussion about this.
Looks like performance was ok with kernel 4.14.44, got reduced at .48 and fixed again at .51

1 Like

yes, i retained my config from pre 4.14 so it's possible there's some weirdness going on and i should reset and manually reconfigure. i have also had the problem where nlbwmon goes crazy and maxes out at 100%, though that hasn't happened for a while.

Is the 18.06 branch >0.51 now? My slightly older one is showing 0.50. Dumb question yes, but I don't know how often kernels get changed between builds.

That can be easily seen from the 18.06 commit log.
https://git.openwrt.org/?p=openwrt/openwrt.git;a=shortlog;h=refs/heads/openwrt-18.06

.52 has been there for 10 days, and yesterday the kernel got bumped into .54

2 Likes

Has anyone got any tips for boosting performance over 5Ghz? After a fresh reboot, the router is able to deliver 350-400Mbps, but after a few minutes I can barely get 250Mbps. Not sure what's going on, or what settings to adjust. This can normally be replicated by opening the likes of speedof.me and run repeated download tests:

  1. 400+Mbps
  2. 350Mbps
  3. 300Mbps
    4)<300Mbps

It will keep dropping until it gets to around 220Mbps, at which point I need to restart the radio or router to get normal speeds again. This is a bone stock install:
image

Yeah, reboots on its own periodically for me too. Under high load especially. I am running this 18.06 r7126 and it just rebooted again.

2 Likes

can confirm this....

I'm running 18.06 R7126 and it has not rebooted by itself. It's been 2.5 days since the update.

Of course, I also have wireless disabled on this router.

owrt1806-r7144-dc52b7b104-20180715-rc2

Today's 18.06 build is pretty close to the rc2 release version being currently compiled by buildbot.

LuCI in 18.06 got major backport, as pretty much all newest changes from master were backported today to 18.06. That means that e.g. the LuCI rollback functionality is now in 18.06.

1 Like

@hnyman
Recently got a r7800 and then was introduced to your builds. When I had a wrt3200acm I ran davidc502's builds. So far everything I use it for just works with your latest master build, OpenWrt SNAPSHOT r7519-1e83f775a3 / LuCI Master (git-18.199.46142-369553c. Thanks for including the bandwidth monitor, at least I am guessing this is not part of the LEDE base. Comes in handy at times.

What I need to do is take the HP laptop that I have decommissioned and install Linux and follow your steps so that I can experiment more with builds. Have always had this bad picture in my head of creating a build that turns the router into a permanent door stop. :wink:
--bill

@hnyman I just got myself a R7800 and flashed owrt1806-r7144-dc52b7b104-20180715-rc2 on.

After some head scratching and command line hacking I believe I found some bug, which I also was able to reproduce multiple times.

As you know the router comes with 192.168.1.1 set by default. My home network, however, is at 192.168.0.x. So bringing the device into the 0.x range doesn't as work as you might expect (neither via static IP, nor via DHCP): When setting a static IP for the router, say 192.168.0.3, the configuration gets applied (popup appears), and then: nothing. The router does not show up in the 0.x range. With some luck I discovered that LUCI does a configuration rollback, which was hidden to me, as the "apply configuration" dialog was shown using the new IP (192.168.0.3) already. My browser, however, is still in the 1.1 subnet.
The rollback dialog shows up with "Failed to confirm apply within 30s, waiting for rollback…".

So, am I doing something wrong here, or is this a (serious) bug?

Thanks!