I've got the modified cfe running on my router and it's working great; good job
For anyone who's wondering, it has fixed the nvram 32k limit and my problem with it bricking after 3 reboots. Asus-Wrt (Merlin) 378.56_alpha2-X5.6 is now my daily driver. I think I need to find the gpio command to turn on the light though as it is off.
5G and 2.4G performance were never a problem on the normal dd-wrt for me and still isn't with the new cfe and different firmware.
And yes, I did have the same problem as rosenrot with it bringing a error of [e]Erasing mtd failed: linux2 and yes the Asus firmware did flash successfully on both firmware paths.
I guess I have finally found a alternative to the stock Linksys firmware
The new cfe, doesn't seem to fix the temperature problems, but I guess I'll just attach a usb hub and hook up a usb fan and continue using my hard drive on another port.
I just have the cover out. Don't need to add anything. The cpu temperature stay about 62°C. I'm thinking just cut out the hole on the cover for the cpu. Let it works just like the 1970 Hi-Fi.
has anyone actually solved the running hot problem, or just ameliorated it with a fan, hole, ice cube?
i've go two of these routers. one runs hot (90-102C), the other cold (60-80C). I have completely reworked these to be identical, with xvortex/LOM CFE (identical except for mac addresses), nvram values, firmware versions, etc. I've swapped power supplies, powered radios on and off, changed power levels, even checked AC power sources. But nothing makes the hot one run cool.
has anyone actually solved the running hot problem, or just ameliorated it with a fan, hole, ice cube?
i've go two of these routers. one runs hot (90-102C), the other cold (60-80C). I have completely reworked these to be identical, with xvortex/LOM CFE (identical except for mac addresses), nvram values, firmware versions, etc. I've swapped power supplies, powered radios on and off, changed power levels, even checked AC power sources. But nothing makes the hot one run cool.
what am i overlooking?
thanks
Unscrew the heatsink, apply new/better paste, re-install the heatsink? _________________ I am far from a guru, I'm barely a novice.
Fan is not a good solution. Since router is running 24/7/52. After a long run, the fan bearing makes noise also it'll have dust stuck on the Fan. I'm thinking to use air cooling. This is my future Star Router. Not sure the big metal will effect the signal. Have to test it
There is a new beta version of dd-wrt out. I was not able to flash this one from merlins web interface. It gave me an error an nothing happened.
Since the Asus firmware from merlin gives me bad 5Ghz performance, I want to go for dd-wrt but it seems that even from the mini dd-wrt it gives an erasing linux2 error.
Could anyone tell me why this is? Or how to make it work?
Hello, I am fairly certain that you cannot use the web interface to flash if you are on modded cfe and Merlin. Use the interface at boot, tftp, or scp the file up and telnet/ssh in to run the flash command.
Hello, I am fairly certain that you cannot use the web interface to flash if you are on modded cfe and Merlin. Use the interface at boot, tftp, or scp the file up and telnet/ssh in to run the flash command.
Which flash command? This failed previously:
mtd write /tmp/temp/link-to-firmware-chosen.bin linux2
A simple solution for those don't want to open the router to drill hole to mount a Fan on their router. Get one of this Fan, put it on the side of the router, it'll help to cool down the router. This Fan uses USB power, if you don't use USB drive, just plug it in the USB on router.
on bootup, the mtd map is checked. if it doesnt match what the firmware wants, it is rewritten. this is one phase of the multiple-reboot process after flashing a new firmware architecture. not all firmwares respct all partitions.
i've always flashed firmware to linux, not linux2.
if that doesn't work, use the bootloader tool.
Do note that dd-wrt has reduced the size of mtd1 to 1MB which means that devinfo is protected for writing to, dd-wrt is neither able to destroy it nor is it able to repair it.
Access to the devinfo area is therefore only available from the original Linksys CFE and its devinfo cmds, or by mtd write when running merlin Asus firmware. _________________ Kernel panic: Aiee, killing interrupt handler!
Do note that dd-wrt has reduced the size of mtd1 to 1MB which means that devinfo is protected for writing to, dd-wrt is neither able to destroy it nor is it able to repair it.
Access to the devinfo area is therefore only available from the original Linksys CFE and its devinfo cmds, or by mtd write when running merlin Asus firmware.
i did notice that dd-wrt reduced the mtd partition size to 1MB, but i did not notice the hole in the partition map that theoretically protects devinfo (unless i did something really stupid!)
thank you for the clarification.
So what is the correct procedure to (for example), move back to dd-wrt firmware using xvortex cfe? I am guessing I should flash it from the miniweb server that starts up at bootup? Or flash it using the command to linux path? I read one post a page back stating that you couldn't flash it from the web gui.
I wanted to try the newest build - maybe the temps will go lower ...
Now I have 27805 and wanted to upload 27858 but after upgrading the router gets back to default settings but remains at 27805. I also tried flashing again "linksys-ea6400-numinit-super-hacky-smaller-version" but still no luck - the router goes to defaults but remains 27805... should I 30-30-30 ?