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.4 2005/08/07 11:15:34 alin Exp $ -->

<guide link="/doc/en/gentoo-amd64-faq.xml">
<title>Gentoo Linux/AMD64 Frequently Asked Questions</title>

<author title="Editor">
  <mail link="lmedinas@gmail.com">Luis Medinas</mail>
</author>
<author title="Editor">
  <mail link="gerrynjr@gentoo.org">Gerald J. Normandin Jr.</mail>
</author>
<author title="Editor">
  <mail link="blubb@gentoo.org">Simon Stelling</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.2</version>
<date>2005-09-19</date>

<chapter>
<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 the authors
explaining the problem.
</p>

</body>
</section>
<section>
<title>Installation</title>
<body>

<ul>
  <li><uri link="#cflags">What CFLAGS should I use for AMD64/EM64T?</uri></li>
  <li><uri link="#kernel">What kernel should I use?</uri></li>
  <li>
    <uri link="#perfup">Will I have a performance upgrade if I use 64-bit
    system instead of 32-bit?</uri>
  </li>
  <li>
    <uri link="#emul32">How do I get 32-bit emulation for my system?</uri>
  </li>
  <li><uri link="#multilib">What is multilib and how can I use it?</uri></li>
  <li><uri link="#chroot32">How do I create a 32-bit chroot?</uri></li>
  <li>
    <uri link="#upgradex86">Can I upgrade from my x86 system to amd64 by doing
    emerge -e world?</uri>
  </li>
  <li><uri link="#reiser4">Can I use Reiser4?</uri></li>
</ul>

</body>
</section>
<section>
<title>Hardware</title>
<body>

<ul>
  <li>
    <uri link="#videobindrivers">Will my binary NVIDIA/ATI drivers work?</uri>
  </li>
  <li>
    <uri link="#coolnquiet">How do I use Cool'n'Quiet/Powernow features?</uri>
  </li>
</ul>

</body>
</section>
<section>
<title>Applications</title>
<body>

<ul>
  <li><uri link="#flash">Can I get Macromedia Flash working?</uri></li>
  <li><uri link="#OOo">Can I get OpenOffice.org working?</uri></li>
  <li><uri link="#java">How do I get java working in my browser?</uri></li>
  <li>
    <uri link="#masked">I want to install package foo, but emerge says: (masked
    by: ~amd64 keyword)</uri>
  </li>
  <li>
    <uri link="#keyword">I want to install package foo, but emerge says:
    (masked by: missing keyword)</uri>
  </li>
</ul>

</body>
</section>
<section>
<title>How can I help the Gentoo/AMD64 project?</title>
<body>

<ul>
  <li><uri link="#bugs">How do I report bugs?</uri></li>
  <li><uri link="#project">How can I help?</uri></li>
</ul>

</body>
</section>
<section>
<title>Other Resources</title>
<body>

<ul>
  <li>
    <uri link="#other">Where can I get more help or information about
    Gentoo/AMD64?</uri>
  </li>
</ul>

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

<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.
For example, you should use <c>CFLAGS="-march=k8 -O2 -pipe"</c> for Athlon64 or
Opteron and <c>CFLAGS="-march=nocona -O2 -pipe"</c> for a EM64T processor. If
you plan to use a 32-bit chroot, you should use <c>CFLAGS="-march=athlon-xp
-O2 -pipe -msse2"</c> for a AMD64 processor; for a EM64T, you should use
<c>CFLAGS="-march=pentium4 -O2 -pipe"</c> <e>inside the chroot</e>.
</p>

<note>
<c>-march=k8</c> is the same as <c>-march=athlon64</c> and
<c>-march=opteron</c>.
</note>

<warn>
You should <e>never</e> place <c>-fPIC</c>, <c>-m32</c> or <c>-m64</c> in
your <c>CFLAGS</c>. They are automatically added whenever they are needed.
Please also note that the <c>-Os</c> flag is currently not supported.
</warn>

