|
Lines 8-15
Link Here
|
| 8 |
|
8 |
|
| 9 |
<sections> |
9 |
<sections> |
| 10 |
|
10 |
|
| 11 |
<version>4.5</version> |
11 |
<version>4.6</version> |
| 12 |
<date>2005-05-12</date> |
12 |
<date>2005-05-26</date> |
| 13 |
|
13 |
|
| 14 |
<section> |
14 |
<section> |
| 15 |
<title>Timezone</title> |
15 |
<title>Timezone</title> |
|
Lines 120-129
Link Here
|
| 120 |
|
120 |
|
| 121 |
<p> |
121 |
<p> |
| 122 |
However, one thing <e>is</e> true: you must know your system when you start |
122 |
However, one thing <e>is</e> true: you must know your system when you start |
| 123 |
configuring a kernel manually. Most information can be gathered by viewing the |
123 |
configuring a kernel manually. Most information can be gathered by emerging |
| 124 |
contents of <path>/proc/pci</path> (or by using <c>lspci</c> if available). You |
124 |
pciutils (<c>emerge pciutils</c>) which contains <c>lscpi</c>. You will now |
| 125 |
can also run <c>lsmod</c> to see what kernel modules the Installation CD uses |
125 |
be able to use <c>lspci</c> within the chrooted environment. You may safely |
| 126 |
(it might provide you with a nice hint on what to enable). |
126 |
ignore any <e>pcilib</e> warnings (like pcilib: cannot open |
|
|
127 |
/sys/bus/pci/devices) that <c>lspci</c> throws out. Alternatively, you can run |
| 128 |
<c>lscpi</c> from a <e>non-chrooted</e> environment. The results are the same. |
| 129 |
You can also run <c>lsmod</c> to see what kernel modules the Installation CD |
| 130 |
uses (it might provide you with a nice hint on what to enable). |
| 127 |
</p> |
131 |
</p> |
| 128 |
|
132 |
|
| 129 |
<p> |
133 |
<p> |
