/[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.11 - (show annotations) (download) (as text)
Sat Feb 11 14:22:50 2006 UTC (8 years, 7 months ago) by swift
Branch: MAIN
Changes since 1.10: +4 -4 lines
File MIME type: application/xml
Link to correct location for 32bit guide, thanks to Mark Tabash for noticing

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

  ViewVC Help
Powered by ViewVC 1.1.20