Attachment #61079 for bug #95800

View | Details | Raw Unified | Return to bug 95800 | Differences between
Collapse All | Expand All





<license/>

<version>1.18</version>
<date>2005-05-11</date>


<chapter>
<title>Installation</title>

<body>

<p>
First be sure you did not mount the ftp server with <e>Finder</e> and then copy the file with drag'n'drop.  This will corrupt the ISO.  Instead, use <c>curl</c>
(with <c>curl -O http://path/to/iso</c>).
the ISO.  Instead, use <c>curl</c> (with <c>curl -O
http://path/to/iso</c>).
</p>

<p>

<body>

<p>
If you have a lot of time to experiment, you could try 
<uri link="http://penguinppc.org/projects/quik/">Quik</uri>. <e>Quik</e> is a
bootloader for OldWorld PPC machines. If your machine uses <e>BootX</e>, you can
use <e>Quik</e>; if it uses <e>yaboot</e>, you can't.  <e>Quik</e> can be
incredibly difficult to install, but the end result is somewhere between "neato"
and "breathtaking" because Mac OS does not have to load. Think yaboot on speed.
end result is somewhere between "neato" and "breathtaking" because Mac OS
does not have to load. Think yaboot on speed.
</p>

<p>
Be sure to read the <uri
link="http://penguinppc.org/projects/quik/quirks.shtml">Quik quirks
page</uri> for help getting your Old World PPC booting with Quik. The
"<uri link="http://www.netbsd.org/Ports/macppc/models.html">NetBSD/MacPPC Model Support</uri>" documents various OpenFirmware versions for various Apple and 
clone PowerPC machines and is also a helpful reference.
link="http://www.imaclinux.net/php/imaclinux_g_h.php3?single=17+index=0">Guide:
Quik - Direct Booting for Older PowerMacs</uri>". "<uri
link="http://www.netbsd.org/Ports/macppc/models.html">NetBSD/macppc
Model Support</uri>" documents OpenFirmware versions for various Apple
and clone PowerPC machines.
</p>

<p>


</body>
</section>

<section>
<title>
  When I rebooted, yaboot didn't work! Now, I'm stuck. How can I fix this?
</title>
<body>

  <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.
  </p>
  
  <note>
    If you <e>really</e> just need to get back to OSX, try holding down the
    Option key on startup.  This should give you a graphical selection of
    bootable disks.  Chose OSX and remember to fix your boot problems later.
  </note>

</body>
</section>

<section>
<title>
  Installation is now complete. However after rebooting, I am getting

<body>

<p>
There is no way to use ctrl-button like on Mac OS X, but you can map just about
any key or combination of keys to emulate the second and third mouse-button.  
The values can be obtained with the command line utility <c>showkey</c> from the
console.  Note that this program does not work as expected from X and should 
only be run from the console.  In addition to having the kernel configuration 
settings from the previous section, you will also need to set the mouse button
values in <path>/etc/sysctl.conf</path>.  Here is an example using F11 and F12:
<path>mouse_button3_keycode</path>.  To keep the settings after reboot,
write them to <path>/etc/sysctl.conf</path>.  Here is an example using
F11 and F12:
</p>

<pre caption="Mouse button emulation with F11 and F12">

</pre>

<p>
Other commonly used keycodes are 125 (The Apple key) and 96 (The Keypad Enter).
</p>

</body>

<body>

<p>
There are four main packages you will need to install.
</p>

<ul>

    and various other preferences.
  </li>
  <li>
    <e>cpudyn</e> allows cpu speed scaling for longer battery life. Other
    packages also provide the same functionality, such as <e>powernowd</e>,
    <e>cpufreqd</e> and <e>speedfreq</e>.
  </li>
</ul>


</pre>

<note>
You should edit <path>/etc/pbbuttonsd.conf</path> to better suit your needs.
The behaviour of the Fx-keys can be controlled here as well as many sleep
options.  To switch the Fx-keys to the OSX behaviour, set KBDMode to fkeyslast.
You can turn off touchpad tapping by setting TPMode to notap.  Many other 
options are available, see man pbbuttonsd.conf for details.
</note>

<p>

<title>Does Gentoo/PPC have support for Flash?</title>
<body>
<p>
Well, not really. Macromedia has not supplied a linux/ppc binary and open source
implementations are incomplete and buggy at this time.  Two projects working on
this problem are <uri link="http://gplflash.sf.net">gplflash2</uri> and 
<uri link="http://swfdec.sf.net">swfdec</uri>, so check there for more 
information. A possible workaround for now is to use qemu (an x86 emulator)
to run the Macromedia Flash Player 6 stand alone player.  This process was
described on the forums: 
<uri>http://forums.gentoo.org/viewtopic.php?t=117774</uri>
</p>
</body>

<body>
<p>
No, not at this time.  The older java plugin is no longer compatible with the
new Mozilla plugin system and a new plugin has not yet been written.
</p>
</body>
</section>

extensions included with the newer X.org releases.  Please disable
these extensions if you're having problems. 
</p>

</body>
</section>
<section>

Device Drivers - Sound ---&gt;
&lt;*&gt; Sound card support
    Advanced Linux Sound Architecture ---&gt;
    &lt;&nbsp;&gt;   PowerMac DMA sound support
      &lt;*&gt; Advanced Linux Sound Architecture
      &lt;*&gt; Sequencer support
      &lt;*&gt; Sequencer dummy client

<section>
<title>Sound setup with OSS</title>
<body>

<note>Again, only use this if you're not using ALSA.</note>

<p>
In <c>make menuconfig</c> you'll need to select:
</p>

Yes, as long as your are running Gentoo Linux/PPC on Apple hardware
(or a Mac-clone). You will need to run <uri
link="http://www.maconlinux.org/">Mac-on-Linux</uri>. Just <c>emerge
mol</c>. MOL supports Mac OS 7.5.2 to 9.2.2, as well as any version of OS X.
It can be run from a console framebuffer or run in a window on X.
</p>

<note>

</note>

<p>
For networking and sound you should install the drivers in the folder
<path>MOL-Install</path> on your Mac OS X-Desktop.  If errors with
networking occur, make sure you have the following kernel options
enabled:

<section>
<title>Can I access my ext2/ext3 partitions from OSX?</title>
<body>

<p>
OSX can support the reading and writing of ext2/ext3 partitions by using the 
kernel extension provided by the <uri link="http://sourceforge.net/projects/ext2fsx">ext2fsx project.</uri>
</p>

<note>
When using MOL, you cannot access a partition that is currently being used by
Linux.
</note>

</body>
</section>
<section>
<title>Which Portage USE flags do not work on PowerPC machines?</title>
<body>

<p>
If you're using an old flat profile, (pre 2005.0) look at <path>/etc/make.profile/use.mask</path> for a list.
</p>

<p>
If you're using a cascaded profile, (2005.0 and onwards) look at <path>/usr/portage/profiles/default-linux/ppc/use.mask</path> for a list.
</p>

</body>
</section>
<section>
<title>How can I set up distcc with my x86 box?</title>
<body>

<p>
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

With that said, here are a few links 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>
</section>
<section>
<title>Why does gcc keep segfaulting during ebuilds?</title>
<body>

<p>
If gcc segfaults during ebuilds, this probably isn't a bug with gcc and isn't
even a problem with your hardware.  Most of the time this problem is due to

<pre caption="Check if preempt is enabled">
$ <i>grep PREEMPT /usr/src/linux/.config</i>
</pre>

<p>
If returns: "# CONFIG_PREEMPT is not set", then you should report the 
segfault as a bug.
</p>

<p>
If it returns: "CONFIG_PREEMPT=y", then you'll need to disable it and rebuild
your kernel.

Return to bug 95800

Lines 26-34 Link Here

(-)gentoo-ppc-faq.xml.bak (-49 / +82 lines)
26		26
27	<license/>	27	<license/>
28		28
29	<version>1.17</version>	29	<version>1.18</version>
30	<date>2005-04-11</date>	30	<date>2005-05-11</date>
31
32		31
33	<chapter>	32	<chapter>
34	<title>Installation</title>	33	<title>Installation</title>
Lines 40-49 Link Here
40	<body>	39	<body>
41		40
42	<p>	41	<p>
43	First be sure you did not mount the ftp server with	42	First be sure you did not mount the ftp server with <e>Finder</e> and then copy the file with drag'n'drop. This will corrupt the ISO. Instead, use <c>curl</c>
44	<e>Finder</e> and then copy the file with drag'n'drop. This will corrupt	43	(with <c>curl -O http://path/to/iso</c>).
45	the ISO. Instead, use <c>curl</c> (with <c>curl -O
46	http://path/to/iso</c>).
47	</p>	44	</p>
48		45
49	<p>	46	<p>
Lines 156-182 Link Here
156	<body>	153	<body>
157		154
158	<p>	155	<p>
159	If you have a lot of time to experiment, you could try <uri	156	If you have a lot of time to experiment, you could try
160	link="http://penguinppc.org/projects/quik/">Quik</uri>. <e>Quik</e> is a	157	<uri link="http://penguinppc.org/projects/quik/">Quik</uri>. <e>Quik</e> is a
161	bootloader for OldWorld PPC machines. If your machine uses <e>BootX</e>,	158	bootloader for OldWorld PPC machines. If your machine uses <e>BootX</e>, you can
162	you can use <e>Quik</e>; if it uses <e>yaboot</e>, you can't.	159	use <e>Quik</e>; if it uses <e>yaboot</e>, you can't. <e>Quik</e> can be
163	<e>Quik</e> can be incredibly difficult to install, and is currently	160	incredibly difficult to install, but the end result is somewhere between "neato"
164	<e>not</e> working with gcc 3.x (read: Gentoo 1.4 or later), but the	161	and "breathtaking" because Mac OS does not have to load. Think yaboot on speed.
165	end result is somewhere between "neato" and "breathtaking" because Mac OS
166	does not have to load. Think yaboot on speed.
167	</p>	162	</p>
168		163
169	<p>	164	<p>
170	Be sure to read the <uri	165	Be sure to read the <uri
171	link="http://penguinppc.org/projects/quik/quirks.shtml">Quik quirks	166	link="http://penguinppc.org/projects/quik/quirks.shtml">Quik quirks
172	page</uri>. Also see "<uri	167	page</uri> for help getting your Old World PPC booting with Quik. The
173	link="http://lppcfom.sourceforge.net/fom-serve/cache/574.html">Is Quik	168	"<uri link="http://www.netbsd.org/Ports/macppc/models.html">NetBSD/MacPPC Model Support</uri>" documents various OpenFirmware versions for various Apple and
174	Bootloader for Mac OS Dead?</uri>" and "<uri	169	clone PowerPC machines and is also a helpful reference.
175	link="http://www.imaclinux.net/php/imaclinux_g_h.php3?single=17+index=0">Guide:
176	Quik - Direct Booting for Older PowerMacs</uri>". "<uri
177	link="http://www.netbsd.org/Ports/macppc/models.html">NetBSD/macppc
178	Model Support</uri>" documents OpenFirmware versions for various Apple
179	and clone PowerPC machines.
180	</p>	170	</p>
181		171
182	<p>	172	<p>
Lines 238-243 Link Here
238		228
239	</body>	229	</body>
240	</section>	230	</section>
		231
		232	<section>
		233	<title>
		234	When I rebooted, yaboot didn't work! Now, I'm stuck. How can I fix this?
		235	</title>
		236	<body>
		237
		238	<p>
		239	It's probably just a misconfigured yaboot.conf. The easiest way to fix
		240	this is to boot the LiveCD again, mount your gentoo partition and check
		241	yaboot.conf for errors. You'll also need to run
		242	<c>ybin -v -C /mnt/gentoo/etc/yaboot.conf</c> to update the boot loader once
		243	you have finished. This can all be done without chrooting back into your
		244	install.
		245	</p>
		246
		247	<note>
		248	If you <e>really</e> just need to get back to OSX, try holding down the
		249	Option key on startup. This should give you a graphical selection of
		250	bootable disks. Chose OSX and remember to fix your boot problems later.
		251	</note>
		252
		253	</body>
		254	</section>
		255
241	<section>	256	<section>
242	<title>	257	<title>
243	Installation is now complete. However after rebooting, I am getting	258	Installation is now complete. However after rebooting, I am getting
Lines 294-309 Link Here
294	<body>	309	<body>
295		310
296	<p>	311	<p>
297	There is no way to get ctrl-button, like on Mac OS X, working. But	312	There is no way to use ctrl-button like on Mac OS X, but you can map just about
298	you can map quite any key or combination of keys to emulate the second	313	any key or combination of keys to emulate the second and third mouse-button.
299	and third mouse-button. The values can be obtained with the command	314	The values can be obtained with the command line utility <c>showkey</c> from the
300	line utility <c>showkey</c>. The mouse button emulation is switched on	315	console. Note that this program does not work as expected from X and should
301	using the proc-device. First run <c>echo "1" >	316	only be run from the console. In addition to having the kernel configuration
302	/proc/sys/dev/mac_hid/mouse_button_emulation</c>. Then copy the right	317	settings from the previous section, you will also need to set the mouse button
303	keycodes to <path>mouse_button2_keycode</path> and	318	values in <path>/etc/sysctl.conf</path>. Here is an example using F11 and F12:
304	<path>mouse_button3_keycode</path>. To keep the settings after reboot,
305	write them to <path>/etc/sysctl.conf</path>. Here is an example using
306	F11 and F12:
307	</p>	319	</p>
308		320
309	<pre caption="Mouse button emulation with F11 and F12">	321	<pre caption="Mouse button emulation with F11 and F12">
Lines 316-322 Link Here
316	</pre>	328	</pre>
317		329
318	<p>	330	<p>
319	Other keys are 100 and 126 for the combinations fn+alt and fn+apple.	331	Other commonly used keycodes are 125 (The Apple key) and 96 (The Keypad Enter).
320	</p>	332	</p>
321		333
322	</body>	334	</body>
Lines 407-413 Link Here
407	<body>	419	<body>
408		420
409	<p>	421	<p>
410	There are three main packages you will need to install.	422	There are four main packages you will need to install.
411	</p>	423	</p>
412		424
413	<ul>	425	<ul>
Lines 429-435 Link Here
429	and various other preferences.	441	and various other preferences.
430	</li>	442	</li>
431	<li>	443	<li>
432	<e>cpudyn</e> allows cpu speed scaling for longer battery life.	444	<e>cpudyn</e> allows cpu speed scaling for longer battery life. Other
		445	packages also provide the same functionality, such as <e>powernowd</e>,
		446	<e>cpufreqd</e> and <e>speedfreq</e>.
433	</li>	447	</li>
434	</ul>	448	</ul>
435		449
Lines 446-455 Link Here
446	</pre>	460	</pre>
447		461
448	<note>	462	<note>
449	You should edit your <path>/etc/pbbuttonsd.conf</path> to your	463	You should edit <path>/etc/pbbuttonsd.conf</path> to better suit your needs.
450	preference. Especially the behaviour of the Fx-keys, as pbbuttonsd	464	The behaviour of the Fx-keys can be controlled here as well as many sleep
451	gives you the availabilty, to use the Fx-keys in the first mode, and the	465	options. To switch the Fx-keys to the OSX behaviour, set KBDMode to fkeyslast.
452	brightness- and sound-keys with the help of Fn.	466	You can turn off touchpad tapping by setting TPMode to notap. Many other
		467	options are available, see man pbbuttonsd.conf for details.
453	</note>	468	</note>
454		469
455	<p>	470	<p>
Lines 571-580 Link Here
571	<title>Does Gentoo/PPC have support for Flash?</title>	586	<title>Does Gentoo/PPC have support for Flash?</title>
572	<body>	587	<body>
573	<p>	588	<p>
574	No, Macromedia has not supplied a linux/ppc binary and until Macromedia opens	589	Well, not really. Macromedia has not supplied a linux/ppc binary and open source
575	the flash format or provides a binary flash will not work on ppc. A possible	590	implementations are incomplete and buggy at this time. Two projects working on
576	work around is to use qemu (an x86 emulator) to run the Macromedia Flash Player	591	this problem are <uri link="http://gplflash.sf.net">gplflash2</uri> and
577	6 stand alone player. This is described here:	592	<uri link="http://swfdec.sf.net">swfdec</uri>, so check there for more
		593	information. A possible workaround for now is to use qemu (an x86 emulator)
		594	to run the Macromedia Flash Player 6 stand alone player. This process was
		595	described on the forums:
578	<uri>http://forums.gentoo.org/viewtopic.php?t=117774</uri>	596	<uri>http://forums.gentoo.org/viewtopic.php?t=117774</uri>
579	</p>	597	</p>
580	</body>	598	</body>
Lines 584-590 Link Here
584	<body>	602	<body>
585	<p>	603	<p>
586	No, not at this time. The older java plugin is no longer compatible with the	604	No, not at this time. The older java plugin is no longer compatible with the
587	new Mozilla plugin system and a new plugin has not been written.	605	new Mozilla plugin system and a new plugin has not yet been written.
588	</p>	606	</p>
589	</body>	607	</body>
590	</section>	608	</section>
Lines 681-686 Link Here
681	extensions included with the newer X.org releases. Please disable	699	extensions included with the newer X.org releases. Please disable
682	these extensions if you're having problems.	700	these extensions if you're having problems.
683	</p>	701	</p>
		702
684	</body>	703	</body>
685	</section>	704	</section>
686	<section>	705	<section>
Lines 733-739 Link Here
733	Device Drivers - Sound --->	752	Device Drivers - Sound --->
734	<*> Sound card support	753	<*> Sound card support
735	Advanced Linux Sound Architecture --->	754	Advanced Linux Sound Architecture --->
736	<*> PowerMac DMA sound support	755	< > PowerMac DMA sound support
737	<*> Advanced Linux Sound Architecture	756	<*> Advanced Linux Sound Architecture
738	<*> Sequencer support	757	<*> Sequencer support
739	<*> Sequencer dummy client	758	<*> Sequencer dummy client
Lines 759-764 Link Here
759	<section>	778	<section>
760	<title>Sound setup with OSS</title>	779	<title>Sound setup with OSS</title>
761	<body>	780	<body>
		781
		782	<note>Again, only use this if you're not using ALSA.</note>
		783
762	<p>	784	<p>
763	In <c>make menuconfig</c> you'll need to select:	785	In <c>make menuconfig</c> you'll need to select:
764	</p>	786	</p>
Lines 848-855 Link Here
848	Yes, as long as your are running Gentoo Linux/PPC on Apple hardware	870	Yes, as long as your are running Gentoo Linux/PPC on Apple hardware
849	(or a Mac-clone). You will need to run <uri	871	(or a Mac-clone). You will need to run <uri
850	link="http://www.maconlinux.org/">Mac-on-Linux</uri>. Just <c>emerge	872	link="http://www.maconlinux.org/">Mac-on-Linux</uri>. Just <c>emerge
851	mol</c>. MOL support Mac OS 7.5.2 to 9.2.2, as well as any version of OS X.	873	mol</c>. MOL supports Mac OS 7.5.2 to 9.2.2, as well as any version of OS X.
852	It can take over your full screen, or run in a window.	874	It can be run from a console framebuffer or run in a window on X.
853	</p>	875	</p>
854		876
855	<note>	877	<note>
Lines 858-864 Link Here
858	</note>	880	</note>
859		881
860	<p>	882	<p>
861	For networking and sound you might install the drivers in the folder	883	For networking and sound you should install the drivers in the folder
862	<path>MOL-Install</path> on your Mac OS X-Desktop. If errors with	884	<path>MOL-Install</path> on your Mac OS X-Desktop. If errors with
863	networking occur, make sure you have the following kernel options	885	networking occur, make sure you have the following kernel options
864	enabled:	886	enabled:
Lines 891-920 Link Here
891	<section>	913	<section>
892	<title>Can I access my ext2/ext3 partitions from OSX?</title>	914	<title>Can I access my ext2/ext3 partitions from OSX?</title>
893	<body>	915	<body>
		916
894	<p>	917	<p>
895	OSX can support the reading and writing of ext2/ext3 partitions by using the	918	OSX can support the reading and writing of ext2/ext3 partitions by using the
896	kernel extension provided by the <uri link="http://sourceforge.net/projects/ext2fsx">ext2fsx project.</uri>	919	kernel extension provided by the <uri link="http://sourceforge.net/projects/ext2fsx">ext2fsx project.</uri>
897	</p>	920	</p>
		921
898	<note>	922	<note>
899	When using MOL, you cannot access a partition that is currently being used by	923	When using MOL, you cannot access a partition that is currently being used by
900	Linux.	924	Linux.
901	</note>	925	</note>
		926
902	</body>	927	</body>
903	</section>	928	</section>
904	<section>	929	<section>
905	<title>Which Portage USE flags do not work on PowerPC machines?</title>	930	<title>Which Portage USE flags do not work on PowerPC machines?</title>
906	<body>	931	<body>
		932
907	<p>	933	<p>
908	If you're using an old flat profile, (pre 2005.0) look at <path>/etc/make.profile/use.mask</path> for a list.	934	If you're using an old flat profile, (pre 2005.0) look at <path>/etc/make.profile/use.mask</path> for a list.
909	</p>	935	</p>
		936
910	<p>	937	<p>
911	If you're using a cascaded profile, (2005.0 and onwards) look at <path>/usr/portage/profiles/default-linux/ppc/use.mask</path> for a list.	938	If you're using a cascaded profile, (2005.0 and onwards) look at <path>/usr/portage/profiles/default-linux/ppc/use.mask</path> for a list.
912	</p>	939	</p>
		940
913	</body>	941	</body>
914	</section>	942	</section>
915	<section>	943	<section>
916	<title>How can I set up distcc with my x86 box?</title>	944	<title>How can I set up distcc with my x86 box?</title>
917	<body>	945	<body>
		946
918	<p>	947	<p>
919	If you've got another faster computer, you can set up distcc to compile binaries	948	If you've got another faster computer, you can set up distcc to compile binaries
920	for your slower ppc processor. It's better to do as much building as possible	949	for your slower ppc processor. It's better to do as much building as possible
Lines 922-933 Link Here
922	With that said, here are a few links to get you started:	951	With that said, here are a few links to get you started:
923	<uri>http://dev.gentoo.org/~vapier/CROSS-COMPILE-HOWTO</uri>	952	<uri>http://dev.gentoo.org/~vapier/CROSS-COMPILE-HOWTO</uri>
924	<uri>http://www.sable.mcgill.ca/~dbelan2/crossdev/crossdev-powerpc-i686.html</uri>	953	<uri>http://www.sable.mcgill.ca/~dbelan2/crossdev/crossdev-powerpc-i686.html</uri>
		954
925	</p>	955	</p>
926	</body>	956	</body>
927	</section>	957	</section>
928	<section>	958	<section>
929	<title>Why does gcc keep segfaulting during ebuilds?</title>	959	<title>Why does gcc keep segfaulting during ebuilds?</title>
930	<body>	960	<body>
		961
931	<p>	962	<p>
932	If gcc segfaults during ebuilds, this probably isn't a bug with gcc and isn't	963	If gcc segfaults during ebuilds, this probably isn't a bug with gcc and isn't
933	even a problem with your hardware. Most of the time this problem is due to	964	even a problem with your hardware. Most of the time this problem is due to
Lines 940-949 Link Here
940	<pre caption="Check if preempt is enabled">	971	<pre caption="Check if preempt is enabled">
941	$ <i>grep PREEMPT /usr/src/linux/.config</i>	972	$ <i>grep PREEMPT /usr/src/linux/.config</i>
942	</pre>	973	</pre>
		974
943	<p>	975	<p>
944	If returns: "# CONFIG_PREEMPT is not set", then you should report the	976	If returns: "# CONFIG_PREEMPT is not set", then you should report the
945	segfault as a bug.	977	segfault as a bug.
946	</p>	978	</p>
		979
947	<p>	980	<p>
948	If it returns: "CONFIG_PREEMPT=y", then you'll need to disable it and rebuild	981	If it returns: "CONFIG_PREEMPT=y", then you'll need to disable it and rebuild
949	your kernel.	982	your kernel.