Keith Owens <kaos@xxxxxxxxxxxxxxxxx> writes:
> Unless you are building a kernel that has to run on multiple machines
> with different hardware (i.e. a distribution) I strongly recommend that
> you do not use mkinitrd. Build your root driver and filesystem into
> the kernel,
How? Via "make xconfig"? Do I just do "lsmod" and configure the listed
modules into the kernel?
> load other objects as modules after boot and forget initrd.
> It is good for distributors but a pain in the neck for everybody else.
So what could be causing the modules not to load?
> Use modprobe loop, not insmod /full/path/name.o.
OK, will do. I presume the boot process does the right thing, though,
and it gets the same errors.
-Dave
|