DD-WRT :: View topic - New Kong build: DD-WRT v3.0-r31205M (02/03/17)

New Kong build: DD-WRT v3.0-r31205M (02/03/17)

DD-WRT Forum Index -> Broadcom SoC based Hardware

Goto page Previous 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 Next

View previous topic :: View next topic

Author

Message

<Kong>
DD-WRT Guru

Joined: 15 Dec 2010
Posts: 4339
Location: Germany

Posted: Tue Feb 14, 2017 18:34 Post subject:

xlr8r wrote:

Alozaros wrote:

to be hones and kill all doubts do what you ware suggested
1. erase nvram via putty
2. post results from - nvram show
3. rebuild manually

my doubts are either win 10 is playing a dodge trick if you use it at all or bad/corrupt nvram witch is so wired...
Personally i did 2 times manual erase nvram and rebuild on this last firmware and no problems with erase at all at all..well i could see bad erase nvram block in syslog but this is something normal and usually the system is not using those blocks for info...
also please post witch version is your R7000 they are 2 or 3 so far on the market.....

thanks, i will give it all another go later tonight;
(but i have done this all 3 times now barr opt 2.)

I cant verify any stickers on the bottom of the router as im at work, but remotely connecting to it , I can say;
my router is ;
CPU Model
Broadcom BCM4709
CPU Cores 2
CPU Clock 1000 MHz
Load Average 2%
0.02, 0.08, 0.02
CPU Temperature CPU 55.2 °C / WL0 45.0 °C / WL1 48.0 °C

its prob a v1 as i got it when they first came out...

