/[gentoo]/xml/htdocs/doc/en/gentoo-amd64-faq.xml
Gentoo

Contents of /xml/htdocs/doc/en/gentoo-amd64-faq.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.14 - (hide annotations) (download) (as text)
Sun Mar 19 22:26:28 2006 UTC (8 years, 4 months ago) by jkt
Branch: MAIN
Changes since 1.13: +14 -3 lines
File MIME type: application/xml
Reiser4 clarification as requested by metalgod

1 neysx 1.1 <?xml version="1.0" encoding="UTF-8"?>
2     <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3 jkt 1.14 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.13 2006/02/26 13:56:07 neysx 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 fox2mike 1.12 <mail link="metalgod@gentoo.org">Luis Medinas</mail>
10 neysx 1.1 </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 jkt 1.14 <version>1.11</version>
30     <date>2006-03-19</date>
31 neysx 1.1
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 smithj 1.2 questions can be found in forums, irc, or mailing lists. If you have suggestions
42 neysx 1.1 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 jkt 1.14 <li><uri link="#reiser4">Can I use Reiser4?</uri></li>
69 neysx 1.1 </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 alin 1.4 <title>How can I help the Gentoo/AMD64 project?</title>
110 neysx 1.1 <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 smithj 1.2 -O2 -pipe -msse2"</c> for a AMD64 processor; for a EM64T, you should use
146 neysx 1.1 <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 smithj 1.2 You should <e>never</e> place <c>-fPIC</c>, <c>-m32</c> or <c>-m64</c> in
156 neysx 1.1 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 smithj 1.2 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 neysx 1.1 </p>
174    
175     <warn>
176 smithj 1.2 You should watch out for some kernel features which are not well tested, such
177 neysx 1.1 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 ---&gt;
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 smithj 1.2 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 neysx 1.1 according profile. The default is a multilib-enabled profile.
242     </p>
243    
244     </body>
245     </section>
246     <section id="chroot32">
247     <title>How do I create a 32-bit chroot?</title>
248     <body>
249    
250     <p>
251     Please read the <uri
252 swift 1.11 link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=2">32-bit chroot
253 neysx 1.1 guide</uri>.
254     </p>
255    
256     </body>
257     </section>
258     <section id="upgradex86">
259     <title>Can I upgrade from my x86 system to amd64 by doing emerge -e world?</title>
260     <body>
261    
262     <p>
263     Due to several differences between an <c>x86</c> and an <c>amd64</c>
264     installation, it is impossible to upgrade. Please perform a fresh install. The
265 smithj 1.2 installation is slightly different than an x86 one, so please use the
266 neysx 1.1 <uri link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri>.
267     </p>
268    
269     </body>
270     </section>
271 jkt 1.14 <section id="reiser4">
272     <title>Can I use Reiser4?</title>
273     <body>
274    
275     <p>
276     Reiser4 is not available from any kernel offered by the Gentoo Kernel project,
277     thus neither AMD64 team supports it. The answer is no.
278     </p>
279     </body>
280     </section>
281 neysx 1.1 </chapter>
282    
283     <chapter>
284     <title>Hardware</title>
285     <section id="videobindrivers">
286     <title>Will my binary NVIDIA/ATI drivers work?</title>
287     <body>
288    
289     <p>
290     Yes, NVIDIA and ATI provide drivers that work on AMD64. You can install them by
291     executing <c>emerge nvidia-kernel</c> or <c>emerge ati-drivers</c>. If you have
292     more questions about these drivers, you should read the <uri
293     link="/doc/en/nvidia-guide.xml">Nvidia guide</uri> or the <uri
294     link="/doc/en/ati-faq.xml">ATI FAQ</uri>.
295     </p>
296    
297     </body>
298     </section>
299     <section id="coolnquiet">
300     <title>How do I use Cool'n'Quiet/Powernow features?</title>
301     <body>
302    
303     <p>
304     You have to compile your kernel with support for these features. You just need
305 smithj 1.2 to enable the features below:
306 neysx 1.1 </p>
307    
308     <pre caption="Kernel options for Cool'n'Quiet/Powernow">
309     Power management options ---&gt;
310     [*] Power Management support
311     CPU Frequency scaling ---&gt;
312     [*] CPU Frequency scaling
313     [*] CPU frequency table helpers
314     [*] AMD Opteron/Athlon64 PowerNow!
315     </pre>
316    
317     <p>
318     Then <c>emerge cpudyn</c> and edit <path>/etc/conf.d/cpudyn</path> with your
319     favorite editor.
320     </p>
321    
322     <pre caption="Example of /etc/conf.d/cpudyn">
323     INTERVAL=1
324     CPU_UP=0.5
325     CPU_DOWN=0.9
326     THROTTLING_LOW=7
327     CPUFREQ_25="/sys/devices/system/cpu/cpu0/cpufreq /sysfs/devices/system/cpu/cpu0/cpufreq"
328     CPUFREQ_ACPI="/proc/acpi/processor/CPU0/throttling"
329     </pre>
330    
331     <p>
332 smithj 1.2 Now you only have to run <c>rc-update add cpudyn default</c> to make sure it is
333     started every time you boot.
334 neysx 1.1 </p>
335    
336     </body>
337     </section>
338     </chapter>
339    
340     <chapter>
341     <title>Applications</title>
342     <section id="flash">
343     <title>Can I get Macromedia Flash working?</title>
344     <body>
345    
346     <p>
347     Yes. To get Flash working, you need a 32-bit browser like <c>mozilla-bin</c>,
348     <c>mozilla-firefox-bin</c> or <c>opera</c> because Macromedia doesn't provide a
349     64-bit version. After emerging the -bin-package of your favorite browser,
350     install flash by doing <c>emerge netscape-flash</c>.
351     </p>
352    
353     </body>
354     </section>
355     <section id="OOo">
356     <title>Can I get OpenOffice.org working?</title>
357     <body>
358    
359     <p>
360 neysx 1.8 OpenOffice 1.x and 2.0.x do not build on 64-bit systems, so you have to use the
361     32-bit binary version, available in portage as <c>openoffice-bin</c>.
362 neysx 1.1 </p>
363    
364     </body>
365     </section>
366     <section id="java">
367     <title>How do I get java working in my browser?</title>
368     <body>
369    
370     <p>
371     Blackdown provides a 64-bit JRE. To install it, <c>emerge blackdown-jre</c>.
372     Then, perform the following step:
373     </p>
374    
375     <pre caption="Example of java link to browser plugins">
376     # <i>ln -s /opt/blackdown-jre-*/plugin/amd64/mozilla/libjavaplugin_oji.so /usr/lib64/nsbrowser/plugins/libjavaplugin_oji.so</i>
377     </pre>
378    
379     </body>
380     </section>
381     <section id="masked">
382     <title>I want to install package foo, but emerge says: (masked by: ~amd64 keyword)</title>
383     <body>
384    
385     <p>
386     This means that the package is still in the 'testing' tree. Please read <c>man
387     portage</c> or the <uri
388     link="/doc/en/handbook/handbook-amd64.xml?part=3&amp;chap=3">Mixing Software
389     Branches</uri> chapter of the <uri
390     link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri> for more
391     information.
392     </p>
393    
394     </body>
395     </section>
396     <section id="keyword">
397     <title>I want to install package foo, but emerge says: (masked by: missing keyword)</title>
398     <body>
399    
400     <p>
401     This means that the package has not been tested yet. It does <e>not
402     necessarily</e> mean that the package does not work. You can unmask it by
403 neysx 1.9 accepting another architecture for the package. The following example shows you
404     can tell Portage to accept the ~x86 keyword for a given package.
405 neysx 1.1 </p>
406    
407     <pre caption="Example of adding package keywords">
408 neysx 1.8 # <i>echo "category/package ~x86" >> /etc/portage/package.keywords</i>
409 smithj 1.3 # <i>emerge package</i>
410 neysx 1.1 </pre>
411    
412     <p>
413     If it works fine for you, please let us know and file a bug on <uri
414 neysx 1.9 link="http://bugs.gentoo.org/">Gentoo's Bugzilla</uri>, so that the AMD64 team
415     can keyword the package and other users can benefit from your test.
416 neysx 1.1 </p>
417    
418     <warn>
419     Do not try commands like <c>ACCEPT_KEYWORDS="~x86" emerge package</c>. It will
420     most certainly break your tree.
421     </warn>
422    
423     </body>
424     </section>
425     </chapter>
426    
427     <chapter>
428     <title>How can help I the Gentoo/AMD64 project?</title>
429     <section id="bugs">
430     <title>How do I report bugs?</title>
431     <body>
432    
433     <p>
434     If you find a bug or you want to send us patches, you need to file a bug
435     report. It only takes you a little while, and your help is really appreciated.
436     Please follow the <uri
437 neysx 1.13 link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=1">Filing a Bug
438 neysx 1.1 Guide</uri>.
439     </p>
440    
441     </body>
442     </section>
443     <section id="project">
444     <title>How can I help?</title>
445     <body>
446    
447     <p>
448     With a growing popularity of the amd64 architecture, we also increasingly need
449     more help. There's still much work to be done to improve the quality of
450     Gentoo/AMD64. An average user can help us by:
451     </p>
452    
453     <ul>
454     <li>Filing general bug reports</li>
455     <li>Testing software that does not yet have the <c>~amd64</c> keyword</li>
456     <li>
457     Participating in the <uri
458     link="/proj/en/base/amd64/tests/index.xml?part=1&amp;chap=1">Arch Testers
459     project</uri>
460     </li>
461     <li>
462     Help answering questions on the mailing lists, forums and IRC channels
463     </li>
464     <li>Sending patches</li>
465     </ul>
466    
467     </body>
468     </section>
469     </chapter>
470    
471     <chapter>
472     <title>Other Resources</title>
473     <section id="other">
474     <title>Where can I get more help or information about Gentoo/AMD64?</title>
475     <body>
476    
477     <p>
478     If any of your questions wasn't answered here, you can try other resources like
479     the <uri link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri>, the
480 neysx 1.7 <uri link="/proj/en/base/amd64/howtos/index.xml">AMD64 Howtos</uri> or
481 neysx 1.1 <uri link="/proj/en/base/amd64/index.xml">our project homepage</uri>. You can
482     also ask us at <c>#gentoo-amd64</c> on <c>irc.freenode.net</c>, <uri
483     link="http://forums.gentoo.org/viewforum-f-46.html">Gentoo/AMD64 Forums</uri>,
484     or on the <c>gentoo-amd64@lists.gentoo.org</c> mailing list.
485     </p>
486    
487     </body>
488     </section>
489     </chapter>
490    
491     </guide>

  ViewVC Help
Powered by ViewVC 1.1.20