Gentoo Logo

1.  Timezone

You first need to select your timezone so that your system knows where it is located. Look for your timezone in /usr/share/zoneinfo, then copy it to /etc/localtime. Please avoid the /usr/share/zoneinfo/Etc/GMT* timezones as their names do not indicate the expected zones. For instance, GMT-8 is in fact GMT+8.

Code Listing 1.1: Setting the timezone information

# ls /usr/share/zoneinfo
(Suppose you want to use GMT)
# cp /usr/share/zoneinfo/GMT /etc/localtime

1.  Installing the Kernel Sources

Choosing a Kernel

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 kernels to choose from. A full listing with description is available at the Gentoo Kernel Guide.

We suggest using gentoo-sources on PPC, which is a recent 2.6 kernel.

Code Listing 1.1: Installing a kernel source

# emerge --usepkg gentoo-sources

If you take a look in /usr/src you should see a symlink named linux pointing to your current kernel source. In this case, the installed kernel source points to gentoo-sources-${kernel-version}. Your version may be different, so keep this in mind.

Code Listing 1.1: Viewing the kernel source symlink

# ls -l /usr/src/linux
lrwxrwxrwx    1 root     root           22  Mar 18 16:23 /usr/src/linux -> linux-${kernel-gentoo}

Now it is time to configure and compile your kernel source. You can use genkernel for this, which will build a generic kernel as used by the Installation CD. We explain the "manual" configuration first though, as it is a more efficient configuration.

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.

1.  Default: Manual Configuration

Introduction

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 few kernels you won'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 emerging pciutils (emerge --usepkg pciutils) which contains the program lspci. You will now be able to use lspci within the chrooted environment. You may safely ignore any pcilib warnings (such as 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 these kernel messages.

Now, go to your kernel source directory, it's time to configure your kernel. Start by configuring a kernel that will boot on most 32 Bit PowerPC machines by first running make pmac32_defconfig. After the default configuration has been generated, run make menuconfig to start an ncurses-based configuration menu.

Code Listing 1.1: Invoking menuconfig

# cd /usr/src/linux
# make pmac32_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).

Activating Required Options

First 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 the /proc file system and Virtual memory. Make sure that you also enable support for Amiga partitions if you are using a Pegasos, or Macintosh partitions if you are using an Apple computer.

Code Listing 1.1: Selecting necessary file systems

File systems --->
  Pseudo Filesystems --->
