doc/en/gentoo-amd64-faq.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.40 2013/01/14 06:30:59 nightmorph Exp $ -->

<guide>
<title>Gentoo Linux/AMD64 Frequently Asked Questions</title>

<author title="Editor">
  <mail link="blubb@gentoo.org">Simon Stelling</mail>
</author>
<author title="Editor">
  <mail link="metalgod@gentoo.org">Luis Medinas</mail>
</author>
<author title="Editor">
  <mail link="gerrynjr@gentoo.org">Gerald J. Normandin Jr.</mail>
</author>
<author title="Editor">
  <mail link="neysx@gentoo.org">Xavier Neys</mail>
</author>
<author title="Editor">
  <mail link="nightmorph"/>
</author>

<abstract>
This is the Gentoo Linux/AMD64 Frequently Asked Questions
</abstract>

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

<version>6</version>
<date>2013-01-13</date>

<faqindex>
<title>Questions</title>
<section>
<title>Introduction to Gentoo/AMD64 FAQ</title>
<body>

<p>
This document contains the most commonly asked questions about Gentoo/AMD64. We
intend to help and provide useful information about Gentoo/AMD64. Some of these
questions can be found in forums, IRC, or mailing lists. If you have
suggestions or questions about this FAQ, you are welcome to send an e-mail to
<mail>amd64@gentoo.org</mail>.
</p>

</body>
</section>
</faqindex>

<chapter>
<title>Installation</title>
<section id="difference">
<title>What's the difference between AMD64 and EM64T?</title>
<body>

<p>
Both refer to 64-bit processors from AMD (AMD64) and Intel (EM64T). AMD's 64-bit
processors include the Athlon 64, Turion, Neo, Phenom, and Opteron families.
Intel's 64-bit processors include the Core2, Core i<e>X</e>, Celeron, Xeon, and
Pentium (all based on the Core2 architecture). The <uri
link="http://en.wikipedia.org/wiki/Em64t#Intel_64">last few versions</uri> of
the old Pentium 4 and Xeon chips also support EM64T.
</p>

<p>
The AMD line of 64-bit processors were released well ahead of Intel's offering.
Therefore, for historical reasons the arch keyword for all x86-64 compatible
architectures is amd64. As such, <e>AMD64</e> is a generic reference to 64-bit
chips, whether AMD or Intel.
</p>

</body>
</section>
<section id="cflags">
<title>What CFLAGS should I use for AMD64/EM64T?</title>
<body>

<p>
You should use simple <c>CFLAGS</c> to avoid future problems with your system.
Supported <c>CFLAGS</c> are <c>-O2 -march=native -pipe</c> for AMD and Intel
(EM64T) systems.
</p>

</body>
</section>
<section id="kernel">
<title>What kernel should I use for AMD64?</title>
<body>

<p>
You can use almost all kernel sources available in Portage. We recommend using
<c>gentoo-sources</c> because it is a special kernel designed for Gentoo Linux.
It contains lots of AMD64-specific patches and therefore is the only kernel
officially supported by Gentoo/AMD64.
</p>

<p>
Make sure you have the <c>IA32_EMULATION</c> option activated in the kernel.
</p>

<pre caption="Activating IA32 Emulation in Kernel source">
# <i>cd /usr/src/linux</i>
# <i>make menuconfig</i>

Executable file formats / Emulations  ---&gt;
  [*] IA32 Emulation
</pre>

<warn>
You may experience build failures on multilib-systems if you deactivate this
option.
</warn>

</body>
</section>
<section id="perfup">
<title>Will I have a performance upgrade if I use a 64bit system instead of 32bit?</title>
<body>

<p>
That is a difficult question to answer. In some cases, you will experience a
performance improvement, in other cases you will not. For everyday use, there is
nearly no difference between 64bit and 32bit. 64bit is generally faster when it
comes to floating point computing which is normally the case in multimedia
applications and 3D rendering. This <uri
link="http://www.linux.com/articles/114024?tid=121">article</uri> (and a <uri
link="http://www.linux.com/feature/43873">related</uri> article) may interest
you. There's also a nice <uri
link="https://forums.gentoo.org/viewtopic-t-349691.html">thread</uri> in our <uri
link="https://forums.gentoo.org">forums</uri>.
</p>

