[coreboot] [PATCH] mkelfImage: set kernel_alignment so 2.6.31+work
Eric W. Biederman
ebiederm at xmission.com
Fri May 21 21:36:01 CEST 2010
"Myles Watson" <mylesgw at gmail.com> writes:
>> > ramdisk-base is just where in ram to load the ramdisk. mkelfImage
>> > to 8M. You are setting it to 20M. With the change to kernels to
>> > them to running at 16M that only leaves 4M for the kernel which I expect
>> > to little. Because mkelfImage is old and the hack is crude I don't
>> > mkelfImage is to stupid to realize that we have a problem.
>> 20M is indeed to small.
> My understanding is that 20M is a location, not a size.
>> The ramdisk (incl. kernel modules) is on the
>> order of 26M; I've tried setting it to 32M - this setting is what allows
>> the kernel to actually start; however (as previously mentioned), the
>> kernel is unable to mount the ramdisk.
> Because the kernel is looking at 20M and you moved it to 32M?
No. These are the parameters passed to the kernel. What I have seen
in the past is the ramdisk being loaded close enough to the kernel
that the kernel stomps it, and corrupts it in early startup. This should
be diagnosable by looking at the boot up messages from the kernel startup.
More information about the coreboot