ps. i tried your option 2. above (via remote access) but got no result/response from router..? (I presume the results pop up in a separate window and this doesn't happen remotely?)
I guess I have to do this from home ...

Getting all sorts of errors in syslog;

Feb 14 13:42:11 NETGEAR kern.err kernel: (detected by 0, t=114032 jiffies, g=6301, c=6300, q=64781)
Feb 14 13:42:11 NETGEAR kern.info kernel: Task dump for CPU 1:
Feb 14 13:42:11 NETGEAR kern.info kernel: wland R running 0 1766 1 0x00000002
Feb 14 13:42:11 NETGEAR kern.warn kernel: Backtrace:
Feb 14 13:42:11 NETGEAR kern.warn kernel: [<80014074>] (__schedule) from [<80014520>] (schedule+0x88/0x98)
Feb 14 13:42:11 NETGEAR kern.warn kernel: r10:8607bed0 r9:8607beec r8:7e11d600 r7:00000003 r6:0000c350 r5:00000001
Feb 14 13:42:11 NETGEAR kern.warn kernel: r4:8607a000
Feb 14 13:42:11 NETGEAR kern.warn kernel: Backtrace aborted due to bad frame pointer <8007de54>
Feb 14 13:45:11 NETGEAR kern.err kernel: INFO: rcu_sched detected stalls on CPUs/tasks:
Feb 14 13:45:11 NETGEAR kern.err kernel: 1-...: (1 GPs behind) idle=367/140000000000000/0 softirq=27780/27781 fqs=131959
Feb 14 13:45:11 NETGEAR kern.err kernel: (detected by 0, t=132037 jiffies, g=6301, c=6300, q=67307)
Feb 14 13:45:11 NETGEAR kern.info kernel: Task dump for CPU 1:
Feb 14 13:45:11 NETGEAR kern.info kernel: wland R running 0 1766 1 0x00000002
Feb 14 13:45:11 NETGEAR kern.warn kernel: Backtrace:
Feb 14 13:45:11 NETGEAR kern.warn kernel: [<80014074>] (__schedule) from [<80014520>] (schedule+0x88/0x98)
Feb 14 13:45:11 NETGEAR kern.warn kernel: r10:8607bed0 r9:8607beec r8:7e11d600 r7:00000003 r6:0000c350 r5:00000001
Feb 14 13:45:11 NETGEAR kern.warn kernel: r4:8607a000
Feb 14 13:45:11 NETGEAR kern.warn kernel: Backtrace aborted due to bad frame pointer <8007de54>
Feb 14 13:48:11 NETGEAR kern.err kernel: INFO: rcu_sched detected stalls on CPUs/tasks:
Feb 14 13:48:11 NETGEAR kern.err kernel: 1-...: (1 GPs behind) idle=367/140000000000000/0 softirq=27780/27781 fqs=149945
Feb 14 13:48:11 NETGEAR kern.err kernel: (detected by 0, t=150042 jiffies, g=6301, c=6300, q=71264)
Feb 14 13:48:11 NETGEAR kern.info kernel: Task dump for CPU 1:
Feb 14 13:48:11 NETGEAR kern.info kernel: wland R running 0 1766 1 0x00000002
Feb 14 13:48:11 NETGEAR kern.warn kernel: Backtrace:
Feb 14 13:48:11 NETGEAR kern.warn kernel: [<80014074>] (__schedule) from [<80014520>] (schedule+0x88/0x98)
Feb 14 13:48:11 NETGEAR kern.warn kernel: r10:8607bed0 r9:8607beec r8:7e11d600 r7:00000003 r6:0000c350 r5:00000001
Feb 14 13:48:11 NETGEAR kern.warn kernel: r4:8607a000
Feb 14 13:48:11 NETGEAR kern.warn kernel: Backtrace aborted due to bad frame pointer <8007de54>
Feb 14 13:51:11 NETGEAR kern.err kernel: INFO: rcu_sched detected stalls on CPUs/tasks:
Feb 14 13:51:11 NETGEAR kern.err kernel: 1-...: (1 GPs behind) idle=367/140000000000000/0 softirq=27780/27781 fqs=167933
Feb 14 13:51:11 NETGEAR kern.err kernel: (detected by 0, t=168047 jiffies, g=6301, c=6300, q=83301)
Feb 14 13:51:11 NETGEAR kern.info kernel: Task dump for CPU 1:
Feb 14 13:51:11 NETGEAR kern.info kernel: wland R running 0 1766 1 0x00000002
Feb 14 13:51:11 NETGEAR kern.warn kernel: Backtrace:
Feb 14 13:51:11 NETGEAR kern.warn kernel: [<80014074>] (__schedule) from [<80014520>] (schedule+0x88/0x98)
Feb 14 13:51:11 NETGEAR kern.warn kernel: r10:8607bed0 r9:8607beec r8:7e11d600 r7:00000003 r6:0000c350 r5:00000001
Feb 14 13:51:11 NETGEAR kern.warn kernel: r4:8607a000
Feb 14 13:51:11 NETGEAR kern.warn kernel: Backtrace aborted due to bad frame pointer <8007de54>
Feb 14 13:54:11 NETGEAR kern.err kernel: INFO: rcu_sched detected stalls on CPUs/tasks:
Feb 14 13:54:11 NETGEAR kern.err kernel: 1-...: (1 GPs behind) idle=367/140000000000000/0 softirq=27780/27781 fqs=185935
Feb 14 13:54:11 NETGEAR kern.err kernel: (detected by 0, t=186052 jiffies, g=6301, c=6300, q=100069)
Feb 14 13:54:11 NETGEAR kern.info kernel: Task dump for CPU 1:
Feb 14 13:54:11 NETGEAR kern.info kernel: wland R running 0 1766 1 0x00000002
Feb 14 13:54:11 NETGEAR kern.warn kernel: Backtrace:
Feb 14 13:54:11 NETGEAR kern.warn kernel: [<80014074>] (__schedule) from [<80014520>] (schedule+0x88/0x98)
Feb 14 13:54:11 NETGEAR kern.warn kernel: r10:8607bed0 r9:8607beec r8:7e11d600 r7:00000003 r6:0000c350 r5:00000001
Feb 14 13:54:11 NETGEAR kern.warn kernel: r4:8607a000
Feb 14 13:54:11 NETGEAR kern.warn kernel: Backtrace aborted due to bad frame pointer <8007de54>

How did you configure wireless, Client/Repeater, VAPs?
_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/

Sponsor

xlr8r
DD-WRT Novice

Joined: 07 May 2014
Posts: 33

Posted: Wed Feb 15, 2017 11:00 Post subject:

<Kong> wrote:

xlr8r wrote:

Alozaros wrote:

How did you configure wireless, Client/Repeater, VAPs?

well.. i have reverted back to Firmware: DD-WRT v3.0-r30700M kongac (09/27/16) and am having NO issues whatsoever so i will just keep it in that for now. cheers

kallsop
DD-WRT User

Joined: 10 Apr 2008
Posts: 135

Posted: Wed Feb 15, 2017 12:42 Post subject:

Locked up solid after approx. 4 days uptime. 2.4G wireless dead, Guest on 2.4G dead, 5G dead. No wired connections, don't know if they still worked. I'll have to look into adding a USB memory stick and logging to that, so I can reboot and look to see what happened before the reboot.

EDIT: forgot to mention, when the WiFi dies, the watchdog doesn't trip ...

WDS/Connection Watchdog
Enable Watchdog Enable
Interval (in seconds) 600
IP Addresses 8.8.8.8

spatmur
DD-WRT Novice

Joined: 19 Aug 2016
Posts: 16
Location: United States of Denial

Posted: Thu Feb 16, 2017 19:38 Post subject:

Router: Netgear R7000
Firmware: DD-WRT v3.0-r31205M kongac (02/03/17)
Kernel: Linux 4.4.45 #248 SMP Fri Feb 3 11:11:57 CET 2017 armv7l
Status: Working
Reset: Yes, erase nvram and reconfigure
Previous: 30645
Errors: None

Up for three days with zero issues. Acting as wireless access point only,
with guest network setup on the horizon.

Thanks for all the great work, Kong!

-Edited to correct Previous firmware version

two4six
DD-WRT Novice

Joined: 17 Mar 2011
Posts: 16

Posted: Thu Feb 16, 2017 20:46 Post subject:

Router: Netgear R7000
Firmware: DD-WRT v3.0-r31205M kongac (02/03/17)
Kernel: Linux 4.4.45 #248 SMP Fri Feb 3 11:11:57 CET 2017 armv7l
Status: Working
Reset: Yes, erase nvram and reconfigure
Previous: 30645
Errors: None
RX errors: 23106728 OK, no error
TX errors: 27620425 OK, 391 errors

Up for twelve days with no issues. Acting as wireless access point 2.4ghz and 5ghz. Only settings besides normal wireless is USB core on (powering netbook fan under r7000). So far so good...

Thanks for all the great work Kong and BS!

johns8
DD-WRT Novice

Joined: 17 Feb 2017
Posts: 8

Posted: Fri Feb 17, 2017 12:35 Post subject:
If anybody has recompiled switch_robo.ko kernel module for R7000 on kong dd-wrt kernel 4.4, please share it. My ppoe internet connection need vlan-id id 20 thanks in advance. John

ScottSee
DD-WRT Novice

Joined: 09 Feb 2017
Posts: 8

Posted: Fri Feb 17, 2017 18:52 Post subject:

ScottSee wrote:

egc wrote:

First set 20MHz choose channel 52 then set 40 MHz, it will revert back to auto , toggle lower/upper and save and then you can choose a channel again choose 52 upper Smile

Ok I'll try that tonight.

Thanks

Okay so even after switching to 52+upper I'm seeing VHT80 clients (which shouldn't happen, right?) and loosing 5Ghz after a random interval.