</body>
</section>
<section id="multilib">
<title>What is multilib and how can I use it?</title>
<body>

<p>
Every AMD64 processor is able to run 32bit code as well as 64bit code.
However, when you have a 32bit application, you are unable to mix it with
64bit libraries or vice versa. You can, however, natively run 32bit
applications if all shared libraries it needs are available as 32bit objects.
You can choose whether you want multilib support or not by selecting the
according profile. The default is a multilib-enabled profile.
</p>

<warn>
Currently you cannot switch from a no-multilib to a multilib-enabled profile,
so think over your decision twice before you use the no-multilib profile.
</warn>

</body>
</section>
<section id="chroot32">
<title>How do I create a 32bit chroot?</title>
<body>

<p>
Please read the <uri link="/proj/en/base/amd64/howtos/chroot.xml">32bit chroot
guide</uri>.
</p>

</body>
</section>
<section id="upgradex86">
<title>Can I upgrade from my x86 system to amd64 by doing emerge -e world?</title>
<body>

<p>
Due to several differences between an <c>x86</c> and an <c>amd64</c>
installation, it is impossible to upgrade. Please perform a fresh install. The
installation is slightly different than an x86 one, so please use the
<uri link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri>.
</p>

<p>
Also, binary files created on an x86 system most likely cannot be read by
packages on an amd64 system. In particular, databases such as MySQL, innoDB,
Berkeley DB, SQLite, OpenLDAP, etc. cannot simply be copied as-is. You will need
to dump the database into an architecture-independent format, such as a text
file, before attempting to restore it on an amd64 system.
</p>

</body>
</section>
<section id="reiser4">
<title>Can I use Reiser4?</title>
<body>

<p>
Reiser4 is not available from any kernel offered by the Gentoo Kernel project,
thus the AMD64 team doesn't support it. The answer is no.
</p>

</body>
</section>
</chapter>

<chapter>
<title>Hardware</title>
<section id="videobindrivers">
<title>Will my binary NVIDIA/ATI drivers work?</title>
<body>

<p>
Yes, NVIDIA and ATI provide drivers that work on AMD64. You can install them by
executing <c>emerge nvidia-drivers</c> or <c>emerge ati-drivers</c>. If you have
more questions about these drivers, you should read the <uri
link="/doc/en/nvidia-guide.xml">Nvidia guide</uri> or the <uri
link="/doc/en/ati-faq.xml">ATI FAQ</uri>.
</p>

</body>
</section>
<section id="coolnquiet">
<title>How do I use Cool'n'Quiet/PowerNow/SpeedStep features?</title>
<body>

<p>
You have to compile your kernel with support for these features. You just need
to enable the features below:
</p>

<pre caption="Kernel options for Cool'n'Quiet/PowerNow/SpeedStep">
Power management options ---&gt;
  [*] Run-time PM core functionality
  [*] ACPI (Advanced Configuration and Power Interface) Support ---&gt;
    &lt;*&gt;   Processor
    &lt;*&gt;     Thermal Zone
  CPU Frequency scaling ---&gt;
  [*] CPU Frequency scaling
         Default CPUFreq governor (ondemand) ---&gt;
  -*-   'performance' governor
  &lt;*&gt;   'userspace' governor for userspace frequency scaling
  -*-   'ondemand' cpufreq policy governor
  &lt;*&gt;   ACPI Processor P-States driver
  &lt;*&gt;   AMD Opteron/Athlon64 PowerNow!
-*- CPU idle PM support
</pre>

<p>
Then <c>emerge cpufrequtils</c> and edit <path>/etc/conf.d/cpufrequtils</path>
with your favorite editor.
</p>

<pre caption="Example of /etc/conf.d/cpufrequtils">
# Options when starting cpufreq (given to the 'cpufreq-set' program)
START_OPTS="--governor ondemand"

# Options when stopping cpufreq (given to the 'cpufreq-set' program)
STOP_OPTS="--governor performance"
</pre>

<p>
Now you only have to run <c>rc-update add cpufrequtils boot</c> to make sure it is
started every time you boot.
</p>

<note>
You may want to read the <uri
link="/doc/en/power-management-guide.xml#doc_chap3">Power Management Guide</uri>
for more tips on CPU power management.
</note>

</body>
</section>
</chapter>

