Boot vs running kernel

I run 2 kernels: a boot kernel that has everything basic compiled in that is enough to mount the harddisks in whichever raidformat, load a new kernel and kexec that one. Why? Well, the linux partition on the internal flash has a max of 2MB, or 1.5 MB or something like that. That's barely enough to get a decent kernel in. So we boot a kernel with kexec support and filesystem support and stuff so it can load are favorite kernel with traffic shaping, ipv6 and other neat stuff we love.

The boot kernel

Compile as usual. Here is my config (2.6.27.8):

Compiling any kernel

The redboot of the em7210 of course does not know what an em7210 is. As always, there are several different machine types, all with the id of an intel development board. This is a patch to overcome this shortsightendness of the developers.

  • zImage: The boot kernel with IP table module support

Topic attachments
I Attachment Action Size Date Who Comment
ziptar 2.6.27.8hkcw.tar manage 1720.0 K 27 Sep 2009 - 13:54 KennyKwok modules , pls extract to /lib/modules
else8-boot config-2.6.27.8-boot manage 30.9 K 29 Jul 2009 - 23:07 ArdVanBreemen config for a boot kernel
else8hkcw config-2.6.27.8hkcw manage 36.5 K 27 Sep 2009 - 13:54 KennyKwok config for a boot kernel by kenny
elsepatch hack_machtypes.patch manage 0.7 K 29 Jul 2009 - 23:50 ArdVanBreemen kernel hack for redboot machine type patch
elseEXT zImage manage 1979.2 K 27 Sep 2009 - 13:53 KennyKwok The boot kernel with IP table module support
elseEXT zImage-boot manage 1945.9 K 29 Jul 2009 - 23:10 ArdVanBreemen The boot kernel
Topic revision: r2 - 27 Sep 2009 - 13:55:00 - KennyKwok
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback