/[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.15 - (hide annotations) (download) (as text)
Tue Mar 28 10:20:35 2006 UTC (8 years, 3 months ago) by neysx
Branch: MAIN
Changes since 1.14: +3 -4 lines
File MIME type: application/xml
#127683 Removed "# emerge emul-linux-x86-glibc"

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

  ViewVC Help
Powered by ViewVC 1.1.20