I tried to roll back to an older KANG (30700 and 30910) and wifi was stable but now it's rebooting every 30 minutes to 12 hours. I didn't have time to erase nvram and start over from scratch so I'll try that this weekend.

<Kong>
DD-WRT Guru

Joined: 15 Dec 2010
Posts: 4339
Location: Germany

Posted: Fri Feb 17, 2017 22:40 Post subject:

johns8 wrote:

If anybody has recompiled switch_robo.ko kernel module for R7000 on kong dd-wrt kernel 4.4, please share it. My ppoe internet connection need vlan-id id 20

thanks in advance.

John

I'm also on pppoe, I need vlan id 7, but I do not need to set anything in my router, because I use a Vigor 130 modem, which handles the vlan tagging while still running in bridge mode.
_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/

howard30
DD-WRT Novice

Joined: 07 Mar 2014
Posts: 33

Posted: Sat Feb 18, 2017 3:17 Post subject:
It seems there are a lot of TX transmission errors. On my R8000 (did erase nvram after upgrading), after 4 days running, I have wl0 Transmitted (TX) 1016472 OK, 52165 errors wl1 Transmitted (TX) 973871 OK, 2117 errors wl2 Transmitted (TX) 2072985 OK, 98039 errors So transmission error rates are about 4-5% on 5Ghz channels. Old firmware didn't have such large TX error rate.

