Dave Sill wrote:
>
> 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?
Actually you are prompted for a yes/module/no (via radio buttons) from
xconfig. Select the yes option instead of the module option.
>
> > 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?
Unresolved dependencies with regards to other modules which failed to
load. Look at your logs (/var/log/syslog) to see what failed to load
and what succeeded. Try insmoding the failed stuff after booting to
single user mode (type "linux single" at the lilo prompt if your kernel
image is named "linux")
--
Joseph Landman, Ph.D., | SGI Americas Technology Center
email: landman@xxxxxxx | Sr. Systems Engineering Specialist
voice: +1 248 427 4469 | Bioinformatics Application Development
fax: +1 248 427 5600 | and Linux Cluster based solutions.
--------------------------+---------------------------------------
http://www.sgi.com/chembio http://reality.sgi.com/landman
------------------------------------------------------------------
|