(/proc may already be forced on by your configuration, if so, you'll see --- instead)
    [*] /proc file system support
    [*] Virtual memory file system support (former shm fs)
  Partition Types --->
    [*] Advanced partition support
    [*]   Amiga partition table support
    [*]   Macintosh partition map support

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

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:

Code Listing 1.1: Activating HFS support

File Systems --->
  Miscellaneous filesystems --->
    <M> Apple Macintosh file system support
    <M> Apple Extended HFS file system 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:

Code Listing 1.1: Selecting PPPoE necessary drivers

Device Drivers --->
  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 always needed. The PPP over Ethernet option might only be used by ppp when configured to perform kernel mode PPPoE.

Don't forget to include support in the kernel for your ethernet card! Most newer Apple computers use the SunGEM ethernet driver. Older iMacs commonly use the BMAC driver.

Code Listing 1.1: Selecting the network driver

Device Drivers --->
  Network device support --->
    Ethernet (10 or 100Mbit) --->
      [*] Ethernet (10 or 100Mbit)
      <*>   Generic Media Independent Interface device support
      <*>   MACE (Power Mac ethernet) support
      <*>   BMAC (G3 ethernet) support
      <*>   Sun GEM support

At this time, full kernel preemption may still be unstable on PPC and may cause compilation failures and random segfaults. It is strongly suggested that you do not use this feature. Both Voluntary Preemption and No Forced Preemption should be safe.

Code Listing 1.1: Ensure the Preemptible Kernel Option is Off

Kernel options --->
(Select One)
  Preemption Model 
    (X) No Forced Preemption (Server)
    (X) Voluntary Kernel Preemption (Desktop)

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.

Code Listing 1.1: Enable support for firewire devices on boot

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.

Code Listing 1.1: Enable support for USB devices on boot

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 Open Firmware framebuffer. If you are using an ATI based chipset, you should select the framebuffer driver based upon your chipset (Mach64, Rage128 or Radeon).

Code Listing 1.1: Choosing a Framebuffer Driver

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

Note: If you select more than one framebuffer device, it may default to a less than optimal driver. Either use only one framebuffer device or specify which to use by passing the driver to use to the kernel on boot by appending a video line such as: video=radeonfb.

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

Compiling and Installing

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

Code Listing 1.1: Compiling the kernel

# make && make modules_install

When the kernel has finished compiling, copy the kernel image to /boot as shown below. If you have a separate boot partition, as on Pegasos computers, be sure that it is mounted properly. If you are using BootX to boot, we'll copy the kernel later.

Yaboot and BootX expect to use an uncompressed kernel unlike many other bootloaders. The uncompressed kernel is called vmlinux and it is placed in /usr/src/linux after the kernel has finished compiling. If you are using a Pegasos machine, the Pegasos firmware requires a compressed kernel called zImage which can be found in /usr/src/linux/arch/powerpc/boot/images.

Code Listing 1.1: Installing the kernel

# cd /usr/src/linux
Note, your kernel version might be different
(Apple/IBM)
# cp vmlinux /boot/${kernel-name}
(Pegasos)
# cp arch/powerpc/boot/images/zImage /boot/${kernel-name} 

Now continue with Installing Separate Kernel Modules.

1.  Installing Separate Kernel Modules

Configuring the 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 if required.

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:

Code Listing 1.1: Viewing all available modules

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

For instance, to automatically load the 3c59x module, edit the kernel-2.6 file and add the module to it, one module on a line.

Code Listing 1.1: Editing /etc/modules.autoload.d/kernel-2.6

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

Code Listing 1.1: /etc/modules.autoload.d/kernel-2.6

3c59x

Continue the installation with (Configuring your System).

1.  Alternative: Using genkernel

Now that your kernel source tree is installed, it's now time to compile your kernel by using our genkernel script to automatically build a kernel for you. genkernel works by configuring a kernel nearly identically to the way our Installation CD kernel is configured. This means that when you use genkernel to build your kernel, your system will generally detect all your hardware at boot-time, just like our Installation CD does. Because genkernel doesn't require any manual kernel configuration, it is an ideal solution for those users who may not be comfortable compiling their own kernels.

Now, let's see how to use genkernel. First, emerge the genkernel ebuild:

Code Listing 1.1: Emerging genkernel

# emerge --usepkg genkernel

Next, copy over the kernel configuration used by the Installation CD to the location where genkernel looks for the default kernel configuration:

Code Listing 1.1: Copying over the Installation CD kernel config

# zcat /proc/config.gz > /usr/share/genkernel/ppc/kernel-config-2.6

If you are using firewire or USB to boot, you'll need to add modules to the initrd. Edit /usr/share/genkernel/ppc/modules_load and change MODULES_FIREWIRE="ieee1394 ohci1394 sbp2" for firewire support or MODULES_USB="usbcore ohci-hcd ehci-hcd usb-storage" for USB support.

Before compiling your sources, the fstab needs a slight adjustment. The rest of the fstab will be completed during a later step, so don't worry about the details now. If you did not create a separate boot partition (NOT bootstrap, that's different), remove the line referencing /boot from /etc/fstab. This will need to be done on most Apple computers.

Code Listing 1.1: Removing /boot from /etc/fstab on machines without a boot partition

# nano -w /etc/fstab
Remove this line
/dev/BOOT		/boot		ext2		noauto,noatime	1 2

Now, compile your kernel sources by running genkernel --genzimage all. For Pegasos, we will need to use a different config and create a zImage instead of the vmlinux kernel used on Apple machines. Be aware, as genkernel compiles a kernel that supports almost all hardware, this compilation can take quite a while to finish!

Note that, if your partition where the kernel should be located doesn't use ext2 or ext3 as filesystem you might need to manually configure your kernel using genkernel --menuconfig all and add support for your filesystem in the kernel (i.e. not as a module). Users of EVMS2 or LVM2 will probably want to add --evms2 or --lvm2 as an argument as well.

Code Listing 1.1: Running genkernel

# genkernel all

Code Listing 1.1: Running genkernel on the Pegasos

# genkernel --genzimage --kernel-config=/usr/share/genkernel/ppc/Pegasos all

Once genkernel completes, a kernel, full set of modules and initial root disk (initrd) will be created. We will use the kernel and initrd when configuring a boot loader later in this document. Write down the names of the kernel and initrd as you will need them when writing the bootloader configuration file. The initrd will be started immediately after booting to perform hardware autodetection (just like on the Installation CD) before your "real" system starts up. Be sure to also copy down the required boot arguments, these are required for a successful boot with genkernel.

Code Listing 1.1: Checking the created kernel image name and initrd

Note, your kernel version might be different
# ls /boot/kernel-genkernel-ppc-${kernel-gentoo} /boot/initramfs-genkernel-ppc-${kernel-gentoo}

Now continue with (Configuring your System).

Page updated April 1, 2008

Donate to support our development efforts.

Copyright 2001-2014 Gentoo Foundation, Inc. Questions, Comments? Contact us.