en/handbook/hb-install-ia64-kernel.xml

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sections SYSTEM "/dtd/book.dtd">

<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->

<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ia64-kernel.xml,v 1.20 2010/07/20 05:14:55 nightmorph Exp $ -->

<sections>

<version>11</version>
<date>2011-08-03</date>

<section>
<title>Timezone</title>
<body>

<p>
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 copy
it to <path>/etc/localtime</path>. Please avoid the
<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not
indicate the expected zones. For instance, <path>GMT-8</path> is in fact
GMT+8.
</p>

<pre caption="Setting the timezone information">
# <i>ls /usr/share/zoneinfo</i>
<comment>(Suppose you want to use GMT)</comment>
# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
</pre>

</body>
</section>
<section>
<title>Installing the Sources</title>
<subsection>
<title>Choosing a Kernel</title>
<body>

<p>
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>. 
</p>

<p>
For <keyval id="arch"/> systems, we will use <c>gentoo-sources</c> (contains
additional patches for extra features).
</p>

<p>
Now install it using <c>emerge</c>.
</p>

<pre caption="Installing a kernel source">
# <i>emerge gentoo-sources</i>
</pre>

<p>
When you take a look in <path>/usr/src</path> you should see a symlink called
<path>linux</path> pointing to your kernel source. In this case, the installed
kernel source points to <c>gentoo-sources-<keyval id="kernel-version"/></c>.
Your version may be different, so keep this in mind.
</p>

<pre caption="Viewing the kernel source symlink">
# <i>ls -l /usr/src/linux</i>
lrwxrwxrwx    1 root   root    12 Oct 13 11:04 /usr/src/linux -&gt; linux-<keyval id="kernel-version"/>
</pre>

<p>
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.
</p>

<p>
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.
</p>

</body>
</subsection>
</section>
<section id="manual">
<title>Default: Manual Configuration</title>
<subsection>
<title>Introduction</title>
<body>

<p>
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 ;)
</p>

<p>
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 emerging 
pciutils (<c>emerge pciutils</c>) which contains <c>lspci</c>. You will now 
be able to  use <c>lspci</c> within the chrooted environment. You may safely 
ignore any <e>pcilib</e> warnings (like pcilib: cannot open 
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run 
<c>lspci</c> from a <e>non-chrooted</e> environment. The results are the same. 
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).
</p>

<p>
Now go to your kernel source directory and execute <c>make menuconfig</c>. This
will fire up an ncurses-based configuration menu.
</p>

<pre caption="Invoking menuconfig">
# <i>cd /usr/src/linux</i>
# <i>make menuconfig</i>
</pre>

<p>
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).
</p>

</body>
</subsection>
<subsection>
<title>Activating Required Options</title>
<body>

<p>
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.
</p>

<p>
Now select the correct system type and processor type. If you don't know what
kind of IA64 system type you have, <c>DIG-compliant</c> is a good default
choice. If you are installing on an SGI system make sure you select the
SGI system type, your kernel may just lock up and refuse to boot otherwise.
</p>

<pre caption="Selecting correct system type">
System type ---&gt;
  <comment>(Change according to your system)</comment>
  <i>DIG-compliant</i>
Processor type ---&gt;
  <comment>(Change according to your system)</comment>
  <i>Itanium 2</i>
</pre>

<p>
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>Virtual memory</c> and <c>/proc
file system</c>.
</p>

<pre caption="Selecting necessary file systems">
File systems ---&gt;
  Pseudo Filesystems ---&gt;
    [*] /proc file system support
    [*] 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

<comment>(Be sure to enable VFAT support for the EFI partition)</comment>
DOS/FAT/NT Filesystems  --->
  &lt;*&gt; VFAT (Windows-95) fs support
</pre>

<p>
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:
</p>

<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>

<p>
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>ppp</c>
when configured to do kernel mode PPPoE.
</p>

<p>
If you require it, don't forget to include support in the kernel for your
ethernet card.
</p>

<p>
If you have an Intel CPU that supports HyperThreading (tm), or you have a
multi-CPU system, you should activate "Symmetric multi-processing support":
</p>

<pre caption="Activating SMP support">
Processor type and features  ---&gt;
  [*] Symmetric multi-processing support
</pre>

<p>
If you use USB Input Devices (like Keyboard or Mouse) don't forget to enable
those as well:
</p>

