Installing from scratch, using networked install, I've built two
kernels from 2.6.14 sources, each time the mods I'd listed autoload
fail to be loaded and are apparently never built.
I resorted to usign genkernel since in the past that has always
provided a working kernel and initrd. And
Harry Putnam wrote:
Installing from scratch, using networked install, I've built two
kernels from 2.6.14 sources, each time the mods I'd listed autoload
fail to be loaded and are apparently never built.
I'm not big on the genkernel thing but I had the same thing earlier and
I was doing it
On Fri, 09 Dec 2005 04:24:26 -0600, Harry Putnam wrote:
Or alternatively it seems one could just use /proc/config.gz as
/usr/src/linux/.config and run it manually. Except I'm at a loss as
to how an intitrd is built manually from a kernel compile.
You don't need an initrd when compiling your
Neil Bothwick wrote:
When you compile a kernel
manually, you choose which modules you need in the kernel, build those in
and either leave the rest out or compile them as separate modules.
Genkernel is intended to make things easier, and it may do when things
work as they should, but I find it
4 matches
Mail list logo
