Neil Bothwick <[EMAIL PROTECTED]> writes: > 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 own kernel. genkernel uses > it because it needs modules for everything, including the kitchen sink, > available to the kernel before mounting the root filesystem. Compiling > them into the kernel would make it bloated. 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.
What about for frame buffering? Isn't it required for that? I thought the initram thingy was the way it was done currently. > Genkernel is intended to make things easier, and it may do when things > work as they should, but I find it makes life more difficult when > anything goes wrong. Building a kernel manually is not rocket science, it > is easier in the long run. Well, like I said I did try manually twice first. But on bootup the modules I needed were not only not available but were apparently not ever built. I must be making some wrong choices somewhere. I did list them in the autoloads file. The mods I need are for networking: 3c59x and e100 for my adapters. On the second build I did get 3c59x but it turned out not to be the one needed for eth0, and eth1 was not present. Looking back thru menuconfig, I don't see a choice that looks like it would build e100. e100 is present in livecd though so I know its there somewhere. I thought maybe genkernel would find it. I've gone thru the network devices in menuconfig several times and still do not see one that appears to include e100. Although in the install I'm replacing it was present going way back. -- gentoo-user@gentoo.org mailing list
