Hello,
* Mathias Kresin (d...@kresin.me) wrote:
> I'm in doubt that the lzma splitter can be fixed.
>
> The dependency to align the rootfs isn't specific to the lzma
> splitter. mtd_find_rootfs_from() in mtdsplit.c uses the erase block
> size as step size.
>
> For the other splitter an not erase
mtdsplit_lzma requires that the rootfs be aligned to a block boundary.
Pad the kernel partition to make this so.
Signed-off-by: Claudio Leite
---
target/linux/ramips/image/rt288x.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/ramips/image/rt288x.mk
b/target
Hello David,
* David Gilman (dgil...@gilslotd.com) wrote:
> Claudio, I have a Kirkwood EA3500 (Audi) board and it seems that at some
> point the patches for this board have regressed the uboot fw_setenv
> utility and semi-bricked my machine. I've been digging into this issue
> and I suspect there
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
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
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
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 (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
Also collapses the three identical configurations into one block.
Signed-off-by: Claudio Leite
---
target/linux/mvebu/base-files/etc/board.d/02_network | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/target/linux/mvebu/base-files/etc/board.d/02_network
b/target