<pre caption="Activating USB Support for Input Devices">
Device Drivers ---&gt;
  [*] HID Devices  ---&gt;
    &lt;*&gt;   USB Human Interface Device (full HID) support
</pre>

<p>
When you've finished configuring the kernel, continue with <uri 
link="#compiling">Compiling and Installing</uri>.
</p>

</body>
</subsection>
<subsection id="compiling">
<title>Compiling and Installing</title>
<body>

<p>
Now that your kernel is configured, it is time to compile and install it. Exit 
the configuration and start the compilation process:
</p>

<pre caption="Compiling the kernel">
# <i>make &amp;&amp; make modules_install</i>
</pre>

<p>
When the kernel has finished compiling, copy the kernel image to
<path>/boot</path>. Use whatever name you feel is appropriate for your kernel
choice and remember it as you will need it later on when you configure your
bootloader. Remember to replace <c><keyval id="kernel-name"/></c> with the
name and version of your kernel.
</p>

<pre caption="Installing the kernel">
# <i>cp vmlinux.gz /boot/<keyval id="kernel-name"/></i>
</pre>

<p>
Now continue with <uri link="#kernel_modules">Kernel Modules</uri>.
</p>

</body>
</subsection>
</section>
<section id="genkernel">
<title>Alternative: Using genkernel</title>
<body>

<p>
If you are reading this section, you have chosen to use our <c>genkernel</c>
script to configure your kernel for you.
</p>

<p>
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.
</p>

<p>
Now, let's see how to use genkernel. First, emerge the genkernel ebuild:
</p>

<pre caption="Emerging genkernel">
# <i>emerge genkernel</i>
</pre>

<p>
Now, compile your kernel sources by running <c>genkernel 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!
</p>

<note>
Users of EVMS2 or LVM2 will probably want to add
<c>--evms2</c> or <c>--lvm2</c> to the genkernel command-line.
</note>

<pre caption="Running genkernel">
# <i>genkernel all</i>
</pre>

<p>
Once <c>genkernel</c> completes, a kernel, full set of modules and 
<e>initial ram 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.
</p>

<pre caption="Checking the created kernel image name and initrd">
# <i>ls /boot/kernel* /boot/initramfs*</i>
</pre>

</body>
</section>
<section id="kernel_modules">
<title>Kernel Modules</title>

<subsection>
<include href="hb-install-kernelmodules.xml"/>
</subsection>

