[ << ] [ < ] [ Home ] [ > ] [ >> ]
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 make a symlink to /etc/localtime using ln:
# ls /usr/share/zoneinfo (Suppose you want to use GMT) # ln -sf /usr/share/zoneinfo/GMT /etc/localtime
7.b. Installing the 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 kernel sources. A full listing with description is available at the Gentoo Kernel Guide.
For x86-based systems we have, amongst other kernels, vanilla-sources (the default kernel source as developed by the linux-kernel developers), gentoo-sources (kernel source patched with performance-enhancing features), gentoo-dev-sources (kernel v2.6 source patched with performance-enhancing features), gs-sources (kernel source patched for server usage), development-sources (vanilla 2.6 kernel source), ...
If you are performing a network-less install you can't pick any of the available kernels as we only provide sources for a few of them. If this is the case, you are restricted to using gentoo-sources, vanilla-sources, development-sources or gentoo-dev-sources.
Choose your kernel source and install it using emerge.
# emerge gentoo-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.4.26-gentoo-r6
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 # cd /usr/src # ln -s linux-2.4.26-gentoo-r6 linux
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 LiveCD. We explain the "manual" configuration first though, as it is the best way to optimize your environment.
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.
7.c. Default: 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).
Activating Required Options
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
Make sure that you compile your kernel with the correct processor family:
Processor type and features ---> Subarchitecture Type (PC Compatible) ---> (Change according to your system) Processor family (Athlon/Duron/K7) --->
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:
(With a 2.4.x kernel) File systems ---> [*] Virtual memory file system support (former shm fs) [*] /proc file system support [*] /dev file system support (EXPERIMENTAL) [*] Automatically mount at boot [ ] /dev/pts file system for Unix98 PTYs (With a 2.6.x kernel) File systems ---> Pseudo Filesystems ---> [*] /proc file system support [*] /dev file system support (OBSOLETE) [*] Automatically mount at boot [*] Virtual memory file system support (former shm fs) (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 your BIOS can't handle large harddrives and you jumpered the harddrive to report a limited size you have to enable the following option to gain access to your whole harddrive:
(2.4.x kernel only) ATA/IDE/MFM/RLL support ---> IDE, ATA and ATAPI Block devices ---> <*> Include IDE/ATA-2 DISK support [ ] Use multi-mode by default [*] Auto-Geometry Resizing 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:
(With a 2.4.x kernel) Network device support ---> <*> PPP (point-to-point protocol) support <*> PPP support for async serial ports <*> PPP support for sync tty ports (With a 2.6.x 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.
If you have an Intel CPU that supports HyperThreading (tm), or you have a multi-CPU system, you should activate "Symmetric multi-processing support":
Processor type and features ---> [*] Symmetric multi-processing support
When you've finished configuring the 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 and run make dep && make bzImage modules modules_install:
(For 2.4 kernel) # make dep && make bzImage modules modules_install (For 2.6 kernel) # make && make modules_install
When the kernel is done compiling, copy over the kernel image to /boot. From here onwards we assume that the kernel you are installing is the 2.4.26 version of the gentoo-sources. Use whatever name you feel is appropriate for your choice and remember it as you will need it later on when you configure your bootloader.
# cp arch/i386/boot/bzImage /boot/kernel-2.4.26-gentoo-r6 # cp System.map /boot/System.map-2.4.26-gentoo-r6
It is also wise to copy over your kernel configuration file to /boot, just in case :)
# cp .config /boot/config-2.4.26-gentoo-r6
Now continue with Installing Separate Kernel Modules.
7.d. Alternative: Using genkernel
If you are reading this section, you have chosen to use our genkernel script to configure your kernel for you.
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 LiveCD 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 Live 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:
# emerge genkernel
Now, compile your kernel sources by running genkernel all. Be aware though, as genkernel compiles a kernel that supports almost all hardware, this compilation will take quite a while to finish!
Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you 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).
# genkernel 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 it when writing the bootloader configuration file. The initrd will be started immediately after booting to perform hardware autodetection (just like on the Live CD) before your "real" system starts up.
# ls /boot/kernel* /boot/initrd*
Now, let's perform one more step to get our system to be more like the Live CD -- let's emerge hotplug. While the initrd autodetects hardware that is needed to boot your system, hotplug autodetects everything else. To emerge and enable hotplug, type the following:
# emerge hotplug # rc-update add hotplug default
7.e. Installing Separate Kernel Modules
Installing Extra 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:
|nvidia-kernel||Accelerated NVIDIA graphics for XFree86||emerge nvidia-kernel|
|nforce-net||On-board ethernet controller on NVIDIA NForce(2) motherboards||emerge nforce-net|
|nforce-audio||On-board audio on NVIDIA NForce(2) motherboards||emerge nforce-audio|
|e100||Intel e100 Fast Ethernet Adapters||emerge e100|
|e1000||Intel e1000 Gigabit Ethernet Adapters||emerge e1000|
|emu10k1||Creative Sound Blaster Live!/Audigy support||emerge emu10k1|
|ati-drivers||Accelerated ATI Radeon 8500+/FireGL graphics for XFree86||emerge ati-drivers|
|ati-drivers-extra||Graphical ATI tools||emerge ati-drivers-extra|
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 emu10k1 package:
# emerge --pretend emu10k1
If you don't like the packages it wants to install, use emerge --pretend --verbose to see what USE-flags are checked when deciding the dependencies:
# emerge --pretend --verbose emu10k1 ... [ebuild N ] media-sound/aumix-2.8 +gpm +nls +gtk +gnome +alsa -gtk2
In the previous example you can see that one of emu10k1's dependencies (aumix) uses the gtk and gnome USE-flags, making gtk (which depends on XFree) be compiled with it.
If you don't want all this to be compiled, deselect all USE-flags, for instance:
# USE="-gpm -nls -gtk -gnome -alsa" emerge --pretend emu10k1
When you're happy with the results, remove the --pretend to start installing emu10k1.
Configuring the Modules
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
Now run modules-update to commit your changes to the /etc/modules.conf file:
Continue the installation with Configuring your System.
[ << ] [ < ] [ Home ] [ > ] [ >> ]