/[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.26 - (show annotations) (download) (as text)
Sat Aug 25 09:49:21 2007 UTC (7 years ago) by neysx
Branch: MAIN
Changes since 1.25: +3 -82 lines
File MIME type: application/xml
Use faqindex from #190087, no content change, hence no bump

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.25 2007/07/22 07:32:28 nightmorph 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="blubb@gentoo.org">Simon Stelling</mail>
10 </author>
11 <author title="Editor">
12 <mail link="metalgod@gentoo.org">Luis Medinas</mail>
13 </author>
14 <author title="Editor">
15 <mail link="gerrynjr@gentoo.org">Gerald J. Normandin Jr.</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.18</version>
30 <date>2007-07-22</date>
31
32 <faqindex>
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
42 suggestions or questions about this FAQ, you are welcome to send an e-mail to
43 <mail>amd64@gentoo.org</mail>.
44 </p>
45
46 </body>
47 </section>
48 </faqindex>
49
50 <chapter>
51 <title>Installation</title>
52 <section id="cflags">
53 <title>What CFLAGS should I use for AMD64/EM64T?</title>
54 <body>
55
56 <p>
57 You should use simple <c>CFLAGS</c> to avoid future problems with your system.
58 Supported <c>CFLAGS</c> are <c>-O2 -march=k8 -pipe</c> for non-EM64T systems and
59 <c>-O2 -march=nocona -pipe</c> for EM64T systems.
60 </p>
61
62 </body>
63 </section>
64 <section id="kernel">
65 <title>What kernel should I use for AMD64?</title>
66 <body>
67
68 <p>
69 You can use almost all kernel sources available in Portage. We recommend using
70 <c>gentoo-sources</c> because it is a special kernel designed for Gentoo Linux.
71 It contains lots of AMD64-specific patches and therefore is the only kernel
72 officially supported by Gentoo/AMD64.
73 </p>
74
75 <warn>
76 You should watch out for some kernel features which are not well tested, such
77 as <c>PREEMPT</c>.
78 </warn>
79
80 <p>
81 Make sure you have the <c>IA32_EMULATION</c> option activated in the kernel.
82 </p>
83
84 <pre caption="Activating IA32 Emulation in Kernel source">
85 # <i>cd /usr/src/linux</i>
86 # <i>make menuconfig</i>
87
88 Executable file formats / Emulations ---&gt;
89 [*] IA32 Emulation
90 </pre>
91
92 <warn>
93 You may experience build failures on multilib-systems if you deactivate this
94 option.
95 </warn>
96
97 </body>
98 </section>
99 <section id="perfup">
100 <title>Will I have a performance upgrade if I use a 64bit system instead of 32bit?</title>
101 <body>
102
103 <p>
104 That is a difficult question to answer. In some cases, you will experience a
105 performance improvement, in other cases you will not. For everyday use, there
106 is nearly no difference between 64bit and 32bit. 64bit is generally faster
107 when it comes to floating point computing which is normally the case in
108 multimedia applications and 3D rendering. This <uri
109 link="http://enterprise.linux.com/enterprise/05/06/09/1413209.shtml?tid=121">article</uri>
110 may interest you. There's also a nice <uri
111 link="http://forums.gentoo.org/viewtopic-t-349691.html">thread</uri> in our
112 <uri link="http://forums.gentoo.org">forums</uri>.
113 </p>
114
115 </body>
116 </section>
117 <section id="multilib">
118 <title>What is multilib and how can I use it?</title>
119 <body>
120
121 <p>
122 Every AMD64 processor is able to run 32bit code as well as 64bit code.
123 However, when you have a 32bit application, you are unable to mix it with
124 64bit libraries or vice versa. You can, however, natively run 32bit
125 applications if all shared libraries it needs are available as 32bit objects.
126 You can choose whether you want multilib support or not by selecting the
127 according profile. The default is a multilib-enabled profile.
128 </p>
129
130 <warn>
131 Currently you cannot switch from a no-multilib to a multilib-enabled profile,
132 so think over your decision twice before you use the no-multilib profile.
133 </warn>
134
135 </body>
136 </section>
137 <section id="chroot32">
138 <title>How do I create a 32bit chroot?</title>
139 <body>
140
141 <p>
142 Please read the <uri link="/proj/en/base/amd64/howtos/chroot.xml">32bit chroot
143 guide</uri>.
144 </p>
145
146 </body>
147 </section>
148 <section id="upgradex86">
149 <title>Can I upgrade from my x86 system to amd64 by doing emerge -e world?</title>
150 <body>
151
152 <p>
153 Due to several differences between an <c>x86</c> and an <c>amd64</c>
154 installation, it is impossible to upgrade. Please perform a fresh install. The
155 installation is slightly different than an x86 one, so please use the
156 <uri link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri>.
157 </p>
158
159 </body>
160 </section>
161 <section id="reiser4">
162 <title>Can I use Reiser4?</title>
163 <body>
164
165 <p>
166 Reiser4 is not available from any kernel offered by the Gentoo Kernel project,
167 thus neither AMD64 team supports it. The answer is no.
168 </p>
169
170 </body>
171 </section>
172 </chapter>
173
174 <chapter>
175 <title>Hardware</title>
176 <section id="videobindrivers">
177 <title>Will my binary NVIDIA/ATI drivers work?</title>
178 <body>
179
180 <p>
181 Yes, NVIDIA and ATI provide drivers that work on AMD64. You can install them by
182 executing <c>emerge nvidia-drivers</c> or <c>emerge ati-drivers</c>. If you have
183 more questions about these drivers, you should read the <uri
184 link="/doc/en/nvidia-guide.xml">Nvidia guide</uri> or the <uri
185 link="/doc/en/ati-faq.xml">ATI FAQ</uri>.
186 </p>
187
188 </body>
189 </section>
190 <section id="coolnquiet">
191 <title>How do I use Cool'n'Quiet/PowerNow features?</title>
192 <body>
193
194 <p>
195 You have to compile your kernel with support for these features. You just need
196 to enable the features below:
197 </p>
198
199 <pre caption="Kernel options for Cool'n'Quiet/PowerNow">
200 Power management options ---&gt;
201 [*] Power Management support
202 CPU Frequency scaling ---&gt;
203 [*] CPU Frequency scaling
204 [*] CPU frequency table helpers
205 [*] AMD Opteron/Athlon64 PowerNow!
206 </pre>
207
208 <p>
209 Then <c>emerge cpudyn</c> and edit <path>/etc/conf.d/cpudyn</path> with your
210 favorite editor.
211 </p>
212
213 <pre caption="Example of /etc/conf.d/cpudyn">
214 INTERVAL=1
215 CPU_UP=0.5
216 CPU_DOWN=0.9
217 THROTTLING_LOW=7
218 CPUFREQ_25="/sys/devices/system/cpu/cpu0/cpufreq /sysfs/devices/system/cpu/cpu0/cpufreq"
219 CPUFREQ_ACPI="/proc/acpi/processor/CPU0/throttling"
220 </pre>
221
222 <p>
223 Now you only have to run <c>rc-update add cpudyn default</c> to make sure it is
224 started every time you boot.
225 </p>
226
227 <note>
228 You may want to read the <uri
229 link="/doc/en/power-management-guide.xml#doc_chap3">Power Management Guide</uri>
230 for more tips on CPU power management.
231 </note>
232
233 </body>
234 </section>
235 </chapter>
236
237 <chapter>
238 <title>Applications</title>
239 <section id="flash">
240 <title>Can I get Macromedia Flash working?</title>
241 <body>
242
243 <p>
244 Yes. To get Flash working, you need a 32bit browser like
245 <c>mozilla-firefox-bin</c> or <c>opera</c> because Macromedia doesn't provide a
246 64bit version. After emerging the -bin package of your favorite browser,
247 install Flash by doing <c>emerge netscape-flash</c>.
248 </p>
249
250 </body>
251 </section>
252 <section id="OOo">
253 <title>Can I get OpenOffice.org working?</title>
254 <body>
255
256 <p>
257 OpenOffice versions prior to 2.0.4 do not build on 64bit systems, so you have to use the
258 32bit binary version, available in Portage as <c>app-office/openoffice-bin</c>.
259 If you feel brave you can <c>emerge openoffice</c>, but be aware that the 64bit version
260 is not yet tested out enough to be considered stable.
261 </p>
262
263 </body>
264 </section>
265 <section id="masked">
266 <title>I want to install package foo, but emerge says: (masked by: ~amd64 keyword)</title>
267 <body>
268
269 <p>
270 This means that the package is still in the 'testing' tree. Please read <c>man
271 portage</c> or the <uri
272 link="/doc/en/handbook/handbook-amd64.xml?part=3&amp;chap=3">Mixing Software
273 Branches</uri> chapter of the <uri
274 link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri> for more
275 information.
276 </p>
277
278 </body>
279 </section>
280 <section id="keyword">
281 <title>I want to install package foo, but emerge says: (masked by: missing keyword)</title>
282 <body>
283
284 <p>
285 This means that the package has not been tested yet. It does <e>not
286 necessarily</e> mean that the package does not work. You can unmask it by
287 accepting another architecture for the package. The following example shows you
288 can tell Portage to accept any keyword for a given package.
289 </p>
290
291 <pre caption="Example of adding package keywords">
292 # <i>echo "category/packagename ~* *" >> /etc/portage/package.keywords</i>
293 # <i>emerge packagename</i>
294 </pre>
295
296 <p>
297 If it works fine for you, please let us know and file a bug on <uri
298 link="http://bugs.gentoo.org/">Gentoo's Bugzilla</uri>, so that the AMD64 team
299 can keyword the package and other users can benefit from your test.
300 </p>
301
302 <warn>
303 Do not try commands like <c>ACCEPT_KEYWORDS="~x86" emerge packagename</c>. It
304 will most certainly break your tree.
305 </warn>
306
307 </body>
308 </section>
309 </chapter>
310
311 <chapter>
312 <title>How can I help the Gentoo/AMD64 project?</title>
313 <section id="project">
314 <title>How can I help?</title>
315 <body>
316
317 <p>
318 With a growing popularity of the amd64 architecture, we also increasingly need
319 more help. There's still much work to be done to improve the quality of
320 Gentoo/AMD64. An average user can help us by:
321 </p>
322
323 <ul>
324 <li>Filing general bug reports</li>
325 <li>Testing software that does not yet have the <c>~amd64</c> keyword</li>
326 <li>
327 Participating in the <uri link="/proj/en/base/amd64/at/">Arch Testers
328 project</uri>
329 </li>
330 <li>
331 Help answering questions on the mailing lists, forums and IRC channels
332 </li>
333 <li>Sending patches</li>
334 </ul>
335
336 </body>
337 </section>
338 </chapter>
339
340 <chapter>
341 <title>Other Resources</title>
342 <section id="other">
343 <title>Where can I get more help or information about Gentoo/AMD64?</title>
344 <body>
345
346 <p>
347 If any of your questions wasn't answered here, you can try other resources
348 listed on <uri link="/proj/en/base/amd64/">our project homepage</uri>. You can
349 also ask us at <c>#gentoo-amd64</c> on <c>irc.freenode.net</c>, <uri
350 link="http://forums.gentoo.org/viewforum-f-46.html">Gentoo/AMD64 Forums</uri>,
351 or on the <c>gentoo-amd64@lists.gentoo.org</c> mailing list.
352 </p>
353
354 </body>
355 </section>
356 </chapter>
357
358 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20