The command for installing the kernel modules didn't work correctly for
me. When I typed
ROOT=/embedded_rootfs make modules_install
the modules where installed in my development host's /lib/modules.
I could instruct the Makefile to install the modules in embedded_rootfs
using:
make INSTALL_MOD_PATH=/embedded_rootfs modules_install
-Xabier
#---- Step 5 - Build and install a kernel to the embedded_rootfs -------------
# Install a kernel into embedded_rootfs.
# First we will emerge it into our development_rootfs, then configure and
# build it.
# ** Warning **
# There appears to be a bug in kernel version >2.6.12 that prevents us
# from "make menuconfig" in the chroot environment. I don't know when it
# will be fixed (I'll assume it has to do with uclibc, right ??).
# A simple work around would be to compile a kernel outside of the
# development_rootfs environment and copy the image over to the
embedded_rootfs
# boot directory. I'm leaving the how-to as is for now, because I feel that
# this "bug" be eventually be fixed upstream.
emerge vanilla-sources
cd /usr/src/
cd linux
make menuconfig
# Configure your kernel for your TARGET SBC here. I HIGHLY suggest you
# configure the kernel to compile everything into the kernel, and nothing
# as a module.
make
ROOT=/embedded_rootfs make modules_install
cp /usr/src/linux/arch/i386/boot/bzImage /embedded_rootfs/boot/vmlinuz-2.6.x
# A few notes on compiling your kernel.
# If deploying to Compact Flash/DiskOnChip/SD use ext2, as the journaling
# filing systems "write" to much for a flash device.
# If deploying to a hard drive use a journaling filing system, such as
# ext3 or reiserfs.
--
[email protected] mailing list
