On 06/07/2016 11:00 AM, Claudio Leite wrote:
On 06/07/2016 10:48 AM, Dheeran Senthilvel wrote:
[snip]
===> Step 3: Reboot <==
After the above procedures, I don’t have the error anymore.
Great -- so you're all set, as far as you can tell?
Wonder what really caused the problem in f
On 06/07/2016 10:48 AM, Dheeran Senthilvel wrote:
[snip]
===> Step 3: Reboot <==
After the above procedures, I don’t have the error anymore.
Great -- so you're all set, as far as you can tell?
Wonder what really caused the problem in first place.
Given the date when you init
===> Step 1 : resetenv & reset <===
__ __ _ _
| \/ | __ _ _ _| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_|\_/ \___|_|_|
_ _ _
| | | | | __ ) ___ ___ | |_
Thanks for the clear output.
* Dheeran Senthilvel (dheeranm...@gmail.com) wrote:
[snip]
> ===> Step 3: Intrupt boot into failsafe <===
>
> Press the [f] key and hit [enter] to enter failsafe mode
> Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
> f
> - failsa
===> Step 1: Reboot <===
BusyBox v1.24.2 () built-in shell (ash)
_
//\ ____ ___ ___
/ LE/ \| | | __| \| __|
/DE /\ | |__| _|| |) | _|
// LE \ ||___|___/|___| lede-project.org
\\
Hello Dheeran,
* Dheeran Senthilvel (dheeranm...@gmail.com) wrote:
> Hi,
> Yes even after I run resetenv followed by a reset command, the
> fw_printenv produces the same output every time.
>
> > On 07-Jun-2016, at 3:54 PM, Claudio Leite wrote:
> >
> > Hi,
> >
> > * Dheeran Senthilvel (
Hi,
Yes even after I run resetenv followed by a reset command, the
fw_printenv produces the same output every time.
> On 07-Jun-2016, at 3:54 PM, Claudio Leite wrote:
>
> Hi,
>
> * Dheeran Senthilvel (dheeranm...@gmail.com) wrote:
>> Hi,
>> Thanks for the reply. But I already do
* Dheeran Senthilvel (dheeranm...@gmail.com) wrote:
> Hi,
> Compiled build r504 followed by clean build. Still not clear what is
> causing the boot error mentioned previously in mailing list - May 2016.
[snip]
>
> auto_recovery_check changes bootcmd: run nandboot
> Hit any key to stop autob
Hi,
Compiled build r504 followed by clean build. Still not clear what is
causing the boot error mentioned previously in mailing list - May 2016.
• [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot failure Dheeran
Senthilvel
• [LEDE-DEV] WRT1900ACS - Kernel 4.4.11 boot
