On Sat, Jan 23, 2016 at 7:17 AM, Martin Michlmayr <t...@cyrius.com> wrote:
> Your patch sets the kernel load address to 0x00c08000.  So u-boot will
> still load the kernel to 0x00100000 but then (I guess) it's
> uncompressed at 0x00c08000.  The problem is that 0x00c08000 is only 4
> MB after the start of the ramdisk (0x00800000), which doesn't leave a
> lot of space for the ramdisk.
>
> You can change initramfs-tools from MODULES=dep to MODULES=most,
> generate and I suspect it wouldn't boot.
>
> Can you try if something like 0x01a08000 works?
>
> BTW, I assume we need to change this for all Linkstation devices.

I only pathced LS-WTGL because it's the only device I can boot with
the change to 0x00c08000.
I don't have other orion5x device, so I tested on a few kirkwood based
Linkstation but all failed with this kinda of trick.

Now it's cleared, as you said, 0x00c08000 is too low that big initrd
may over-write to its address.
I tried 0x01a08000, yes, my kirkwood devices boot okay, but still have
the following error in dmesg:

[    0.361974] Unpacking initramfs...
[    0.884688] Initramfs unpacking failed: junk in compressed archive

the initrd I used to test is 3.4M initramfs initrd.
And it's 7.9M after gunzip.

Indeed, I have no clue why initramfs complain there's junk, since
kernel already set to higher address as 0x01a08000.

Cheers,
Roger

Reply via email to