Your reports for Broadcom units are greatly appreciated !
Router:
Firmware:
Kernel:
Status:
Reset:
Errors:
This build thread is for reporting successes and problem with loading this experimental test build. This is important info for developers and users. Always state your hardware and SPECIFIC build (e.g. 29440_NEWD-2_K2.6_mega-nv64k.bin). Do not ask questions about your specific router or how to configure it in this thread; create your own thread to discuss any specific problems you have or need resolved. Please also do not respond to such questions. This thread is to report info, not to seek it. Posts that do not add to understanding this build will be deleted. Make sure you know how to flash properly and the risk before using this build. It is important to adhere to these requirements, to keep this thread from becoming impossibly long and useless. If you don't know what build to flash and how to flash properly and have a means of recovery if things should go wrong, do NOT flash this experimental test build. _________________ Unofficial Kong's release repository : http://ddwrt-kong.clonevince.fr/
Posted: Tue May 10, 2016 19:45 Post subject: Errors on Netgear R6300v2
Previous build 29580
router Netgear R6300v2 with USB stick 64GB.
reset: no
With USB stick 64GB attached (two partitions SDA1-ext2 and OPT-ext2) into router I can't log in.
Router is not opeartional: no wifi, no internet. After removing USB stick and power off router, I can log in.
Going back to build 29580 and all is OK - no errors at all.
Posted: Tue May 10, 2016 20:04 Post subject: Re: Errors on Netgear R6300v2
alkanbw wrote:
Previous build 29580
router Netgear R6300v2 with USB stick 64GB.
reset: no
With USB stick 64GB attached (two partitions SDA1-ext2 and OPT-ext2) into router I can't log in.
Router is not opeartional: no wifi, no internet. After removing USB stick and power off router, I can log in.
Going back to build 29580 and all is OK - no errors at all.
Works fine here on a R6300V2 with a 32GB USB stick and 3 partitions including swap. Maybe you have some access restriction in place, that now works. Previous builds had broken access restrictions. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Router: Netgear R6700
Firmware: DD-WRT v3.0-r29620M kongac (05/10/16)
Kernel: Linux 3.10.101 #15 SMP Tue May 10 00:09:18 CEST 2016 armv7l
Status: OK
Reset: NO
Errors: NO
Router: Netgear R7000
Firmware: DD-WRT v3.0-r29620M kongac (05/10/16)
Kernel: Linux 3.10.101 #15 SMP Tue May 10 00:09:18 CEST 2016 armv7l
Status: OK
Reset: NO
Errors: NO
I assume reset means all settings reset which did not happen.
I almost talked myself out of posting this because my fear was that it'd be seen as complaining. So let me say, I'm NOT complaining! Just trying to understand, and for me, it's pretty much always been Kong or nothing... even back when I had the R7000 and I actually had a choice (have the R8500 now).
That said, I'm trying to understand the reason that we (the Kong gang) are "stuck" on kernel 3.10.101 when the latest (in the timeline and BS builds) is 4.4.10 and the k3 kernel is now at 3.18? Am I the only one who wonders if there have not been fixes and improvements from 3.10 to 3.18 that might be good to have? For me personally, I don't plan to update again until we're back on the 4.x kernels because I find 29200 the most responsive and stable on my R8500. And yes, I've tried a couple of the latest Kong builds with a reset and manual setup (up to but not including this one, yet): I still have problems with all but 29200.
Just wondering what we're "missing" by running on the 3.10 kernel since that alone is 8 versions old by now since 3.18 seems to be the one in the timeline, not to mention the 4.x kernels.
I almost talked myself out of posting this because my fear was that it'd be seen as complaining. So let me say, I'm NOT complaining! Just trying to understand, and for me, it's pretty much always been Kong or nothing... even back when I had the R7000 and I actually had a choice (have the R8500 now).
That said, I'm trying to understand the reason that we (the Kong gang) are "stuck" on kernel 3.10.101 when the latest (in the timeline and BS builds) is 4.4.10 and the k3 kernel is now at 3.18? Am I the only one who wonders if there have not been fixes and improvements from 3.10 to 3.18 that might be good to have? For me personally, I don't plan to update again until we're back on the 4.x kernels because I find 29200 the most responsive and stable on my R8500. And yes, I've tried a couple of the latest Kong builds with a reset and manual setup (up to but not including this one, yet): I still have problems with all but 29200.
Just wondering what we're "missing" by running on the 3.10 kernel since that alone is 8 versions old by now since 3.18 seems to be the one in the timeline, not to mention the 4.x kernels.
Just wondering.
Mike
I don't feel we are stuck nor "stuck" in anything. I don't see performance difference between BS and Kong, I have been going back and forth between these two and always get back to Kong's build, it is way more stable on my 6200.
Few months back he said that 4.4 kernel wasn't passing his tests suite that he runs.
Thanks for that: good enough for me. Just odd that I get crashes and reboots on my R8500 with the 3.10 stuff (up to and including 29580, with full reset) but never 29200 with the 4.4 kernel.
Joined: 09 Nov 2014 Posts: 314 Location: Bakersfield, CA
Posted: Wed May 11, 2016 19:15 Post subject:
I just upgraded to this build on my r7000 via "ddup --flash-latest" and so far, this build seems super solid. Faster speedtests than the previous build I was running (29440-5) over my client bridges on the same-day BS build.
It is setup as a basic gateway, no special setup, so there may be issues with features. But the basic functions seem up to par, and it stays at the same speed. No jumping around during speedtests. _________________ Deployed Routers:
Netgear R7800 - 1x build 46979
- Gateway (USB /w Entware, CAKE QoS)
Netgear R7000 - 3x build 46979
Last edited by SinCalChewy on Wed May 11, 2016 20:45; edited 1 time in total