<chapter>
<title>Applications</title>
<section id="flash">
<title>Can I get Adobe Flash working?</title>
<body>

<p>
Yes. Just <c>emerge adobe-flash</c>. Be sure to read any messages displayed by
the ebuild once it has been emerged.
<!-- Adobe killed 10.0 for security reasons, and 10.1 is only 32-bit -->
<!--
Adobe has provided a 64-bit Flash plugin starting with version 10.0.22.87. If
you don't need the 32-bit plugin, then run <c>echo "www-plugins/adobe-flash
-32bit" >> /etc/portage/package.use</c>. This will install only the 64-bit Flash
plugin.
-->
</p>

</body>
</section>
<section id="masked">
<title>I want to install package foo, but emerge says: (masked by: ~amd64 keyword)</title>
<body>

<p>
This means that the package is still in the 'testing' tree. Please read <c>man
portage</c> or the <uri
link="/doc/en/handbook/handbook-amd64.xml?part=3&amp;chap=3">Mixing Software
Branches</uri> chapter of the <uri
link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri> for more
information.
</p>

</body>
</section>
<section id="keyword">
<title>I want to install package foo, but emerge says: (masked by: missing keyword)</title>
<body>

<p>
This means that the package has not been tested yet. It does <e>not
necessarily</e> mean that the package does not work. You can unmask it by
accepting another architecture for the package. The following example shows you
can tell Portage to accept any keyword for a given package.
</p>

<pre caption="Example of adding package keywords">
# <i>echo "category/packagename **" >> /etc/portage/package.accept_keywords</i>
# <i>emerge packagename</i>
</pre>

<p>
If it works fine for you, please let us know and file a bug on <uri
link="https://bugs.gentoo.org/">Gentoo's Bugzilla</uri>, so that the AMD64 team
can keyword the package and other users can benefit from your test.
</p>

<warn>
Do not try commands like <c>ACCEPT_KEYWORDS="~x86" emerge packagename</c>. It
will most certainly break your tree.
</warn>

</body>
</section>
</chapter>

<chapter>
<title>How can I help the Gentoo/AMD64 project?</title>
<section id="project">
<title>How can I help?</title>
<body>

<p>
With a growing popularity of the amd64 architecture, we also increasingly need
more help. There's still much work to be done to improve the quality of
Gentoo/AMD64. An average user can help us by:
</p>

<ul>
  <li>Filing general bug reports</li>
  <li>Testing software that does not yet have the <c>~amd64</c> keyword</li>
  <li>
    Participating in the <uri link="/proj/en/base/amd64/at/">Arch Testers
    project</uri>
  </li>
  <li>
    Help answering questions on the mailing lists, forums and IRC channels
  </li>
  <li>Sending patches</li>
</ul>

</body>
</section>
</chapter>

<chapter>
<title>Other Resources</title>
<section id="other">
<title>Where can I get more help or information about Gentoo/AMD64?</title>
<body>

<p>
If any of your questions wasn't answered here, you can try other resources
listed on <uri link="/proj/en/base/amd64/">our project homepage</uri>. You can
also ask us at <c>#gentoo-amd64</c> on <c>irc.freenode.net</c>, <uri
link="https://forums.gentoo.org/viewforum-f-46.html">Gentoo/AMD64 Forums</uri>,
or on the <c>gentoo-amd64@lists.gentoo.org</c> mailing list.
</p>

</body>
</section>
</chapter>

