josejx 06/04/30 23:23:53 Modified: gentoo-ppc-faq.xml Log: PPC FAQ updates.
Revision Changes Path 1.48 xml/htdocs/doc/en/gentoo-ppc-faq.xml 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 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 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 Index: gentoo-ppc-faq.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml,v retrieving revision 1.47 retrieving revision 1.48 diff -u -r1.47 -r1.48 --- gentoo-ppc-faq.xml 4 Apr 2006 00:33:45 -0000 1.47 +++ gentoo-ppc-faq.xml 30 Apr 2006 23:23:53 -0000 1.48 @@ -1,6 +1,6 @@ <?xml version='1.0' encoding="UTF-8"?> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml,v 1.47 2006/04/04 00:33:45 nightmorph Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml,v 1.48 2006/04/30 23:23:53 josejx Exp $ --> <guide link="/doc/en/gentoo-ppc-faq.xml"> <title>Gentoo Linux/PowerPC Frequently Asked Questions</title> @@ -27,8 +27,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>1.26</version> -<date>2006-02-18</date> +<version>1.27</version> +<date>2006-04-31</date> <chapter> <title>Questions</title> @@ -66,8 +66,8 @@ <li> <uri link="#bwof"> I have an early NewWorld Mac such as the Blue and White G3. It should be - compatible with the LiveCD, but on boot it returns an "Unknown or corrupt - filesystem" error. + compatible with the InstallCD, but on boot it returns an "Unknown or + corrupt filesystem" error. </uri> </li> <li> @@ -99,6 +99,12 @@ When I rebooted, yaboot didn't work! Now, I'm stuck. How can I fix this? </uri> </li> + <li> + <uri link="#applebrokeit"> + I installed an OSX update and now my computer only boots into OSX! How + can I fix it? + </uri> + </li> </ul> </body> @@ -150,6 +156,12 @@ How can I make my Mac power up after a power failure? </uri> </li> + <li> + <uri link="#infrombadport"> + I see lots of "IN from bad port" errors in my kernel dmesg, how do I + fix that? + </uri> + </li> </ul> </body> @@ -180,6 +192,12 @@ <uri link="#drm">How do I configure DRM and OpenGL acceleration?</uri> </li> <li> + <uri link="#xorgerror"> + I have a VBIOS or "Invalid I/O allocation" error in my xorg.log. Is this + a problem? + </uri> + </li> + <li> <uri link="#glfreeze"> When using OpenGL DRI or playing movies, the system sometimes locks up unexpectedly. What can I do? @@ -366,7 +384,7 @@ <section id="bwof"> <title> I have an early NewWorld Mac such as the Blue and White G3. It should be -compatible with the LiveCD, but on boot it returns an "Unknown or corrupt +compatible with the InstallCD, but on boot it returns an "Unknown or corrupt filesystem" error. </title> <body> @@ -460,10 +478,11 @@ <p> It's probably just a misconfigured yaboot.conf. The easiest way to fix this is -to boot the LiveCD again, mount your gentoo partition and check yaboot.conf for -errors. You'll also need to run <c>ybin -v -C /mnt/gentoo/etc/yaboot.conf</c> -to update the boot loader once you have finished. This can all be done without -chrooting back into your install. +to boot the InstallCD again, mount your gentoo partition and check yaboot.conf +for errors. You'll also need to run +<c>ybin -v -C /mnt/gentoo/etc/yaboot.conf</c> to update the boot loader once +you have finished. This can all be done without chrooting back into your +install. </p> <note> @@ -474,6 +493,22 @@ </body> </section> +<section id="applebrokeit"> +<title> +I installed an OSX update and now my computer only boots into OSX! How can I +fix it? +</title> +<body> + +<p> +Hold down the option key on boot. This will bring you to a graphical boot +device selector. Wait until a hard drive with a penguin shows up and click +on the icon. This will boot your linux install as usual. Once you've +booted, rerun <c>ybin -v</c> to fix the bootloader. +</p> + +</body> +</section> </chapter> <chapter> @@ -758,6 +793,10 @@ </p> <pre caption="Kernel options for ALSA"> +Device Drivers - I2c support ---> + I2C Hardware Bus Support ---> + <*> Powermac I2C interface (Keywest on 2.6.15 and older) + Device Drivers - Sound ---> <*> Sound card support Advanced Linux Sound Architecture ---> @@ -773,7 +812,12 @@ </pre> <p> -(or configure as modules and ensure they're loaded on boot). +(or configure as modules and ensure they're loaded on boot). If you have a +late model Powerbook, you should look into snd-aoa instead. If you're using +snd-aoa, be sure to disaable the +PowerMac (AWACS, DACA, Burgundy, Tumbler, Keywest) driver above. snd-aoa is +available in this git repository: +<uri>http://johannes.sipsolutions.net/snd-aoa.git</uri> </p> <note> @@ -804,6 +848,11 @@ </p> <pre caption="Kernel options for OSS"> +Device Drivers - I2c support ---> + I2C Hardware Bus Support ---> + <*> Powermac I2C interface (Keywest on 2.6.15 and older) + +Device Drivers - Sound ---> <*> Sound card support <*> PowerMac DMA sound support </pre> @@ -842,6 +891,47 @@ </body> </section> +<section id="infrombadport"> +<title> +I see lots of "IN from bad port" errors in my kernel dmesg, how do I fix that? +</title> +<body> + +<p> +This is caused by drivers written for devices that you don't have on your +system. These messages are usually harmless, but it's a good idea to +disable the unused drivers anway. See below to match up port numbers with +kernel configuration options. Note that even if the numbers don't match, +try disabling these kernel options anyway, most PPC machines don't use these +drivers. +</p> + +<pre caption="IN from bad port 61 - Disable PC Speaker support"> +Device Drivers - Input device support ---> +[*] Miscellanous devices ---> + < > PC Speaker Support +</pre> + +<pre caption="IN from bad port 64 - Disable i8042 keyboard support"> +Device Drivers - Input device support ---> +Hardware I/O Ports ---> + < > Serial I/O support + < > i8042 PC Keyboard controller +</pre> + +<pre caption="IN from bad port 2E9,2F9,3E9,3F9 - Disable 8250/16550 support"> +Device Drivers - Character devices ---> +Serial drivers ---> + < > 8250/16550 and compatible serial support +</pre> + +<p> +If you have another IN from bad port message that you're not sure about, please +let us know! +</p> + +</body> +</section> </chapter> <chapter> @@ -966,7 +1056,8 @@ <c>Xorgautoconfig</c> to generate the config for your setup. If you would like to set a keyboard layout, you can use the --keymap flag. Note that although <c>Xorgautoconfig</c> does set up DRM for most users, you may need to change -your kernel configuration to support this. +your kernel configuration to support this. Be sure that you've configured your +kernel as shown in the question below for optimal performance. </p> </body> @@ -1022,14 +1113,20 @@ and not commented out. </impo> -<note> -There currently isn't any DRI support for the R300/R400 chipsets, but a project -has been started at <uri>http://r300.sourceforge.net</uri>. Initial support for -the chipset is slated to be included in the next major version of X.org as the -r300 project is now part of the DRI project. nVidia chipsets are also mostly -unsupported on PPC, there is basic 2D acceleration provied by the nv driver, -but no 3D acceleration. -</note> +</body> +</section> +<section id="xorgerror"> +<title> +I have a VBIOS or "Invalid I/O allocation" error in my xorg.log. Is this +a problem? +</title> +<body> + +<p> +No, this is simply X.org probing your video card. It attempts to open the +x86 only video BIOS and fails, leaving one of these messages. It's +harmless, don't worry about it! +</p> </body> </section> @@ -1208,9 +1305,8 @@ If you've got another faster computer, you can set up distcc to compile binaries for your slower ppc processor. It's better to do as much building as possible on the faster machine, if possible, don't even build on the slower -computer. With that said, here are a few links to get you started: +computer. With that said, here's a link to get you started: <uri>http://dev.gentoo.org/~vapier/CROSS-COMPILE-HOWTO</uri> -<uri>http://www.sable.mcgill.ca/~dbelan2/crossdev/crossdev-powerpc-i686.html</uri> </p> </body> -- [email protected] mailing list
