Posted: Sun Dec 29, 2013 3:23 Post subject: Re: Buffalo WZR-1750DHP Flashing with cfe tftp
<Kong> wrote:
dusan2 wrote:
***
***
check_trx: start flash1.trx
Invalid boot block on disk
check_trx: exit flash1.trx
fw is broken
blinking led 2
***
Well if you had a look at your previous logfiles you would have noticed, that the problem is only the cpu clock, as soon as you touch the Admin page (Management.asp) your cpu clock gets set and then your problems start, it will reboot constantly modifying the cpu clock:-)
That is why I removed overclocking from my builds, because on new units overclocking works even worse than on older units, e.g. no ram clock is set. Thus my build should have worked since weeks on the 1750:-)
Have to disagree Kong, the clock error is only for the ddram clock and it will not cause a reboot loop, it will only change the routers performance.
If the clock is way too wrong then there would be a crash already in the boot loader and long before the boot attempt.
The cause for the reboot loop is given and is correct - invalid boot block.
I have a theory of what is happening..
@dusan2
Can you please do an nvram show all from within the CFE before booting ddwrt and then an nvram show after ddwrt has booted. Upload both of them here. _________________ Kernel panic: Aiee, killing interrupt handler!
Posted: Sun Dec 29, 2013 6:25 Post subject: Re: Buffalo WZR-1750DHP Flashing nvram logs
dusan2 wrote:
hi
Buffalo WZR-1750DHP Flashing nvram logs
is this it ?
yes thanks and with that my theory of the cause has failed.
The 2 nvram areas are identical except for one variable which is unimportant, action_service=management _________________ Kernel panic: Aiee, killing interrupt handler!
Posted: Sun Dec 29, 2013 8:41 Post subject: Re: Buffalo WZR-1750DHP Flashing with cfe tftp
LOM wrote:
<Kong> wrote:
dusan2 wrote:
***
***
check_trx: start flash1.trx
Invalid boot block on disk
check_trx: exit flash1.trx
fw is broken
blinking led 2
***
Well if you had a look at your previous logfiles you would have noticed, that the problem is only the cpu clock, as soon as you touch the Admin page (Management.asp) your cpu clock gets set and then your problems start, it will reboot constantly modifying the cpu clock:-)
That is why I removed overclocking from my builds, because on new units overclocking works even worse than on older units, e.g. no ram clock is set. Thus my build should have worked since weeks on the 1750:-)
Have to disagree Kong, the clock error is only for the ddram clock and it will not cause a reboot loop, it will only change the routers performance.
If the clock is way too wrong then there would be a crash already in the boot loader and long before the boot attempt.
The cause for the reboot loop is given and is correct - invalid boot block.
I have a theory of what is happening..
@dusan2
Can you please do an nvram show all from within the CFE before booting ddwrt and then an nvram show after ddwrt has booted. Upload both of them here.
LOM, on this one you are right, but the output on page 4 shows a reboot loop in which clock gets changed at every boot.
And the above snipped with flash error does not help. If it is an offset problem, e.g. wrong start adress of linux partition, then it will work but may be overritten with any nvram change or another flash via webif.
Thus with this error it is neccessary to have serioul output with oem fw and then with dd-wrt after flashing via tftpd before the invalid boot block error shows. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
which has user clock frequency setting disabled.
I need to narrow down the possible reasons for your boot problem and want to be sure if it is related to overclocking enabled in Brainslayers build. _________________ Kernel panic: Aiee, killing interrupt handler!
Posted: Mon Dec 30, 2013 4:28 Post subject: Re: Buffalo WZR-1750DHP Flashing tftp kong 23250
dusan2 wrote:
hi
Buffalo WZR-1750DHP Flashing with tftp kong 23250
used tftp pumpkin 2.7.3 an teraterm for serial terminal
and log of flashing , wifi test 5ghz and 2.4ghz, nvram show.
dusan2
Thanks, so is it stable now?
No more boot problem after saving in Administration/Management? _________________ Kernel panic: Aiee, killing interrupt handler!
which has user clock frequency setting disabled.
I need to narrow down the possible reasons for your boot problem and want to be sure if it is related to overclocking enabled in Brainslayers build.
which has user clock frequency setting disabled.
I need to narrow down the possible reasons for your boot problem and want to be sure if it is related to overclocking enabled in Brainslayers build.
Edit: latest kong wont flash via the buffalo gui
Because I don't provide a initial build for flashing from oem, as I can't test it. I only provide initial builds for models I can test. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/