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

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

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

Revision 1.24 Revision 1.25
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-hppa-kernel.xml,v 1.24 2005/07/04 15:57:32 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-hppa-kernel.xml,v 1.25 2005/08/09 09:43:58 swift Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>1.17</version> 11<version>1.18</version>
12<date>2005-07-04</date> 12<date>2005-08-09</date>
13 13
14<section> 14<section>
15<title>Timezone</title> 15<title>Timezone</title>
16<body> 16<body>
17 17
42available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel 42available at the <uri link="/doc/en/gentoo-kernel.xml">Gentoo Kernel
43Guide</uri>. 43Guide</uri>.
44</p> 44</p>
45 45
46<p> 46<p>
47HPPA doesn't support 2.4 series anymore. You have to use <c>hppa-sources</c>. 47For HPPA we have <c>hppa-sources</c>. Default these sources are based on
48the 2.6 kernel sources. If you want to install a 2.4 kernel, you will need
49to install Gentoo from a working Internet connection as we do not supply those
50sources on our Installation CD. Continue by installing the kernel source:
48</p> 51</p>
49 52
50<pre caption="Installing the kernel source"> 53<pre caption="Installing a kernel source">
51# <i>emerge hppa-sources</i> 54# <i>emerge hppa-sources</i>
52</pre> 55</pre>
53 56
54<p> 57<p>
55When you take a look in <path>/usr/src</path> you should see a symlink called 58When you take a look in <path>/usr/src</path> you should see a symlink called
56<path>linux</path> pointing to your kernel source: 59<path>linux</path> pointing to your kernel source:
57</p> 60</p>
58 61
59<pre caption="Viewing the kernel source symlink"> 62<pre caption="Viewing the kernel source symlink">
60# <i>ls -l /usr/src/linux</i> 63# <i>ls -l /usr/src/linux</i>
61lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.6.10_p1 64lrwxrwxrwx 1 root root 12 Oct 13 11:04 /usr/src/linux -&gt; linux-2.6.12.2-pa2
62</pre> 65</pre>
63 66
64<p> 67<p>
65If this isn't the case (i.e. the symlink points to a different kernel source) 68If this isn't the case (i.e. the symlink points to a different kernel source)
66change the symlink before you continue: 69change the symlink before you continue:
67</p> 70</p>
68 71
69<pre caption="Changing the kernel source symlink"> 72<pre caption="Changing the kernel source symlink">
70# <i>rm /usr/src/linux</i> 73# <i>rm /usr/src/linux</i>
71# <i>cd /usr/src</i> 74# <i>cd /usr/src</i>
72# <i>ln -s linux-2.6.10_p1 linux</i> 75# <i>ln -s linux-2.6.12.2-pa2 linux</i>
73</pre> 76</pre>
74 77
75<p> 78<p>
76Now it is time to configure and compile your kernel source. All architectures 79Now it is time to configure and compile your kernel source. All architectures
77can use <c>genkernel</c> for this, which will build a generic kernel as used 80can use <c>genkernel</c> for this, which will build a generic kernel as used
78by the LiveCD. We explain the "manual" configuration first though, as it is 81by the Installation CD. We explain the "manual" configuration first though, as
79the best way to optimize your environment. 82it is the best way to optimize your environment.
80</p> 83</p>
81 84
82<p> 85<p>
83If you want to manually configure your kernel, continue now with <uri 86If you want to manually configure your kernel, continue now with <uri
84link="#manual">Default: Manual Configuration</uri>. If you want to use 87link="#manual">Default: Manual Configuration</uri>. If you want to use
197<p> 200<p>
198If you have a HIL mouse or keyboard, do not forget to compile in support for 201If you have a HIL mouse or keyboard, do not forget to compile in support for
199them. 202them.
200</p> 203</p>
201 204
202<pre caption="Activating HIL keyboard support">
203Input device support ---&gt;
204 [*] Keyboards
205 [*] HP HIL keyboard support
206</pre>
207<pre caption="Activating HIL mouse support"> 205<pre caption="Activating HIL support">
208 [*] Mice 206Input core support ---&gt;
209 [*] HIL pointers (mice etc). 207 [*] Keyboard support
208 [*] Mouse support
209 [*] Event interface support
210</pre>
211
212<p>
213If you have no mouse on your HIL port, only use the basic support:
210</pre> 214</p>
211 215
216<pre caption="Basic HIL support">
217HIL support ---&gt;
218 [*] HIL Keyboard (basic) support
219</pre>
220
221<p>
222If you however want <e>full</e> HIL support, select the following options:
223</p>
224
225<pre caption="Full HIL support">
226HIL support ---&gt;
227 [*] HP System Device Controller i8042 Support
228 [*] HIL MLC Support
229 [*] HIL Keyboard (full) support
230 [*] HIL Mouse &amp; Pointer support
231</pre>
212 232
213<p> 233<p>
214Also include display driver support: 234Also include display driver support:
215</p> 235</p>
216 236
218Graphics support ---&gt; 238Graphics support ---&gt;
219 [*] Support for frame buffer devices 239 [*] Support for frame buffer devices
220 [*] HP STI frame buffer device support 240 [*] HP STI frame buffer device support
221 Console display driver support ---&gt; 241 Console display driver support ---&gt;
222 [*] STI text console 242 [*] STI text console
223 [*] Framebuffer Console support
224</pre> 243</pre>
225 244
226<p> 245<p>
227When you're done configuring your kernel, continue with <uri 246When you're done configuring your kernel, continue with <uri
228link="#compiling">Compiling and Installing</uri>. 247link="#compiling">Compiling and Installing</uri>.
244</pre> 263</pre>
245 264
246<p> 265<p>
247When the kernel has finished compiling, copy the kernel image to 266When the kernel has finished compiling, copy the kernel image to
248<path>/boot</path>. In the next example we assume you have configured and 267<path>/boot</path>. In the next example we assume you have configured and
249compiled <c>hppa-sources-2.6.10_p1</c> (which may not be the right kernel for 268compiled <c>hppa-sources-2.6.12.2-pa2</c>.
250your architecture!):
251</p> 269</p>
252 270
253<pre caption="Installing the kernel"> 271<pre caption="Installing the kernel">
254# <i>cp vmlinux /boot/vmlinux</i> 272# <i>cp vmlinux /boot/kernel-2.6.12.2-pa2</i>
255# <i>cp System.map /boot/System.map-2.6.10</i> 273# <i>cp System.map /boot/System.map-2.6.12.2-pa2</i>
256</pre> 274</pre>
257 275
258<p> 276<p>
259It is also wise to copy over your kernel configuration file to 277It is also wise to copy over your kernel configuration file to
260<path>/boot</path>, just in case :) 278<path>/boot</path>, just in case :)
261</p> 279</p>
262 280
263<pre caption="Backing up your kernel configuration"> 281<pre caption="Backing up your kernel configuration">
264# <i>cp .config /boot/config-2.6.10</i> 282# <i>cp .config /boot/config-2.6.12.2-pa2</i>
265</pre> 283</pre>
266 284
267<p> 285<p>
268Now continue with <uri link="#kernel_modules">Configuring Kernel 286Now continue with <uri link="#kernel_modules">Configuring Kernel
269Modules</uri>. 287Modules</uri>.
283 301
284<p> 302<p>
285Now that your kernel source tree is installed, it's now time to compile your 303Now that your kernel source tree is installed, it's now time to compile your
286kernel by using our <c>genkernel</c> script to automatically build a kernel for 304kernel by using our <c>genkernel</c> script to automatically build a kernel for
287you. <c>genkernel</c> works by configuring a kernel nearly identically to the 305you. <c>genkernel</c> works by configuring a kernel nearly identically to the
288way our LiveCD kernel is configured. This means that when you use 306way our Installation CD kernel is configured. This means that when you use
289<c>genkernel</c> to build your kernel, your system will generally detect all 307<c>genkernel</c> to build your kernel, your system will generally detect all
290your hardware at boot-time, just like our Live CD does. Because genkernel 308your hardware at boot-time, just like our Installation CD does. Because genkernel
291doesn't require any manual kernel configuration, it is an ideal solution for 309doesn't require any manual kernel configuration, it is an ideal solution for
292those users who may not be comfortable compiling their own kernels. 310those users who may not be comfortable compiling their own kernels.
293</p> 311</p>
294 312
295<p> 313<p>
313module). 331module).
314</p> 332</p>
315 333
316<pre caption="Running genkernel"> 334<pre caption="Running genkernel">
317# <i>genkernel all</i> 335# <i>genkernel all</i>
318GenKernel v3.0.1_beta10
319* ARCH: HPPA
320* KERNEL VER: 2.4.24
321* kernel: configuring source
322* kernel: running mrproper
323<comment>(Output removed to increase readability)</comment> 336<comment>(Output removed to increase readability)</comment>
324* Kernel compiled successfully! 337* Kernel compiled successfully!
325* Required Kernel Params: 338* Required Kernel Params:
326* : root=/dev/ram0 init=/linuxrc real_root=/dev/$ROOT 339* : root=/dev/ram0 init=/linuxrc real_root=/dev/$ROOT
327* where $ROOT is the devicenode for your root partition as 340* where $ROOT is the devicenode for your root partition as
342Once <c>genkernel</c> completes, a kernel, full set of modules and 355Once <c>genkernel</c> completes, a kernel, full set of modules and
343<e>initial root disk</e> (initrd) will be created. We will use the kernel 356<e>initial root disk</e> (initrd) will be created. We will use the kernel
344and initrd when configuring a boot loader later in this document. Write 357and initrd when configuring a boot loader later in this document. Write
345down the names of the kernel and initrd as you will need it when writing 358down the names of the kernel and initrd as you will need it when writing
346the bootloader configuration file. The initrd will be started immediately after 359the bootloader configuration file. The initrd will be started immediately after
347booting to perform hardware autodetection (just like on the Live CD) before 360booting to perform hardware autodetection (just like on the Installation CD)
348your "real" system starts up. 361before your "real" system starts up.
349</p> 362</p>
350 363
351<pre caption="Checking the created kernel image name and initrd"> 364<pre caption="Checking the created kernel image name and initrd">
352# <i>ls /boot/kernel* /boot/initrd*</i> 365# <i>ls /boot/kernel* /boot/initrd*</i>
353</pre> 366</pre>
354 367
355<p> 368<p>
356Now, let's perform one more step to get our system to be more like the Live 369Now, let's perform one more step to get our system to be more like the
357CD -- let's emerge <c>coldplug</c>. While the initrd autodetects hardware that 370Installation CD -- let's emerge <c>coldplug</c>. While the initrd autodetects
358is needed to boot your system, <c>coldplug</c> autodetects everything else. 371hardware that is needed to boot your system, <c>coldplug</c> autodetects
359To emerge and enable <c>coldplug</c>, type the following: 372everything else. To emerge and enable <c>coldplug</c>, type the following:
360</p> 373</p>
361 374
362<pre caption="Emerging and enabling coldplug"> 375<pre caption="Emerging and enabling coldplug">
363# <i>emerge coldplug</i> 376# <i>emerge coldplug</i>
364# <i>rc-update add coldplug boot</i> 377# <i>rc-update add coldplug default</i>
365</pre> 378</pre>
366 379
367</body> 380</body>
368</section> 381</section>
369<section id="kernel_modules"> 382<section id="kernel_modules">
372<title>Configuring the Modules</title> 385<title>Configuring the Modules</title>
373<body> 386<body>
374 387
375<p> 388<p>
376You should list the modules you want automatically loaded in 389You should list the modules you want automatically loaded in
377<path>/etc/modules.autoload.d/kernel-2.6</path>. 390<path>/etc/modules.autoload.d/kernel-2.6</path>.
378You can add extra options to the modules too if you want. 391You can add extra options to the modules too if you want.
379</p> 392</p>
380 393
381<p> 394<p>
382To view all available modules, run the following <c>find</c> command. Don't 395To view all available modules, run the following <c>find</c> command. Don't

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

  ViewVC Help
Powered by ViewVC 1.1.20