Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Wed Apr 13, 2011 20:01 Post subject:
appleguru wrote:
Somehow I missed this thread.. just tried to flash my WNDR3300 with dd-wrt.v24-16785_NEWD-2_K2.6_openvpn_small.bin... Seems I've bricked it now. Any advice on un-bricking?
Its a Serial Terminal only (No JTAG) You will have to break into the CFE using Serial then issue the tftpd command in order to use the tftp utility to reflash the unit with a trailed build...like this one.
Somehow I missed this thread.. just tried to flash my WNDR3300 with dd-wrt.v24-16785_NEWD-2_K2.6_openvpn_small.bin... Seems I've bricked it now. Any advice on un-bricking?
Its a Serial Terminal only (No JTAG) You will have to break into the CFE using Serial then issue the tftpd command in order to use the tftp utility to reflash the unit with a trailed build...like this one.
Ok, working on soldering a header to my wndr3300 and then repurposing my arduino as a serial adapter.. once I do all that, how do I break into the CFE? _________________ WNDR3300
FW: Eko 12268 mini-supp
Config: WL0: AP mode, WPA2 Personal, Mixed (bgn)
WL1: 802.1X client mode, 9dbi directional panel antenna soldered to board (right antenna)
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Wed Apr 13, 2011 20:19 Post subject:
appleguru wrote:
Ok, working on soldering a header to my wndr3300 and then repurposing my arduino as a serial adapter.. once I do all that, how do I break into the CFE?
Rapid fire Cntl-C in the Serial Terminal window when you plug in the router.
You should get a CFE> prompt.
redhawk _________________ The only stupid question....is the unasked one.
Please direct all your Serial questions to the thread I split off from the build thread.
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=136616 _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Posted: Thu May 05, 2011 16:00 Post subject: Re: [Important Info] k2.6 builds no longer support old devic
redhawk0 wrote:
Current k2.6 builds after ~16500 no longer support any old devices. This means that if you have a device that uses k2.4 then you must use k2.4 builds, and if you have a device that uses k2.6 then you must use k2.6 builds! CPU 4704 Owners (corerev=11) - No K26 builds after 15314 on the unit.
All other CPU's Corerev <16 - no K26 builds after 16500.
[b]UPDATE It is now learned that any router with a corerev lower than 16 will no longer be supported with the K26 builds after ~16500. (per Eko)
It is advised that you test your unit's corerev BEFORE attempting to use the K26 builds on it.
redhawk
this link points to a router/corerev listing, and is reasoanbly up-to-date:
That actually seems like a stupid development decision. What is the reasoning to potentially brick plenty of devices? And if there really is a good reason for it, why is there not a huge red-letter warning on the frontpage?
I could understand dropping official support but I fail to understand why the kernel can not run on the old devices at all?
Support for older devices was removed to reduce the size of the k2.6 kernel because it was growing too big for the CFE to boot it. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Support for older devices was removed to reduce the size of the k2.6 kernel because it was growing too big for the CFE to boot it.
Couldn't there be less static drivers and more modules loadable after the fact to reduce the size of the kernel binary itself?
This seems liable to cause a lot of major problems simply because of a space issue. Plus you throw out useful stuff like 6rd that (to my knowledge, correct me if I'm wrong) hasn't been backported to 2.4.
I'm adminning k2.6 WRT310n now and really don't like the fact that either my or my friend's upgrading without noticing this *not so slight* issue would have screwed him out of a router. I truly doubt that he'd have the wherewithal to reflash it via serial/jtag, nor would he want to have to send it cross-country to me to fix it.
His option would likely be buying a new router at the local worstbuy or walfart.
Seems time to throw out the even slightly old routers and get new ones eh? Kernel 2.4 isn't getting any newer...
Then again, when will ath9k be integrated into the Atheros units so I can finally stop recommending Openwrt to those who really want to use them without crappy wifi performance & bugs?
So what if you do a ram upgrade? I mean if a similar package device from the same manufacturer exists that could be soldered in. Would a newer kernel work then? I think the version on my router is 2.4.37.
Couldn't there be less static drivers and more modules loadable after the fact to reduce the size of the kernel binary itself?
Maybe? I don't know how feasible this is and only the devs could really answer because the Broadcom wireless driver is closed source, but I can tell you not to get your hopes up is a rule of thumb.
Radiotubes wrote:
So what if you do a ram upgrade? I mean if a similar package device from the same manufacturer exists that could be soldered in. Would a newer kernel work then? I think the version on my router is 2.4.37.
The problem isn't the size of RAM, it's how the CFE allocates space for the kernel to load into. Different CFE's allocate different amounts of space for the kernel and it needs to be able to fit into that space. Old router models that didn't allocate enough space for older k2.6 firmwares to load could sometimes have their CFE's replaced so that they would allocate enough space, but the kernel was growing too big and so the microcode for old radio corerevs had to be cut so that new models that really need k2.6 could load it. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
This is retarded, is there anyone who can answer the question what is the latest firmware that will actually run on a wnr 3500L? This is so confusing its giving me a migraine.
You can try it. It might be too big. Newer builds have gotten bigger. Some have said that big no longer fits. You might need to use the std. _________________ I am far from a guru, I'm barely a novice.