</guide>
1	<?xml version="1.0" encoding="UTF-8"?>
2	<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3	<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.40 2013/01/14 06:30:59 nightmorph Exp $ -->
4
5	<guide>
6	<title>Gentoo Linux/AMD64 Frequently Asked Questions</title>
7
8	<author title="Editor">
9	<mail link="blubb@gentoo.org">Simon Stelling</mail>
10	</author>
11	<author title="Editor">
12	<mail link="metalgod@gentoo.org">Luis Medinas</mail>
13	</author>
14	<author title="Editor">
15	<mail link="gerrynjr@gentoo.org">Gerald J. Normandin Jr.</mail>
16	</author>
17	<author title="Editor">
18	<mail link="neysx@gentoo.org">Xavier Neys</mail>
19	</author>
20	<author title="Editor">
21	<mail link="nightmorph"/>
22	</author>
23
24	<abstract>
25	This is the Gentoo Linux/AMD64 Frequently Asked Questions
26	</abstract>
27
28	<!-- The content of this document is licensed under the CC-BY-SA license -->
29	<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
30	<license/>
31
32	<version>6</version>
33	<date>2013-01-13</date>
34
35	<faqindex>
36	<title>Questions</title>
37	<section>
38	<title>Introduction to Gentoo/AMD64 FAQ</title>
39	<body>
40
41	<p>
42	This document contains the most commonly asked questions about Gentoo/AMD64. We
43	intend to help and provide useful information about Gentoo/AMD64. Some of these
44	questions can be found in forums, IRC, or mailing lists. If you have
45	suggestions or questions about this FAQ, you are welcome to send an e-mail to
46	<mail>amd64@gentoo.org</mail>.
47	</p>
48
49	</body>
50	</section>
51	</faqindex>
52
53	<chapter>
54	<title>Installation</title>
55	<section id="difference">
56	<title>What's the difference between AMD64 and EM64T?</title>
57	<body>
58
59	<p>
60	Both refer to 64-bit processors from AMD (AMD64) and Intel (EM64T). AMD's 64-bit
61	processors include the Athlon 64, Turion, Neo, Phenom, and Opteron families.
62	Intel's 64-bit processors include the Core2, Core i<e>X</e>, Celeron, Xeon, and
63	Pentium (all based on the Core2 architecture). The <uri
64	link="http://en.wikipedia.org/wiki/Em64t#Intel_64">last few versions</uri> of
65	the old Pentium 4 and Xeon chips also support EM64T.
66	</p>
67
68	<p>
69	The AMD line of 64-bit processors were released well ahead of Intel's offering.
70	Therefore, for historical reasons the arch keyword for all x86-64 compatible
71	architectures is amd64. As such, <e>AMD64</e> is a generic reference to 64-bit
72	chips, whether AMD or Intel.
73	</p>
74
75	</body>
76	</section>
77	<section id="cflags">
78	<title>What CFLAGS should I use for AMD64/EM64T?</title>
79	<body>
80
81	<p>
82	You should use simple <c>CFLAGS</c> to avoid future problems with your system.
83	Supported <c>CFLAGS</c> are <c>-O2 -march=native -pipe</c> for AMD and Intel
84	(EM64T) systems.
85	</p>
86
87	</body>
88	</section>
89	<section id="kernel">
90	<title>What kernel should I use for AMD64?</title>
91	<body>
92
93	<p>
94	You can use almost all kernel sources available in Portage. We recommend using
95	<c>gentoo-sources</c> because it is a special kernel designed for Gentoo Linux.
96	It contains lots of AMD64-specific patches and therefore is the only kernel
97	officially supported by Gentoo/AMD64.
98	</p>
99
100	<p>
101	Make sure you have the <c>IA32_EMULATION</c> option activated in the kernel.
102	</p>
103
104	<pre caption="Activating IA32 Emulation in Kernel source">
105	# <i>cd /usr/src/linux</i>
106	# <i>make menuconfig</i>
107
108	Executable file formats / Emulations --->
109	[*] IA32 Emulation
110	</pre>
111
112	<warn>
113	You may experience build failures on multilib-systems if you deactivate this
114	option.
115	</warn>
116
117	</body>
118	</section>
119	<section id="perfup">
120	<title>Will I have a performance upgrade if I use a 64bit system instead of 32bit?</title>
121	<body>
122
123	<p>
124	That is a difficult question to answer. In some cases, you will experience a
125	performance improvement, in other cases you will not. For everyday use, there is
126	nearly no difference between 64bit and 32bit. 64bit is generally faster when it
127	comes to floating point computing which is normally the case in multimedia
128	applications and 3D rendering. This <uri
129	link="http://www.linux.com/articles/114024?tid=121">article</uri> (and a <uri
130	link="http://www.linux.com/feature/43873">related</uri> article) may interest
131	you. There's also a nice <uri
132	link="https://forums.gentoo.org/viewtopic-t-349691.html">thread</uri> in our <uri
133	link="https://forums.gentoo.org">forums</uri>.
134	</p>
135
136	</body>
137	</section>
138	<section id="multilib">
139	<title>What is multilib and how can I use it?</title>
140	<body>
141
142	<p>
143	Every AMD64 processor is able to run 32bit code as well as 64bit code.
144	However, when you have a 32bit application, you are unable to mix it with
145	64bit libraries or vice versa. You can, however, natively run 32bit
146	applications if all shared libraries it needs are available as 32bit objects.
147	You can choose whether you want multilib support or not by selecting the
148	according profile. The default is a multilib-enabled profile.
149	</p>
150
151	<warn>
152	Currently you cannot switch from a no-multilib to a multilib-enabled profile,
153	so think over your decision twice before you use the no-multilib profile.
154	</warn>
155
156	</body>
157	</section>
158	<section id="chroot32">
159	<title>How do I create a 32bit chroot?</title>
160	<body>
161
162	<p>
163	Please read the <uri link="/proj/en/base/amd64/howtos/chroot.xml">32bit chroot
164	guide</uri>.
165	</p>
166
167	</body>
168	</section>
169	<section id="upgradex86">
170	<title>Can I upgrade from my x86 system to amd64 by doing emerge -e world?</title>
171	<body>
172
173	<p>
174	Due to several differences between an <c>x86</c> and an <c>amd64</c>
175	installation, it is impossible to upgrade. Please perform a fresh install. The
176	installation is slightly different than an x86 one, so please use the
177	<uri link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri>.
178	</p>
179
180	<p>
181	Also, binary files created on an x86 system most likely cannot be read by
182	packages on an amd64 system. In particular, databases such as MySQL, innoDB,
183	Berkeley DB, SQLite, OpenLDAP, etc. cannot simply be copied as-is. You will need
184	to dump the database into an architecture-independent format, such as a text
185	file, before attempting to restore it on an amd64 system.
186	</p>
187
188	</body>
189	</section>
190	<section id="reiser4">
191	<title>Can I use Reiser4?</title>
192	<body>
193
194	<p>
195	Reiser4 is not available from any kernel offered by the Gentoo Kernel project,
196	thus the AMD64 team doesn't support it. The answer is no.
197	</p>
198
199	</body>
200	</section>
201	</chapter>
202
203	<chapter>
204	<title>Hardware</title>
205	<section id="videobindrivers">
206	<title>Will my binary NVIDIA/ATI drivers work?</title>
207	<body>
208
209	<p>
210	Yes, NVIDIA and ATI provide drivers that work on AMD64. You can install them by
211	executing <c>emerge nvidia-drivers</c> or <c>emerge ati-drivers</c>. If you have
212	more questions about these drivers, you should read the <uri
213	link="/doc/en/nvidia-guide.xml">Nvidia guide</uri> or the <uri
214	link="/doc/en/ati-faq.xml">ATI FAQ</uri>.
215	</p>
216
217	</body>
218	</section>
219	<section id="coolnquiet">
220	<title>How do I use Cool'n'Quiet/PowerNow/SpeedStep features?</title>
221	<body>
222
223	<p>
224	You have to compile your kernel with support for these features. You just need
225	to enable the features below:
226	</p>
227
228	<pre caption="Kernel options for Cool'n'Quiet/PowerNow/SpeedStep">
229	Power management options --->
230	[*] Run-time PM core functionality
231	[*] ACPI (Advanced Configuration and Power Interface) Support --->
232	<*> Processor
233	<*> Thermal Zone
234	CPU Frequency scaling --->
235	[*] CPU Frequency scaling
236	Default CPUFreq governor (ondemand) --->
237	-*- 'performance' governor
238	<*> 'userspace' governor for userspace frequency scaling
239	-*- 'ondemand' cpufreq policy governor
240	<*> ACPI Processor P-States driver
241	<*> AMD Opteron/Athlon64 PowerNow!
242	-*- CPU idle PM support
243	</pre>
244
245	<p>
246	Then <c>emerge cpufrequtils</c> and edit <path>/etc/conf.d/cpufrequtils</path>
247	with your favorite editor.
248	</p>
249
250	<pre caption="Example of /etc/conf.d/cpufrequtils">
251	# Options when starting cpufreq (given to the 'cpufreq-set' program)
252	START_OPTS="--governor ondemand"
253
254	# Options when stopping cpufreq (given to the 'cpufreq-set' program)
255	STOP_OPTS="--governor performance"
256	</pre>
257
258	<p>
259	Now you only have to run <c>rc-update add cpufrequtils boot</c> to make sure it is
260	started every time you boot.
261	</p>
262
263	<note>
264	You may want to read the <uri
265	link="/doc/en/power-management-guide.xml#doc_chap3">Power Management Guide</uri>
266	for more tips on CPU power management.
267	</note>
268
269	</body>
270	</section>
271	</chapter>
272
273	<chapter>
274	<title>Applications</title>
275	<section id="flash">
276	<title>Can I get Adobe Flash working?</title>
277	<body>
278
279	<p>
280	Yes. Just <c>emerge adobe-flash</c>. Be sure to read any messages displayed by
281	the ebuild once it has been emerged.
282	<!-- Adobe killed 10.0 for security reasons, and 10.1 is only 32-bit -->
283	<!--
284	Adobe has provided a 64-bit Flash plugin starting with version 10.0.22.87. If
285	you don't need the 32-bit plugin, then run <c>echo "www-plugins/adobe-flash
286	-32bit" >> /etc/portage/package.use</c>. This will install only the 64-bit Flash
287	plugin.
288	-->
289	</p>
290
291	</body>
292	</section>
293	<section id="masked">
294	<title>I want to install package foo, but emerge says: (masked by: ~amd64 keyword)</title>
295	<body>
296
297	<p>
298	This means that the package is still in the 'testing' tree. Please read <c>man
299	portage</c> or the <uri
300	link="/doc/en/handbook/handbook-amd64.xml?part=3&chap=3">Mixing Software
301	Branches</uri> chapter of the <uri
302	link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri> for more
303	information.
304	</p>
305
306	</body>
307	</section>
308	<section id="keyword">
309	<title>I want to install package foo, but emerge says: (masked by: missing keyword)</title>
310	<body>
311
312	<p>
313	This means that the package has not been tested yet. It does <e>not
314	necessarily</e> mean that the package does not work. You can unmask it by
315	accepting another architecture for the package. The following example shows you
316	can tell Portage to accept any keyword for a given package.
317	</p>
318
319	<pre caption="Example of adding package keywords">
320	# <i>echo "category/packagename **" >> /etc/portage/package.accept_keywords</i>
321	# <i>emerge packagename</i>
322	</pre>
323
324	<p>
325	If it works fine for you, please let us know and file a bug on <uri
326	link="https://bugs.gentoo.org/">Gentoo's Bugzilla</uri>, so that the AMD64 team
327	can keyword the package and other users can benefit from your test.
328	</p>
329
330	<warn>
331	Do not try commands like <c>ACCEPT_KEYWORDS="~x86" emerge packagename</c>. It
332	will most certainly break your tree.
333	</warn>
334
335	</body>
336	</section>
337	</chapter>
338
339	<chapter>
340	<title>How can I help the Gentoo/AMD64 project?</title>
341	<section id="project">
342	<title>How can I help?</title>
343	<body>
344
345	<p>
346	With a growing popularity of the amd64 architecture, we also increasingly need
347	more help. There's still much work to be done to improve the quality of
348	Gentoo/AMD64. An average user can help us by:
349	</p>
350
351	<ul>
352	<li>Filing general bug reports</li>
353	<li>Testing software that does not yet have the <c>~amd64</c> keyword</li>
354	<li>
355	Participating in the <uri link="/proj/en/base/amd64/at/">Arch Testers
356	project</uri>
357	</li>
358	<li>
359	Help answering questions on the mailing lists, forums and IRC channels
360	</li>
361	<li>Sending patches</li>
362	</ul>
363
364	</body>
365	</section>
366	</chapter>
367
368	<chapter>
369	<title>Other Resources</title>
370	<section id="other">
371	<title>Where can I get more help or information about Gentoo/AMD64?</title>
372	<body>
373
374	<p>
375	If any of your questions wasn't answered here, you can try other resources
376	listed on <uri link="/proj/en/base/amd64/">our project homepage</uri>. You can
377	also ask us at <c>#gentoo-amd64</c> on <c>irc.freenode.net</c>, <uri
378	link="https://forums.gentoo.org/viewforum-f-46.html">Gentoo/AMD64 Forums</uri>,
379	or on the <c>gentoo-amd64@lists.gentoo.org</c> mailing list.
380	</p>
381
382	</body>
383	</section>
384	</chapter>
385
386	</guide>