</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. You can try <c>vanilla-sources</c> as
well. If you feel brave or you need extra hardware support, you can always try
the experimental kernel from Andrew Morton called <c>mm-sources</c>.
</p>

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

</body>
</section>
<section id="perfup">
<title>Will I have a performance upgrade if I use 64-bit system instead of 32-bit?</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 64-bit and 32-bit. 64-bit 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="emul32">
<title>How do I get 32-bit emulation for my system?</title>
<body>

<p>
You have to install a few packages to get 32-bit libraries into your system.
These packages are automatically pulled in as dependencies for 32-bit
applications by Portage, so there is no need to manually emerge them. You can
install such packages by doing:
</p>

<pre caption="Installing 32-bit libraries">
# <i>emerge emul-linux-x86-baselibs</i>
# <i>emerge emul-linux-x86-compat</i>
# <i>emerge emul-linux-x86-glibc</i>
</pre>

<p>
Furthermore, you need 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>

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

<note>
If you are using an old profile (2004.3 or older), please upgrade to 2005.0 and
read the <uri
link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=1">2005.0 Upgrade
Guide</uri> carefully.
</note>

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

<p>
Please read the <uri
link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=3">32-bit 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>

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

<p>
Reiser4 is <e>broken</e> and will <e>cause data corruption</e>. You can try
previous version of Reiser, but it is not recommended.
</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-kernel</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>

</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 32-bit browser like <c>mozilla-bin</c>,
<c>mozilla-firefox-bin</c> or <c>opera</c> because Macromedia doesn't provide a
64-bit 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 1.x does not build on 64-bit systems, so you have to use the 32-bit
binary version, available in portage as <c>openoffice-bin</c>.
</p>

</body>
</section>
<section id="java">
<title>How do I get java working in my browser?</title>
<body>

<p>
Blackdown provides a 64-bit JRE. To install it, <c>emerge blackdown-jre</c>.
Then, perform the following step:
</p>

<pre caption="Example of java link to browser plugins">
# <i>ln -s /opt/blackdown-jre-*/plugin/amd64/mozilla/libjavaplugin_oji.so /usr/lib64/nsbrowser/plugins/libjavaplugin_oji.so</i>
</pre>

</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
performing the following steps:
</p>

<pre caption="Example of adding package keywords">
# <i>echo "category/package x86" >> /etc/portage/package.keywords</i>
# <i>emerge package</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 other users can
benefit too.
</p>

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

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

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

<p>
If you find a bug or you want to send us patches, you need to file a bug
report. It only takes you a little while, and your help is really appreciated.
Please follow the <uri
link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=2">Filing a Bug
Guide</uri>.
</p>

