| 1 |
josejx 06/04/30 23:23:53 |
| 2 |
|
| 3 |
Modified: gentoo-ppc-faq.xml |
| 4 |
Log: |
| 5 |
PPC FAQ updates. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.48 xml/htdocs/doc/en/gentoo-ppc-faq.xml |
| 9 |
|
| 10 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-ppc-faq.xml?rev=1.48&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
| 11 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-ppc-faq.xml?rev=1.48&content-type=text/plain&cvsroot=gentoo |
| 12 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-ppc-faq.xml.diff?r1=1.47&r2=1.48&cvsroot=gentoo |
| 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.47 |
| 18 |
retrieving revision 1.48 |
| 19 |
diff -u -r1.47 -r1.48 |
| 20 |
--- gentoo-ppc-faq.xml 4 Apr 2006 00:33:45 -0000 1.47 |
| 21 |
+++ gentoo-ppc-faq.xml 30 Apr 2006 23:23:53 -0000 1.48 |
| 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.47 2006/04/04 00:33:45 nightmorph Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml,v 1.48 2006/04/30 23:23:53 josejx Exp $ --> |
| 27 |
|
| 28 |
<guide link="/doc/en/gentoo-ppc-faq.xml"> |
| 29 |
<title>Gentoo Linux/PowerPC Frequently Asked Questions</title> |
| 30 |
@@ -27,8 +27,8 @@ |
| 31 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 32 |
<license/> |
| 33 |
|
| 34 |
-<version>1.26</version> |
| 35 |
-<date>2006-02-18</date> |
| 36 |
+<version>1.27</version> |
| 37 |
+<date>2006-04-31</date> |
| 38 |
|
| 39 |
<chapter> |
| 40 |
<title>Questions</title> |
| 41 |
@@ -66,8 +66,8 @@ |
| 42 |
<li> |
| 43 |
<uri link="#bwof"> |
| 44 |
I have an early NewWorld Mac such as the Blue and White G3. It should be |
| 45 |
- compatible with the LiveCD, but on boot it returns an "Unknown or corrupt |
| 46 |
- filesystem" error. |
| 47 |
+ compatible with the InstallCD, but on boot it returns an "Unknown or |
| 48 |
+ corrupt filesystem" error. |
| 49 |
</uri> |
| 50 |
</li> |
| 51 |
<li> |
| 52 |
@@ -99,6 +99,12 @@ |
| 53 |
When I rebooted, yaboot didn't work! Now, I'm stuck. How can I fix this? |
| 54 |
</uri> |
| 55 |
</li> |
| 56 |
+ <li> |
| 57 |
+ <uri link="#applebrokeit"> |
| 58 |
+ I installed an OSX update and now my computer only boots into OSX! How |
| 59 |
+ can I fix it? |
| 60 |
+ </uri> |
| 61 |
+ </li> |
| 62 |
</ul> |
| 63 |
|
| 64 |
</body> |
| 65 |
@@ -150,6 +156,12 @@ |
| 66 |
How can I make my Mac power up after a power failure? |
| 67 |
</uri> |
| 68 |
</li> |
| 69 |
+ <li> |
| 70 |
+ <uri link="#infrombadport"> |
| 71 |
+ I see lots of "IN from bad port" errors in my kernel dmesg, how do I |
| 72 |
+ fix that? |
| 73 |
+ </uri> |
| 74 |
+ </li> |
| 75 |
</ul> |
| 76 |
|
| 77 |
</body> |
| 78 |
@@ -180,6 +192,12 @@ |
| 79 |
<uri link="#drm">How do I configure DRM and OpenGL acceleration?</uri> |
| 80 |
</li> |
| 81 |
<li> |
| 82 |
+ <uri link="#xorgerror"> |
| 83 |
+ I have a VBIOS or "Invalid I/O allocation" error in my xorg.log. Is this |
| 84 |
+ a problem? |
| 85 |
+ </uri> |
| 86 |
+ </li> |
| 87 |
+ <li> |
| 88 |
<uri link="#glfreeze"> |
| 89 |
When using OpenGL DRI or playing movies, the system sometimes locks up |
| 90 |
unexpectedly. What can I do? |
| 91 |
@@ -366,7 +384,7 @@ |
| 92 |
<section id="bwof"> |
| 93 |
<title> |
| 94 |
I have an early NewWorld Mac such as the Blue and White G3. It should be |
| 95 |
-compatible with the LiveCD, but on boot it returns an "Unknown or corrupt |
| 96 |
+compatible with the InstallCD, but on boot it returns an "Unknown or corrupt |
| 97 |
filesystem" error. |
| 98 |
</title> |
| 99 |
<body> |
| 100 |
@@ -460,10 +478,11 @@ |
| 101 |
|
| 102 |
<p> |
| 103 |
It's probably just a misconfigured yaboot.conf. The easiest way to fix this is |
| 104 |
-to boot the LiveCD again, mount your gentoo partition and check yaboot.conf for |
| 105 |
-errors. You'll also need to run <c>ybin -v -C /mnt/gentoo/etc/yaboot.conf</c> |
| 106 |
-to update the boot loader once you have finished. This can all be done without |
| 107 |
-chrooting back into your install. |
| 108 |
+to boot the InstallCD again, mount your gentoo partition and check yaboot.conf |
| 109 |
+for errors. You'll also need to run |
| 110 |
+<c>ybin -v -C /mnt/gentoo/etc/yaboot.conf</c> to update the boot loader once |
| 111 |
+you have finished. This can all be done without chrooting back into your |
| 112 |
+install. |
| 113 |
</p> |
| 114 |
|
| 115 |
<note> |
| 116 |
@@ -474,6 +493,22 @@ |
| 117 |
|
| 118 |
</body> |
| 119 |
</section> |
| 120 |
+<section id="applebrokeit"> |
| 121 |
+<title> |
| 122 |
+I installed an OSX update and now my computer only boots into OSX! How can I |
| 123 |
+fix it? |
| 124 |
+</title> |
| 125 |
+<body> |
| 126 |
+ |
| 127 |
+<p> |
| 128 |
+Hold down the option key on boot. This will bring you to a graphical boot |
| 129 |
+device selector. Wait until a hard drive with a penguin shows up and click |
| 130 |
+on the icon. This will boot your linux install as usual. Once you've |
| 131 |
+booted, rerun <c>ybin -v</c> to fix the bootloader. |
| 132 |
+</p> |
| 133 |
+ |
| 134 |
+</body> |
| 135 |
+</section> |
| 136 |
</chapter> |
| 137 |
|
| 138 |
<chapter> |
| 139 |
@@ -758,6 +793,10 @@ |
| 140 |
</p> |
| 141 |
|
| 142 |
<pre caption="Kernel options for ALSA"> |
| 143 |
+Device Drivers - I2c support ---> |
| 144 |
+ I2C Hardware Bus Support ---> |
| 145 |
+ <*> Powermac I2C interface (Keywest on 2.6.15 and older) |
| 146 |
+ |
| 147 |
Device Drivers - Sound ---> |
| 148 |
<*> Sound card support |
| 149 |
Advanced Linux Sound Architecture ---> |
| 150 |
@@ -773,7 +812,12 @@ |
| 151 |
</pre> |
| 152 |
|
| 153 |
<p> |
| 154 |
-(or configure as modules and ensure they're loaded on boot). |
| 155 |
+(or configure as modules and ensure they're loaded on boot). If you have a |
| 156 |
+late model Powerbook, you should look into snd-aoa instead. If you're using |
| 157 |
+snd-aoa, be sure to disaable the |
| 158 |
+PowerMac (AWACS, DACA, Burgundy, Tumbler, Keywest) driver above. snd-aoa is |
| 159 |
+available in this git repository: |
| 160 |
+<uri>http://johannes.sipsolutions.net/snd-aoa.git</uri> |
| 161 |
</p> |
| 162 |
|
| 163 |
<note> |
| 164 |
@@ -804,6 +848,11 @@ |
| 165 |
</p> |
| 166 |
|
| 167 |
<pre caption="Kernel options for OSS"> |
| 168 |
+Device Drivers - I2c support ---> |
| 169 |
+ I2C Hardware Bus Support ---> |
| 170 |
+ <*> Powermac I2C interface (Keywest on 2.6.15 and older) |
| 171 |
+ |
| 172 |
+Device Drivers - Sound ---> |
| 173 |
<*> Sound card support |
| 174 |
<*> PowerMac DMA sound support |
| 175 |
</pre> |
| 176 |
@@ -842,6 +891,47 @@ |
| 177 |
|
| 178 |
</body> |
| 179 |
</section> |
| 180 |
+<section id="infrombadport"> |
| 181 |
+<title> |
| 182 |
+I see lots of "IN from bad port" errors in my kernel dmesg, how do I fix that? |
| 183 |
+</title> |
| 184 |
+<body> |
| 185 |
+ |
| 186 |
+<p> |
| 187 |
+This is caused by drivers written for devices that you don't have on your |
| 188 |
+system. These messages are usually harmless, but it's a good idea to |
| 189 |
+disable the unused drivers anway. See below to match up port numbers with |
| 190 |
+kernel configuration options. Note that even if the numbers don't match, |
| 191 |
+try disabling these kernel options anyway, most PPC machines don't use these |
| 192 |
+drivers. |
| 193 |
+</p> |
| 194 |
+ |
| 195 |
+<pre caption="IN from bad port 61 - Disable PC Speaker support"> |
| 196 |
+Device Drivers - Input device support ---> |
| 197 |
+[*] Miscellanous devices ---> |
| 198 |
+ < > PC Speaker Support |
| 199 |
+</pre> |
| 200 |
+ |
| 201 |
+<pre caption="IN from bad port 64 - Disable i8042 keyboard support"> |
| 202 |
+Device Drivers - Input device support ---> |
| 203 |
+Hardware I/O Ports ---> |
| 204 |
+ < > Serial I/O support |
| 205 |
+ < > i8042 PC Keyboard controller |
| 206 |
+</pre> |
| 207 |
+ |
| 208 |
+<pre caption="IN from bad port 2E9,2F9,3E9,3F9 - Disable 8250/16550 support"> |
| 209 |
+Device Drivers - Character devices ---> |
| 210 |
+Serial drivers ---> |
| 211 |
+ < > 8250/16550 and compatible serial support |
| 212 |
+</pre> |
| 213 |
+ |
| 214 |
+<p> |
| 215 |
+If you have another IN from bad port message that you're not sure about, please |
| 216 |
+let us know! |
| 217 |
+</p> |
| 218 |
+ |
| 219 |
+</body> |
| 220 |
+</section> |
| 221 |
</chapter> |
| 222 |
|
| 223 |
<chapter> |
| 224 |
@@ -966,7 +1056,8 @@ |
| 225 |
<c>Xorgautoconfig</c> to generate the config for your setup. If you would like |
| 226 |
to set a keyboard layout, you can use the --keymap flag. Note that although |
| 227 |
<c>Xorgautoconfig</c> does set up DRM for most users, you may need to change |
| 228 |
-your kernel configuration to support this. |
| 229 |
+your kernel configuration to support this. Be sure that you've configured your |
| 230 |
+kernel as shown in the question below for optimal performance. |
| 231 |
</p> |
| 232 |
|
| 233 |
</body> |
| 234 |
@@ -1022,14 +1113,20 @@ |
| 235 |
and not commented out. |
| 236 |
</impo> |
| 237 |
|
| 238 |
-<note> |
| 239 |
-There currently isn't any DRI support for the R300/R400 chipsets, but a project |
| 240 |
-has been started at <uri>http://r300.sourceforge.net</uri>. Initial support for |
| 241 |
-the chipset is slated to be included in the next major version of X.org as the |
| 242 |
-r300 project is now part of the DRI project. nVidia chipsets are also mostly |
| 243 |
-unsupported on PPC, there is basic 2D acceleration provied by the nv driver, |
| 244 |
-but no 3D acceleration. |
| 245 |
-</note> |
| 246 |
+</body> |
| 247 |
+</section> |
| 248 |
+<section id="xorgerror"> |
| 249 |
+<title> |
| 250 |
+I have a VBIOS or "Invalid I/O allocation" error in my xorg.log. Is this |
| 251 |
+a problem? |
| 252 |
+</title> |
| 253 |
+<body> |
| 254 |
+ |
| 255 |
+<p> |
| 256 |
+No, this is simply X.org probing your video card. It attempts to open the |
| 257 |
+x86 only video BIOS and fails, leaving one of these messages. It's |
| 258 |
+harmless, don't worry about it! |
| 259 |
+</p> |
| 260 |
|
| 261 |
</body> |
| 262 |
</section> |
| 263 |
@@ -1208,9 +1305,8 @@ |
| 264 |
If you've got another faster computer, you can set up distcc to compile |
| 265 |
binaries for your slower ppc processor. It's better to do as much building as |
| 266 |
possible on the faster machine, if possible, don't even build on the slower |
| 267 |
-computer. With that said, here are a few links to get you started: |
| 268 |
+computer. With that said, here's a link to get you started: |
| 269 |
<uri>http://dev.gentoo.org/~vapier/CROSS-COMPILE-HOWTO</uri> |
| 270 |
-<uri>http://www.sable.mcgill.ca/~dbelan2/crossdev/crossdev-powerpc-i686.html</uri> |
| 271 |
</p> |
| 272 |
|
| 273 |
</body> |
| 274 |
|
| 275 |
|
| 276 |
|
| 277 |
-- |
| 278 |
gentoo-doc-cvs@g.o mailing list |
Archives