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

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

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.6 Revision 1.24
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> 2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3 3
4<!-- The content of this document is licensed under the CC-BY-SA license --> 4<!-- The content of this document is licensed under the CC-BY-SA license -->
5<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml,v 1.6 2004/08/21 04:43:14 vapier Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-alpha-kernel.xml,v 1.24 2005/06/02 17:18:54 swift Exp $ -->
8 8
9<sections> 9<sections>
10
11<version>2.3</version>
12<date>2005-06-02</date>
13
10<section> 14<section>
11<title>Timezone</title> 15<title>Timezone</title>
12<body> 16<body>
13 17
14<p> 18<p>
38available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel 42available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel
39Guide</uri>. 43Guide</uri>.
40</p> 44</p>
41 45
42<p> 46<p>
43For alpha-based systems we have <c>vanilla-sources</c> (the default kernel 47For alpha-based systems we have <c>vanilla-sources</c> (the default 2.6 kernel source).
44source as developed by the linux-kernel developers), <c>alpha-sources</c>
45(kernel source optimized for alpha users) and <c>compaq-sources</c> (kernel
46source as used by RedHat for Alpha, maintained by Compaq).
47</p> 48</p>
48 49
49<p> 50<p>
50Choose your kernel source and install it using <c>emerge</c>. 51Choose your kernel source and install it using <c>emerge</c>.
51</p> 52</p>
64<path>linux</path> pointing to your kernel source: 65<path>linux</path> pointing to your kernel source:
65</p> 66</p>
66 67
67<pre caption="Viewing the kernel source symlink"> 68<pre caption="Viewing the kernel source symlink">
68# <i>ls -l /usr/src/linux</i> 69# <i>ls -l /usr/src/linux</i>
69lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.4.24 70lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.6.11.2
70</pre> 71</pre>
71 72
72<p> 73<p>
73If this isn't the case (i.e. the symlink points to a different kernel source) 74If this isn't the case (i.e. the symlink points to a different kernel source)
74change the symlink before you continue: 75change the symlink before you continue:
75</p> 76</p>
76 77
77<pre caption="Changing the kernel source symlink"> 78<pre caption="Changing the kernel source symlink">
78# <i>rm /usr/src/linux</i> 79# <i>rm /usr/src/linux</i>
79# <i>cd /usr/src</i> 80# <i>cd /usr/src</i>
80# <i>ln -s linux-2.4.24 linux</i> 81# <i>ln -s linux-2.6.11.2 linux</i>
81</pre> 82</pre>
82 83
83<p> 84<p>
84Now it is time to configure and compile your kernel source. You 85Now it is time to configure and compile your kernel source. You
85can use <c>genkernel</c> for this, which will build a generic kernel as used 86can use <c>genkernel</c> for this, which will build a generic kernel as used
86by the LiveCD. We explain the "manual" configuration first though, as it is 87by the Installation CD. We explain the "manual" configuration first though, as it is
87the best way to optimize your environment. 88the best way to optimize your environment.
88</p> 89</p>
89 90
90<p> 91<p>
91If you want to manually configure your kernel, continue now with <uri 92If you want to manually configure your kernel, continue now with <uri
102<subsection> 103<subsection>
103<title>Introduction</title> 104<title>Introduction</title>
104<body> 105<body>
105 106
106<p> 107<p>
107Manually configuring a kernel is often seen as the most difficult course every 108Manually configuring a kernel is often seen as the most difficult procedure a
108Linux users ever has to go through. Nothing is less true -- after configuring a 109Linux user ever has to perform. Nothing is less true -- after configuring a
109couple of kernels you don't even remember that it was difficult ;) 110couple of kernels you don't even remember that it was difficult ;)
110</p> 111</p>
111 112
112<p> 113<p>
113However, one thing <e>is</e> true: you must know your system when you start 114However, one thing <e>is</e> true: you must know your system when you start
114configuring a kernel manually. Most information can be gathered by viewing the 115configuring a kernel manually. Most information can be gathered by emerging
115contents of <path>/proc/pci</path> (or by using <c>lspci</c> if available). You 116pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now
117be able to use <c>lspci</c> within the chrooted environment. You may safely
118ignore any <e>pcilib</e> warnings (like pcilib: cannot open
119/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run
120<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same.
116can also run <c>lsmod</c> to see what kernel modules the LiveCD uses (it might 121You can also run <c>lsmod</c> to see what kernel modules the Installation CD
117provide you with a nice hint on what to enable). 122uses (it might provide you with a nice hint on what to enable).
118</p> 123</p>
119 124
120<p> 125<p>
121Now go to your kernel source directory and execute <c>make menuconfig</c>. This 126Now go to your kernel source directory and execute <c>make menuconfig</c>. This
122will fire up an ncurses-based configuration menu. 127will fire up an ncurses-based configuration menu.
150</pre> 155</pre>
151 156
152<p> 157<p>
153Now go to <c>File Systems</c> and select support for the filesystems you use. 158Now 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 159<e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
155able to mount your partitions. Also select <c>Virtual memory</c>, <c>/proc 160able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc
156file system</c>, <c>/dev file system</c> + <c>Automatically mount at boot</c>: 161file system</c>. If you are using a 2.4 kernel, you should also select the
162<c>/dev file system</c> and <c>Automatically mount at boot</c> options, and
163you should make sure to <c>emerge devfsd</c>.
157</p> 164</p>
158 165
159<pre caption="Selecting necessary file systems"> 166<pre caption="Selecting necessary file systems">
160<comment>(With a 2.4.x kernel)</comment> 167<comment>(With a 2.4.x kernel)</comment>
161File systems ---&gt; 168File systems ---&gt;
167 174
168<comment>(With a 2.6.x kernel)</comment> 175<comment>(With a 2.6.x kernel)</comment>
169File systems ---&gt; 176File systems ---&gt;
170 Pseudo Filesystems ---&gt; 177 Pseudo Filesystems ---&gt;
171 [*] /proc file system support 178 [*] /proc file system support
172 [*] /dev file system support (OBSOLETE) 179 [ ] /dev file system support (OBSOLETE)
173 [*] Automatically mount at boot
174 [*] Virtual memory file system support (former shm fs) 180 [*] Virtual memory file system support (former shm fs)
175 181
176<comment>(Select one or more of the following options as needed by your system)</comment> 182<comment>(Select one or more of the following options as needed by your system)</comment>
177 &lt;*&gt; Reiserfs support 183 &lt;*&gt; Reiserfs support
178 &lt;*&gt; Ext3 journalling file system support 184 &lt;*&gt; Ext3 journalling file system support
211If you require it, don't forget to include support in the kernel for your 217If you require it, don't forget to include support in the kernel for your
212ethernet card. 218ethernet card.
213</p> 219</p>
214 220
215<p> 221<p>
216The following Alpha-specific options are recommended as well: 222The following options are recommended as well:
217</p> 223</p>
218 224
219<pre caption="Alpha-specific options"> 225<pre caption="Recommended Alpha options">
220General setup ---&gt; 226General setup ---&gt;
221 &lt;*&gt; SRM environment through procfs 227 &lt;*&gt; SRM environment through procfs
222 &lt;*&gt; Configure uac policy via sysctl 228 &lt;*&gt; Configure uac policy via sysctl
223 229
224Plug and Play configuration ---&gt; 230Plug and Play configuration ---&gt;
281<title>Compiling and Installing</title> 287<title>Compiling and Installing</title>
282<body> 288<body>
283 289
284<p> 290<p>
285Now that your kernel is configured, it is time to compile and install it. Exit 291Now that your kernel is configured, it is time to compile and install it. Exit
286the configuration and run <c>make dep &amp;&amp; make vmlinux modules 292the configuration and start the compilation process:
287modules_install</c>:
288</p> 293</p>
289 294
290<pre caption="Compiling the kernel"> 295<pre caption="Compiling the kernel">
291<comment>(For 2.4 kernel)</comment> 296<comment>(For 2.4 kernel)</comment>
292# <i>make dep &amp;&amp; make vmlinux modules modules_install</i> 297# <i>make dep &amp;&amp; make vmlinux modules modules_install</i>
297<comment>(For all kernels)</comment> 302<comment>(For all kernels)</comment>
298# <i>make boot</i> 303# <i>make boot</i>
299</pre> 304</pre>
300 305
301<p> 306<p>
302When the kernel is done compiling, copy over the kernel image to 307When the kernel has finished compiling, copy the kernel image to
303<path>/boot</path>. In the next example we assume you have configured and 308<path>/boot</path>. In the next example we assume you have configured and
304compiled <c>vanilla-sources-2.4.24</c>: 309compiled <c>vanilla-sources-2.6.11.2</c>; recent kernels might create
310<path>vmlinux</path> instead of <path>vmlinux.gz</path>.
305</p> 311</p>
306 312
307<pre caption="Installing the kernel"> 313<pre caption="Installing the kernel">
308# <i>cp arch/alpha/boot/vmlinux.gz /boot/</i> 314# <i>cp arch/alpha/boot/vmlinux.gz /boot/</i>
309# <i>cp System.map /boot/System.map-2.4.24</i> 315# <i>cp System.map /boot/System.map-2.6.11.2</i>
310</pre> 316</pre>
311 317
312<p> 318<p>
313It is also wise to copy over your kernel configuration file to 319It is also wise to copy over your kernel configuration file to
314<path>/boot</path>, just in case :) 320<path>/boot</path>, just in case :)
315</p> 321</p>
316 322
317<pre caption="Backing up your kernel configuration"> 323<pre caption="Backing up your kernel configuration">
318# <i>cp .config /boot/config-2.4.24</i> 324# <i>cp .config /boot/config-2.6.11.2</i>
319</pre> 325</pre>
320 326
321<p> 327<p>
322Now continue with <uri link="#kernel_modules">Installing Separate Kernel 328Now continue with <uri link="#kernel_modules">Installing Separate Kernel
323Modules</uri>. 329Modules</uri>.
337 343
338<p> 344<p>
339Now that your kernel source tree is installed, it's now time to compile your 345Now that your kernel source tree is installed, it's now time to compile your
340kernel by using our <c>genkernel</c> script to automatically build a kernel for 346kernel by using our <c>genkernel</c> script to automatically build a kernel for
341you. <c>genkernel</c> works by configuring a kernel nearly identically to the 347you. <c>genkernel</c> works by configuring a kernel nearly identically to the
342way our LiveCD kernel is configured. This means that when you use 348way our Installation CD kernel is configured. This means that when you use
343<c>genkernel</c> to build your kernel, your system will generally detect all 349<c>genkernel</c> to build your kernel, your system will generally detect all
344your hardware at boot-time, just like our Live CD does. Because genkernel 350your hardware at boot-time, just like our Installation CD does. Because genkernel
345doesn't require any manual kernel configuration, it is an ideal solution for 351doesn't require any manual kernel configuration, it is an ideal solution for
346those users who may not be comfortable compiling their own kernels. 352those users who may not be comfortable compiling their own kernels.
347</p> 353</p>
348 354
349<p> 355<p>
369 375
370<pre caption="Running genkernel"> 376<pre caption="Running genkernel">
371# <i>genkernel all</i> 377# <i>genkernel all</i>
372GenKernel v3.0.1_beta10 378GenKernel v3.0.1_beta10
373* ARCH: Alpha 379* ARCH: Alpha
374* KERNEL VER: 2.4.24 380* KERNEL VER: 2.6.11.2
375* kernel: configuring source 381* kernel: configuring source
376* kernel: running mrproper 382* kernel: running mrproper
377<comment>(Output removed to increase readability)</comment> 383<comment>(Output removed to increase readability)</comment>
378* Kernel compiled successfully! 384* Kernel compiled successfully!
379* Required Kernel Params: 385* Required Kernel Params:
396Once <c>genkernel</c> completes, a kernel, full set of modules and 402Once <c>genkernel</c> completes, a kernel, full set of modules and
397<e>initial root disk</e> (initrd) will be created. We will use the kernel 403<e>initial root disk</e> (initrd) will be created. We will use the kernel
398and initrd when configuring a boot loader later in this document. Write 404and initrd when configuring a boot loader later in this document. Write
399down the names of the kernel and initrd as you will need it when writing 405down the names of the kernel and initrd as you will need it when writing
400the bootloader configuration file. The initrd will be started immediately after 406the bootloader configuration file. The initrd will be started immediately after
401booting to perform hardware autodetection (just like on the Live CD) before 407booting to perform hardware autodetection (just like on the Installation CD) before
402your "real" system starts up. 408your "real" system starts up.
403</p> 409</p>
404 410
405<pre caption="Checking the created kernel image name and initrd"> 411<pre caption="Checking the created kernel image name and initrd">
406# <i>ls /boot/kernel* /boot/initrd*</i> 412# <i>ls /boot/kernel* /boot/initrd*</i>
407</pre> 413</pre>
408 414
409<p> 415<p>
410Now, let's perform one more step to get our system to be more like the Live 416Now, let's perform one more step to get our system to be more like the Installation CD -- let's emerge <c>coldplug</c>. While the initrd autodetects hardware that
411CD -- let's emerge <c>hotplug</c>. While the initrd autodetects hardware that
412is needed to boot your system, <c>hotplug</c> autodetects everything else. 417is needed to boot your system, <c>coldplug</c> autodetects everything else.
413To emerge and enable <c>hotplug</c>, type the following: 418To emerge and enable <c>coldplug</c>, type the following:
419</p>
420
421<pre caption="Emerging and enabling coldplug">
422# <i>emerge coldplug</i>
423# <i>rc-update add coldplug boot</i>
424</pre>
425
426<p>
427If you want your system to react to hotplugging events, you would need to
428install and setup hotplug as well:
414</p> 429</p>
415 430
416<pre caption="Emerging and enabling hotplug"> 431<pre caption="Emerging and enabling hotplug">
417# <i>emerge hotplug</i> 432# <i>emerge hotplug</i>
418# <i>rc-update add hotplug default</i> 433# <i>rc-update add hotplug default</i>
439 <th>Ebuild</th> 454 <th>Ebuild</th>
440 <th>Purpose</th> 455 <th>Purpose</th>
441 <th>Command</th> 456 <th>Command</th>
442</tr> 457</tr>
443<tr> 458<tr>
444 <ti>xfree-drm</ti> 459 <ti>x11-drm</ti>
445 <ti> 460 <ti>
446 Accelerated graphics for ATI Radeon up to 9200, Rage128, Matrox, Voodoo and 461 Accelerated graphics for ATI Radeon up to 9200, Rage128, Matrox, Voodoo and
447 other cards for XFree86. Please check the <c>IUSE_VIDEO_CARDS</c> variable 462 other cards for xorg-x11. Please check the <c>IUSE_VIDEO_CARDS</c> variable
448 in the <path>/usr/portage/x11-base/xfree-drm</path> ebuilds to see what you 463 in the <path>/usr/portage/x11-base/x11-drm</path> ebuilds to see what you
449 need to fill in as <c>yourcard</c>. 464 need to fill in as <c>yourcard</c>.
450 </ti> 465 </ti>
451 <ti><c>VIDEO_CARDS="yourcard" emerge xfree-drm</c></ti> 466 <ti><c>VIDEO_CARDS="yourcard" emerge x11-drm</c></ti>
452</tr> 467</tr>
453</table> 468</table>
454 469
455<p> 470<p>
456Beware though, some of these ebuilds might deal with big dependencies. To verify 471Beware though, some of these ebuilds might deal with big dependencies. To verify
457what packages will be installed by emerging an ebuild, use <c>emerge 472what packages will be installed by emerging an ebuild, use <c>emerge
458--pretend</c>. For instance, for the <c>xfree-drm</c> package: 473--pretend</c>. For instance, for the <c>x11-drm</c> package:
459</p> 474</p>
460 475
461<pre caption="View full installation package listing"> 476<pre caption="View full installation package listing">
462# <i>emerge --pretend xfree-drm</i> 477# <i>emerge --pretend x11-drm</i>
463</pre> 478</pre>
464 479
465</body> 480</body>
466</subsection> 481</subsection>
467<subsection> 482<subsection>
498<pre caption="/etc/modules.autoload.d/kernel-2.4 or kernel-2.6"> 513<pre caption="/etc/modules.autoload.d/kernel-2.4 or kernel-2.6">
4993c59x 5143c59x
500</pre> 515</pre>
501 516
502<p> 517<p>
503Now run <c>modules-update</c> to commit your changes to the
504<path>/etc/modules.conf</path> file:
505</p>
506
507<pre caption="Running modules-update">
508# <i>modules-update</i>
509</pre>
510
511<p>
512Continue the installation with <uri link="?part=1&amp;chap=8">Configuring 518Continue the installation with <uri link="?part=1&amp;chap=8">Configuring
513your System</uri>. 519your System</uri>.
514</p> 520</p>
515 521
516</body> 522</body>

Legend:
Removed from v.1.6  
changed lines
  Added in v.1.24

  ViewVC Help
Powered by ViewVC 1.1.20