Build for Netgear R7800

Spoke too soon. mac80211 crashed, same trace as reported before. Didn't take the device down, it recovered from it.

[60521.528498] ------------[ cut here ]------------
[60521.528604] WARNING: CPU: 0 PID: 767 at backports-5.8-rc2-1/net/mac80211/sta_info.c:1929 ieee80211_sta_update_pending_airtime+0x1f8/0x1fc [mac80211]
[60521.532185] STA xxxx AC 2 txq pending airtime underflow: 4294967248, 48
...

https://bugs.openwrt.org/index.php?do=details&task_id=3204

googling on the error shows that non-openwrt devices (general linux systems) also suffer from the same issue. I think it's something that will need to be fixed upstream, not something that Felix can repair himself.

Indeed. I was just hoping an update of mac80211 to 5.8 would have a fix for it, but it did not.

Just upgraded from hnyman 19.07 to latest trunk build...all good!
thxs for your hard work

1 Like

I have added "irqbalance" at the topmost portion of the /etc/rc.common file, as the first command, right under the "# Copyright (C) 2006-2012 OpenWrt.org"

Is this ideal? Sorry, I'm also a noob as well.

You do not need that, just make sure the irqbalance service is enabled on system/startup page in the web interface. But in the past I suspected irqbalance to cause issues, personally I keep it disabled and just manually move a couple of IRQs in /etc/rc.local

# Manual IRQ affinity (cat /proc/interrupts)
# IRQ31=eth0, IRQ32=eth1
# 1=CPU0, 2=CPU1
echo 2 > /proc/irq/31/smp_affinity
echo 2 > /proc/irq/32/smp_affinity

hostpad/80211 seems to have issues with the inactivity timer. I see disconnects in the log from devices that are clearly active:

Sun Aug  2 08:49:39 2020 daemon.info hostapd: wlan0: STA 10:xxx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Aug  2 10:15:09 2020 daemon.info hostapd: wlan0-1: STA 38:xxx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

I know there's some option to disable it, just saying I didn't have to in the past.

The recent mac80211 and hostapd updates seem to be causing some wifi instability :frowning:

How is this load balancing if you are moving both to the same cpu? I only moved one and left the other as is...is that not right?
thxs

**edit..oh wait, forgot about wireless....so moving wan to cpu1 and that leaves wlan on eth0?

1 Like

You can cat /proc/interrupts and see how the IRQs are distributed. Unfortunately we can't move IRQs 45 and 46 ath10k_pci.

Yes I know that....but just trying to understand, should I move both eth over to same cpu or like I previously said, move just one eth over?

These might be better threads for these types of questions:
https://forum.openwrt.org/t/r7800-performance/15780
https://forum.openwrt.org/t/netgear-r7800-exploration-ipq8065-qca9984/285

When upgrading to build 14023 the R7800 power LED started flashing orange and it didn't come back up after flashing like it normally does when upgrading to a new build. Powering off and back on manually got it going.

I've seen cases too when I reboot it from the command line it doesn't come back up, it restarts but can't connect to it. I have to pull the power.

1 Like

I want to use nfs, uas and f2fs but can't use the kmods from opkg because of different kernel versions. The version is actually the same but the checksum is different. Do I need to create my own build to make this work? I tried using --force-depends when installing the nfs kmod and it hard crashed the router. Had to use the reset button on the back.

Yes, you need your own build if you want to install kernel kmods. The checksum check is there for a reason, just like you noticed. Just build you own version with the needed kmods included.

(Or alternatively, you can use the official release 19.07.3 builds.)

1 Like

If transferring from official release builds to your builds (and vice versa), which one do we flash? The one from your builds labeled *factory.img or *sysupgrade.bin

Sysupgrade, naturally.

  • Sysupgrade image is used to upgrade from a running OpenWrt via sysupgrade
  • Factory image is used to upgrade from a running OEM firmware or using OEM bootloader's TFTP flash routine (or similar recovery tool). So the image needs to match OEM expectations...

That holds true to >95% of routers.

2 Likes

How can I open the UPNP in your newest vision?I tried,but it didn't work.

This fix looks promising

You need to set upnp "enabled" first. Use LuCI to toggle the config setting or manually edit /etc/config/upnpd first by toggling "enabled from 0 to 1 (and restart the service):

root@router1:~# cat /etc/config/upnpd
config upnpd config
        option enabled          0
        option enable_natpmp    1
        option enable_upnp      1
        option secure_mode      1
        option log_output       0
...