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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.24 - (hide annotations) (download) (as text)
Sun Sep 18 17:37:47 2011 UTC (3 years, 2 months ago) by swift
Branch: MAIN
Changes since 1.23: +11 -5 lines
File MIME type: application/xml
Fix bug #383523 - Kernel configuration should mention EGI GUID Partition support. Thanks to Justin "yoosty" for reporting

1 vapier 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/2.5 -->
6    
7 swift 1.24 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ia64-kernel.xml,v 1.23 2011/09/03 07:18:27 swift Exp $ -->
8 vapier 1.1
9     <sections>
10    
11 swift 1.24 <version>14</version>
12     <date>2011-09-18</date>
13 vapier 1.1
14     <section>
15     <title>Timezone</title>
16     <body>
17    
18     <p>
19     You first need to select your timezone so that your system knows where it is
20 neysx 1.6 located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy
21     it to <path>/etc/localtime</path>. Please avoid the
22 vapier 1.1 <path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not
23 neysx 1.6 indicate the expected zones. For instance, <path>GMT-8</path> is in fact
24     GMT+8.
25 vapier 1.1 </p>
26    
27     <pre caption="Setting the timezone information">
28     # <i>ls /usr/share/zoneinfo</i>
29     <comment>(Suppose you want to use GMT)</comment>
30 neysx 1.6 # <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
31 vapier 1.1 </pre>
32    
33     </body>
34     </section>
35     <section>
36     <title>Installing the Sources</title>
37     <subsection>
38     <title>Choosing a Kernel</title>
39     <body>
40    
41     <p>
42     The core around which all distributions are built is the Linux kernel. It is the
43     layer between the user programs and your system hardware. Gentoo provides its
44     users several possible kernel sources. A full listing with description is
45     available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel
46     Guide</uri>.
47     </p>
48    
49     <p>
50 nightmorph 1.20 For <keyval id="arch"/> systems, we will use <c>gentoo-sources</c> (contains
51     additional patches for extra features).
52 vapier 1.1 </p>
53    
54     <p>
55 nightmorph 1.3 Now install it using <c>emerge</c>.
56 vapier 1.1 </p>
57    
58     <pre caption="Installing a kernel source">
59 nightmorph 1.3 # <i>emerge gentoo-sources</i>
60 vapier 1.1 </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. In this case, the installed
65     kernel source points to <c>gentoo-sources-<keyval id="kernel-version"/></c>.
66     Your version may be different, so keep this in mind.
67     </p>
68    
69     <pre caption="Viewing the kernel source symlink">
70     # <i>ls -l /usr/src/linux</i>
71     lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -&gt; linux-<keyval id="kernel-version"/>
72     </pre>
73    
74     <p>
75     Now it is time to configure and compile your kernel source. You can use
76     <c>genkernel</c> for this, which will build a generic kernel as used by the
77     Installation CD. We explain the "manual" configuration first though, as it is
78     the best way to optimize your environment.
79     </p>
80    
81     <p>
82     If you want to manually configure your kernel, continue now with <uri
83     link="#manual">Default: Manual Configuration</uri>. If you want to use
84     <c>genkernel</c> you should read <uri link="#genkernel">Alternative: Using
85     genkernel</uri> instead.
86     </p>
87    
88     </body>
89     </subsection>
90     </section>
91     <section id="manual">
92     <title>Default: Manual Configuration</title>
93     <subsection>
94     <title>Introduction</title>
95     <body>
96    
97     <p>
98     Manually configuring a kernel is often seen as the most difficult procedure a
99     Linux user ever has to perform. Nothing is less true -- after configuring a
100     couple of kernels you don't even remember that it was difficult ;)
101     </p>
102    
103     <p>
104     However, one thing <e>is</e> true: you must know your system when you start
105     configuring a kernel manually. Most information can be gathered by emerging
106     pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now
107     be able to use <c>lspci</c> within the chrooted environment. You may safely
108     ignore any <e>pcilib</e> warnings (like pcilib: cannot open
109     /sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run
110     <c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same.
111     You can also run <c>lsmod</c> to see what kernel modules the Installation CD
112     uses (it might provide you with a nice hint on what to enable).
113     </p>
114    
115     <p>
116     Now go to your kernel source directory and execute <c>make menuconfig</c>. This
117     will fire up an ncurses-based configuration menu.
118     </p>
119    
120     <pre caption="Invoking menuconfig">
121     # <i>cd /usr/src/linux</i>
122     # <i>make menuconfig</i>
123     </pre>
124    
125     <p>
126     You will be greeted with several configuration sections. We'll first list some
127     options you must activate (otherwise Gentoo will not function, or not function
128     properly without additional tweaks).
129     </p>
130    
131     </body>
132     </subsection>
133     <subsection>
134     <title>Activating Required Options</title>
135     <body>
136    
137     <p>
138     Make sure that every driver that is vital to the booting of your system (such as
139     SCSI controller, ...) is compiled <e>in</e> the kernel and not as a module,
140     otherwise your system will not be able to boot completely.
141     </p>
142    
143     <p>
144     Now select the correct system type and processor type. If you don't know what
145     kind of IA64 system type you have, <c>DIG-compliant</c> is a good default
146     choice. If you are installing on an SGI system make sure you select the
147     SGI system type, your kernel may just lock up and refuse to boot otherwise.
148     </p>
149    
150     <pre caption="Selecting correct system type">
151     System type ---&gt;
152     <comment>(Change according to your system)</comment>
153     <i>DIG-compliant</i>
154     Processor type ---&gt;
155     <comment>(Change according to your system)</comment>
156     <i>Itanium 2</i>
157     </pre>
158    
159     <p>
160     Now go to <c>File Systems</c> and select support for the filesystems you use.
161     <e>Don't</e> compile them as modules, otherwise your Gentoo system will not be
162     able to mount your partitions. Also select <c>Virtual memory</c> and <c>/proc
163     file system</c>.
164     </p>
165    
166     <pre caption="Selecting necessary file systems">
167     File systems ---&gt;
168     Pseudo Filesystems ---&gt;
169     [*] /proc file system support
170     [*] Virtual memory file system support (former shm fs)
171    
172     <comment>(Select one or more of the following options as needed by your system)</comment>
173     &lt;*&gt; Reiserfs support
174     &lt;*&gt; Ext3 journalling file system support
175     &lt;*&gt; JFS filesystem support
176     &lt;*&gt; Second extended fs support
177     &lt;*&gt; XFS filesystem support
178    
179     <comment>(Be sure to enable VFAT support for the EFI partition)</comment>
180 swift 1.24 DOS/FAT/NT Filesystems ---&gt;
181     &lt;*&gt; VFAT (Windows-95) fs support
182    
183     <comment>(Enable GPT partition label support if you used that previously</comment>
184     Partition Types ---&gt;
185     [*] Advanced partition selection
186     ...
187     [*] EFI GUID Partition support
188 vapier 1.1 </pre>
189    
190     <p>
191     If you are using PPPoE to connect to the Internet or you are using a dial-up
192     modem, you will need the following options in the kernel:
193     </p>
194    
195     <pre caption="Selecting PPPoE necessary drivers">
196     Device Drivers ---&gt;
197     Networking Support ---&gt;
198     &lt;*&gt; PPP (point-to-point protocol) support
199     &lt;*&gt; PPP support for async serial ports
200     &lt;*&gt; PPP support for sync tty ports
201     </pre>
202    
203     <p>
204     The two compression options won't harm but are not definitely needed, neither
205 nightmorph 1.5 does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c>
206     when configured to do kernel mode PPPoE.
207 vapier 1.1 </p>
208    
209     <p>
210     If you require it, don't forget to include support in the kernel for your
211     ethernet card.
212     </p>
213    
214     <p>
215     If you have an Intel CPU that supports HyperThreading (tm), or you have a
216     multi-CPU system, you should activate "Symmetric multi-processing support":
217     </p>
218    
219     <pre caption="Activating SMP support">
220     Processor type and features ---&gt;
221     [*] Symmetric multi-processing support
222     </pre>
223    
224     <p>
225     If you use USB Input Devices (like Keyboard or Mouse) don't forget to enable
226     those as well:
227     </p>
228    
229     <pre caption="Activating USB Support for Input Devices">
230     Device Drivers ---&gt;
231 nightmorph 1.18 [*] HID Devices ---&gt;
232 vapier 1.1 &lt;*&gt; USB Human Interface Device (full HID) support
233     </pre>
234    
235     <p>
236     When you've finished configuring the kernel, continue with <uri
237     link="#compiling">Compiling and Installing</uri>.
238     </p>
239    
240     </body>
241     </subsection>
242     <subsection id="compiling">
243     <title>Compiling and Installing</title>
244     <body>
245    
246     <p>
247     Now that your kernel is configured, it is time to compile and install it. Exit
248     the configuration and start the compilation process:
249     </p>
250    
251     <pre caption="Compiling the kernel">
252     # <i>make &amp;&amp; make modules_install</i>
253     </pre>
254    
255     <p>
256     When the kernel has finished compiling, copy the kernel image to
257     <path>/boot</path>. Use whatever name you feel is appropriate for your kernel
258     choice and remember it as you will need it later on when you configure your
259     bootloader. Remember to replace <c><keyval id="kernel-name"/></c> with the
260     name and version of your kernel.
261     </p>
262    
263     <pre caption="Installing the kernel">
264     # <i>cp vmlinux.gz /boot/<keyval id="kernel-name"/></i>
265     </pre>
266    
267     <p>
268     Now continue with <uri link="#kernel_modules">Kernel Modules</uri>.
269     </p>
270    
271     </body>
272     </subsection>
273     </section>
274     <section id="genkernel">
275     <title>Alternative: Using genkernel</title>
276     <body>
277    
278     <p>
279     If you are reading this section, you have chosen to use our <c>genkernel</c>
280     script to configure your kernel for you.
281     </p>
282    
283     <p>
284     Now that your kernel source tree is installed, it's now time to compile your
285     kernel by using our <c>genkernel</c> script to automatically build a kernel for
286     you. <c>genkernel</c> works by configuring a kernel nearly identically to the
287     way our Installation CD kernel is configured. This means that when you use
288     <c>genkernel</c> to build your kernel, your system will generally detect all
289     your hardware at boot-time, just like our Installation CD does. Because
290     genkernel doesn't require any manual kernel configuration, it is an ideal
291     solution for those users who may not be comfortable compiling their own kernels.
292     </p>
293    
294     <p>
295     Now, let's see how to use genkernel. First, emerge the genkernel ebuild:
296     </p>
297    
298     <pre caption="Emerging genkernel">
299     # <i>emerge genkernel</i>
300     </pre>
301    
302     <p>
303 nightmorph 1.19 Now, compile your kernel sources by running <c>genkernel all</c>. Be aware
304     though, as <c>genkernel</c> compiles a kernel that supports almost all hardware,
305     this compilation will take quite a while to finish!
306 vapier 1.1 </p>
307    
308     <note>
309 swift 1.23 Users of LVM2 will probably want to add <c>--lvm2</c> to the genkernel
310     command-line.
311 vapier 1.1 </note>
312    
313     <pre caption="Running genkernel">
314 nightmorph 1.19 # <i>genkernel all</i>
315 vapier 1.1 </pre>
316    
317     <p>
318     Once <c>genkernel</c> completes, a kernel, full set of modules and
319 swift 1.22 <e>initial ram disk</e> (initramfs) will be created. We will use the kernel
320 vapier 1.1 and initrd when configuring a boot loader later in this document. Write
321     down the names of the kernel and initrd as you will need it when writing
322     the bootloader configuration file. The initrd will be started immediately after
323     booting to perform hardware autodetection (just like on the Installation CD)
324     before your "real" system starts up.
325     </p>
326    
327     <pre caption="Checking the created kernel image name and initrd">
328     # <i>ls /boot/kernel* /boot/initramfs*</i>
329     </pre>
330    
331     </body>
332     </section>
333     <section id="kernel_modules">
334     <title>Kernel Modules</title>
335 nightmorph 1.16
336 vapier 1.1 <subsection>
337 nightmorph 1.16 <include href="hb-install-kernelmodules.xml"/>
338     </subsection>
339 vapier 1.1
340     </section>
341     </sections>

  ViewVC Help
Powered by ViewVC 1.1.20