Posted: Thu Aug 11, 2016 2:49 Post subject: working fine... just 3 points of feedback
I have done the flash and used the method 2 to get round the NVRAM issue which has yet to be proven to work so fingers crossed.
1) when initial flashing, the webui does not always refresh, so I opened a new browser tab to access 192.168.1.1 - this gets to the flashed landing page even while the flashing tab still displays 'waiting' status
2) after updating to latest builds do we still need to flash twice each time to ensure both the firmwares are updated? Also is there anyway to check the version of both sets? eg by telnet?
3) is there any feedback on whether the method 2 of NVRAM is a better workaround or would it restrict future functionality when DD-WRT keep expanding its capabilities?
Again it was very helpful to have read this page before flashing... I could have bricked mine if went ahead initial flashing with the latest builds?!
Joined: 18 Mar 2014 Posts: 12881 Location: Netherlands
Posted: Thu Aug 11, 2016 7:34 Post subject: Re: working fine... just 3 points of feedback
Glad it worked
You can check method 2 by observing your Status page, under Space usage, there the used NVRAM is shown. After applying method 2 this is usually in the low twenties (if you did not enable SSH, as described)
Method 2 which you applied is non destructive and does not restrict any functionality
HTML issues are mostly due to your webbrowser, using Internet Explorer works best, and yes you have to refresh sometimes and wait until the gui refreshes, you have to be patiient
You do not have to flash twice but in case something goes wrong you probably revert to an earlier version you downloaded. You can check that you still have two linux partitions with the the following command from command prompt: cat /proc/mtd
Yours should have an extra linux2 partition, mine does not have it because I have used method 3
wufwufwuf wrote:
I have done the flash and used the method 2 to get round the NVRAM issue which has yet to be proven to work so fingers crossed.
1) when initial flashing, the webui does not always refresh, so I opened a new browser tab to access 192.168.1.1 - this gets to the flashed landing page even while the flashing tab still displays 'waiting' status
2) after updating to latest builds do we still need to flash twice each time to ensure both the firmwares are updated? Also is there anyway to check the version of both sets? eg by telnet?
3) is there any feedback on whether the method 2 of NVRAM is a better workaround or would it restrict future functionality when DD-WRT keep expanding its capabilities?
Again it was very helpful to have read this page before flashing... I could have bricked mine if went ahead initial flashing with the latest builds?!
Joined: 18 Mar 2014 Posts: 12881 Location: Netherlands
Posted: Thu Aug 11, 2016 9:47 Post subject:
Glad that I can be of assistance
As your partition scheme shows your are on the original Linksys scheme, you basically have two firmware partitions linux and linux2 (with their accompanying rootfs)
This also means that your NVRAM of 64 Kb is split into two 32 Kb parts hence the 32 Kb bug, which therefore also applies to your EA6900
With 28 Kb used your are good to go, but when adding more settings this can increase, so keep a look at the used NVRAM
You can flash both partitions, for flashing the second partiton substitute the appropriate line in the guide with:
mtd write linksys-ea6900-webflash.bin linux2
However it is not necessary, keeping an earlier working partition is not bad, so i would advise not to do so.
If you want to get rid of the 32 Kb bug use method 3, but only if you really have to, because there are drawbacks as described.
Feel free to ask anything
Groeten en succes!
wufwufwuf wrote:
Goedemorgen!
Thank you for teaching us the basics... indeed I see two 'partitions'(?) as follows:
Posted: Tue Aug 16, 2016 16:28 Post subject: suspected bricking?
Sorry to report that despite all the good progress above, it seems that this morning there was no network access via the router (I think I put in a self boot tick in the set up screen), and even browser access to 192.168.1.1 is not working!
Joined: 18 Mar 2014 Posts: 12881 Location: Netherlands
Posted: Tue Aug 16, 2016 17:23 Post subject: Re: suspected bricking?
The latest builds have, unfortunately, stability issues.
You can probably recover by doing the following:
Hold WPS button (the little protruding blue button at the back)
Unplug
Wait 10 seconds
Plug in
Wait approx. 25 seconds untill the linksys light start blinking
You router should come back up in a couple of minutes
A very stable build for me was 29620M, a Kong build, you can get older Kong builds at Clonevince website (see the guide)
Do not forget to reset to factory defaults, before and after upgrading (see the guide)
wufwufwuf wrote:
Sorry to report that despite all the good progress above, it seems that this morning there was no network access via the router (I think I put in a self boot tick in the set up screen), and even browser access to 192.168.1.1 is not working!
Posted: Tue Aug 16, 2016 18:06 Post subject: Phew!
Thank you for coming to the rescue again!
Not sure how you knew these weird combos, but it worked again! This brings up the problem of using new builds... is there a place to share / find out the latest stable build for each router? The Wiki table appears to be a bit out of date?
Joined: 18 Mar 2014 Posts: 12881 Location: Netherlands
Posted: Wed Aug 17, 2016 8:46 Post subject: Re: Phew!
There is no such thing as a "stable" build. Stability is also dependend on the configuration/settings you use, so what is rock solid for me can be unstable for you.
That said, some builds are more "stable" than others.
The last builds using linux Kernel 3 form Kong are regarded as very stable.
I have never had problems with Kong's build 29620M, so if you are looking for a "stable" build, that is the one I recommend, but 29300M is also regarded as very stable.
I have added a section in the install guide about "stable" builds.
wufwufwuf wrote:
Thank you for coming to the rescue again!
Not sure how you knew these weird combos, but it worked again! This brings up the problem of using new builds... is there a place to share / find out the latest stable build for each router? The Wiki table appears to be a bit out of date?
I just bought this router today and it was loaded with the latest stock firmware.
I'm unable to perform the initial flash on this router as I consistently get the "Invalid firmware file" error message. I've even tried downgrading the firmware with no luck.
Joined: 18 Mar 2014 Posts: 12881 Location: Netherlands
Posted: Sat Aug 27, 2016 8:29 Post subject:
Linksys is locking their routers down starting mid this year (exceptions are the WRT models). So it is possible that you no longer can load a non linksys firmware.
However the latest firmware I saw was from 2014 so perhaps it is still possible.
Forth downgrade to an earlier firmware using internet explorer
dqs5005 wrote:
I just bought this router today and it was loaded with the latest stock firmware.
I'm unable to perform the initial flash on this router as I consistently get the "Invalid firmware file" error message. I've even tried downgrading the firmware with no luck.
Hi egc, appreciate all the help you've been suggesting. I just gave the tftp option a try as well to downgrade the linksys firmware with no luck.
Unfortunately, it looks like I may have a version of the firmware that blocks me from downgrading. V1.1.42.172191 is what I have, which seems to be a more update version than what is currently listed on their support page.