On 01/30/2011 05:56 PM, Eric Cooper wrote:
On Sun, Jan 30, 2011 at 05:08:07PM +0000, Jason wrote:
Have you tried compiling the commandline options into the kernel
you're trying to kexec? eg CONFIG_CMDLINE
I don't think I need to. The --append option to kexec seems to work
fine. (See the boot transcript in the thread I referenced -- the
command line is being passed correctly.)
Gah, sorry, my mistake. I was looking at my local archives of the
thread and I don't seem to have anything after the second message... weird.
Unfortunately, the only thing I can think of is to try a known good (for
kexec) ARM kernel [1] as your bootloader, and make sure the kexec build
and runtime kernels are proper, then strip down/forward port the
bootloader kernel.
As an aside, the end of this [2] thread points to a few good references.
You've probably already come across them, but just in case you
haven't... Also, this thread [3] really digs into the guts of it.
Do you have a write-up somewhere?
Not yet. All I've done so far is a minimal kernel config and a
simple-minded rootfs with busybox and kexec-tools. I'll write a HOWTO
if I can ever get it actually working.
I'm in a similar situation with LVM on 2.6.37 on the kirkwood. But
that's a discussion for a different thread.
hth,
Jason.
[1]
http://openmoko-public-mailinglists.1958.n2.nabble.com/Kexec-Not-working-Please-help-td2233929.html
[2]
http://www.linux-archive.org/ubuntu-kernel-team/231053-fix-kexec-arm-properly-calling-relocation-function.html
[3] http://www.spinics.net/lists/arm-kernel/msg92099.html
--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d462069.6060...@lakedaemon.net
