The base that all distributions are built upon is the Linux kernel. It is the layer between the your programs and your system hardware. Gentoo provides its users several possible kernel sources. A full listing with description is available at the Gentoo Kernel Guide.

We suggest using either vanilla-sources or gentoo-sources on PPC, which are both 2.6 kernels. The latter is available when you perform a networkless installation. So let's continue with emerge'ing the kernel sources. The USE="-doc" is necessary to avoid installing xorg-x11 or other dependencies at this point:

# USE="-doc" emerge gentoo-sources

If you take a look in /usr/src you should see a symlink named linux pointing to your current kernel source. Here, we will assume that the kernel source installed is gentoo-sources-2.6.12-r4:

# ls -l /usr/src/linux
lrwxrwxrwx    1 root     root           22  Mar 18 16:23 /usr/src/linux -> linux-2.6.12-gentoo-r4

If the symlink doesn't point to the kernel source of your choice (note that linux-2.6.12-gentoo-r4 is merely an example) you should change it to the desired kernel sources:

# rm /usr/src/linux
# cd /usr/src
# ln -s linux-2.6.12-gentoo-r4 linux

It is now time to configure and compile your kernel source. You can use genkernel to build a generic kernel similar to the one used by the Installation CD, or you can perform a manual configuration to best suit your system.

If you want to manually configure your kernel, continue now with Default: Manual Configuration. If you want to use genkernel you should read Alternative: Using genkernel instead.

Manually configuring a kernel is often seen as the most difficult procedure a Linux user ever has to perform. Nothing is less true, after configuring a couple of kernels you won't even remember it being that difficult ;)

However, one thing is true: you must know your system when you start configuring a kernel manually. Most information can be gathered by emerging pciutils (emerge pciutils) which contains lspci. You will now be able to use lspci within the chrooted environment. You may safely ignore any pcilib warnings (like pcilib: cannot open /sys/bus/pci/devices) that lspci throws out. Alternatively, you can run lspci from a non-chrooted environment. The results are the same. You can also run lsmod to see what kernel modules the Installation CD uses (it might provide you with a nice hint on what to enable). Another place to look for clues as to what components to enable is to check the kernel message logs from the successful boot that got you this far. Type dmesg to see the kernel messages.

Now go to your kernel source directory, it's time to configure your kernel. It is recommended that you add the default settings to your configuration by first running make defconfig. After the default configuration has been generated, run make menuconfig which will fire up an ncurses-based configuration menu.

# cd /usr/src/linux
# make defconfig
# make menuconfig

You will be greeted with several configuration sections. We'll first list some options you must activate (otherwise Gentoo will not function, or not function properly without additional tweaks).

First of all, activate the use of development and experimental code/drivers. You need this, otherwise some very important code/drivers won't show up:

Code maturity level options --->
  [*] Prompt for development and/or incomplete code/drivers
General setup --->
  [*] Support for hot-pluggable devices

Now go to File Systems and select support for the filesystems you use. Don't compile them as modules, otherwise your Gentoo system will not be able to mount your partitions. Also select /proc file system and Virtual memory. Do not select the /dev file system.

File systems --->
  Pseudo Filesystems --->
    [*] /proc file system support
    [ ] /dev file system support (OBSOLETE)
    [*] Virtual memory file system support (former shm fs)

(Select one or more of the following options as needed by your system)
  <*> Second extended fs support
  <*> Ext3 journalling file system support
  <*> Reiserfs support
  <*> XFS filesystem support

If you are using PPPoE to connect to the Internet or you are using a dial-up modem, you will need the following options in the kernel:

Device Drivers --->
  Networking support --->
    <*> PPP (point-to-point protocol) support
    <*>   PPP support for async serial ports
    <*>   PPP support for sync tty ports

The two compression options won't harm but are not definitely needed, neither does the PPP over Ethernet option, that might only be used by rp-pppoe when configured to do kernel mode PPPoE.

If you require it, don't forget to include support in the kernel for your ethernet card.

Users of NewWorld and OldWorld machines will want HFS support as well. OldWorld users require it for copying compiled kernels to the MacOS partition. NewWorld users require it for configuring the special Apple_Bootstrap partition:

File Systems --->
  [*] HFS Support

At this time, kernel preemption is still unstable on PPC and may cause compilation failures and random segfaults. It is strongly suggested that you do not use this feature.

Platform options --->
  [ ] Preemptible Kernel

If you're booting from Firewire, you'll need to enable these options. If you do not want to compile in support, you'll need to include these modules and their dependencies in an initrd.

Device Drivers --->
  IEEE 1394 (FireWire) support --->
    <*> IEEE 1394 (FireWire) support
    <*>   OHCI-1394 support
    <*>   SBP-2 support (Harddisks etc.)

If you're booting from USB, you'll need to enable these options. If you do not want to compile in support, you'll need to include these modules and their dependencies in an initrd.

Device Drivers --->
  USB support --->
    <*> Support for Host-side USB
    <*>   OHCI HCD support
    <*>   USB Mass Storage support

Do not turn off kernel framebuffer support as it is required for a successful boot. If you are using an NVIDIA based chipset, you should use the OpenFirmware framebuffer. If you are using an ATI based chipset, you should select the framebuffer driver based upon your chipset (Mach64, Rage128 or Radeon).

Device Drivers --->
  Graphics support --->
    <*> Support for frame buffer devices
    [*] Open Firmware frame buffer device support
    <*> ATI Radeon display support
    <*> ATI Rage128 display support
    <*> ATI Mach64 display support
    Console display driver support --->
      <*> Framebuffer Console support

When you're done configuring your kernel, continue with Compiling and Installing.

Now that your kernel is configured, it is time to compile and install it. Exit the configuration and run the commands which will compile the kernel:

# make && make modules_install

When the kernel has finished compiling, copy the kernel image to /boot (be sure that it is mounted properly on the Pegasos).

replace 2.6.12 with your kernel-version
(Apple/IBM)  # cp vmlinux /boot/kernel-2.6.12
(Pegasos)    # cp arch/ppc/boot/images/zImage.chrp /boot/kernel-2.6.12

It is also wise to copy over your kernel configuration file to /boot, just in case :)

# cp .config /boot/config-2.6.12-gentoo-r4

Now continue with Installing Separate Kernel Modules.

You should list the modules you want automatically loaded in /etc/modules.autoload.d/kernel-2.6. You can add extra options to the modules too if needed.

To view all available modules, run the following find command. Don't forget to substitute "<kernel version>" with the version of the kernel you just compiled:

# find /lib/modules/<kernel version>/ -type f -iname '*.o' -or -iname '*.ko'

For instance, to automatically load the 3c59x.o module, edit the kernel-2.6 file and enter the module name in it.

# nano -w /etc/modules.autoload.d/kernel-2.6

3c59x

Continue the installation with Configuring your System.