Well, its nice to see TomatoUSB running, but where is the page with all the nice connection strength info I get on the frontpage of DD-WRT?
Well, on to trying DD-WRT again, this time I'll try the latest initial file: dd-wrt.v24-19342_NEWD-2_K2.6_mini_RT-N66U.trx
It upgrades fine from the web interface, and counts down 30 seconds and 50-60 seconds. And I wait another 4 minutes before I reset the router.
Bummer. No ping, no web interface, no blue blinking lights.
For now, my RT-N66U will be running other firmware, so I can get my RT-N16 freed for other testing, like helping Tornado with the 32k -> 60-64k fix on the RT-N16, which hopefully will lead to a similar fix for the RT-N66U
I bricked mine several times and it is really important to wait 10-15 minutes.
No need to reset. The router will come back after the firmware update. Just keep waiting.
I've read the whole thread, Peacock, etc and I'm new to flashing firmware on routers but ready to put ddwrt on my new asus rt-n66u. Is this still the officially recommended firmware to start with:
I've read the whole thread, Peacock, etc and I'm new to flashing firmware on routers but ready to put ddwrt on my new asus rt-n66u. Is this still the officially recommended firmware to start with:
Since they were able to increase the NVRAM in the kernel and without touching the CFE, would it not be possible, in theory, to replicate these changes in other firmwares? For example, I have a WRT-600n, could it not be made to use 64k NVRAM as well (if he has the space to do so).
Since they were able to increase the NVRAM in the kernel and without touching the CFE, would it not be possible, in theory, to replicate these changes in other firmwares? For example, I have a WRT-600n, could it not be made to use 64k NVRAM as well (if he has the space to do so).
A DD-WRT dev would have to look into it. We do not know if Asus implemented other changes in the binary-only components of the firmware. And DD-WRT's architecture might not necessarily be designed to do that kind of thing.
Well I'm still hoping that in the interests of good customer relations and tech support, Asus will do the decent thing and release a tool to change the CFE instead of making a kernel level fix which only benefits their firmware.
Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Thu Jun 28, 2012 23:19 Post subject:
User AndyMS was working with asus. RMerlin may also be. There was a post from asus stating they were working on a solution for dd-wrt users.
All we need is the cfe and a dd-wrt build to support it. We can change our cfe the same way the converts are done (610_v2 => e3000 and 320 => e2000)
We are dd-wrt users so asus does not need to come up with a flash that will change out the cfe. We can do that. All we need is the cfe (and a dd-wrt build to support it, or an asus build to start with) _________________ [Moderator Deleted]