/[gentoo]/xml/htdocs/doc/en/gentoo-amd64-faq.xml
Gentoo

Diff of /xml/htdocs/doc/en/gentoo-amd64-faq.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.1 Revision 1.2
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.1 2005/07/16 09:44:33 neysx Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-amd64-faq.xml,v 1.2 2005/07/16 15:08:25 smithj Exp $ -->
4 4
5<guide link="/doc/en/gentoo-amd64-faq.xml"> 5<guide link="/doc/en/gentoo-amd64-faq.xml">
6<title>Gentoo Linux/AMD64 Frequently Asked Questions</title> 6<title>Gentoo Linux/AMD64 Frequently Asked Questions</title>
7 7
8<author title="Editor"> 8<author title="Editor">
36<body> 36<body>
37 37
38<p> 38<p>
39This document contains the most commonly asked questions about Gentoo/AMD64. We 39This document contains the most commonly asked questions about Gentoo/AMD64. We
40intend to help and provide useful information about Gentoo/AMD64. Some of these 40intend to help and provide useful information about Gentoo/AMD64. Some of these
41questions can be found in forums, irc or mailing lists. If you have suggestions 41questions can be found in forums, irc, or mailing lists. If you have suggestions
42or questions about this FAQ, you are welcome to send an e-mail to the authors 42or questions about this FAQ, you are welcome to send an e-mail to the authors
43explaining the problem. 43explaining the problem.
44</p> 44</p>
45 45
46</body> 46</body>
140<p> 140<p>
141You should use simple <c>CFLAGS</c> to avoid future problems with your system. 141You should use simple <c>CFLAGS</c> to avoid future problems with your system.
142For example, you should use <c>CFLAGS="-march=k8 -O2 -pipe"</c> for Athlon64 or 142For example, you should use <c>CFLAGS="-march=k8 -O2 -pipe"</c> for Athlon64 or
143Opteron and <c>CFLAGS="-march=nocona -O2 -pipe"</c> for a EM64T processor. If 143Opteron and <c>CFLAGS="-march=nocona -O2 -pipe"</c> for a EM64T processor. If
144you plan to use a 32-bit chroot, you should use <c>CFLAGS="-march=athlon-xp 144you 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 145-O2 -pipe -msse2"</c> for a AMD64 processor; for a EM64T, you should use
146<c>CFLAGS="-march=pentium4 -O2 -pipe"</c> <e>inside the chroot</e>. 146<c>CFLAGS="-march=pentium4 -O2 -pipe"</c> <e>inside the chroot</e>.
147</p> 147</p>
148 148
149<note> 149<note>
150<c>-march=k8</c> is the same as <c>-march=athlon64</c> and 150<c>-march=k8</c> is the same as <c>-march=athlon64</c> and
151<c>-march=opteron</c>. 151<c>-march=opteron</c>.
152</note> 152</note>
153 153
154<warn> 154<warn>
155You should <e>never</e> stick <c>-fPIC</c>, <c>-m32</c> or <c>-m64</c> into 155You should <e>never</e> place <c>-fPIC</c>, <c>-m32</c> or <c>-m64</c> in
156your <c>CFLAGS</c>. They are automatically added whenever they are needed. 156your <c>CFLAGS</c>. They are automatically added whenever they are needed.
157Please also note that the <c>-Os</c> flag is currently not supported. 157Please also note that the <c>-Os</c> flag is currently not supported.
158</warn> 158</warn>
159 159
160</body> 160</body>
162<section id="kernel"> 162<section id="kernel">
163<title>What kernel should I use for AMD64?</title> 163<title>What kernel should I use for AMD64?</title>
164<body> 164<body>
165 165
166<p> 166<p>
167You can use almost all kernel sources available in Portage. We recommend to use 167You can use almost all kernel sources available in Portage. We recommend using
168<c>gentoo-sources</c> because it is a special flavor kernel designed for Gentoo 168<c>gentoo-sources</c> because it is a special kernel designed for Gentoo Linux.
169Linux. It contains lots of AMD64-specific patches and therefore is the only 169It contains lots of AMD64-specific patches and therefore is the only kernel
170flavor supported by Gentoo/AMD64. You can try <c>vanilla-sources</c> as well. 170officially supported by Gentoo/AMD64. You can try <c>vanilla-sources</c> as
171If you feel brave or you need extra hardware support, you can always try the 171well. If you feel brave or you need extra hardware support, you can always try
172experimental kernel from Andrew Morton called <c>mm-sources</c>. 172the experimental kernel from Andrew Morton called <c>mm-sources</c>.
173</p> 173</p>
174 174
175<warn> 175<warn>
176You should watch out for some kernel features which are not tested well, such 176You should watch out for some kernel features which are not well tested, such
177as <c>PREEMPT</c>. 177as <c>PREEMPT</c>.
178</warn> 178</warn>
179 179
180</body> 180</body>
181</section> 181</section>
231<section id="multilib"> 231<section id="multilib">
232<title>What is multilib and how can I use it?</title> 232<title>What is multilib and how can I use it?</title>
233<body> 233<body>
234 234
235<p> 235<p>
236Right now, every AMD64 processor is able to run 32-bit code as well as 64-bit 236Every AMD64 processor is able to run 32-bit code as well as 64-bit code.
237code. However, when you have a 32-bit application, you are unable to mix it 237However, when you have a 32-bit application, you are unable to mix it with
238with 64-bit libraries or vice versa. However, you can natively run 32-bit 23864-bit libraries or vice versa. You can, however, natively run 32-bit
239applications if all shared libraries it needs are available as 32-bit objects 239applications if all shared libraries it needs are available as 32-bit objects.
240too. You can choose whether you want multilib support or not by selecting the 240You can choose whether you want multilib support or not by selecting the
241according profile. The default is a multilib-enabled profile. 241according profile. The default is a multilib-enabled profile.
242</p> 242</p>
243 243
244<note> 244<note>
245If you use an old profile (2004.3 or older), please upgrade to 2005.0 and read 245If you are using an old profile (2004.3 or older), please upgrade to 2005.0 and
246read the <uri
246the <uri link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=1">2005.0 247link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=1">2005.0 Upgrade
247Upgrade Guide</uri> carefully. 248Guide</uri> carefully.
248</note> 249</note>
249 250
250</body> 251</body>
251</section> 252</section>
252<section id="chroot32"> 253<section id="chroot32">
266<body> 267<body>
267 268
268<p> 269<p>
269Due to several differences between an <c>x86</c> and an <c>amd64</c> 270Due to several differences between an <c>x86</c> and an <c>amd64</c>
270installation, it is impossible to upgrade. Please perform a fresh install. The 271installation, it is impossible to upgrade. Please perform a fresh install. The
271installation is slightly different than an x86 one, therefore please use the 272installation is slightly different than an x86 one, so please use the
272<uri link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri>. 273<uri link="/doc/en/handbook/handbook-amd64.xml">AMD64 Handbook</uri>.
273</p> 274</p>
274 275
275</body> 276</body>
276</section> 277</section>
307<title>How do I use Cool'n'Quiet/Powernow features?</title> 308<title>How do I use Cool'n'Quiet/Powernow features?</title>
308<body> 309<body>
309 310
310<p> 311<p>
311You have to compile your kernel with support for these features. You just need 312You have to compile your kernel with support for these features. You just need
312to enable these features below: 313to enable the features below:
313</p> 314</p>
314 315
315<pre caption="Kernel options for Cool'n'Quiet/Powernow"> 316<pre caption="Kernel options for Cool'n'Quiet/Powernow">
316Power management options ---&gt; 317Power management options ---&gt;
317 [*] Power Management support 318 [*] Power Management support
334CPUFREQ_25="/sys/devices/system/cpu/cpu0/cpufreq /sysfs/devices/system/cpu/cpu0/cpufreq" 335CPUFREQ_25="/sys/devices/system/cpu/cpu0/cpufreq /sysfs/devices/system/cpu/cpu0/cpufreq"
335CPUFREQ_ACPI="/proc/acpi/processor/CPU0/throttling" 336CPUFREQ_ACPI="/proc/acpi/processor/CPU0/throttling"
336</pre> 337</pre>
337 338
338<p> 339<p>
339Now you only have to run <c>rc-update add cpudyn default</c> to make sure it 340Now you only have to run <c>rc-update add cpudyn default</c> to make sure it is
340gets started every time you boot. 341started every time you boot.
341</p> 342</p>
342 343
343</body> 344</body>
344</section> 345</section>
345</chapter> 346</chapter>

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.2

  ViewVC Help
Powered by ViewVC 1.1.20