/[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.31 - (show annotations) (download) (as text)
Thu Mar 12 07:07:10 2009 UTC (5 years, 6 months ago) by nightmorph
Branch: MAIN
Changes since 1.30: +9 -25 lines
File MIME type: application/xml
Updated Flash and OpenOffice sections of the AMD64 FAQ, bug 262236

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

  ViewVC Help
Powered by ViewVC 1.1.20