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.28 2008/07/25 18:55:00 nightmorph Exp $ -->

<guide link="/doc/en/gentoo-amd64-faq.xml">
<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>

<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>1.20</version>
<date>2008-09-02</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="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=k8 -pipe</c> for non-EM64T systems and
<c>-O2 -march=nocona -pipe</c> for 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>

<warn>
You should watch out for some kernel features which are not well tested, such
as <c>PREEMPT</c>.
</warn>

<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://enterprise.linux.com/enterprise/05/06/09/1413209.shtml?tid=121">article</uri>
may interest you. There's also a nice <uri
link="http://forums.gentoo.org/viewtopic-t-349691.html">thread</uri> in our
<uri link="http://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 neither AMD64 team supports 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 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">
Power management options ---&gt;
  [*] Power Management support
CPU Frequency scaling ---&gt;
  [*] CPU Frequency scaling
  [*] CPU frequency table helpers
  [*] AMD Opteron/Athlon64 PowerNow!
</pre>

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

<pre caption="Example of /etc/conf.d/cpudyn">
INTERVAL=1
CPU_UP=0.5
CPU_DOWN=0.9
THROTTLING_LOW=7
CPUFREQ_25="/sys/devices/system/cpu/cpu0/cpufreq /sysfs/devices/system/cpu/cpu0/cpufreq"
CPUFREQ_ACPI="/proc/acpi/processor/CPU0/throttling"
</pre>

<p>
Now you only have to run <c>rc-update add cpudyn default</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 Macromedia Flash working?</title>
<body>

<p>
Yes. To get Flash working, you need a 32bit browser like
<c>mozilla-firefox-bin</c> or <c>opera</c> because Macromedia doesn't provide a
64bit version. After emerging the -bin package of your favorite browser,
install Flash by doing <c>emerge netscape-flash</c>.
</p>

</body>
</section>
<section id="OOo">
<title>Can I get OpenOffice.org working?</title>
<body>

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