Will it work when flashed to an R6300 v2 via TFTP?
Or I'd better to wait for a newer version which can be flashed via webif.
I can't bear the stock fw of R6300 anymore
Some simple questions:)
How good is the Wifi Speed and Range from your release compared to the stockfirmware.
How is the Overall Performance compared to the actual stockfirmware?
Will it work when flashed to an R6300 v2 via TFTP?
Or I'd better to wait for a newer version which can be flashed via webif.
I can't bear the stock fw of R6300 anymore
oh failed, it couldn't be flashed
I thought the fw could be flashed to r6300v2 after I had flashed any dd-wrt, so I flashed the one on myopenrouter first. But when I tried to flash the fw by kong, it just failed for unknown reason. I even tried tftp, it couldn't work either for 'timeout'.
It seems that I'll have to find another way to flash, or wait for a more suitable fw.
then 3rd flash
stock firm(.22) -> another firm is not working.
so i run telnet command at before 3rd flash.
is there any step to erase dd-wrt?
btw, after run this command(burnboardid U12H270T00_NETGEAR) at telnet, i try another dd-wrt( at myopenrouter ) firm.
after flash,my router is bricked
so i ordered serial connection devices
i can't test for a while...
The build on myopenrouter was not done by us and uses a kernel from netgear firmware. The dd-wrt sources used in this build is missing some very important things, which I just added a few weeks ago. Thus it is very likely, that your cfe is now partly corrupt and TTL might not be able to fix this. We will see once you have serial output. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Will it work when flashed to an R6300 v2 via TFTP?
Or I'd better to wait for a newer version which can be flashed via webif.
I can't bear the stock fw of R6300 anymore
oh failed, it couldn't be flashed
I thought the fw could be flashed to r6300v2 after I had flashed any dd-wrt, so I flashed the one on myopenrouter first. But when I tried to flash the fw by kong, it just failed for unknown reason. I even tried tftp, it couldn't work either for 'timeout'.
It seems that I'll have to find another way to flash, or wait for a more suitable fw.
Quote:
any dd-wrt
Any regular dd-wrt, yes but this is no regular dd-wrt it just puts dd-wrt webif on top of netgears kernel with a few changes in the sources.
The myopenrouter builds from tathagata for the latest netgear models, usually don't have proper upgrade code in order to flash a universal dd-wrt build *.bin, they usually only accept chk format and I didn't see any chksum generation in his build for R6300v2 thus flashing from webif should not work at all. Also does not properly safe some cfe vars, thus most likely already partly corrupted your cfe.
Thus you may be in deep shit trouble:-)
I only test compatibility with oem firmware and can only help you with issues that were caused when flashing back and forth between oem and dd-wrt. Not by third party builds. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
could you please explain the method to go from Netgear OEM to your R7000.bin build but on the R6250/R6300v2, I assume these two models are very similar and it's eben possible.
The build on myopenrouter was not done by us and uses a kernel from netgear firmware. The dd-wrt sources used in this build is missing some very important things, which I just added a few weeks ago. Thus it is very likely, that your cfe is now partly corrupt and TTL might not be able to fix this. We will see once you have serial output.
Do you mean that the build you made is missing the important things, or the one that was made on myopenrouter?
The build on myopenrouter was not done by us and uses a kernel from netgear firmware. The dd-wrt sources used in this build is missing some very important things, which I just added a few weeks ago. Thus it is very likely, that your cfe is now partly corrupt and TTL might not be able to fix this. We will see once you have serial output.
Do you mean that the build you made is missing the important things, or the one that was made on myopenrouter?
No the build on myopenrouter is missing important code parts. I just recently added these parts to dd-wrt.
You will find info on how to install dd-wrt in the Readme:
but is it possible after flashing to DD-WRT to run: burnsku 0x0002 to change the Wifi Settings to Worldwide or is it only possible in the Netgear Stockfirmware?
The build on myopenrouter was not done by us and uses a kernel from netgear firmware. The dd-wrt sources used in this build is missing some very important things, which I just added a few weeks ago. Thus it is very likely, that your cfe is now partly corrupt and TTL might not be able to fix this. We will see once you have serial output.
Do you mean that the build you made is missing the important things, or the one that was made on myopenrouter?
No the build on myopenrouter is missing important code parts. I just recently added these parts to dd-wrt.
You will find info on how to install dd-wrt in the Readme:
Flashing back to oem fw works through dd-wrt webinterface.
The R6250/R6300v2 port is not complete yet.
So basically, your build is all good? I've just flashed it to my R7000 and it works quite good. I first did the .chk then the .bin. Do I need to do anything else or am I good to go?
So basically, your build is all good? I've just flashed it to my R7000 and it works quite good. I first did the .chk then the .bin. Do I need to do anything else or am I good to go?
Yes this build is fine only usb is bugging me a bit, but I'm just debugging it. Maybe I can fix something tonight.
Quote:
but is it possible after flashing to DD-WRT to run: burnsku 0x0002 to change the Wifi Settings to Worldwide or is it only possible in the Netgear Stockfirmware?
Posted: Mon Nov 04, 2013 23:24 Post subject: CPU Maxed out?
Been on this build without issue for about 24 hours or so uptime. Came home from work to find CPU pegged at 100%, temperatures normal, and performance normal. Reboot made it go away but not sure why?
Load Average
100%
3.10, 3.05, 3.05
CPU Temperature
CPU 53.0 °C / WL0 45.01 °C / WL1 43.01 °C
Posted: Mon Nov 04, 2013 23:30 Post subject: Re: CPU Maxed out?
thedak wrote:
Been on this build without issue for about 24 hours or so uptime. Came home from work to find CPU pegged at 100%, temperatures normal, and performance normal. Reboot made it go away but not sure why?
Load Average
100%
3.10, 3.05, 3.05
CPU Temperature
CPU 53.0 °C / WL0 45.01 °C / WL1 43.01 °C
What is the procedure to go back to stock from DD-WRT? Is there any recovery mode like on DLink routers?