johns8
DD-WRT Novice

Joined: 17 Feb 2017
Posts: 8

Posted: Sat Feb 18, 2017 7:25 Post subject:

<Kong> wrote:

johns8 wrote:

If anybody has recompiled switch_robo.ko kernel module for R7000 on kong dd-wrt kernel 4.4, please share it. My ppoe internet connection need vlan-id id 20

thanks in advance.

John

I'm also on pppoe, I need vlan id 7, but I do not need to set anything in my router, because I use a Vigor 130 modem, which handles the vlan tagging while still running in bridge mode.

Thank you Kong for fast responding. Greatly appreciated.

I don’t use a separate modem and R7000 is used to dial the ppoe. Currently I use the recompiled switch_robo(vlan id up to 127) on DD-WRT v3.0-r29300M kongac(04/14/16). I would like to upgrade it to new firmware which use kernel 4.4, but it doesn't support vlad-id on wan interface. If you don’t mind, could you please provide a recompiled switch_robo.ko module with vlan id. It will be helpful for many.

Thank you again.

John

<Kong>
DD-WRT Guru

Joined: 15 Dec 2010
Posts: 4339
Location: Germany

Posted: Sat Feb 18, 2017 16:03 Post subject:

johns8 wrote:

<Kong> wrote:

johns8 wrote:

If anybody has recompiled switch_robo.ko kernel module for R7000 on kong dd-wrt kernel 4.4, please share it. My ppoe internet connection need vlan-id id 20

thanks in advance.

John

I'm also on pppoe, I need vlan id 7, but I do not need to set anything in my router, because I use a Vigor 130 modem, which handles the vlan tagging while still running in bridge mode.

The previous precompiled ko was provided by a user that did not submit the patch, otherwise it would by already included in the builds.
_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/

ddaniel51
DD-WRT Guru

Joined: 19 Feb 2013
Posts: 1464

Posted: Sat Feb 18, 2017 19:43 Post subject:

Get a smart switch like a NETGEAR ProSAFE GS105Ev2 to manage your vlan id and tagging on a couple of ports between the router and modem. With this you can use any of Kong's builds.

I use 4 ports in a vlan from my 20 port switch to connect 3 router WAN ports to my modem.

johns8 wrote:

<Kong> wrote:

johns8 wrote:

If anybody has recompiled switch_robo.ko kernel module for R7000 on kong dd-wrt kernel 4.4, please share it. My ppoe internet connection need vlan-id id 20

thanks in advance.

John

I'm also on pppoe, I need vlan id 7, but I do not need to set anything in my router, because I use a Vigor 130 modem, which handles the vlan tagging while still running in bridge mode.

_________________
Segment 1 XR700 10Gb LAN, 1Gb WAN ISP BS
Wired AP 1 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 2 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 3 Unifi Wifi 6 LR US 1Gb LAN
Syslog Services Asustor 7110T NAS 10GB
NetGear XS716T 10GB Switch
download1.dd-wrt.com/dd-wrtv2/downloads/betas/ (Brain Slayer)
YAMon https://usage-monitoring.com/index.php

DRAGO.NET
DD-WRT Novice

Joined: 08 Oct 2016
Posts: 14

Posted: Sat Feb 18, 2017 22:27 Post subject: this firmware can not be used on Buffalo Wzr_d1800h?
this firmware can not be used on Buffalo Wzr_d1800h?

ddaniel51
DD-WRT Guru

Joined: 19 Feb 2013
Posts: 1464

Posted: Sat Feb 18, 2017 23:53 Post subject: Re: this firmware can not be used on Buffalo Wzr_d1800h?

DRAGO.NET wrote:

this firmware can not be used on Buffalo Wzr_d1800h?

