>>>Furthermore, how to ensure coherent kernel version between kexecboot >>>installation and (future) test image? >> Well, really you shouldn't care too much. You can boot any 2.6 >> (recent) kernel with old 2.6.26 or 2.6.3x kexecboot (actually in >> testing-phase).. > > The initial matter was to have a fresh kernel. The matter is running a > 2.6.24 kernel with 2.6.26 system: loadable modules are not found.
Kexecboot kernel has own initramfs userspace and does not need any module. The kernel you launch resides in a rootfs which expectedly contains the corresponding modules. > A question I suggest to add to FAQ (I will do it): with narcissus, how > can I prepare a zImage.bin for updater.sh? Narcissus provides a single > file. Is there an associated repository somewhere? At the moment Narcissus creates *standard* jffs2 images. The 16bytes header/signature is requested by the legacy updater.sh used by Sharp Zaurus only. We are thinking about a modern updater.sh for flashing standard jffs2 images. For the moment you can edit the initrd.bin with an hexeditor and add 16 bytes at the beginning (or do it with simple shell commands). Then updater.sh will strip these again and will flash the image properly (aligned). >Personally, I naively renamed a /boot/zImage.2.6.26 from an image >generated by narcissus to zImage.bin and tried to flash it. The >updater complaints about too huge file (16M instead of 13M, as I >remember). That wouldn't work. We expect only the linux-kexecboot kernel in nand, now. Other (production) kernels are just too big to fit in the mtd partition (needing to be able to boot from CF/SD/MTD, ...) Thx for your testing Andrea _______________________________________________ Angstrom-distro-users mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
