/[gentoo]/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml
Gentoo

Contents of /xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.10 - (hide annotations) (download) (as text)
Wed Oct 20 09:32:44 2004 UTC (10 years, 2 months ago) by swift
Branch: MAIN
Changes since 1.9: +3 -2 lines
File MIME type: application/xml
#68162 - Recent kernels create uncompressed images

1 swift 1.1 <?xml version='1.0' encoding='UTF-8'?>
2     <!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3    
4     <!-- The content of this document is licensed under the CC-BY-SA license -->
5     <!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
6    
7 swift 1.10 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml,v 1.9 2004/09/19 19:49:17 vapier Exp $ -->
8 swift 1.1
9     <sections>
10     <section>
11     <title>Timezone</title>
12     <body>
13    
14     <p>
15     You first need to select your timezone so that your system knows where it is
16     located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then make a
17     symlink to <path>/etc/localtime</path> using <c>ln</c>:
18     </p>
19    
20     <pre caption="Setting the timezone information">
21     # <i>ls /usr/share/zoneinfo</i>
22     <comment>(Suppose you want to use GMT)</comment>
23     # <i>ln -sf /usr/share/zoneinfo/GMT /etc/localtime</i>
24     </pre>
25    
26     </body>
27     </section>
28     <section>
29     <title>Installing the Sources</title>
30     <subsection>
31     <title>Choosing a Kernel</title>
32     <body>
33    
34     <p>
35     The core around which all distributions are built is the Linux kernel. It is the
36     layer between the user programs and your system hardware. Gentoo provides its
37     users several possible kernel sources. A full listing with description is
38     available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel
39     Guide</uri>.
40     </p>
41    
42     <p>
43     For alpha-based systems we have <c>vanilla-sources</c> (the default kernel
44     source as developed by the linux-kernel developers), <c>alpha-sources</c>
45     (kernel source optimized for alpha users) and <c>compaq-sources</c> (kernel
46     source as used by RedHat for Alpha, maintained by Compaq).
47     </p>
48    
49     <p>
50     Choose your kernel source and install it using <c>emerge</c>.
51     </p>
52    
53     <p>
54     In the next example we install the <c>vanilla-sources</c>.
55     Of course substitute with your choice of sources, this is merely an example:
56     </p>
57    
58     <pre caption="Installing a kernel source">
59     # <i>emerge vanilla-sources</i>
60     </pre>
61    
62     <p>
63     When you take a look in <path>/usr/src</path> you should see a symlink called
64     <path>linux</path> pointing to your kernel source:
65     </p>
66    
67     <pre caption="Viewing the kernel source symlink">
68     # <i>ls -l /usr/src/linux</i>
69     lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.4.24
70     </pre>
71    
72     <p>
73     If this isn't the case (i.e. the symlink points to a different kernel source)
74     change the symlink before you continue:
75     </p>
76    
77     <pre caption="Changing the kernel source symlink">
78 swift 1.3 # <i>rm /usr/src/linux</i>
79     # <i>cd /usr/src</i>
80     # <i>ln -s linux-2.4.24 linux</i>
81 swift 1.1 </pre>
82    
83     <p>
84     Now it is time to configure and compile your kernel source. You
85     can use <c>genkernel</c> for this, which will build a generic kernel as used
86     by the LiveCD. We explain the "manual" configuration first though, as it is
87     the best way to optimize your environment.
88     </p>
89    
90     <p>
91     If you want to manually configure your kernel, continue now with <uri
92     link="#manual">Default: Manual Configuration</uri>. If you want to use
93     <c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using
94     genkernel</uri> instead.
95     </p>
96    
97     </body>
98     </subsection>
99     </section>
100     <section id="manual">
101     <title>Default: Manual Configuration</title>
102     <subsection>
103     <title>Introduction</title>
104     <body>
105    
106     <p>
107 neysx 1.7 Manually configuring a kernel is often seen as the most difficult procedure a
108 neysx 1.8 Linux user ever has to perform. Nothing is less true -- after configuring a
109 swift 1.1 couple of kernels you don't even remember that it was difficult ;)
110     </p>
111    
112     <p>
113     However, one thing <e>is</e> true: you must know your system when you start
114     configuring a kernel manually. Most information can be gathered by viewing the
115     contents of <path>/proc/pci</path> (or by using <c>lspci</c> if available). You
116     can also run <c>lsmod</c> to see what kernel modules the LiveCD uses (it might
117     provide you with a nice hint on what to enable).
118     </p>
119    
120     <p>
121     Now go to your kernel source directory and execute <c>make menuconfig</c>. This
122     will fire up an ncurses-based configuration menu.
123     </p>
124    
125     <pre caption="Invoking menuconfig">
126     # <i>cd /usr/src/linux</i>
127     # <i>make menuconfig</i>
128     </pre>
129    
130     <p>
131     You will be greeted with several configuration sections. We'll first list some
132     options you must activate (otherwise Gentoo will not function, or not function
133     properly without additional tweaks).
134     </p>
135    
136     </body>
137     </subsection>
138     <subsection>
139     <title>Activating Required Options</title>
140     <body>
141    
142     <p>
143     First of all, activate the use of development and experimental code/drivers.
144     You need this, otherwise some very important code/drivers won't show up:
145     </p>
146    
147     <pre caption="Selecting experimental code/drivers">
148     Code maturity level options ---&gt;
149     [*] Prompt for development and/or incomplete code/drivers
150     </pre>
151    
152     <p>
153     Now go to <c>File Systems</c> and select support for the filesystems you use.
154     <e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
155     able to mount your partitions. Also select <c>Virtual memory</c>, <c>/proc
156     file system</c>, <c>/dev file system</c> + <c>Automatically mount at boot</c>:
157     </p>
158    
159     <pre caption="Selecting necessary file systems">
160 neysx 1.4 <comment>(With a 2.4.x kernel)</comment>
161 swift 1.1 File systems ---&gt;
162     [*] Virtual memory file system support (former shm fs)
163     [*] /proc file system support
164     [*] /dev file system support (EXPERIMENTAL)
165     [*] Automatically mount at boot
166 neysx 1.4 [ ] /dev/pts file system for Unix98 PTYs
167 swift 1.1
168 neysx 1.4 <comment>(With a 2.6.x kernel)</comment>
169     File systems ---&gt;
170     Pseudo Filesystems ---&gt;
171     [*] /proc file system support
172     [*] /dev file system support (OBSOLETE)
173     [*] Automatically mount at boot
174     [*] Virtual memory file system support (former shm fs)
175 swift 1.1
176     <comment>(Select one or more of the following options as needed by your system)</comment>
177     &lt;*&gt; Reiserfs support
178     &lt;*&gt; Ext3 journalling file system support
179     &lt;*&gt; JFS filesystem support
180     &lt;*&gt; Second extended fs support
181     &lt;*&gt; XFS filesystem support
182     </pre>
183    
184     <p>
185     If you are using PPPoE to connect to the Internet or you are using a dial-up
186     modem, you will need the following options in the kernel:
187     </p>
188    
189     <pre caption="Selecting PPPoE necessary drivers">
190 neysx 1.4 <comment>(With a 2.4.x kernel)</comment>
191 swift 1.1 Network device support ---&gt;
192     &lt;*&gt; PPP (point-to-point protocol) support
193     &lt;*&gt; PPP support for async serial ports
194     &lt;*&gt; PPP support for sync tty ports
195 neysx 1.4
196     <comment>(With a 2.6.x kernel)</comment>
197     Device Drivers ---&gt;
198     Networking support ---&gt;
199     &lt;*&gt; PPP (point-to-point protocol) support
200     &lt;*&gt; PPP support for async serial ports
201     &lt;*&gt; PPP support for sync tty ports
202 swift 1.1 </pre>
203    
204     <p>
205     The two compression options won't harm but are not definitely needed, neither
206     does the <c>PPP over Ethernet</c> option, that might only be used by
207     <c>rp-pppoe</c> when configured to do kernel mode PPPoE.
208     </p>
209    
210     <p>
211     If you require it, don't forget to include support in the kernel for your
212     ethernet card.
213     </p>
214    
215     <p>
216 vapier 1.9 The following options are recommended as well:
217 swift 1.1 </p>
218    
219 vapier 1.9 <pre caption="Recommended Alpha options">
220 swift 1.1 General setup ---&gt;
221     &lt;*&gt; SRM environment through procfs
222     &lt;*&gt; Configure uac policy via sysctl
223    
224     Plug and Play configuration ---&gt;
225     &lt;*&gt; Plug and Play support
226     &lt;M&gt; ISA Plug and Play support
227    
228     SCSI support ---&gt;
229     SCSI low-level drivers ---&gt;
230     &lt;*&gt; SYM53C8XX Version 2 SCSI support (NEW)
231     &lt;*&gt; Qlogic ISP SCSI support
232    
233     Network device support ---&gt;
234     Ethernet (10 or 100 Mbit) ---&gt;
235     &lt;M&gt; DECchip Tulip (dc21x4x) PCI support
236     &lt;M&gt; Generic DECchip &amp; DIGITAL EtherWORKS PCI/EISA
237     &lt;M&gt; EtherExpressPro/100 support (eepro100)
238     &lt;M&gt; EtherExpressPro/100 support (e100)
239     Ethernet (1000 Mbit) ---&gt;
240     &lt;M&gt; Alteon AceNIC
241     [*] Omit support for old Tigon I
242     &lt;M&gt; Broadcom Tigon3
243     [*] FDDI driver support
244     &lt;M&gt; Digital DEFEA and DEFPA
245     &lt;*&gt; PPP support
246     &lt;*&gt; PPP Deflate compression
247    
248     Character devices ---&gt;
249     [*] Support for console on serial port
250     [*] Direct Rendering Manager
251    
252     File systems ---&gt;
253     &lt;*&gt; Kernel automounter version 4 support
254     Network File Systems ---&gt;
255     &lt;*&gt; NFS
256     [*] NFSv3 client
257     &lt;*&gt; NFS server
258     [*] NFSv3 server
259     Partition Types ---&gt;
260     [*] Advanced partition selection
261     [*] Alpha OSF partition support
262     Native Language Support
263     &lt;*&gt; NLS ISO 8859-1
264    
265     Sound ---&gt;
266     &lt;M&gt; Sound card support
267     &lt;M&gt; OSS sound modules
268     [*] Verbose initialisation
269     [*] Persistent DMA buffers
270     &lt;M&gt; 100% Sound Blaster compatibles
271     </pre>
272    
273     <p>
274     When you've finished configuring the kernel, continue with <uri
275     link="#compiling">Compiling and Installing</uri>.
276     </p>
277    
278     </body>
279     </subsection>
280     <subsection id="compiling">
281     <title>Compiling and Installing</title>
282     <body>
283    
284     <p>
285     Now that your kernel is configured, it is time to compile and install it. Exit
286     the configuration and run <c>make dep &amp;&amp; make vmlinux modules
287     modules_install</c>:
288     </p>
289    
290     <pre caption="Compiling the kernel">
291     <comment>(For 2.4 kernel)</comment>
292     # <i>make dep &amp;&amp; make vmlinux modules modules_install</i>
293    
294     <comment>(For 2.6 kernel)</comment>
295     # <i>make &amp;&amp; make modules_install</i>
296 vapier 1.6
297     <comment>(For all kernels)</comment>
298     # <i>make boot</i>
299 swift 1.1 </pre>
300    
301     <p>
302 neysx 1.7 When the kernel has finished compiling, copy the kernel image to
303 swift 1.1 <path>/boot</path>. In the next example we assume you have configured and
304 swift 1.10 compiled <c>vanilla-sources-2.4.24</c>; recent kernels might create
305     <path>vmlinux</path> instead of <path>vmlinux.gz</path>.
306 swift 1.1 </p>
307    
308     <pre caption="Installing the kernel">
309 vapier 1.6 # <i>cp arch/alpha/boot/vmlinux.gz /boot/</i>
310 swift 1.1 # <i>cp System.map /boot/System.map-2.4.24</i>
311     </pre>
312    
313     <p>
314     It is also wise to copy over your kernel configuration file to
315     <path>/boot</path>, just in case :)
316     </p>
317    
318     <pre caption="Backing up your kernel configuration">
319     # <i>cp .config /boot/config-2.4.24</i>
320     </pre>
321    
322     <p>
323     Now continue with <uri link="#kernel_modules">Installing Separate Kernel
324     Modules</uri>.
325     </p>
326    
327     </body>
328     </subsection>
329     </section>
330     <section id="genkernel">
331     <title>Alternative: Using genkernel</title>
332     <body>
333    
334     <p>
335     If you are reading this section, you have chosen to use our <c>genkernel</c>
336     script to configure your kernel for you.
337     </p>
338    
339     <p>
340     Now that your kernel source tree is installed, it's now time to compile your
341     kernel by using our <c>genkernel</c> script to automatically build a kernel for
342     you. <c>genkernel</c> works by configuring a kernel nearly identically to the
343     way our LiveCD kernel is configured. This means that when you use
344     <c>genkernel</c> to build your kernel, your system will generally detect all
345     your hardware at boot-time, just like our Live CD does. Because genkernel
346     doesn't require any manual kernel configuration, it is an ideal solution for
347     those users who may not be comfortable compiling their own kernels.
348     </p>
349    
350     <p>
351     Now, let's see how to use genkernel. First, emerge the genkernel ebuild:
352     </p>
353    
354     <pre caption="Emerging genkernel">
355     # <i>emerge genkernel</i>
356     </pre>
357    
358     <p>
359     Now, compile your kernel sources by running <c>genkernel all</c>.
360     Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all
361     hardware, this compilation will take quite a while to finish!
362     </p>
363    
364     <p>
365     Note that, if your boot partition doesn't use ext2 or ext3 as filesystem you
366     need to manually configure your kernel using <c>genkernel --menuconfig all</c>
367     and add support for your filesystem <e>in</e> the kernel (i.e. <e>not</e> as a
368     module).
369     </p>
370    
371     <pre caption="Running genkernel">
372     # <i>genkernel all</i>
373     GenKernel v3.0.1_beta10
374     * ARCH: Alpha
375     * KERNEL VER: 2.4.24
376     * kernel: configuring source
377     * kernel: running mrproper
378     <comment>(Output removed to increase readability)</comment>
379     * Kernel compiled successfully!
380     * Required Kernel Params:
381     * : root=/dev/ram0 init=/linuxrc real_root=/dev/$ROOT
382     * where $ROOT is the devicenode for your root partition as
383     * you should have specified in /etc/fstab
384     *
385     * You MUST tell your bootloader to use the generated initrd
386     *
387     * Recommended Kernel Params:
388     * : vga=0x317 splash=verbose
389     *
390     * Do NOT report kernel bugs (configs included) as genkernel bugs.
391     * Make sure you have the latest genkernel before reporting bugs
392     *
393     * For more info see /usr/share/genkernel/README
394     </pre>
395    
396     <p>
397     Once <c>genkernel</c> completes, a kernel, full set of modules and
398     <e>initial root disk</e> (initrd) will be created. We will use the kernel
399     and initrd when configuring a boot loader later in this document. Write
400     down the names of the kernel and initrd as you will need it when writing
401     the bootloader configuration file. The initrd will be started immediately after
402     booting to perform hardware autodetection (just like on the Live CD) before
403     your "real" system starts up.
404     </p>
405    
406     <pre caption="Checking the created kernel image name and initrd">
407     # <i>ls /boot/kernel* /boot/initrd*</i>
408     </pre>
409    
410     <p>
411     Now, let's perform one more step to get our system to be more like the Live
412     CD -- let's emerge <c>hotplug</c>. While the initrd autodetects hardware that
413     is needed to boot your system, <c>hotplug</c> autodetects everything else.
414     To emerge and enable <c>hotplug</c>, type the following:
415     </p>
416    
417     <pre caption="Emerging and enabling hotplug">
418     # <i>emerge hotplug</i>
419     # <i>rc-update add hotplug default</i>
420     </pre>
421    
422     </body>
423     </section>
424     <section id="kernel_modules">
425     <title>Installing Separate Kernel Modules</title>
426     <subsection>
427     <title>Installing Extra Modules</title>
428     <body>
429    
430     <p>
431     If appropriate, you should emerge ebuilds for any additional hardware that is
432     on your system. Here is a list of kernel-related ebuilds that you could emerge:
433     </p>
434    
435     <table>
436     <tcolumn width="1in"/>
437     <tcolumn width="4in"/>
438     <tcolumn width="2in"/>
439     <tr>
440     <th>Ebuild</th>
441     <th>Purpose</th>
442     <th>Command</th>
443     </tr>
444     <tr>
445     <ti>xfree-drm</ti>
446     <ti>
447     Accelerated graphics for ATI Radeon up to 9200, Rage128, Matrox, Voodoo and
448     other cards for XFree86. Please check the <c>IUSE_VIDEO_CARDS</c> variable
449     in the <path>/usr/portage/x11-base/xfree-drm</path> ebuilds to see what you
450     need to fill in as <c>yourcard</c>.
451     </ti>
452     <ti><c>VIDEO_CARDS="yourcard" emerge xfree-drm</c></ti>
453     </tr>
454     </table>
455    
456     <p>
457     Beware though, some of these ebuilds might deal with big dependencies. To verify
458     what packages will be installed by emerging an ebuild, use <c>emerge
459     --pretend</c>. For instance, for the <c>xfree-drm</c> package:
460     </p>
461    
462     <pre caption="View full installation package listing">
463 neysx 1.2 # <i>emerge --pretend xfree-drm</i>
464 swift 1.1 </pre>
465    
466     </body>
467     </subsection>
468     <subsection>
469     <title>Configuring the Modules</title>
470     <body>
471    
472     <p>
473     You should list the modules you want automatically loaded in
474     <path>/etc/modules.autoload.d/kernel-2.4</path> (or <path>kernel-2.6</path>).
475     You can add extra options to the modules too if you want.
476     </p>
477    
478     <p>
479     To view all available modules, run the following <c>find</c> command. Don't
480     forget to substitute "&lt;kernel version&gt;" with the version of the kernel you
481     just compiled:
482     </p>
483    
484     <pre caption="Viewing all available modules">
485     # <i>find /lib/modules/&lt;kernel version&gt;/ -type f -iname '*.o' -or -iname '*.ko'</i>
486     </pre>
487    
488     <p>
489     For instance, to automatically load the <c>3c59x.o</c> module, edit the
490     <path>kernel-2.4</path> or <path>kernel-2.6</path> file and enter the module
491     name in it.
492     </p>
493    
494     <pre caption="Editing /etc/modules.autoload.d/kernel-2.4">
495     <comment>(Example for 2.4 kernels)</comment>
496     # <i>nano -w /etc/modules.autoload.d/kernel-2.4</i>
497     </pre>
498    
499     <pre caption="/etc/modules.autoload.d/kernel-2.4 or kernel-2.6">
500     3c59x
501     </pre>
502    
503     <p>
504     Now run <c>modules-update</c> to commit your changes to the
505     <path>/etc/modules.conf</path> file:
506     </p>
507    
508     <pre caption="Running modules-update">
509     # <i>modules-update</i>
510     </pre>
511    
512     <p>
513     Continue the installation with <uri link="?part=1&amp;chap=8">Configuring
514     your System</uri>.
515     </p>
516    
517     </body>
518     </subsection>
519     </section>
520     </sections>

  ViewVC Help
Powered by ViewVC 1.1.20