</body>
</section>
<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/tests/index.xml?part=1&amp;chap=1">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 like
the <uri link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri>, the
<uri link="/proj/en/base/amd64/technotes/index.xml">AMD64 Technotes</uri> or
<uri link="/proj/en/base/amd64/index.xml">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	<?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.4 2005/08/07 11:15:34 alin Exp $ -->
4
5	<guide link="/doc/en/gentoo-amd64-faq.xml">
6	<title>Gentoo Linux/AMD64 Frequently Asked Questions</title>
7
8	<author title="Editor">
9	<mail link="lmedinas@gmail.com">Luis Medinas</mail>
10	</author>
11	<author title="Editor">
12	<mail link="gerrynjr@gentoo.org">Gerald J. Normandin Jr.</mail>
13	</author>
14	<author title="Editor">
15	<mail link="blubb@gentoo.org">Simon Stelling</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	<version>1.2</version>
30	<date>2005-09-19</date>
31
32	<chapter>
33	<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	questions can be found in forums, irc, or mailing lists. If you have suggestions
42	or questions about this FAQ, you are welcome to send an e-mail to the authors
43	explaining the problem.
44	</p>
45
46	</body>
47	</section>
48	<section>
49	<title>Installation</title>
50	<body>
51
52	<ul>
53	<li><uri link="#cflags">What CFLAGS should I use for AMD64/EM64T?</uri></li>
54	<li><uri link="#kernel">What kernel should I use?</uri></li>
55	<li>
56	<uri link="#perfup">Will I have a performance upgrade if I use 64-bit
57	system instead of 32-bit?</uri>
58	</li>
59	<li>
60	<uri link="#emul32">How do I get 32-bit emulation for my system?</uri>
61	</li>
62	<li><uri link="#multilib">What is multilib and how can I use it?</uri></li>
63	<li><uri link="#chroot32">How do I create a 32-bit chroot?</uri></li>
64	<li>
65	<uri link="#upgradex86">Can I upgrade from my x86 system to amd64 by doing
66	emerge -e world?</uri>
67	</li>
68	<li><uri link="#reiser4">Can I use Reiser4?</uri></li>
69	</ul>
70
71	</body>
72	</section>
73	<section>
74	<title>Hardware</title>
75	<body>
76
77	<ul>
78	<li>
79	<uri link="#videobindrivers">Will my binary NVIDIA/ATI drivers work?</uri>
80	</li>
81	<li>
82	<uri link="#coolnquiet">How do I use Cool'n'Quiet/Powernow features?</uri>
83	</li>
84	</ul>
85
86	</body>
87	</section>
88	<section>
89	<title>Applications</title>
90	<body>
91
92	<ul>
93	<li><uri link="#flash">Can I get Macromedia Flash working?</uri></li>
94	<li><uri link="#OOo">Can I get OpenOffice.org working?</uri></li>
95	<li><uri link="#java">How do I get java working in my browser?</uri></li>
96	<li>
97	<uri link="#masked">I want to install package foo, but emerge says: (masked
98	by: ~amd64 keyword)</uri>
99	</li>
100	<li>
101	<uri link="#keyword">I want to install package foo, but emerge says:
102	(masked by: missing keyword)</uri>
103	</li>
104	</ul>
105
106	</body>
107	</section>
108	<section>
109	<title>How can I help the Gentoo/AMD64 project?</title>
110	<body>
111
112	<ul>
113	<li><uri link="#bugs">How do I report bugs?</uri></li>
114	<li><uri link="#project">How can I help?</uri></li>
115	</ul>
116
117	</body>
118	</section>
119	<section>
120	<title>Other Resources</title>
121	<body>
122
123	<ul>
124	<li>
125	<uri link="#other">Where can I get more help or information about
126	Gentoo/AMD64?</uri>
127	</li>
128	</ul>
129
130	</body>
131	</section>
132	</chapter>
133
134	<chapter>
135	<title>Installation</title>
136	<section id="cflags">
137	<title>What CFLAGS should I use for AMD64/EM64T?</title>
138	<body>
139
140	<p>
141	You should use simple <c>CFLAGS</c> to avoid future problems with your system.
142	For example, you should use <c>CFLAGS="-march=k8 -O2 -pipe"</c> for Athlon64 or
143	Opteron and <c>CFLAGS="-march=nocona -O2 -pipe"</c> for a EM64T processor. If
144	you plan to use a 32-bit chroot, you should use <c>CFLAGS="-march=athlon-xp
145	-O2 -pipe -msse2"</c> for a AMD64 processor; for a EM64T, you should use
146	<c>CFLAGS="-march=pentium4 -O2 -pipe"</c> <e>inside the chroot</e>.
147	</p>
148
149	<note>
150	<c>-march=k8</c> is the same as <c>-march=athlon64</c> and
151	<c>-march=opteron</c>.
152	</note>
153
154	<warn>
155	You should <e>never</e> place <c>-fPIC</c>, <c>-m32</c> or <c>-m64</c> in
156	your <c>CFLAGS</c>. They are automatically added whenever they are needed.
157	Please also note that the <c>-Os</c> flag is currently not supported.
158	</warn>
159
160	</body>
161	</section>
162	<section id="kernel">
163	<title>What kernel should I use for AMD64?</title>
164	<body>
165
166	<p>
167	You can use almost all kernel sources available in Portage. We recommend using
168	<c>gentoo-sources</c> because it is a special kernel designed for Gentoo Linux.
169	It contains lots of AMD64-specific patches and therefore is the only kernel
170	officially supported by Gentoo/AMD64. You can try <c>vanilla-sources</c> as
171	well. If you feel brave or you need extra hardware support, you can always try
172	the experimental kernel from Andrew Morton called <c>mm-sources</c>.
173	</p>
174
175	<warn>
176	You should watch out for some kernel features which are not well tested, such
177	as <c>PREEMPT</c>.
178	</warn>
179
180	</body>
181	</section>
182	<section id="perfup">
183	<title>Will I have a performance upgrade if I use 64-bit system instead of 32-bit?</title>
184	<body>
185
186	<p>
187	That is a difficult question to answer. In some cases, you will experience a
188	performance improvement, in other cases you will not. For everyday use, there
189	is nearly no difference between 64-bit and 32-bit. 64-bit is generally faster
190	when it comes to floating point computing which is normally the case in
191	multimedia applications and 3D rendering. This <uri
192	link="http://enterprise.linux.com/enterprise/05/06/09/1413209.shtml?tid=121">article</uri>
193	may interest you. There's also a nice <uri
194	link="http://forums.gentoo.org/viewtopic-t-349691.html">thread</uri> in our
195	<uri link="http://forums.gentoo.org">forums</uri>.
196	</p>
197
198	</body>
199	</section>
200	<section id="emul32">
201	<title>How do I get 32-bit emulation for my system?</title>
202	<body>
203
204	<p>
205	You have to install a few packages to get 32-bit libraries into your system.
206	These packages are automatically pulled in as dependencies for 32-bit
207	applications by Portage, so there is no need to manually emerge them. You can
208	install such packages by doing:
209	</p>
210
211	<pre caption="Installing 32-bit libraries">
212	# <i>emerge emul-linux-x86-baselibs</i>
213	# <i>emerge emul-linux-x86-compat</i>
214	# <i>emerge emul-linux-x86-glibc</i>
215	</pre>
216
217	<p>
218	Furthermore, you need the <c>IA32_EMULATION</c> option activated in the kernel.
219	</p>
220
221	<pre caption="Activating IA32 Emulation in Kernel source">
222	# <i>cd /usr/src/linux</i>
223	# <i>make menuconfig</i>
224
225	Executable file formats / Emulations --->
226	[*] IA32 Emulation
227	</pre>
228
229	</body>
230	</section>
231	<section id="multilib">
232	<title>What is multilib and how can I use it?</title>
233	<body>
234
235	<p>
236	Every AMD64 processor is able to run 32-bit code as well as 64-bit code.
237	However, when you have a 32-bit application, you are unable to mix it with
238	64-bit libraries or vice versa. You can, however, natively run 32-bit
239	applications if all shared libraries it needs are available as 32-bit objects.
240	You can choose whether you want multilib support or not by selecting the
241	according profile. The default is a multilib-enabled profile.
242	</p>
243
244	<note>
245	If you are using an old profile (2004.3 or older), please upgrade to 2005.0 and
246	read the <uri
247	link="/proj/en/base/amd64/howtos/index.xml?part=1&chap=1">2005.0 Upgrade
248	Guide</uri> carefully.
249	</note>
250
251	</body>
252	</section>
253	<section id="chroot32">
254	<title>How do I create a 32-bit chroot?</title>
255	<body>
256
257	<p>
258	Please read the <uri
259	link="/proj/en/base/amd64/howtos/index.xml?part=1&chap=3">32-bit chroot
260	guide</uri>.
261	</p>
262
263	</body>
264	</section>
265	<section id="upgradex86">
266	<title>Can I upgrade from my x86 system to amd64 by doing emerge -e world?</title>
267	<body>
268
269	<p>
270	Due to several differences between an <c>x86</c> and an <c>amd64</c>
271	installation, it is impossible to upgrade. Please perform a fresh install. The
272	installation is slightly different than an x86 one, so please use the
273	<uri link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri>.
274	</p>
275
276	</body>
277	</section>
278	<section id="reiser4">
279	<title>Can I use Reiser4?</title>
280	<body>
281
282	<p>
283	Reiser4 is <e>broken</e> and will <e>cause data corruption</e>. You can try
284	previous version of Reiser, but it is not recommended.
285	</p>
286
287	</body>
288	</section>
289	</chapter>
290
291	<chapter>
292	<title>Hardware</title>
293	<section id="videobindrivers">
294	<title>Will my binary NVIDIA/ATI drivers work?</title>
295	<body>
296
297	<p>
298	Yes, NVIDIA and ATI provide drivers that work on AMD64. You can install them by
299	executing <c>emerge nvidia-kernel</c> or <c>emerge ati-drivers</c>. If you have
300	more questions about these drivers, you should read the <uri
301	link="/doc/en/nvidia-guide.xml">Nvidia guide</uri> or the <uri
302	link="/doc/en/ati-faq.xml">ATI FAQ</uri>.
303	</p>
304
305	</body>
306	</section>
307	<section id="coolnquiet">
308	<title>How do I use Cool'n'Quiet/Powernow features?</title>
309	<body>
310
311	<p>
312	You have to compile your kernel with support for these features. You just need
313	to enable the features below:
314	</p>
315
316	<pre caption="Kernel options for Cool'n'Quiet/Powernow">
317	Power management options --->
318	[*] Power Management support
319	CPU Frequency scaling --->
320	[*] CPU Frequency scaling
321	[*] CPU frequency table helpers
322	[*] AMD Opteron/Athlon64 PowerNow!
323	</pre>
324
325	<p>
326	Then <c>emerge cpudyn</c> and edit <path>/etc/conf.d/cpudyn</path> with your
327	favorite editor.
328	</p>
329
330	<pre caption="Example of /etc/conf.d/cpudyn">
331	INTERVAL=1
332	CPU_UP=0.5
333	CPU_DOWN=0.9
334	THROTTLING_LOW=7
335	CPUFREQ_25="/sys/devices/system/cpu/cpu0/cpufreq /sysfs/devices/system/cpu/cpu0/cpufreq"
336	CPUFREQ_ACPI="/proc/acpi/processor/CPU0/throttling"
337	</pre>
338
339	<p>
340	Now you only have to run <c>rc-update add cpudyn default</c> to make sure it is
341	started every time you boot.
342	</p>
343
344	</body>
345	</section>
346	</chapter>
347
348	<chapter>
349	<title>Applications</title>
350	<section id="flash">
351	<title>Can I get Macromedia Flash working?</title>
352	<body>
353
354	<p>
355	Yes. To get Flash working, you need a 32-bit browser like <c>mozilla-bin</c>,
356	<c>mozilla-firefox-bin</c> or <c>opera</c> because Macromedia doesn't provide a
357	64-bit version. After emerging the -bin-package of your favorite browser,
358	install flash by doing <c>emerge netscape-flash</c>.
359	</p>
360
361	</body>
362	</section>
363	<section id="OOo">
364	<title>Can I get OpenOffice.org working?</title>
365	<body>
366
367	<p>
368	OpenOffice 1.x does not build on 64-bit systems, so you have to use the 32-bit
369	binary version, available in portage as <c>openoffice-bin</c>.
370	</p>
371
372	</body>
373	</section>
374	<section id="java">
375	<title>How do I get java working in my browser?</title>
376	<body>
377
378	<p>
379	Blackdown provides a 64-bit JRE. To install it, <c>emerge blackdown-jre</c>.
380	Then, perform the following step:
381	</p>
382
383	<pre caption="Example of java link to browser plugins">
384	# <i>ln -s /opt/blackdown-jre-*/plugin/amd64/mozilla/libjavaplugin_oji.so /usr/lib64/nsbrowser/plugins/libjavaplugin_oji.so</i>
385	</pre>
386
387	</body>
388	</section>
389	<section id="masked">
390	<title>I want to install package foo, but emerge says: (masked by: ~amd64 keyword)</title>
391	<body>
392
393	<p>
394	This means that the package is still in the 'testing' tree. Please read <c>man
395	portage</c> or the <uri
396	link="/doc/en/handbook/handbook-amd64.xml?part=3&chap=3">Mixing Software
397	Branches</uri> chapter of the <uri
398	link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri> for more
399	information.
400	</p>
401
402	</body>
403	</section>
404	<section id="keyword">
405	<title>I want to install package foo, but emerge says: (masked by: missing keyword)</title>
406	<body>
407
408	<p>
409	This means that the package has not been tested yet. It does <e>not
410	necessarily</e> mean that the package does not work. You can unmask it by
411	performing the following steps:
412	</p>
413
414	<pre caption="Example of adding package keywords">
415	# <i>echo "category/package x86" >> /etc/portage/package.keywords</i>
416	# <i>emerge package</i>
417	</pre>
418
419	<p>
420	If it works fine for you, please let us know and file a bug on <uri
421	link="http://bugs.gentoo.org/">Gentoo's Bugzilla</uri>, so other users can
422	benefit too.
423	</p>
424
425	<warn>
426	Do not try commands like <c>ACCEPT_KEYWORDS="~x86" emerge package</c>. It will
427	most certainly break your tree.
428	</warn>
429
430	</body>
431	</section>
432	</chapter>
433
434	<chapter>
435	<title>How can help I the Gentoo/AMD64 project?</title>
436	<section id="bugs">
437	<title>How do I report bugs?</title>
438	<body>
439
440	<p>
441	If you find a bug or you want to send us patches, you need to file a bug
442	report. It only takes you a little while, and your help is really appreciated.
443	Please follow the <uri
444	link="/proj/en/base/amd64/howtos/index.xml?part=1&chap=2">Filing a Bug
445	Guide</uri>.
446	</p>
447
448	</body>
449	</section>
450	<section id="project">
451	<title>How can I help?</title>
452	<body>
453
454	<p>
455	With a growing popularity of the amd64 architecture, we also increasingly need
456	more help. There's still much work to be done to improve the quality of
457	Gentoo/AMD64. An average user can help us by:
458	</p>
459
460	<ul>
461	<li>Filing general bug reports</li>
462	<li>Testing software that does not yet have the <c>~amd64</c> keyword</li>
463	<li>
464	Participating in the <uri
465	link="/proj/en/base/amd64/tests/index.xml?part=1&chap=1">Arch Testers
466	project</uri>
467	</li>
468	<li>
469	Help answering questions on the mailing lists, forums and IRC channels
470	</li>
471	<li>Sending patches</li>
472	</ul>
473
474	</body>
475	</section>
476	</chapter>
477
478	<chapter>
479	<title>Other Resources</title>
480	<section id="other">
481	<title>Where can I get more help or information about Gentoo/AMD64?</title>
482	<body>
483
484	<p>
485	If any of your questions wasn't answered here, you can try other resources like
486	the <uri link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri>, the
487	<uri link="/proj/en/base/amd64/technotes/index.xml">AMD64 Technotes</uri> or
488	<uri link="/proj/en/base/amd64/index.xml">our project homepage</uri>. You can
489	also ask us at <c>#gentoo-amd64</c> on <c>irc.freenode.net</c>, <uri
490	link="http://forums.gentoo.org/viewforum-f-46.html">Gentoo/AMD64 Forums</uri>,
491	or on the <c>gentoo-amd64@lists.gentoo.org</c> mailing list.
492	</p>
493
494	</body>
495	</section>
496	</chapter>
497
498	</guide>