Attachment 58305 Details for Bug 91242 – 2005.0 Networkless Handbook Update - Kernel Installation - adds modules.autoload.d

2005.0 Networkless Handbook Update - Kernel Installation - adds modules.autoload.d

hb-install-x86-kernel.xml (text/plain), 14.40 KB, created by Sean D. Quinn on 2005-05-07 18:16:16 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Sean D. Quinn

Created: 2005-05-07 18:16:16 UTC

Size: 14.40 KB

patch

obsolete

><?xml version='1.0' encoding='UTF-8'?>
><!DOCTYPE sections SYSTEM "/dtd/book.dtd">
>
>
>
>
>
>
>
>
><sections>
>
><version>4.4</version>
><date>2005-03-29</date>
>
><section>
><title>Timezone</title>
><body>
>
>
>You first need to select your timezone so that your system knows where it is
>located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a
>symlink to <path>/etc/localtime</path> using <c>ln</c>:
>
>
><pre caption="Setting the timezone information">
># ls /usr/share/zoneinfo
><comment>(Suppose you want to use GMT)</comment>
># ln -sf /usr/share/zoneinfo/GMT /etc/localtime
></pre>
>
></body>
></section>
><section>
><title>Installing the Sources</title>
><subsection>
><title>Choosing a Kernel</title>
><body>
>
>
>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 <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel
>Guide</uri>. 
>
>
>
>For x86-based systems, our main supported kernel is named
><c>gentoo-sources</c>. This kernel is based on the official Linux sources, but
>has security, stability, compatibility and bug fixes applied on top.
>Alternatively, the plain and unpatched Linux sources are supplied through the
><c>vanilla-sources</c> package.
>
>
>
>Both kernel sources are based on the official 2.6 kernel sources. If you
>want to install a 2.4-based kernel, you will need to install Gentoo with a
>working Internet connection as we do not supply these sources on our
>Installation CD.
>
>
>
>Choose your kernel source and install it using <c>emerge</c>. 
>
>
><pre caption="Installing a kernel source">
># emerge gentoo-sources
></pre>
>
>
>When you take a look in <path>/usr/src</path> you should see a symlink called
><path>linux</path> pointing to your kernel source. We will assume the kernel
>source installed is <c>gentoo-sources-2.6.11-r3</c>:
>
>
><pre caption="Viewing the kernel source symlink">
># ls -l /usr/src/linux
>lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.6.11-gentoo-r3
></pre>
>
>
>If the symlink doesn't point to the kernel source of your choice (note that
><c>linux-2.6.11-gentoo-r3</c> is merely an example) you should change it to the
>right kernel:
>
>
><pre caption="Changing the kernel source symlink">
># rm /usr/src/linux
># cd /usr/src
># ln -s linux-2.6.11-gentoo-r3 linux
></pre>
>
>
>Now it is time to configure and compile your kernel source. You 
>can use <c>genkernel</c> for this, which will build a generic kernel as used 
>by the Installation CD. 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 <uri
>link="#manual">Default: Manual Configuration</uri>. If you want to use 
><c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using 
>genkernel</uri> instead.
>
>
></body>
></subsection>
></section>
><section id="manual">
><title>Default: Manual Configuration</title>
><subsection>
><title>Introduction</title>
><body>
>
>
>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 don't even remember that it was difficult ;)
>
>
>
>However, one thing <e>is</e> true: you must know your system when you start
>configuring a kernel manually. Most information can be gathered by viewing the
>contents of <path>/proc/pci</path> (or by using <c>lspci</c> if available). You
>can also run <c>lsmod</c> to see what kernel modules the Installation CD uses 
>(it might provide you with a nice hint on what to enable).
>
>
>
>Now go to your kernel source directory and execute <c>make menuconfig</c>. This
>will fire up an ncurses-based configuration menu.
>
>
><pre caption="Invoking menuconfig">
># cd /usr/src/linux
># make menuconfig
></pre>
>
>
>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).
>
>
></body>
></subsection>
><subsection>
><title>Activating Required Options</title>
><body>
>
>
>Make sure that every driver that is vital to the booting of your system (such as
>SCSI controller, ...) is compiled <e>in</e> the kernel and not as a module,
>otherwise your system will not be able to boot completely.
>
>
>
>Now select the correct processor family:
>
>
><pre caption="Selecting correct processor family">
>Processor type and features ---&gt;
> Subarchitecture Type (PC-compatible) ---&gt;
> <comment>(Change according to your system)</comment>
> (Athlon/Duron/K7) Processor family
></pre>
>
>
>Now go to <c>File Systems</c> and select support for the filesystems you use.
><e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
>able to mount your partitions. Also select <c>/proc file system</c> and
><c>Virtual memory</c>. Do <e>not</e> select the <c>/dev file system</c>.
>
>
><pre caption="Selecting necessary file systems">
>File systems ---&gt;
> Pseudo Filesystems ---&gt;
> &lt;*&gt; /proc file system support
> &lt; &gt; /dev file system support (OBSOLETE)
> &lt;*&gt; Virtual memory file system support (former shm fs)
>
>
><comment>(Select one or more of the following options as needed by your system)</comment>
> &lt;*&gt; Reiserfs support
> &lt;*&gt; Ext3 journalling file system support
> &lt;*&gt; JFS filesystem support
> &lt;*&gt; Second extended fs support
> &lt;*&gt; XFS filesystem support
></pre>
>
>
>Do not forget to enable DMA for your drives:
>
>
><pre caption="Activating DMA">
>Device Drivers ---&gt;
> ATA/ATAPI/MFM/RLL support ---&gt;
> [*] Generic PCI bus-master DMA support
> [*] Use PCI DMA by default when available
></pre>
>
>
>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:
>
>
><pre caption="Selecting PPPoE necessary drivers">
>Device Drivers ---&gt;
> Networking support ---&gt;
> &lt;*&gt; PPP (point-to-point protocol) support
> &lt;*&gt; PPP support for async serial ports
> &lt;*&gt; PPP support for sync tty ports
></pre>
>
>
>The two compression options won't harm but are not definitely needed, neither
>does the <c>PPP over Ethernet</c> option, that might only be used by 
><c>rp-pppoe</c> 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":
>
>
><pre caption="Activating SMP support">
>Processor type and features ---&gt;
> &lt;*&gt; Symmetric multi-processing support
></pre>
>
>
>If you use USB Input Devices (like Keyboard or Mouse) don't forget to enable
>those as well:
>
>
><pre caption="Activating USB Support for Input Devices">
>Device Drivers ---&gt;
> USB Support ---&gt;
> &lt;*&gt; USB Human Interface Device (full HID) support
> [*] HID input layer support 
></pre>
>
>
>If you are a laptop user and require PCMCIA support, remember to compile it
>into the kernel. As well as the option below, be sure to enable support for
>the PCMCIA card bridge present in your system (found in the same menu of the
>configuration).
>
>
><pre caption="Activating PCMCIA support">
>Bus options (PCI, PCMCIA, EISA, MCA, ISA) ---&gt;
> PCCARD (PCMCIA/CardBus) support ---&gt;
> &lt;*&gt; PCCard (PCMCIA/CardBus) support
> <comment>(select 16 bit if you need support for older PCMCIA cards. Most people want this.)</comment>
> &lt;*&gt; 16-bit PCMCIA support
> [*] 32-bit CardBus support
> <comment>(select the relevant bridges below)</comment>
> --- PC-card bridges
> &lt;*&gt; CardBus yenta-compatible bridge support (NEW)
> &lt;*&gt; Cirrus PD6729 compatible bridge support (NEW)
> &lt;*&gt; i82092 compatible bridge support (NEW)
> &lt;*&gt; i82365 compatible bridge support (NEW)
> &lt;*&gt; Databook TCIC host bridge support (NEW)
></pre>
>
></body>
></subsection>
><subsection id="compiling">
><title>Compiling and Installing</title>
><body>
>
>
>Now that your kernel is configured, it is time to compile and install it. Exit 
>the configuration and start the compilation process:
>
>
><pre caption="Compiling the kernel">
># make &amp;&amp; make modules_install
></pre>
>
>
>When the kernel has finished compiling, copy the kernel image to
><path>/boot</path>. From here onwards we assume that the kernel you are
>installing is the 2.6.11-r3 version of the <c>gentoo-sources</c>. 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.
>
>
><pre caption="Installing the kernel">
># cp arch/i386/boot/bzImage /boot/kernel-2.6.11-gentoo-r3
></pre>
>
>
>It is also wise to copy over your kernel configuration file to
><path>/boot</path>, just in case :)
>
>
><pre caption="Backing up your kernel configuration">
># cp .config /boot/config-2.6.11-gentoo-r3
></pre>
>
>
>Now continue with <uri link="?part=1&amp;chap=8">Configuring your System</uri>.
>
>
></body>
></subsection>
></section>
><section id="genkernel">
><title>Alternative: Using genkernel</title>
><body>
>
>
>If you are reading this section, you have chosen to use our <c>genkernel</c>
>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 <c>genkernel</c> script to automatically build a kernel for 
>you. <c>genkernel</c> works by configuring a kernel nearly identically to the 
>way our Installation CD kernel is configured. This means that when you use 
><c>genkernel</c> 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:
>
>
><pre caption="Emerging genkernel">
># emerge genkernel
></pre>
>
>
>Next, copy over the kernel configuration used by the Installation CD to the 
>location where genkernel looks for the default kernel configuration:
>
>
><pre caption="Copying over the Installation CD kernel config">
># zcat /proc/config.gz > /usr/share/genkernel/x86/kernel-config-2.6
></pre>
>
>
>Now, compile your kernel sources by running <c>genkernel --udev all</c>.
>Be aware though, as <c>genkernel</c> 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
>might need to manually configure your kernel using <c>genkernel --menuconfig 
>all</c> and add support for your filesystem <e>in</e> the kernel (i.e. 
><e>not</e> as a module). Users of EVMS2 or LVM2 will probably want to add
><c>--evms2</c> or <c>--lvm2</c> as argument as well.
>
>
><pre caption="Running genkernel">
># genkernel --udev all
></pre>
>
>
>Once <c>genkernel</c> completes, a kernel, full set of modules and 
><e>initial root disk</e> (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 Installation CD) 
>before your "real" system starts up.
>
>
><pre caption="Checking the created kernel image name and initrd">
># ls /boot/kernel* /boot/initrd*
></pre>
></body>
><subsection>
><title>Configuring the Modules</title>
><body>
>
>If you want your system to be more like the Installation CD you should,
>when your Gentoo installation is over, emerge <c>coldplug</c>. While the 
>initrd autodetects hardware that is needed to boot your system, 
><c>coldplug</c> autodetects everything else. <c>coldplug</c> is available as one
>of the packages on the Package CD.
>
>
><pre caption="Emerging and enabling coldplug">
><comment>(Do this after the installation, during the GRP installation instructions)</comment>
># emerge -k coldplug
># rc-update add coldplug boot
></pre>
>
>
>If you want your system to react to hotplugging events, you will need to install
>and setup <c>hotplug</c> as well:
>
>
><pre caption="Emerging and enabling hotplug">
><comment>(Do this after the installation, during the GRP installation instructions)</comment>
># emerge -k hotplug
># rc-update add hotplug default
></pre>
>
>
>There is an alternative to using <c>coldplug</c> or <c>hotplug</c>. To have your kernel modules detected on boot, you must edit <path>/etc/modules.autoload.d/kernel-2.6 (or 2.4)</path> to include the modules you want to have automatically detected at boot. Extra options can be added to the modules as well, if you wish.
>
>
>
>To find all the modules installed on your system, you must run the below command. Remember to replace "&lt;kernel version&gt; with the correct kernel version.
>
>
><pre caption="Viewing all installed modules">
># find /lib/modules/&lt;kernel version&gt;/ -type f -iname '*.o' -or -iname '*.ko' 	 
></pre> 	 
>
>	 
>For instance, to automatically load the <c>3c59x.o</c> module, edit the <path>kernel-2.4</path> or <path>kernel-2.6</path> file and enter the module name in it. 	 
> 
>
>	 
><pre caption="Editing /etc/modules.autoload.d/kernel-2.4"> 	 
><comment>(Example for 2.4 kernels)</comment> 	 
># nano -w /etc/modules.autoload.d/kernel-2.4 	 
></pre> 	 
> 	 
><pre caption="/etc/modules.autoload.d/kernel-2.4 or kernel-2.6"> 	 
>3c59x 	 
></pre> 	 
> 	 
> 	 
>Now run <c>modules-update</c> to commit your changes to the 	 
><path>/etc/modules.conf</path> file: 	 
> 	 
> 	 
><pre caption="Running modules-update"> 	 
># modules-update
></pre>
>
>
>
>Now continue with <uri link="?part=1&amp;chap=8">Configuring your System</uri>.
>
>
></body>
></subsection>
></section>
></sections>

Actions: View

Attachments on bug 91242: 58305 | 58306 | 58310