[LEDE-DEV] WRT1900ACS - Kernel 4.4.12 boot failure
Claudio Leite
leitec at gmail.com
Tue Jun 7 07:10:39 PDT 2016
Thanks for the clear output.
* Dheeran Senthilvel (dheeranmech at 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
> - failsafe -
> [ 4.986830] random: dropbearkey urandom read with 121 bits of entropy available
[snip]
> root@(none):/# strings /dev/mtd1
> [ 44.008437] random: nonblocking pool is initialized
OK, this is definitely not right. It should be a long list of variables.
> =======> Step 4: Reboot <=======
> *** Warning - bad CRC, using default environment
again not right. this should have been cleared up the first time booting
after resetenv erased the old settings:
>
> S-ENV offset == 0x240000
>
>
> #### auto_recovery ####
> [u_env] get auto_recovery == yes
> [u_env] get auto_recovery == yes
> [u_env] get boot_part == 1
> [u_env] get boot_part_ready == 3
> auto_recovery enabled:1, boot_part:1, boot_part_ready:3
This bit looks OK, though.
I'm a little confused because I thought after resetenv and a reset the
bootloader would actually write the default values to flash. This may
not have happened here, since mtd1 is empty. I think it's fairly safe
to say reads from NAND are OK, since otherwise you would get lots of
errors when booting the system.
So, one more test, again trying to clear and reset the u-boot
environment:
(these are all u-boot commands)
resetenv; reset
<interrupt boot>
printenv
if the default values are there, then do
saveenv
reset
and interrupt the boot again and run 'printenv'. Are they there?
-Claudio
More information about the Lede-dev
mailing list