The core around which all distributions are built is the Linux kernel. It is the layer between the user 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.

For PPC you can choose between ppc-sources, ppc-sources-benh, ppc-sources-dev, ppc-sources-crypto and ppc-development-sources. This latter kernel is available when you perform a networkless installation. So let's continue with emerge'ing the kernel sources:

# emerge ppc-development-sources

When you take a look in /usr/src you should see a symlink called linux pointing to your kernel source:

# ls -l /usr/src/linux
lrwxrwxrwx    1 root     root           12 Oct 13 11:04 /usr/src/linux -> linux-2.6.1

If this isn't the case (i.e. the symlink points to a different kernel source) change the symlink before you continue:

# rm /usr/src/linux && ln -s /usr/src/linux-2.6.1 /usr/src/linux

Now it is time to configure and compile your kernel source. All architectures can use genkernel for this, which will build a generic kernel as used by the LiveCD. We explain the "manual" configuration first though, as it is the best way to optimize your environment.

Continue now with Manual Configuration.

Manually configuring a kernel is often seen as the most difficult course every Linux users ever has to go through. Nothing is less true -- after configuring a couple of kernels you don't even remember that it was difficult ;)

However, one thing is true: you must know your system when you start configuring a kernel manually. Most information can be gathered by viewing the contents of /proc/pci (or by using lspci if available). You can also run lsmod to see what kernel modules the LiveCD uses (it might provide you with a nice hint on what to enable).

Now go to your kernel source directory and execute make menuconfig. This will fire up an ncurses-based configuration menu.

# cd /usr/src/linux
# 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

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 Virtual memory, /proc file system, /dev file system + Automatically mount at boot:

File systems --->
  [*] Virtual memory file system support (former shm fs)
  [*] /proc file system support
  [*] /dev file system support (EXPERIMENTAL)
  [*]   Automatically mount at boot

(Deselect the following unless you have a 2.6 kernel)
  [ ] /dev/pts file system for Unix98 PTYs

(Select one or more of the following options as needed by your system)
  <*> Reiserfs support
  <*> Ext3 journalling file system support
  <*> JFS filesystem support
  <*> Second extended fs 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:

Network device 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.

Disable ADB raw keycodes:

Macintosh Device Drivers --->
  [ ] Support for ADB raw keycodes

Also choose the correct RTC support (disable the Enhanced RTC option):

Character devices --->
  [ ] Enhanced RTC

General setup --->
  [*] Support for /dev/rtc

Users of OldWorld machines will want HFS support so they can copy compiled kernels to the MacOS partition.

File Systems --->
  [*] HFS 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 make dep && make vmlinux modules modules_install or on the Pegasos run make dep && make zImage modules modules_install:

(Apple/IBM)  # make dep && make vmlinux modules modules_install
(Pegasos)    # make dep && make zImage modules modules_install

When the kernel is done compiling, copy over the kernel image to /boot.

(Apple/IBM)  # cp vmlinux /boot/kernel-2.4.24
(Pegasos)    # cp arch/ppc/boot/images/zImage.chrp /boot/kernel-2.4.24

Also don't forget to copy over the system map:

# cp System.map /boot/System.map-2.4.24

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

# cp .config /boot/config-2.4.24

Now continue with Installing Separate Kernel Modules.

If appropriate, you should emerge ebuilds for any additional hardware that is on your system. Here is a list of kernel-related ebuilds that you could emerge:

Beware though, some of these ebuilds might deal with big dependencies. To verify what packages will be installed by emerging an ebuild, use emerge --pretend. For instance, for the xfree-drm package:

# emerge --pretend xfree-drm

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

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.4 or kernel-2.6 file and enter the module name in it.

(Example for 2.4 kernels)
# nano -w /etc/modules.autoload.d/kernel-2.4

3c59x

Now run modules-update to commit your changes to the /etc/modules.conf file:

# modules-update

Continue the installation with Configuring your System.