</section>
</sections>
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	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-ia64-kernel.xml,v 1.20 2010/07/20 05:14:55 nightmorph Exp $ -->
8
9	<sections>
10
11	<version>11</version>
12	<date>2011-08-03</date>
13
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	located. Look for your timezone in <path>/usr/share/zoneinfo</path>, then copy
21	it to <path>/etc/localtime</path>. Please avoid the
22	<path>/usr/share/zoneinfo/Etc/GMT*</path> timezones as their names do not
23	indicate the expected zones. For instance, <path>GMT-8</path> is in fact
24	GMT+8.
25	</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	# <i>cp /usr/share/zoneinfo/GMT /etc/localtime</i>
31	</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	For <keyval id="arch"/> systems, we will use <c>gentoo-sources</c> (contains
51	additional patches for extra features).
52	</p>
53
54	<p>
55	Now install it using <c>emerge</c>.
56	</p>
57
58	<pre caption="Installing a kernel source">
59	# <i>emerge gentoo-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. 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 -> 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 --->
152	<comment>(Change according to your system)</comment>
153	<i>DIG-compliant</i>
154	Processor type --->
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 --->
168	Pseudo Filesystems --->
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	<*> Reiserfs support
174	<*> Ext3 journalling file system support
175	<*> JFS filesystem support
176	<*> Second extended fs support
177	<*> XFS filesystem support
178
179	<comment>(Be sure to enable VFAT support for the EFI partition)</comment>
180	DOS/FAT/NT Filesystems --->
181	<*> VFAT (Windows-95) fs 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	Device Drivers --->
191	Networking Support --->
192	<*> PPP (point-to-point protocol) support
193	<*> PPP support for async serial ports
194	<*> PPP support for sync tty ports
195	</pre>
196
197	<p>
198	The two compression options won't harm but are not definitely needed, neither
199	does the <c>PPP over Ethernet</c> option, that might only be used by <c>ppp</c>
200	when configured to do kernel mode PPPoE.
201	</p>
202
203	<p>
204	If you require it, don't forget to include support in the kernel for your
205	ethernet card.
206	</p>
207
208	<p>
209	If you have an Intel CPU that supports HyperThreading (tm), or you have a
210	multi-CPU system, you should activate "Symmetric multi-processing support":
211	</p>
212
213	<pre caption="Activating SMP support">
214	Processor type and features --->
215	[*] Symmetric multi-processing support
216	</pre>
217
218	<p>
219	If you use USB Input Devices (like Keyboard or Mouse) don't forget to enable
220	those as well:
221	</p>
222
223	<pre caption="Activating USB Support for Input Devices">
224	Device Drivers --->
225	[*] HID Devices --->
226	<*> USB Human Interface Device (full HID) support
227	</pre>
228
229	<p>
230	When you've finished configuring the kernel, continue with <uri
231	link="#compiling">Compiling and Installing</uri>.
232	</p>
233
234	</body>
235	</subsection>
236	<subsection id="compiling">
237	<title>Compiling and Installing</title>
238	<body>
239
240	<p>
241	Now that your kernel is configured, it is time to compile and install it. Exit
242	the configuration and start the compilation process:
243	</p>
244
245	<pre caption="Compiling the kernel">
246	# <i>make && make modules_install</i>
247	</pre>
248
249	<p>
250	When the kernel has finished compiling, copy the kernel image to
251	<path>/boot</path>. Use whatever name you feel is appropriate for your kernel
252	choice and remember it as you will need it later on when you configure your
253	bootloader. Remember to replace <c><keyval id="kernel-name"/></c> with the
254	name and version of your kernel.
255	</p>
256
257	<pre caption="Installing the kernel">
258	# <i>cp vmlinux.gz /boot/<keyval id="kernel-name"/></i>
259	</pre>
260
261	<p>
262	Now continue with <uri link="#kernel_modules">Kernel Modules</uri>.
263	</p>
264
265	</body>
266	</subsection>
267	</section>
268	<section id="genkernel">
269	<title>Alternative: Using genkernel</title>
270	<body>
271
272	<p>
273	If you are reading this section, you have chosen to use our <c>genkernel</c>
274	script to configure your kernel for you.
275	</p>
276
277	<p>
278	Now that your kernel source tree is installed, it's now time to compile your
279	kernel by using our <c>genkernel</c> script to automatically build a kernel for
280	you. <c>genkernel</c> works by configuring a kernel nearly identically to the
281	way our Installation CD kernel is configured. This means that when you use
282	<c>genkernel</c> to build your kernel, your system will generally detect all
283	your hardware at boot-time, just like our Installation CD does. Because
284	genkernel doesn't require any manual kernel configuration, it is an ideal
285	solution for those users who may not be comfortable compiling their own kernels.
286	</p>
287
288	<p>
289	Now, let's see how to use genkernel. First, emerge the genkernel ebuild:
290	</p>
291
292	<pre caption="Emerging genkernel">
293	# <i>emerge genkernel</i>
294	</pre>
295
296	<p>
297	Now, compile your kernel sources by running <c>genkernel all</c>. Be aware
298	though, as <c>genkernel</c> compiles a kernel that supports almost all hardware,
299	this compilation will take quite a while to finish!
300	</p>
301
302	<note>
303	Users of EVMS2 or LVM2 will probably want to add
304	<c>--evms2</c> or <c>--lvm2</c> to the genkernel command-line.
305	</note>
306
307	<pre caption="Running genkernel">
308	# <i>genkernel all</i>
309	</pre>
310
311	<p>
312	Once <c>genkernel</c> completes, a kernel, full set of modules and
313	<e>initial ram disk</e> (initrd) will be created. We will use the kernel
314	and initrd when configuring a boot loader later in this document. Write
315	down the names of the kernel and initrd as you will need it when writing
316	the bootloader configuration file. The initrd will be started immediately after
317	booting to perform hardware autodetection (just like on the Installation CD)
318	before your "real" system starts up.
319	</p>
320
321	<pre caption="Checking the created kernel image name and initrd">
322	# <i>ls /boot/kernel* /boot/initramfs*</i>
323	</pre>
324
325	</body>
326	</section>
327	<section id="kernel_modules">
328	<title>Kernel Modules</title>
329
330	<subsection>
331	<include href="hb-install-kernelmodules.xml"/>
332	</subsection>
333
334	</section>
335	</sections>