Build dd-wrt.v24-K3_AC_ARM_STD.bin supports:
#################################################
ASUS_AC56U
ASUS AC67U
ASUS AC68U

BUFFALO WZR900DHP
BUFFALO WZR1750
BUFFALO WXR1900DHP

DLINK DIR868
DLINK DIR860
DLINK DIR880

LINKSYS EA6350
LINKSYS EA6400
LINKSYS EA6700
LINKSYS EA6900

NETGEAR AC1450
NETGEAR R6250
NETGEAR R6300V2
NETGEAR R7000
#################################################

Build dd-wrt.v24-K3_AC_ARM_STD_128K.bin supports:
#################################################
NETGEAR R6400
#################################################

Build dd-wrt.v24-K3_AC_ARM_R8000.bin supports:
#################################################
Asus AC3200

DLINK DIR885
DLINK DIR890

Netgear R8000
#################################################

Build dd-wrt.v24-K3_AC_ARM_R8500.bin supports:
#################################################
Netgear R8500
#################################################

Note:

- *.bin files can only be flashed from dd-wrt webif.
- *.chk can be flashed from Netgear factory fw and from dd-wrt webif

- I don't provide factory to dd-wrt for non Netgear models
since I do not own any non Netgear Broadcom units

All builds include ddup util, which allows update checking
and flashing of the following models:

Netgear EX6200
Netgear AC1450
Netgear R6250
Netgear R6300V2
Netgear R6400
Netgear R7000
Netgear R8000
Netgear R8500
Asus RT-AC68R
Asus RT-AC68U
Asus RT-AC56U
Asus RT-AC3200
Asus RT-AC5300
Buffalo WXR-1900DHP
Linksys EA6900
Linksys EA6700
_________________
Segment 1 XR700 10Gb LAN, 1Gb WAN ISP BS
Wired AP 1 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 2 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 3 Unifi Wifi 6 LR US 1Gb LAN
Syslog Services Asustor 7110T NAS 10GB
NetGear XS716T 10GB Switch
download1.dd-wrt.com/dd-wrtv2/downloads/betas/ (Brain Slayer)
YAMon https://usage-monitoring.com/index.php

Tarv
DD-WRT Novice

Joined: 08 Oct 2007
Posts: 47
Location: Winnipeg, MB

Posted: Sun Feb 19, 2017 2:07 Post subject:

Still having issues with new builds, 30880 running solid. I posted in a previous topic last time I tried.

Router: R7000
Firmware: 30880 -> 31205
Previously tried Firmware: 30880 -> 31085 -> 31100
Status: Intermittent hard lock
Reset: YES -> ddup with power cycle -> erase nvram with power cycle

This morning I did a ddup from the 30880 to this build. 30880 was showing 47 days of uptime, for reference. I updated, power cycled and waited.

Within an hour the unit hard locked, lost network connectivity and could not access the router. Had to power cycle to bring it back up.

I did a erase nvram to go back to factory, then manually set everything back up. When done, I power cycled again and waited.

Just now, the router was locked up as before. Had to power cycle. Flashed back to 30880 again as unfortunately I don't have time to test further with the possibility of losing my network.

Something changed between 30880 and 31085 that is causing this issue for me.

Is there something I can do to log what is happening?

I'll list some features I'm using that might not be standard. Basically this is what I enabled or changed after the factory reset:
- ntp server is set
- ddns with dyndns
- advanced routing, two static routes
- wireless using both radios, plus one guest network, unbridged with it's own dhcp
- static leases, 56 are set
- dnsmasq with local dns
- secure shell enabled
- zabbix client enabled
- port forwarding, 27 are set
- port range fwd, 3 are set
- qos enabled, htb fq_codel, 10 services set, 2 netmasks set
- ip filter set to westwood, tcp timeout decreased to 300
- custom firewall forcing some routing for dns and a local static route
_________________
Switched to UniFi

Goto page Previous 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 Next

Display posts from previous:

Page 8 of 10

DD-WRT Forum Index -> Broadcom SoC based Hardware

All times are GMT

Navigation

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum

Log in

New Kong build: DD-WRT v3.0-r31205M (02/03/17)

Quick Links

Log in