older discussion:
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=500621
(with details on how to blow away your entire CFE) _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
I keep seeing people posting "nvram erase && reboot" throughout the forum and contemplated making a PSA post but decided against it.
To avoid confusion it's best to uncouple the reboot line so the console will give you an error when you use the wrong command.
nvram erase && reboot will always reboot giving the user a false sense of success because it'll always reboot as if it were sucessful.
nvram erase will give you an invalid argument for nvram error while erase nvram will give an indication of erasing the memory block.
Afterwards, just type reboot and hit enter and you're set.
OK, following your clue, I have experimented various combinations. Here are the result, at least on my router R7000:
1. nvram erase (not working AND without error message)
2. erase nvram (working despite "invalid argument" message, followed by "reboot")
3. erase nvram && reboot ( despite message "invalid argument", will erase nvram, but will not reboot, have to type "reboot".)
4. erase nvram;reboot (works with error message "invalid argument")
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
did this release require a reset? I upgraded to this recent Kong release and brick my R7000 router. Tried to recover but could not. I had insurance on it so I went and replaced it with a new R7000. I was able to upgrade it to the recent release but seem to have issue setting up the wireless. Sometimes find that even the hard wired PC will show unidentified network and can't connect to the router and will have to reset... try again and the same thing. I going to work this again tomorrow but may drop back to the last release. It was running without issue.
No, not if you came from a Kong build since late Feb.
Even if it did, not performing the reset would not brick the router.
Your issue is something else.
deanpeak wrote:
did this release require a reset?
_________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
No, not if you came from a Kong build since late Feb.
Even if it did, not performing the reset would not brick the router.
Your issue is something else.
deanpeak wrote:
did this release require a reset?
Thanks for the response. I did not think it would but I was performing the upgrade from Kong's 26450M that has been running solid and for some reason if stayed in the timer window longer than normal. then the time counter to zero and it was still sitting. after waiting a little longer and noticed the power LED was blinking white/red, I decided to unplug it. That made no difference or trying to do a hard reset. So decided it was dead, for whatever reason, and went exchanged it for another. Then I think I just had a few issues... the cable modem being married to the old router my PC's seeing the new router as public, and so on. So after much time and cussing, I now seem to have everything up and running happily on Kong's 26500M. Monday was just not my day but Tuesday is looking up... lol.
So I read through the last month or so of posts on this thread and came to the conclusion that 26160M appears to be stable for most. I upgraded my R7000 from 25090M and I've had no reboots for 2+ days now. Sweet! Thanks everyone, especially Kong, for your efforts.
I did an nvram reset after the upgrade, and reconfigured from scratch... including OpenVPN. Took some time, but wasn't that bad.
I was wondering if someone could clarify something for me. I've gathered from the posts that Kong does his testing and the results are posted at the link below. Correct? Is it safe to assume that his newer test versions overright previous test versions? How can you tell the new version numbers, as they are not noted in the filename?
http://www.desipro.de/ddwrt/K3-AC-Arm/