/[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.1 - (show annotations) (download) (as text)
Sat Jul 16 09:44:33 2005 UTC (9 years, 2 months ago) by neysx
Branch: MAIN
File MIME type: application/xml
#99168 New AMD64/FAQ

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

  ViewVC Help
Powered by ViewVC 1.1.20