/[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.16 - (hide annotations) (download) (as text)
Tue Apr 1 08:53:46 2008 UTC (6 years, 5 months ago) by nightmorph
Branch: MAIN
Changes since 1.15: +7 -52 lines
File MIME type: application/xml
release time. note that since this is beta1, the release dir and stage/media names have been adjusted accordingly. also, the handbooks are marked with a disclaimer=draft, so once the final is out, that will be removed and the release names adjusted. in the mean time, these are live. the beta is officially released. no, it's not april fools, but it is april 1st. :)

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 nightmorph 1.16 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-install-ia64-kernel.xml,v 1.10 2008/03/31 21:48:58 nightmorph Exp $ -->
8 vapier 1.1
9     <sections>
10    
11 nightmorph 1.16 <version>9.0</version>
12     <date>2008-04-01</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.3 For IA64 systems, we will use <c>gentoo-sources</c> (contains additional patches
51 neysx 1.13 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     DOS/FAT/NT Filesystems --->
181     &lt;*&gt; VFAT (Windows-95) fs support
182     </pre>
183    
184     <p>
185     Do not forget to enable DMA for your drives:
186     </p>
187    
188     <pre caption="Activating DMA">
189     Device Drivers ---&gt;
190     ATA/ATAPI/MFM/RLL support ---&gt;
191     [*] Generic PCI bus-master DMA support
192     </pre>
193    
194     <p>
195     If you are using PPPoE to connect to the Internet or you are using a dial-up
196     modem, you will need the following options in the kernel:
197     </p>
198    
199     <pre caption="Selecting PPPoE necessary drivers">
200     Device Drivers ---&gt;
201     Networking Support ---&gt;
202     &lt;*&gt; PPP (point-to-point protocol) support
203     &lt;*&gt; PPP support for async serial ports
204     &lt;*&gt; PPP support for sync tty ports
205     </pre>
206    
207     <p>
208     The two compression options won't harm but are not definitely needed, neither
209 nightmorph 1.5 does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c>
210     when configured to do kernel mode PPPoE.
211 vapier 1.1 </p>
212    
213     <p>
214     If you require it, don't forget to include support in the kernel for your
215     ethernet card.
216     </p>
217    
218     <p>
219     If you have an Intel CPU that supports HyperThreading (tm), or you have a
220     multi-CPU system, you should activate "Symmetric multi-processing support":
221     </p>
222    
223     <pre caption="Activating SMP support">
224     Processor type and features ---&gt;
225     [*] Symmetric multi-processing support
226     </pre>
227    
228     <p>
229     If you use USB Input Devices (like Keyboard or Mouse) don't forget to enable
230     those as well:
231     </p>
232    
233     <pre caption="Activating USB Support for Input Devices">
234     Device Drivers ---&gt;
235 nightmorph 1.16 USB Support ---&gt;
236 vapier 1.1 &lt;*&gt; USB Human Interface Device (full HID) support
237     </pre>
238    
239     <p>
240     When you've finished configuring the kernel, continue with <uri
241     link="#compiling">Compiling and Installing</uri>.
242     </p>
243    
244     </body>
245     </subsection>
246     <subsection id="compiling">
247     <title>Compiling and Installing</title>
248     <body>
249    
250     <p>
251     Now that your kernel is configured, it is time to compile and install it. Exit
252     the configuration and start the compilation process:
253     </p>
254    
255     <pre caption="Compiling the kernel">
256     # <i>make &amp;&amp; make modules_install</i>
257     </pre>
258    
259     <p>
260     When the kernel has finished compiling, copy the kernel image to
261     <path>/boot</path>. Use whatever name you feel is appropriate for your kernel
262     choice and remember it as you will need it later on when you configure your
263     bootloader. Remember to replace <c><keyval id="kernel-name"/></c> with the
264     name and version of your kernel.
265     </p>
266    
267     <pre caption="Installing the kernel">
268     # <i>cp vmlinux.gz /boot/<keyval id="kernel-name"/></i>
269     </pre>
270    
271     <p>
272     Now continue with <uri link="#kernel_modules">Kernel Modules</uri>.
273     </p>
274    
275     </body>
276     </subsection>
277     </section>
278     <section id="genkernel">
279     <title>Alternative: Using genkernel</title>
280     <body>
281    
282     <p>
283     If you are reading this section, you have chosen to use our <c>genkernel</c>
284     script to configure your kernel for you.
285     </p>
286    
287     <p>
288     Now that your kernel source tree is installed, it's now time to compile your
289     kernel by using our <c>genkernel</c> script to automatically build a kernel for
290     you. <c>genkernel</c> works by configuring a kernel nearly identically to the
291     way our Installation CD kernel is configured. This means that when you use
292     <c>genkernel</c> to build your kernel, your system will generally detect all
293     your hardware at boot-time, just like our Installation CD does. Because
294     genkernel doesn't require any manual kernel configuration, it is an ideal
295     solution for those users who may not be comfortable compiling their own kernels.
296     </p>
297    
298     <p>
299     Now, let's see how to use genkernel. First, emerge the genkernel ebuild:
300     </p>
301    
302     <pre caption="Emerging genkernel">
303     # <i>emerge genkernel</i>
304     </pre>
305    
306     <p>
307     Now, compile your kernel sources by running <c>genkernel --udev all</c>.
308     Be aware though, as <c>genkernel</c> compiles a kernel that supports almost all
309     hardware, this compilation will take quite a while to finish!
310     </p>
311    
312     <note>
313     Users of EVMS2 or LVM2 will probably want to add
314     <c>--evms2</c> or <c>--lvm2</c> to the genkernel command-line.
315     </note>
316    
317     <pre caption="Running genkernel">
318     # <i>genkernel --udev all</i>
319     </pre>
320    
321     <p>
322     Once <c>genkernel</c> completes, a kernel, full set of modules and
323     <e>initial root disk</e> (initrd) will be created. We will use the kernel
324     and initrd when configuring a boot loader later in this document. Write
325     down the names of the kernel and initrd as you will need it when writing
326     the bootloader configuration file. The initrd will be started immediately after
327     booting to perform hardware autodetection (just like on the Installation CD)
328     before your "real" system starts up.
329     </p>
330    
331     <pre caption="Checking the created kernel image name and initrd">
332     # <i>ls /boot/kernel* /boot/initramfs*</i>
333     </pre>
334    
335     </body>
336     </section>
337     <section id="kernel_modules">
338     <title>Kernel Modules</title>
339 nightmorph 1.16
340 vapier 1.1 <subsection>
341 nightmorph 1.16 <include href="hb-install-kernelmodules.xml"/>
342     </subsection>
343 vapier 1.1
344     </section>
345     </sections>

  ViewVC Help
Powered by ViewVC 1.1.20