Posted: Sun Jan 10, 2016 22:31 Post subject: Re: Incorrect NVRAM Total Size on K3.X builds?
CTEC wrote:
A router can't magically increase NVRAM size no matter what firmware is running.
Sure it can
CTEC wrote:
Will this become an issue?
At times it seems to be a bit crazy --- but that is really a whole different topic.
The increased NVRAM size is a key part of dd-wrt broadcom k3.x ... it should not be a problem for you.
Unless my memory is wrong, then why does the CFE show a different NVRAM available size?
I flashed a 32K build from the start (21605) but it changed total to 128K. Later builds doubled it. I didn't flash any tailored build that said 64K or more. In fact, the custom builds for this router don't even work as DD-WRT will report instantly flash successfully upon uploading the firmware via webGUI. _________________ ASUS RT-AC68R: 42954
Belkin F7D7302: 43078
Unless my memory is wrong, then why does the CFE show a different NVRAM available size?
You're thinking of the base nvram partition; k3x builds expand it in the application code.
CTEC wrote:
In fact, the custom builds for this router don't even work as DD-WRT will report instantly flash successfully upon uploading the firmware via webGUI.
That normally happens when the build size gets too big for your router/model (and also if I try to use the 'reset after flash' option).
E.g. the 28647 k3x builds are too big, but 28598 flashes on my WNDR4000 (has other issues, but that's another story). _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Unless my memory is wrong, then why does the CFE show a different NVRAM available size?
You're thinking of the base nvram partition; k3x builds expand it in the application code.
CTEC wrote:
In fact, the custom builds for this router don't even work as DD-WRT will report instantly flash successfully upon uploading the firmware via webGUI.
That normally happens when the build size gets too big for your router/model (and also if I try to use the 'reset after flash' option).
E.g. the 28647 k3x builds are too big, but 28598 flashes on my WNDR4000 (has other issues, but that's another story).
Oh so that explains why running "nvram erase" in DD-WRT can spell disaster.
As for build size, I'm on the latest version mega Broadcom generic. However, if I try flashing the F7D7301 tailored build, I get the instant flash success with zero changes and sometimes increased NVRAM consumption. _________________ ASUS RT-AC68R: 42954
Belkin F7D7302: 43078
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Tue Jan 12, 2016 5:40 Post subject:
a few devices. lets call them linksys (not all, but some) should not be treated with "erase nvram", since they wont recover the default data sometimes. i have seen lost mac addresses etc. this is why dd-wrt is also not erasing the flash anymore, but just restoring the default data if selected and keeping factory values untouched _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
