| 1 |
josejx 12/12/28 15:58:18 |
| 2 |
|
| 3 |
Modified: gentoo-ppc-faq.xml |
| 4 |
Log: |
| 5 |
Updated PPC FAQ for KMS and removed some obsolete material. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.73 xml/htdocs/doc/en/gentoo-ppc-faq.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml?rev=1.73&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml?rev=1.73&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml?r1=1.72&r2=1.73 |
| 13 |
|
| 14 |
Index: gentoo-ppc-faq.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml,v |
| 17 |
retrieving revision 1.72 |
| 18 |
retrieving revision 1.73 |
| 19 |
diff -u -r1.72 -r1.73 |
| 20 |
--- gentoo-ppc-faq.xml 24 Jul 2012 12:12:51 -0000 1.72 |
| 21 |
+++ gentoo-ppc-faq.xml 28 Dec 2012 15:58:18 -0000 1.73 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version='1.0' encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml,v 1.72 2012/07/24 12:12:51 swift Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml,v 1.73 2012/12/28 15:58:18 josejx Exp $ --> |
| 27 |
|
| 28 |
<guide> |
| 29 |
<title>Gentoo Linux/PowerPC Frequently Asked Questions</title> |
| 30 |
@@ -30,8 +30,8 @@ |
| 31 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 32 |
<license/> |
| 33 |
|
| 34 |
-<version>3</version> |
| 35 |
-<date>2012-07-24</date> |
| 36 |
+<version>4</version> |
| 37 |
+<date>2012-12-29</date> |
| 38 |
|
| 39 |
<faqindex> |
| 40 |
<title>Questions</title> |
| 41 |
@@ -253,12 +253,16 @@ |
| 42 |
<body> |
| 43 |
|
| 44 |
<p> |
| 45 |
-No. If you are not using a separate boot partition (<path>/boot</path>) then |
| 46 |
+Maybe. If you are not using a separate boot partition (<path>/boot</path>) then |
| 47 |
you do not need this line and can safely just delete it from |
| 48 |
<path>/etc/fstab</path>. The Apple bootstrap partition is <e>not</e> |
| 49 |
-<path>/boot</path> and is not related in any way. In general, Apple PowerPC |
| 50 |
-machines do not need a separate <path>/boot</path> partition, and the bootstrap |
| 51 |
-partition should not be mounted or referred to in your fstab. |
| 52 |
+<path>/boot</path> and is not related in any way. |
| 53 |
+</p> |
| 54 |
+ |
| 55 |
+<p>If you are using a partition type that's not natively supported by the |
| 56 |
+bootloader (such as ext4 and yaboot), you will need to use a separate boot |
| 57 |
+partition. In this case, you will want to specify <path>/dev/BOOT</path> in |
| 58 |
+your fstab. |
| 59 |
</p> |
| 60 |
|
| 61 |
</body> |
| 62 |
@@ -323,17 +327,14 @@ |
| 63 |
</section> |
| 64 |
<section id="stupidclock"> |
| 65 |
<title> |
| 66 |
-I can't boot the InstallCD! It stops while trying to set the hardware clock. |
| 67 |
-What do I do? |
| 68 |
+I want to set the hardware clock from Open Firmware, is that possible? |
| 69 |
</title> |
| 70 |
<body> |
| 71 |
|
| 72 |
<p> |
| 73 |
-Unfortunately, there was a bug in some versions of the baselayout scripts. To |
| 74 |
-get the system booting, the hardware clock will need to be set. To set the |
| 75 |
-clock boot into Open Firmware (using the key combination of Apple + O + F). |
| 76 |
-Once you are at the Open Firmware prompt, you can set the clock using the |
| 77 |
-command below: |
| 78 |
+To set the clock boot into Open Firmware (using the key combination of |
| 79 |
+Apple + O + F). Once you are at the Open Firmware prompt, you can set the clock |
| 80 |
+using the command below: |
| 81 |
</p> |
| 82 |
|
| 83 |
<pre caption="Setting the clock at the open firmware prompt"> |
| 84 |
@@ -346,9 +347,8 @@ |
| 85 |
</pre> |
| 86 |
|
| 87 |
<p> |
| 88 |
-Open Firmware will return with an ok after the clock is set. The system should |
| 89 |
-boot normally now. Type <c>mac-boot</c> to continue booting after the clock is |
| 90 |
-set. |
| 91 |
+Open Firmware will return with an ok after the clock is set. Type |
| 92 |
+<c>mac-boot</c> to continue booting after the clock is set. |
| 93 |
</p> |
| 94 |
|
| 95 |
</body> |
| 96 |
@@ -468,6 +468,12 @@ |
| 97 |
# <i>sysctl -p /etc/sysctl.conf</i> |
| 98 |
</pre> |
| 99 |
|
| 100 |
+<p> |
| 101 |
+Apple Powerbooks and iBooks that use the Appletouch driver, can alternatively |
| 102 |
+configure multi-finger tapping to allow 2nd and 3rd button control. See the |
| 103 |
+documentation for this driver for configuration options. |
| 104 |
+</p> |
| 105 |
+ |
| 106 |
</body> |
| 107 |
</section> |
| 108 |
<section id="airport"> |
| 109 |
@@ -518,8 +524,8 @@ |
| 110 |
Note that the driver should select the proper driver between b43 and b43-legacy. |
| 111 |
The firmware used for these two drivers is different, with the legacy version |
| 112 |
supporting older 4306 cards. If you have a 4306 card, build both, otherwise, |
| 113 |
-it should be safe to only build b43. Also, to enable either driver, mac80211 |
| 114 |
-must be selected first. |
| 115 |
+it should be safe to only build b43. To enable either driver, mac80211 must be |
| 116 |
+selected first. |
| 117 |
</p> |
| 118 |
|
| 119 |
<pre caption="Adding b43 support to the kernel"> |
| 120 |
@@ -536,8 +542,10 @@ |
| 121 |
|
| 122 |
<p> |
| 123 |
After compiling your kernel, you'll need to emerge <c>b43-fwcutter</c> to |
| 124 |
-install the firmware. For additional information, please see this |
| 125 |
-<uri link="http://forums.gentoo.org/viewtopic-t-409194.html">forum post.</uri> |
| 126 |
+install the firmware and get a copy of the firmware. The instructions for this |
| 127 |
+are found at: |
| 128 |
+<uri link="http://linuxwireless.org/en/users/Drivers/b43#Other_distributions_not_mentioned_above"> |
| 129 |
+linuxwireless.org</uri>, and follow the directions for extracting the firmware. |
| 130 |
</p> |
| 131 |
|
| 132 |
<p> |
| 133 |
@@ -577,16 +585,10 @@ |
| 134 |
<body> |
| 135 |
|
| 136 |
<p> |
| 137 |
-Sleep (suspend to ram) works very well on all G3 iBooks and TiBooks. Recently, a |
| 138 |
-kernel patch has been released that adds sleep support for G4 iBooks and Radeon |
| 139 |
-based AlBooks. If you have one of these laptops, use gentoo-sources 2.6.11 (or |
| 140 |
-newer) for built in support. |
| 141 |
+Sleep used to work well with the User Mode Setting kernel drivers, but modern |
| 142 |
+X servers using KMS do not sleep properly at this time. |
| 143 |
</p> |
| 144 |
|
| 145 |
-<note> |
| 146 |
-Note that the 12" PowerBook is not yet supported due to its nVidia chipset. |
| 147 |
-</note> |
| 148 |
- |
| 149 |
</body> |
| 150 |
</section> |
| 151 |
<section id="sound"> |
| 152 |
@@ -907,21 +909,7 @@ |
| 153 |
|
| 154 |
</body> |
| 155 |
</section> |
| 156 |
-<section id="xorg"> |
| 157 |
-<title>Is there an easy way to configure X?</title> |
| 158 |
-<body> |
| 159 |
|
| 160 |
-<p> |
| 161 |
-Simply emerge <c>xac</c>. Once the package has been emerged, run <c>xac</c> to |
| 162 |
-generate the config for your setup. If you would like to set a keyboard layout, |
| 163 |
-you can use the --kbd-layout option. Note that although <c>xac</c> does set up |
| 164 |
-DRM for most users, you may need to change your kernel configuration and emerge |
| 165 |
-additional drivers to support the suggested configuration. Be sure that you've |
| 166 |
-configured your kernel as shown in the question below for optimal performance. |
| 167 |
-</p> |
| 168 |
- |
| 169 |
-</body> |
| 170 |
-</section> |
| 171 |
<section id="drm"> |
| 172 |
<title>What is required for DRM?</title> |
| 173 |
<body> |
| 174 |
@@ -929,9 +917,9 @@ |
| 175 |
<p> |
| 176 |
When emerging xorg-server, make sure the dri use flag is enabled. You should |
| 177 |
also set the VIDEO_CARDS variable in make.conf with your video card, |
| 178 |
-VIDEO_CARDS="radeon" for radeon support, VIDEO_CARDS="nv" for nvidia support |
| 179 |
-and so on. For a backup option, add fbdev to the list of VIDEO_CARDS, this |
| 180 |
-driver should always work. |
| 181 |
+VIDEO_CARDS="radeon" for radeon support, VIDEO_CARDS="nouveau" for nvidia |
| 182 |
+support and so on. For a backup option, add fbdev to the list of VIDEO_CARDS, |
| 183 |
+this driver should always work. |
| 184 |
</p> |
| 185 |
|
| 186 |
<p> |
| 187 |
@@ -939,61 +927,57 @@ |
| 188 |
</p> |
| 189 |
|
| 190 |
<pre caption="Rage128 DRM kernel configuration"> |
| 191 |
-Device Drivers - Character devices ---> |
| 192 |
+Device Drivers - Graphics Support ---> |
| 193 |
<*> /dev/agpgart (AGP Support) |
| 194 |
- [*] Apple UniNorth support |
| 195 |
+ [*] Apple UniNorth support |
| 196 |
[*] Direct Rendering Manager (DRI support) |
| 197 |
- <*> ATI Rage 128 |
| 198 |
-Device Drivers - Graphics Support ---> |
| 199 |
- <*> ATI Rage 128 display support |
| 200 |
+ <*> ATI Rage 128 |
| 201 |
+ -*- Support for frame buffer devices |
| 202 |
+ <*> ATI Rage 128 display support |
| 203 |
</pre> |
| 204 |
|
| 205 |
<pre caption="Radeon DRM kernel configuration"> |
| 206 |
-Device Drivers - Character devices ---> |
| 207 |
+Device Drivers - Graphics Support ---> |
| 208 |
<*> /dev/agpgart (AGP Support) |
| 209 |
- [*] Apple UniNorth support |
| 210 |
+ [*] Apple UniNorth support |
| 211 |
[*] Direct Rendering Manager (DRI support) |
| 212 |
- <*> ATI Radeon |
| 213 |
-Device Drivers - Graphics Support ---> |
| 214 |
- <*> ATI Radeon display support |
| 215 |
+ <*> ATI Radeon |
| 216 |
+ [*] Enable modesetting on radeon by default - NEW DRIVER |
| 217 |
</pre> |
| 218 |
|
| 219 |
<pre caption="nVidia kernel configuration"> |
| 220 |
Device Drivers - Graphics Support ---> |
| 221 |
- <*> nVidia Framebuffer Support |
| 222 |
+ <*> /dev/agpgart (AGP Support) |
| 223 |
+ [*] Apple UniNorth support |
| 224 |
+ [*] Direct Rendering Manager (DRI support) |
| 225 |
+ <*> Nouveau (nVidia) cards |
| 226 |
+ [*] Support for backlight control |
| 227 |
</pre> |
| 228 |
|
| 229 |
<note> |
| 230 |
-There is currently no support for DRM on nVidia cards since nVidia has not |
| 231 |
-released any drivers for PPC and there are no open drivers for 3D acceleration. |
| 232 |
+For nVidia and Radeon devices using KMS, be sure to disable the built in frame |
| 233 |
+buffer devices, these prevent the KMS drivers from starting. |
| 234 |
</note> |
| 235 |
|
| 236 |
-<p> |
| 237 |
-Rebuild and install the kernel if necessary. After this, make sure you |
| 238 |
-have booted to the native framebuffer (i.e. radeonfb or atyfb128 and |
| 239 |
-<e>not</e> from offb or ofonly video), and run <c>xac</c>. |
| 240 |
-</p> |
| 241 |
- |
| 242 |
<impo> |
| 243 |
You may need to edit your <path>/etc/X11/xorg.conf</path> file depending on |
| 244 |
-your card setup. Ensure that the device driver selected is either ati or your |
| 245 |
-specific driver (r128 or radeon). Also check that the DRI extension is loaded |
| 246 |
-and not commented out. |
| 247 |
+your card setup. Ensure that the device driver selected is the specific driver |
| 248 |
+for your device, (such as radeon or nouveau). Also check that the DRI extension |
| 249 |
+is loaded and not commented out. |
| 250 |
</impo> |
| 251 |
|
| 252 |
</body> |
| 253 |
</section> |
| 254 |
<section id="noati"> |
| 255 |
<title> |
| 256 |
-I've installed X.org and configured it correctly, but the radeon driver is |
| 257 |
-missing. What's wrong? |
| 258 |
+I've installed X.org and configured it correctly, but the radeon or nouveau |
| 259 |
+driver is missing. What's wrong? |
| 260 |
</title> |
| 261 |
<body> |
| 262 |
|
| 263 |
<p> |
| 264 |
-Add the appropriate VIDEO_CARDS line to <path>/etc/portage/make.conf</path> (specify |
| 265 |
-r128 or radeon) and recompile <c>xorg-server</c> and <c>mesa</c> to rebuild the |
| 266 |
-driver. |
| 267 |
+Add the appropriate VIDEO_CARDS line to <path>/etc/portage/make.conf</path> and |
| 268 |
+recompile <c>xorg-server</c> and <c>mesa</c> to build the drivers. |
| 269 |
</p> |
| 270 |
|
| 271 |
</body> |
| 272 |
@@ -1031,13 +1015,8 @@ |
| 273 |
</pre> |
| 274 |
|
| 275 |
<p> |
| 276 |
-Also, there are some known issues with the composite extension, please disable |
| 277 |
-this extension if you're having problems. |
| 278 |
-</p> |
| 279 |
- |
| 280 |
-<p> |
| 281 |
-Finally, if you are still having trouble, please try disabling dri in your |
| 282 |
-xorg.conf and see if the problems go away. |
| 283 |
+If you are still having trouble, please try disabling dri in your xorg.conf to |
| 284 |
+see if the problems go away. |
| 285 |
</p> |
| 286 |
|
| 287 |
</body> |
| 288 |
@@ -1083,66 +1062,7 @@ |
| 289 |
|
| 290 |
</body> |
| 291 |
</section> |
| 292 |
-<section id="mol"> |
| 293 |
-<title>Can I run Mac OS 9 or Mac OS X under Gentoo Linux?</title> |
| 294 |
-<body> |
| 295 |
- |
| 296 |
-<p> |
| 297 |
-Yes, as long as you are running Gentoo Linux on 32 bit PPC hardware, you can |
| 298 |
-use <uri link="http://www.maconlinux.org/">Mac-on-Linux</uri> which allows you |
| 299 |
-to run an instance of OS 9, OS X or Linux as a process on Linux. Simply |
| 300 |
-<c>emerge mol</c> to install this package. MOL supports Mac OS 7.5.2 to 9.2.2, |
| 301 |
-as well as any version of OS X. It can be run from a console framebuffer or run |
| 302 |
-in a window on X. |
| 303 |
-</p> |
| 304 |
- |
| 305 |
-<note> |
| 306 |
-Currently, there is no support for running MOL on 64 bit PowerPC Processors. |
| 307 |
-</note> |
| 308 |
- |
| 309 |
-<note> |
| 310 |
-To run MOL fullscreen, you'll need to compile MOL with the fbcon use flag |
| 311 |
-enabled and run it in a console framebuffer. |
| 312 |
-</note> |
| 313 |
|
| 314 |
-<p> |
| 315 |
-For networking and sound you should install the drivers in the folder |
| 316 |
-<path>MOL-Install</path> on your Mac OS X-Desktop. If errors with networking |
| 317 |
-occur, make sure you have the following kernel options enabled: |
| 318 |
-</p> |
| 319 |
- |
| 320 |
-<p> |
| 321 |
-For OSX Networking: |
| 322 |
-</p> |
| 323 |
- |
| 324 |
-<ul> |
| 325 |
- <li>Universal TUN/TAP device driver support (CONFIG_TUN)</li> |
| 326 |
-</ul> |
| 327 |
- |
| 328 |
-<p> |
| 329 |
-For the DHCP server: |
| 330 |
-</p> |
| 331 |
- |
| 332 |
-<ul> |
| 333 |
- <li>Socket Filtering (CONFIG_FILTER)</li> |
| 334 |
- <li>Packet Socket (CONFIG_PACKET)</li> |
| 335 |
-</ul> |
| 336 |
- |
| 337 |
-<p> |
| 338 |
-For NAT: |
| 339 |
-</p> |
| 340 |
- |
| 341 |
-<ul> |
| 342 |
- <li>Network packet filtering (CONFIG_NETFILTER)</li> |
| 343 |
- <li>Connection tracking (CONFIG_IP_NF_CONNTRACK)</li> |
| 344 |
- <li>IP tables support (CONFIG_IP_NF_IPTABLES)</li> |
| 345 |
- <li>Packet filtering (CONFIG_IP_NF_FILTER)</li> |
| 346 |
- <li>Full NAT (CONFIG_IP_NF_NAT)</li> |
| 347 |
- <li>MASQUERADE target support (CONFIG_IP_NF_TARGET_MASQUERADE)</li> |
| 348 |
-</ul> |
| 349 |
- |
| 350 |
-</body> |
| 351 |
-</section> |
| 352 |
<section id="ext"> |
| 353 |
<title>Can I access my ext2/ext3 partitions from OSX?</title> |
| 354 |
<body> |
| 355 |
@@ -1192,35 +1112,6 @@ |
| 356 |
|
| 357 |
</body> |
| 358 |
</section> |
| 359 |
-<section id="gccsegfaults"> |
| 360 |
-<title>Why does gcc keep segfaulting during ebuilds?</title> |
| 361 |
-<body> |
| 362 |
- |
| 363 |
-<p> |
| 364 |
-If gcc segfaults during ebuilds, this probably isn't a bug with gcc and isn't |
| 365 |
-even a problem with your hardware. Most of the time this problem is due to |
| 366 |
-kernel preemption being enabled. Although this option is safe on x86, it can |
| 367 |
-cause cache corruption on PPC which is why it is noticed most frequently during |
| 368 |
-compiles. To prevent this from happening, simply recompile the kernel with |
| 369 |
-preempt turned off. To check if preempt is enabled: |
| 370 |
-</p> |
| 371 |
- |
| 372 |
-<pre caption="Check if preempt is enabled"> |
| 373 |
-$ <i>grep PREEMPT /usr/src/linux/.config</i> |
| 374 |
-</pre> |
| 375 |
- |
| 376 |
-<p> |
| 377 |
-If returns: "# CONFIG_PREEMPT is not set", then you should report the segfault |
| 378 |
-as a bug. |
| 379 |
-</p> |
| 380 |
- |
| 381 |
-<p> |
| 382 |
-If it returns: "CONFIG_PREEMPT=y", then you'll need to disable it and rebuild |
| 383 |
-your kernel. |
| 384 |
-</p> |
| 385 |
- |
| 386 |
-</body> |
| 387 |
-</section> |
| 388 |
</chapter> |
| 389 |
|
| 390 |
<chapter> |
Archives