XVortex, this is like a christmass present !!!!
You rock !
Just put your new CFE with my macs and pass.
If I have time in the future I will try stock FW.
But I report that all I tested is working fine so far !
Thanks a lot buddy!
Reboot the router, enter recovery, clear nvram, upload firmware...
Well, I seem to have buggered myself up here.
I have working CFE, because I get TTL=100 responses during boot. I can TFTP firmware during that time (I've tried stock, various levels of DD-WRT, the ASUS Merlin and Tomato you provided) but now I can't get any OS to run. It boots, TTL=100 for 30-45 sec then when the light goes solid the pings stop. I never get to a TTL=64. I've tried clearing the NVRAM via a 30 sec reset, but no go.
I've tried clearing the NVRAM via a 30 sec reset, but no go.
Once you switch from the Linksys CFE to the Asus CFE, the clear-nvram procedure changes from requiring you to hold the reset button to the requiring you to hold the wps button instead.
Another way with the Asus CFE is to power on while holding the reset button. This will boot into recovery mode, which provides a web page where you can clear nvram and/or upload a new image.
And idea on how to re flash CFE if you can't get an OS to start (TTL=64)?
I'm stuck at TTL=100 for 90 sec then no communication, no ping, no radio.
Thanks,
Stephen
When I first migrated to Asus CFE, I had something like this. But I was able to get to the recovery page and send the Firmware. Try to reset all again, turn it on for a while, checking the ping ....
Oh, mea culpa, sorry!
Forget to change some nvram Asus parameters to Linksys.
Here is the fixed CFE. Don't forget to edit your macs/pw again!
Hi XVortex,
For my understanding and confirm that we have as someone said before a Xmas present in March.
I'm having the AC68U CFE that it works, but with ramdon reboots with the 23900.
So with your CFE it's a kind of brand new one like an original without problems on where we can run the EA6900 DD-WRT software rather than the Asus one ?
Let's put it that way: it will be like EA6900 2.0 CFE ?
I'm just in shock, because I wasn't expecting no one else taking care of this model anymore.
If so you are for sure the one that make me and a couple of collesgues that bought the router with my same problem the most happiest persons in Barcelona.
Many thanks and I hope you did it...
Best regards. _________________ 7 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v3.0-r31899 giga (04/24/17)
1 x Marvel Armada 385 - LinkSys WRT1900ACS ---------> v3.0-r31899 std (04/24/17)
1 x Marvel Armada 370/XP - LinkSys WRT1900AC -------> v3.0-r31899 std (04/24/17)
1 x QCA IPQ806X - Linksys EA8500 -------------------> v3.0-r31899 std (04/24/17)
1 x Broadcom BCM4709 - Asus RT-AC3200 --------------> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Asus RT-AC68U ----> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Linksys EA6900 ---> v3.0-r30880 std (11/14/16)
1 x ARM Cortex-A9 Processor - Net Gear R7000 -------> v3.0-r30880 std (11/14/16)
5 x Broadcom BCM4716 chip rev 1 - Linksys E4200 ----> v24-sp2 (06/07/14) kingkong
1 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v24-sp2 (04/01/13) giga
I'm having the AC68U CFE that it works, but with ramdon reboots with the 23900.
I think is reboots are not due to Asus or wrong CFE.
Bronk-S wrote:
So with your CFE it's a kind of brand new one like an original without problems on where we can run the EA6900 DD-WRT software rather than the Asus one ?
Yes, at least. Also You can run my Tomato for EA6900 or even my AsusWRT-Merlin (XWRT or CrossWRT). AsusWRT is rock-solid on EA6900!
I'm having the AC68U CFE that it works, but with ramdon reboots with the 23900.
I think is reboots are not due to Asus or wrong CFE.
Bronk-S wrote:
So with your CFE it's a kind of brand new one like an original without problems on where we can run the EA6900 DD-WRT software rather than the Asus one ?
Yes, at least. Also You can run my Tomato for EA6900 or even my AsusWRT-Merlin (XWRT or CrossWRT). AsusWRT is rock-solid on EA6900!
Hi XVortex,
Many thanks for this and I did it, just did a copy of my current CFE, changed the MACs and password and later install it. (my MACs since I did the change of the standard CFE to the Asus one I just lost this information...) Here is a post on where I put this information, but I'm not sure what is what, so I don't want to create a big mes...
Then since I did this my USB 3.0 literally stopped to work, nothing that is connected there it works, neither a 3G stick, pen-drive or HDD.
Not sure if the random reboots are related to the CFE, you said that isn't the case, but I will try and see, but this item of the USB 3.0 is a really annoying one.
Many thanks in any case I will let you know now in some days how it goes.
Best regards. _________________ 7 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v3.0-r31899 giga (04/24/17)
1 x Marvel Armada 385 - LinkSys WRT1900ACS ---------> v3.0-r31899 std (04/24/17)
1 x Marvel Armada 370/XP - LinkSys WRT1900AC -------> v3.0-r31899 std (04/24/17)
1 x QCA IPQ806X - Linksys EA8500 -------------------> v3.0-r31899 std (04/24/17)
1 x Broadcom BCM4709 - Asus RT-AC3200 --------------> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Asus RT-AC68U ----> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Linksys EA6900 ---> v3.0-r30880 std (11/14/16)
1 x ARM Cortex-A9 Processor - Net Gear R7000 -------> v3.0-r30880 std (11/14/16)
5 x Broadcom BCM4716 chip rev 1 - Linksys E4200 ----> v24-sp2 (06/07/14) kingkong
1 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v24-sp2 (04/01/13) giga
Then since I did this my USB 3.0 literally stopped to work, nothing that is connected there it works, neither a 3G stick, pen-drive or HDD.
Have you tried the "gpio10=usbport2" setting?
Hi p120ph37,
Yes I did after your post or I hope I understood this well...
I did :
nvram set gpio10=usbport2
nvram commit
reboot
Same results nothing changed, but I saw my problem and it's regarding the boardtype.
If I'm using the EA6900 model doesn't work, but if I'm using the AC68U it does, but as you know after set the boardtype like this it changes the information of the router to Asus AC68U.
Then.. Any other suggestion ?
I'm not now in front of the computer, but if other possibility is to add/edit the gpio item in the CFE happy to test.
Many thanks for your close support.
Best regards. _________________ 7 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v3.0-r31899 giga (04/24/17)
1 x Marvel Armada 385 - LinkSys WRT1900ACS ---------> v3.0-r31899 std (04/24/17)
1 x Marvel Armada 370/XP - LinkSys WRT1900AC -------> v3.0-r31899 std (04/24/17)
1 x QCA IPQ806X - Linksys EA8500 -------------------> v3.0-r31899 std (04/24/17)
1 x Broadcom BCM4709 - Asus RT-AC3200 --------------> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Asus RT-AC68U ----> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Linksys EA6900 ---> v3.0-r30880 std (11/14/16)
1 x ARM Cortex-A9 Processor - Net Gear R7000 -------> v3.0-r30880 std (11/14/16)
5 x Broadcom BCM4716 chip rev 1 - Linksys E4200 ----> v24-sp2 (06/07/14) kingkong
1 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v24-sp2 (04/01/13) giga
Just to comment on regular reboots. This issue has nothing to do with CFE and happens on both Linksys and Asus CFE. It is now well established that the problem is because of the buggy Broadcom driver. In approximately mid-January BrainSlayer got access to a new version of the driver and the problem is fixed now - there is a special thread about that: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=278372
I used to have constant reboots upon connection of a particular WiFi client (iPhone 4S, by the way ), but now my router is absolutely stable - one month of uptime already.
Just to comment on regular reboots. This issue has nothing to do with CFE and happens on both Linksys and Asus CFE. It is now well established that the problem is because of the buggy Broadcom driver. In approximately mid-January BrainSlayer got access to a new version of the driver and the problem is fixed now - there is a special thread about that: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=278372
I used to have constant reboots upon connection of a particular WiFi client (iPhone 4S, by the way ), but now my router is absolutely stable - one month of uptime already.
Hi depswa,
Many thanks for this I wasn't aware at all of this matter.
Then I did the upgrade to 26450 if I'm not wrong (latest from Kong released yesterday I think), but wireless wasn't working well, OpenVPN-TAP isn't working at all and guest-network (wired/wireless) doesn't work neither. So, I did the roll-back to the 23900 and I did the installation again of the CFE and now everything is OK, the USB 3.0 included with the information over the Info-Sys correct as well showing LinkSys EA6900.
Now the reboots with this build it persists (we are all aware ¬¬'), because I just had right now another one again, so I tried to go and install over the 26450, 26138 and 26446 I'm unable to upload a new build the process it gets finished, but I'm getting stuck in the 29300 without the chance to go for another different build...
Might I ask an stupid question ? Do we have the option to install the drivers without change the build ?
Let me highlight that with the AC68U the 26450 everything works well, less the Lighttpd and someone said that light of the 5 Ghz is working and for me isn't, but there everything is working OpenVpn-Tun, guest-network (wired/wireless) and the WiFi as well.
Also when you said this that your iPhone 4S makes your router to be rebooted just realized that my iPhone 5S did it this, but I didn't realized until you mention this... (iPad 2 Air doesn't and iPhone 6+ neither it does this weird thing).
Many thanks and I hope there is a chance to upload drivers without change the build.
Best regards. _________________ 7 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v3.0-r31899 giga (04/24/17)
1 x Marvel Armada 385 - LinkSys WRT1900ACS ---------> v3.0-r31899 std (04/24/17)
1 x Marvel Armada 370/XP - LinkSys WRT1900AC -------> v3.0-r31899 std (04/24/17)
1 x QCA IPQ806X - Linksys EA8500 -------------------> v3.0-r31899 std (04/24/17)
1 x Broadcom BCM4709 - Asus RT-AC3200 --------------> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Asus RT-AC68U ----> v3.0-r30880 std (11/14/16)
1 x ARMv7 Processor rev 0 (v7l) - Linksys EA6900 ---> v3.0-r30880 std (11/14/16)
1 x ARM Cortex-A9 Processor - Net Gear R7000 -------> v3.0-r30880 std (11/14/16)
5 x Broadcom BCM4716 chip rev 1 - Linksys E4200 ----> v24-sp2 (06/07/14) kingkong
1 x Broadcom BCM5300 chip rev 1 - Asus RT-AC66U ----> v24-sp2 (04/01/13) giga
To my knowledge (which is limited), it is not possible to update drivers keeping the old firmware, because they are usually tightly bound to the kernel. However, what I read in the mentioned thread on buggy ARM driver, is that you should make a complete reset of nvram after upgrading, which is not possible with 30/30/30. The only reliable way to do that is to run from telnet/ssh:
Code:
erase nvram
All other ways of resetting tend to preserve nvram variables. I also saw reports on guest network not working in that thread, but Kong has fixed all the bugs. However, they were gone only provided the "erase nvram" procedure was done. So I would try that.