| 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> |
| 39 | This document contains the most commonly asked questions about Gentoo/AMD64. We |
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 |
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 |
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 |
42 | or questions about this FAQ, you are welcome to send an e-mail to the authors |
| 43 | explaining the problem. |
43 | explaining the problem. |
| 44 | </p> |
44 | </p> |
| 45 | |
45 | |
| 46 | </body> |
46 | </body> |
| … | |
… | |
| 140 | <p> |
140 | <p> |
| 141 | You should use simple <c>CFLAGS</c> to avoid future problems with your system. |
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 |
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 |
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 |
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 |
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> |
| 155 | You should <e>never</e> stick <c>-fPIC</c>, <c>-m32</c> or <c>-m64</c> into |
155 | You should <e>never</e> place <c>-fPIC</c>, <c>-m32</c> or <c>-m64</c> in |
| 156 | your <c>CFLAGS</c>. They are automatically added whenever they are needed. |
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. |
157 | Please 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> |
| 167 | You can use almost all kernel sources available in Portage. We recommend to use |
167 | You 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. |
| 169 | Linux. It contains lots of AMD64-specific patches and therefore is the only |
169 | It contains lots of AMD64-specific patches and therefore is the only kernel |
| 170 | flavor supported by Gentoo/AMD64. You can try <c>vanilla-sources</c> as well. |
170 | officially supported by Gentoo/AMD64. You can try <c>vanilla-sources</c> as |
| 171 | If you feel brave or you need extra hardware support, you can always try the |
171 | well. If you feel brave or you need extra hardware support, you can always try |
| 172 | experimental kernel from Andrew Morton called <c>mm-sources</c>. |
172 | the experimental kernel from Andrew Morton called <c>mm-sources</c>. |
| 173 | </p> |
173 | </p> |
| 174 | |
174 | |
| 175 | <warn> |
175 | <warn> |
| 176 | You should watch out for some kernel features which are not tested well, such |
176 | You should watch out for some kernel features which are not well tested, such |
| 177 | as <c>PREEMPT</c>. |
177 | as <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> |
| 236 | Right now, every AMD64 processor is able to run 32-bit code as well as 64-bit |
236 | Every AMD64 processor is able to run 32-bit code as well as 64-bit code. |
| 237 | code. However, when you have a 32-bit application, you are unable to mix it |
237 | However, when you have a 32-bit application, you are unable to mix it with |
| 238 | with 64-bit libraries or vice versa. However, you can natively run 32-bit |
238 | 64-bit libraries or vice versa. You can, however, natively run 32-bit |
| 239 | applications if all shared libraries it needs are available as 32-bit objects |
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 |
240 | You can choose whether you want multilib support or not by selecting the |
| 241 | according profile. The default is a multilib-enabled profile. |
241 | according profile. The default is a multilib-enabled profile. |
| 242 | </p> |
242 | </p> |
| 243 | |
243 | |
| 244 | <note> |
244 | <note> |
| 245 | If you use an old profile (2004.3 or older), please upgrade to 2005.0 and read |
245 | If you are using an old profile (2004.3 or older), please upgrade to 2005.0 and |
|
|
246 | read the <uri |
| 246 | the <uri link="/proj/en/base/amd64/howtos/index.xml?part=1&chap=1">2005.0 |
247 | link="/proj/en/base/amd64/howtos/index.xml?part=1&chap=1">2005.0 Upgrade |
| 247 | Upgrade Guide</uri> carefully. |
248 | Guide</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> |
| 269 | Due to several differences between an <c>x86</c> and an <c>amd64</c> |
270 | 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, 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 | installation 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> |
| 311 | You have to compile your kernel with support for these features. You just need |
312 | You have to compile your kernel with support for these features. You just need |
| 312 | to enable these features below: |
313 | to 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"> |
| 316 | Power management options ---> |
317 | Power management options ---> |
| 317 | [*] Power Management support |
318 | [*] Power Management support |
| … | |
… | |
| 334 | CPUFREQ_25="/sys/devices/system/cpu/cpu0/cpufreq /sysfs/devices/system/cpu/cpu0/cpufreq" |
335 | CPUFREQ_25="/sys/devices/system/cpu/cpu0/cpufreq /sysfs/devices/system/cpu/cpu0/cpufreq" |
| 335 | CPUFREQ_ACPI="/proc/acpi/processor/CPU0/throttling" |
336 | CPUFREQ_ACPI="/proc/acpi/processor/CPU0/throttling" |
| 336 | </pre> |
337 | </pre> |
| 337 | |
338 | |
| 338 | <p> |
339 | <p> |
| 339 | Now you only have to run <c>rc-update add cpudyn default</c> to make sure it |
340 | Now you only have to run <c>rc-update add cpudyn default</c> to make sure it is |
| 340 | gets started every time you boot. |
341 | started every time you boot. |
| 341 | </p> |
342 | </p> |
| 342 | |
343 | |
| 343 | </body> |
344 | </body> |
| 344 | </section> |
345 | </section> |
| 345 | </chapter> |
346 | </chapter> |
Parent Directory
| 
Revision Log
| 
Patch