Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
View | Details | Raw Unified | Return to bug 95800 | Differences between
and this patch

Collapse All | Expand All

(-)gentoo-ppc-faq.xml (-150 / +241 lines)
Lines 4-10 Link Here
4
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5
5
6
<guide link="/doc/en/gentoo-ppc-faq.xml">
6
<guide link="/doc/en/gentoo-ppc-faq.xml">
7
7
<title>Gentoo Linux/PowerPC Frequently Asked Questions</title>
8
<title>Gentoo Linux/PowerPC Frequently Asked Questions</title>
9
8
<author title="Editor">
10
<author title="Editor">
9
  <mail link="rajiv@gentoo.org">Rajiv Manglani</mail>
11
  <mail link="rajiv@gentoo.org">Rajiv Manglani</mail>
10
</author>
12
</author>
Lines 12-22 Link Here
12
  <mail link="pylon@gentoo.org">Lars Weiler</mail>
14
  <mail link="pylon@gentoo.org">Lars Weiler</mail>
13
</author>
15
</author>
14
<author title="Editor">
16
<author title="Editor">
15
    <mail link="sejo@gentoo.org">Jochen Maes </mail>
17
  <mail link="sejo@gentoo.org">Jochen Maes </mail>
16
</author>
18
</author>
17
<author title="Editor">
19
<author title="Editor">
18
    <mail link="josejx@gentoo.org">Joseph Jezak</mail>
20
  <mail link="josejx@gentoo.org">Joseph Jezak</mail>
19
</author>
21
</author>
22
20
<abstract>
23
<abstract>
21
This FAQ is a collection of questions and answers collected from the
24
This FAQ is a collection of questions and answers collected from the
22
gentoo-ppc-dev mailing list and from IRC -- if you have any questions (or
25
gentoo-ppc-dev mailing list and from IRC -- if you have any questions (or
Lines 26-49 Link Here
26
29
27
<license/>
30
<license/>
28
31
29
<version>1.17</version>
32
<version>1.18</version>
30
<date>2005-04-11</date>
33
<date>2005-05-11</date>
31
32
34
33
<chapter>
35
<chapter>
34
<title>Installation</title>
36
<title>Installation</title>
35
<section>
37
<section>
36
<title>
38
<title>How do I verify with Mac OS X the downloaded ISO is not corrupted?</title>
37
  How do I verify with Mac OS X the downloaded ISO is not
38
  corrupted? 
39
</title>
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
44
<e>Finder</e> and then copy the file with drag'n'drop.  This will corrupt
43
the file with drag'n'drop.  This will corrupt the ISO.  Instead, use <c>curl</c>
45
the ISO.  Instead, use <c>curl</c> (with <c>curl -O
44
(with <c>curl -O http://path/to/iso</c>).
46
http://path/to/iso</c>).
47
</p>
45
</p>
48
46
49
<p>
47
<p>
Lines 53-60 Link Here
53
</p>
51
</p>
54
52
55
<pre caption="md5sum with the help of openssl">
53
<pre caption="md5sum with the help of openssl">
54
<comment>(This could take some time depending of the size of the ISO and your CPU)</comment>
56
$ <i>openssl md5 /path/to/iso</i>
55
$ <i>openssl md5 /path/to/iso</i>
57
<comment>This could take some time depending of the size of the ISO and your CPU</comment>
58
</pre>
56
</pre>
59
57
60
<p>
58
<p>
Lines 73-91 Link Here
73
<p>
71
<p>
74
Yes you can! In fact, <e>yabootconfig</e> will automatically detect
72
Yes you can! In fact, <e>yabootconfig</e> will automatically detect
75
and setup <path>/etc/yaboot.conf</path> with Linux, Mac OS X and even
73
and setup <path>/etc/yaboot.conf</path> with Linux, Mac OS X and even
76
classic Mac OS (see the <uri
74
classic Mac OS (see the 
77
link="/doc/en/handbook/handbook-ppc.xml?part=1&amp;chap=9#yaboot">Gentoo Handbook</uri> 
75
<uri link="/doc/en/handbook/handbook-ppc.xml?part=1&amp;chap=10">Gentoo Handbook
78
for details on yabootconfig). The trick is in how you partition your hard
76
</uri> for details on yabootconfig). The trick is in how you partition your hard
79
drive. Before installing Gentoo, startup with the Mac OS X Install CD.
77
drive. Before installing Gentoo, startup with the Mac OS X Install CD. Use the 
80
Use the <c>Disk Utility</c> to partition the drive in your machine into
78
<c>Disk Utility</c> to partition the drive in your machine into two or three 
81
two or three partitions.  Alternatively use <c>parted</c> from the
79
partitions.  Alternatively, use <c>parted</c> from the recent LiveCD, since that
82
recent LiveCD, that can handle HFS and HFS+ partitions.  Furthermore, it
80
can handle HFS and HFS+ partitions.  Parted is also able to shrink a partition 
83
is able to shrink a partition so you don't need to delete your whole
81
so you don't need to delete your existing install. The first partition should 
84
disk.  The first partition should be big enough to contain all your
82
be big enough to contain all your Linux partitions (root+swap+/home etc.). The 
85
Linux partitions (root+swap+/home etc.). The format of this partition
83
format of this partition does not matter.  The second partition should be for 
86
does not matter. The second partition should be for OS X.  The third (and
84
OS X.  The third (and optional) partition should be for classic Mac OS. It is 
87
optional) partition should be for classic Mac OS. It is needed only if
85
needed only if you want to put Mac OS 9 on a separate partition.
88
you want to put Mac OS 9 on a separate partition.
89
</p>
86
</p>
90
87
91
<note>
88
<note>
Lines 100-106 Link Here
100
When you get to the section on partitioning, use <c>mac-fdisk</c> to 
97
When you get to the section on partitioning, use <c>mac-fdisk</c> to 
101
<e>delete</e> the large partition you created for Gentoo. In its place, 
98
<e>delete</e> the large partition you created for Gentoo. In its place, 
102
create a bootstrap partition, root, swap, and any other partitions you 
99
create a bootstrap partition, root, swap, and any other partitions you 
103
want to use with Gentoo.
100
wish to use with Gentoo.
104
</p>
101
</p>
105
102
106
<p>
103
<p>
Lines 110-148 Link Here
110
bootstrap partition.
107
bootstrap partition.
111
</p>
108
</p>
112
109
110
<note>
111
If yabootconfig does not detect your MacOS partitions, you can manually add 
112
them to your yaboot.config.  See the example yaboot.conf in the 
113
<uri link="/doc/en/handbook/handbook-ppc.xml?part=1&amp;chap=10#doc_chap_pre6">
114
handbook</uri> for details.
115
</note>
116
113
</body>
117
</body>
114
</section>
118
</section>
115
116
<section>
119
<section>
117
<title>
120
<title>
118
  I have an early NewWorld Mac such as the Blue and White G3.  It should be
121
I have an early NewWorld Mac such as the Blue and White G3.  It should be
119
  compatible with the LiveCD, but on boot it returns an "Unknown or corrupt
122
compatible with the LiveCD, but on boot it returns an "Unknown or corrupt
120
  filesystem" error.
123
filesystem" error.
121
</title>
124
</title>
122
<body>
125
<body>
126
123
<p>
127
<p>
124
  As a workaround, boot into Open Firmware by holding down the Apple + Option +
128
As a workaround, boot into Open Firmware by holding down the Apple + Option +
125
  O + F keys on startup.  When the prompt appears, type:
129
O + F keys on startup.  When the prompt appears, type:
126
</p>
130
</p>
131
127
<pre caption="Early NewWorld Mac Open Firmware work around">
132
<pre caption="Early NewWorld Mac Open Firmware work around">
128
<i>boot cd:,\\yaboot</i>
133
<i>boot cd:,\\yaboot</i>
129
</pre>
134
</pre>
135
130
<p>
136
<p>
131
The CD should load as expected afterwards.  Thanks to John Plesmid for this
137
The CD should load as expected afterwards.  Thanks to John Plesmid for this
132
workaround.
138
workaround.
133
</p>
139
</p>
140
134
</body>
141
</body>
135
</section>
142
</section>
136
137
<section>
143
<section>
138
<title>
144
<title>
139
  I have an OldWorld Macintosh and need to use BootX. However, I am
145
I have an OldWorld Macintosh and need to use BootX. However, I am having trouble
140
  having trouble opening the BootX installer archive. What can I do?
146
opening the BootX installer archive. What can I do?
141
</title>
147
</title>
142
<body>
148
<body>
143
149
144
<p>
150
<p>
145
You will need a new version of <e>StuffIt Expander</e> to open the archive. You can <uri link="http://www.stuffit.com/expander/download.html">download it</uri>
151
You will need a new version of <e>StuffIt Expander</e> to open the archive. 
152
You can 
153
<uri link="http://www.stuffit.com/expander/download.html">download it</uri>
146
for free.
154
for free.
147
</p>
155
</p>
148
156
Lines 150-182 Link Here
150
</section>
158
</section>
151
<section>
159
<section>
152
<title>
160
<title>
153
  Is it possible to boot Gentoo Linux on an OldWorld machine without Mac OS? I 
161
Is it possible to boot Gentoo Linux on an OldWorld machine without Mac OS? I 
154
  would like to have a Mac OS-free machine.
162
would like to have a Mac OS-free machine.
155
</title>
163
</title>
156
<body>
164
<body>
157
165
158
<p>
166
<p>
159
If you have a lot of time to experiment, you could try <uri
167
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
168
<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>,
169
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.
170
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
171
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
172
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>
173
</p>
168
174
169
<p>
175
<p>
170
Be sure to read the <uri
176
Be sure to read the <uri
171
link="http://penguinppc.org/projects/quik/quirks.shtml">Quik quirks
177
link="http://penguinppc.org/projects/quik/quirks.shtml">Quik quirks
172
page</uri>. Also see "<uri
178
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
179
"<uri link="http://www.netbsd.org/Ports/macppc/models.html">NetBSD/MacPPC Model
174
Bootloader for Mac OS Dead?</uri>" and "<uri
180
Support</uri>" documents various OpenFirmware versions for various Apple and 
175
link="http://www.imaclinux.net/php/imaclinux_g_h.php3?single=17+index=0">Guide:
181
clone PowerPC machines and is also a helpful reference.
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>
182
</p>
181
183
182
<p>
184
<p>
Lines 187-194 Link Here
187
</section>
189
</section>
188
<section>
190
<section>
189
<title>
191
<title>
190
  I have a Beige G3 machine. Can I install Gentoo Linux/PPC on a
192
I have a Beige G3 machine. Can I install Gentoo Linux/PPC on a second IDE hard 
191
  second IDE hard drive?
193
drive?
192
</title>
194
</title>
193
<body>
195
<body>
194
196
Lines 206-213 Link Here
206
</section>
208
</section>
207
<section>
209
<section>
208
<title>
210
<title>
209
  When I try and install Gentoo on my PowerBook or iBook the internal
211
When I try and install Gentoo on my PowerBook or iBook the internal
210
  hard drive does not show up. What should I do?
212
hard drive does not show up. What should I do?
211
</title>
213
</title>
212
<body>
214
<body>
213
215
Lines 222-248 Link Here
222
</section>
224
</section>
223
<section>
225
<section>
224
<title>
226
<title>
225
  My /etc/fstab file has /dev/BOOT in it.
227
I have a revision A or B iMac.  I've replaced the hard drive with a larger one
226
  Do I need to setup this line for my bootstrap partition?
228
and now I can't boot into anything!
227
</title>
229
</title>
228
<body>
230
<body>
229
231
230
<p>
232
<p>
231
No. If you are not running a separate boot partition
233
There is an 8GB limit for the root partition on these machines.  Ensure that
232
(<path>/boot</path>) then you do not need this line and can safely just
234
your root partition is less than 8GB and it should work as expected.  This also
233
delete it from <path>/etc/fstab</path>.  The bootstrap partition is
235
applies to OS X and later versions of OS 9.
234
<e>not</e> <path>/boot</path> and is not related in anyway. In general,
235
PowerPC machines do not need a separate <path>/boot</path> partition,
236
and the bootstrap partition should not be mounted.
237
</p>
236
</p>
238
237
239
</body>
238
</body>
240
</section>
239
</section>
241
<section>
240
<section>
242
<title>
241
<title>
243
  Installation is now complete. However after rebooting, I am getting
242
My /etc/fstab file has /dev/BOOT in it. Do I need to setup this line for my 
244
  different characters than the keys I press on my machine's keyboard. What
243
bootstrap partition?
245
  should I do?
244
</title>
245
<body>
246
247
<p>
248
No. If you are not running a separate boot partition (<path>/boot</path>) then 
249
you do not need this line and can safely just delete it from 
250
<path>/etc/fstab</path>.  The bootstrap partition is <e>not</e> 
251
<path>/boot</path> and is not related in anyway. In general, PowerPC machines 
252
do not need a separate <path>/boot</path> partition, and the bootstrap partition
253
should not be mounted.
254
</p>
255
256
</body>
257
</section>
258
<section>
259
<title>
260
When I rebooted, yaboot didn't work! Now, I'm stuck. How can I fix this?
261
</title>
262
<body>
263
264
<p>
265
It's probably just a misconfigured yaboot.conf.  The easiest way to fix 
266
this is to boot the LiveCD again, mount your gentoo partition and check 
267
yaboot.conf for errors.  You'll also need to run 
268
<c>ybin -v -C /mnt/gentoo/etc/yaboot.conf</c> to update the boot loader once
269
you have finished.  This can all be done without chrooting back into your
270
install.
271
</p>
272
  
273
<note>
274
If you <e>really</e> just need to get back to OSX, try holding down the
275
Option key on startup.  This should give you a graphical selection of
276
bootable disks.  Chose OSX and remember to fix your boot problems later.
277
</note>
278
279
</body>
280
</section>
281
<section>
282
<title>
283
Installation is now complete. However after rebooting, I am getting
284
different characters than the keys I press on my machine's keyboard. What
285
should I do?
246
</title> 
286
</title> 
247
<body>
287
<body>
248
288
Lines 288-331 Link Here
288
</section>
328
</section>
289
<section>
329
<section>
290
<title>
330
<title>
291
  I only have one mouse-button.  How can I make use of the second and
331
I only have one mouse-button.  How can I make use of the second and third one, 
292
  third one, since ctrl-button does not work?
332
since ctrl-button does not work?
293
</title>
333
</title>
294
<body>
334
<body>
295
335
296
<p>
336
<p>
297
There is no way to get ctrl-button, like on Mac OS X, working.  But
337
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
338
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
339
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
340
console.  Note that this program does not work as expected from X and should 
301
using the proc-device.  First run <c>echo "1" >
341
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
342
settings from the previous section, you will also need to set the mouse button
303
keycodes to <path>mouse_button2_keycode</path> and
343
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>
344
</p>
308
345
309
<pre caption="Mouse button emulation with F11 and F12">
346
<pre caption="Mouse button emulation with F11 and F12">
310
# Enable mouse button emulation
347
<comment># Enable mouse button emulation</comment>
311
dev.mac_hid.mouse_button_emulation = 1
348
dev.mac_hid.mouse_button_emulation = 1
312
# Set 2nd button to 87 - F11
349
<comment># Set 2nd button to 87 - F11</comment>
313
dev.mac_hid.mouse_button2_keycode = 87
350
dev.mac_hid.mouse_button2_keycode = 87
314
# Set 3rd button to 88 - F12
351
<comment># Set 3rd button to 88 - F12</comment>
315
dev.mac_hid.mouse_button3_keycode = 88
352
dev.mac_hid.mouse_button3_keycode = 88
316
</pre>
353
</pre>
317
354
318
<p>
355
<p>
319
Other keys are 100 and 126 for the combinations fn+alt and fn+apple.
356
Other commonly used keycodes are 125 (The Apple key) and 96 (The Keypad Enter).
320
</p>
357
</p>
321
358
359
<note>
360
The easiest way to activate these settings it to reboot after changing them.
361
</note>
362
322
</body>
363
</body>
323
</section>
364
</section>
324
<section>
365
<section>
325
<title>
366
<title>
326
  Installation is now complete. However, after my machine boots into
367
Installation is now complete. However, after my machine boots into
327
  Gentoo and I try to emerge anything, I see errors saying it cannot 'stat'
368
Gentoo and I try to emerge anything, I see errors saying it cannot 'stat'
328
  a file. What is wrong?
369
a file. What is wrong?
329
</title>
370
</title>
330
<body>
371
<body>
331
372
Lines 346-354 Link Here
346
<title>Laptop Support</title>
387
<title>Laptop Support</title>
347
<section>
388
<section>
348
<title>
389
<title>
349
  How do I enable the full processor speed on my PowerBook while running Linux?
390
How do I enable the full processor speed on my PowerBook while running Linux?
350
</title>
391
</title>
351
<body>
392
<body>
393
352
<note>
394
<note>
353
Most (if not all) processors should now work at the correct speed with modern 
395
Most (if not all) processors should now work at the correct speed with modern 
354
kernels.  If you still have this problem, you should upgrade to the latest 
396
kernels.  If you still have this problem, you should upgrade to the latest 
Lines 401-413 Link Here
401
</section>
443
</section>
402
<section>
444
<section>
403
<title>
445
<title>
404
  I'm running Gentoo on a PowerPC laptop. What packages should I
446
I'm running Gentoo on a PowerPC laptop. What packages should I
405
  install to enable laptop-specific functionality?
447
install to enable laptop-specific functionality?
406
</title>
448
</title>
407
<body>
449
<body>
408
450
409
<p>
451
<p>
410
There are three main packages you will need to install.
452
There are four main packages you will need to install.
411
</p>
453
</p>
412
454
413
<ul>
455
<ul>
Lines 429-435 Link Here
429
    and various other preferences.
471
    and various other preferences.
430
  </li>
472
  </li>
431
  <li>
473
  <li>
432
    <e>cpudyn</e> allows cpu speed scaling for longer battery life.
474
    <e>cpudyn</e> allows cpu speed scaling for longer battery life. Other
475
    packages also provide the same functionality, such as <e>powernowd</e>,
476
    <e>cpufreqd</e> and <e>speedfreq</e>.
433
  </li>
477
  </li>
434
</ul>
478
</ul>
435
479
Lines 446-455 Link Here
446
</pre>
490
</pre>
447
491
448
<note>
492
<note>
449
You should edit your <path>/etc/pbbuttonsd.conf</path> to your
493
You should edit <path>/etc/pbbuttonsd.conf</path> to better suit your needs.
450
preference.  Especially the behaviour of the Fx-keys, as pbbuttonsd
494
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
495
options.  To switch the Fx-keys to the OSX behaviour, set KBDMode to fkeyslast.
452
brightness- and sound-keys with the help of Fn.
496
You can turn off touchpad tapping by setting TPMode to notap.  Many other 
497
options are available, see man pbbuttonsd.conf for details.
453
</note>
498
</note>
454
499
455
<p>
500
<p>
Lines 468-484 Link Here
468
<body>
513
<body>
469
514
470
<p>
515
<p>
471
First, make sure you have support for the airport card compiled into
516
Make sure you have support for the airport card compiled into the kernel, or 
472
the kernel, or compiled as a module and loaded. Changing the wireless settings
517
compiled as a module and loaded. Changing the wireless settings is accomplished
473
is accomplished using iwconfig.  This is part of the 
518
using iwconfig.  This is part of the <c>wireless-tools</c> package.
474
<c>wireless-tools</c> package.
475
</p>
519
</p>
476
520
477
<p>
521
<p>
478
As an example of using iwconfig, to set your SSID to home_ssid:
522
As an example of using iwconfig, to set your SSID to home_ssid:
479
</p>
523
</p>
524
480
<pre caption="Setting an SSID">
525
<pre caption="Setting an SSID">
481
# iwconfig wlan0 essid home_ssid
526
# <i>iwconfig wlan0 essid home_ssid</i>
482
</pre>
527
</pre>
483
528
484
<p>
529
<p>
Lines 496-501 Link Here
496
<title>Will the internal modem in an iBook2 or PowerBook work?</title>
541
<title>Will the internal modem in an iBook2 or PowerBook work?</title>
497
<body>
542
<body>
498
543
544
<note>
545
Unless you have purchased a key from Linuxant, this driver will only work at
546
14.4 and will not support FAX.
547
</note>
548
499
<p>
549
<p>
500
Emerge <c>net-dialin/hcfusbmodem</c> which will provide
550
Emerge <c>net-dialin/hcfusbmodem</c> which will provide
501
<path>/dev/ttySHCF0</path>.  Then set up ppp like usual.  Further
551
<path>/dev/ttySHCF0</path>.  Then set up ppp like usual.  Further
Lines 508-520 Link Here
508
<section>
558
<section>
509
<title>Does sleep work on my iBook/PowerBook?</title>
559
<title>Does sleep work on my iBook/PowerBook?</title>
510
<body>
560
<body>
561
511
<p>
562
<p>
512
Sleep (suspend to ram) works very well on all G3 iBooks and TiBooks.  Recently,
563
Sleep (suspend to ram) works very well on all G3 iBooks and TiBooks.  Recently,
513
a kernel patch has been released that adds sleep support for G4 iBooks and 
564
a kernel patch has been released that adds sleep support for G4 iBooks and 
514
Radeon based AlBooks.  If you have one of these laptops, please see this forum
565
Radeon based AlBooks.  If you have one of these laptops, use 
515
thread for more details: <uri>http://forums.gentoo.org/viewtopic.php?t=254232</uri>.  Additionally, this patch is included with gentoo-sources-2.6.11 and will
566
vanilla-sources-2.6.12 or gentoo-sources 2.6.11 for built in support.
516
be included with vanilla-sources-2.6.12.
517
</p>
567
</p>
568
518
<note>
569
<note>
519
Note that the 12" PowerBook is not yet supported due to its nVidia chipset.
570
Note that the 12" PowerBook is not yet supported due to its nVidia chipset.
520
</note>
571
</note>
Lines 526-594 Link Here
526
<chapter>
577
<chapter>
527
<title>Applications</title>
578
<title>Applications</title>
528
<section>
579
<section>
529
<title>I can't emerge a package, and get an error about it being masked.  What should I do?</title>
580
<title>
581
I can't emerge a package, and get an error about it being masked.  What should I
582
do?
583
</title>
530
<body>
584
<body>
585
531
<p>
586
<p>
532
There are two common reasons why a package will not emerge: either it hasn't
587
There are two common reasons why a package will not emerge: either it hasn't
533
been tested on PPC or it has been tested, but hasn't yet been marked stable.
588
been tested on PPC or it has been tested, but hasn't yet been marked stable.
534
</p>
589
</p>
590
535
<p>
591
<p>
536
If your package hasn't yet been tested on PPC, youll need to first mark the
592
If your package hasn't yet been tested on PPC, youll need to first mark the
537
ebuild with the ppc keyword.  This is done using the ekeyword tool which is 
593
ebuild with the ppc keyword.  This is done using the ekeyword tool which is 
538
part of the gentoolkit-dev package.  To mark the ebuild ppc:
594
part of the gentoolkit-dev package.  To mark the ebuild ppc:
539
</p>
595
</p>
596
540
<pre caption="Adding the ppc keyword to app-foo/bar">
597
<pre caption="Adding the ppc keyword to app-foo/bar">
541
        ekeyword ppc /usr/portage/app-foo/bar/bar-1.0.ebuild
598
$ <i>ekeyword ppc /usr/portage/app-foo/bar/bar-1.0.ebuild</i>
542
</pre>
599
</pre>
600
543
<p>
601
<p>
544
Once the ebuild has been keyworded, you can now emerge it as usual.  Test the
602
Once the ebuild has been keyworded, you can now emerge it as usual.  Test the
545
application and if it works, <b>please</b> report it as a bug so one of the 
603
application and if it works, <b>please</b> report it as a bug so one of the 
546
developers can add the keyword.
604
developers can add the keyword.
547
</p>
605
</p>
606
548
<note>
607
<note>
549
This change will only last until the next sync.  If you need a more permanant 
608
This change will only last until the next sync.  If you need a more permanant 
550
fix, you can maintain a portage overlay.  See the portage documentation for 
609
fix, you can maintain a portage overlay.  See the portage documentation for 
551
more information.
610
more information.
552
</note>
611
</note>
612
553
<p>
613
<p>
554
If your package already has the ~ppc keyword, you have two options.  Either
614
If your package already has the ~ppc keyword, you have two options.  Either
555
follow the above instructions and replace the ~ppc keyword with ppc, or you can
615
follow the above instructions and replace the ~ppc keyword with ppc, or you can
556
use /etc/portage to unmask the specific package.
616
use /etc/portage to unmask the specific package.
557
</p>
617
</p>
618
558
<pre caption="Using /etc/portage to unmask app-foo/bar">
619
<pre caption="Using /etc/portage to unmask app-foo/bar">
559
        echo "=app-foo/bar-1.0 ~ppc" > /etc/portage/package.keywords
620
$ <i>echo "=app-foo/bar-1.0 ~ppc" > /etc/portage/package.keywords</i>
560
</pre>
621
</pre>
622
561
<note>
623
<note>
562
If the /etc/portage directory does not exist, make sure to create it first.
624
If the /etc/portage directory does not exist, make sure to create it first.
563
</note>
625
</note>
626
564
<p>
627
<p>
565
Now emerge the package as normal.  Once you're sure the app is stable, <b>please
628
Now emerge the package as normal.  Once you're sure the app is stable, <b>please
566
</b> report this as a bug so the developers can add the keyword.
629
</b> report this as a bug so the developers can add the keyword.
567
</p>
630
</p>
631
568
</body>
632
</body>
569
</section>
633
</section>
570
<section>
634
<section>
571
<title>Does Gentoo/PPC have support for Flash?</title>
635
<title>Does Gentoo/PPC have support for Flash?</title>
572
<body>
636
<body>
637
573
<p>
638
<p>
574
No, Macromedia has not supplied a linux/ppc binary and until Macromedia opens
639
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 
640
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
641
this problem are <uri link="http://gplflash.sf.net">gplflash2</uri> and 
577
6 stand alone player.  This is described here: 
642
<uri link="http://swfdec.sf.net">swfdec</uri>, so check there for more 
643
information. A possible workaround for now is to use qemu (an x86 emulator)
644
to run the Macromedia Flash Player 6 stand alone player.  This process was
645
described on the forums: 
578
<uri>http://forums.gentoo.org/viewtopic.php?t=117774</uri>
646
<uri>http://forums.gentoo.org/viewtopic.php?t=117774</uri>
579
</p>
647
</p>
648
580
</body>
649
</body>
581
</section>
650
</section>
582
<section>
651
<section>
583
<title>Does Gentoo/PPC have a java plugin?</title>
652
<title>Does Gentoo/PPC have a Java plugin?</title>
584
<body>
653
<body>
654
585
<p>
655
<p>
586
No, not at this time.  The older java plugin is no longer compatible with the
656
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.
657
new Mozilla plugin system and a new plugin has not yet been written.
588
</p>
658
</p>
659
589
</body>
660
</body>
590
</section>
661
</section>
591
592
<section>
662
<section>
593
<title>Is there an easy way to configure X?</title>
663
<title>Is there an easy way to configure X?</title>
594
<body>
664
<body>
Lines 602-608 Link Here
602
</body>
672
</body>
603
</section>
673
</section>
604
<section>
674
<section>
605
<title>How can I enable Direct Rendering (DRM) on rage128 or radeon cards?</title>
675
<title>
676
How can I enable Direct Rendering (DRM) on rage128 or radeon cards?
677
</title>
606
<body>
678
<body>
607
679
608
<p>
680
<p>
Lines 633-653 Link Here
633
ati or your specific driver (r128 or radeon).  Also check that the
705
ati or your specific driver (r128 or radeon).  Also check that the
634
DRI extension is loaded and not commented out.
706
DRI extension is loaded and not commented out.
635
</impo>
707
</impo>
708
636
<note>
709
<note>
637
There currently isn't any DRI support for the R300/R400 chipsets, a
710
There currently isn't any DRI support for the R300/R400 chipsets, a project has
638
project has been started at <uri>http://r300.sourceforge.net</uri>.
711
been started at <uri>http://r300.sourceforge.net</uri>. nVidia chipsets are also
639
nVidia chipsets are also mostly unsupported on PPC, there is basic
712
mostly unsupported on PPC, there is basic 2D acceleration provied by the nv 
640
support provided by the nv driver, but no 3D acceleration.
713
driver, but no 3D acceleration.
641
</note>
714
</note>
715
642
</body>
716
</body>
643
</section>
717
</section>
644
<section>
718
<section>
645
<title>
719
<title>
646
  I recently emerged Xorg, but when using it, my international
720
I recently emerged Xorg, but when using it, my international
647
  keyboard layout does not work correctly. The main keys work fine but I am
721
keyboard layout does not work correctly. The main keys work fine but I am
648
  unable to compose special characters like the "at" sign. The startx output
722
unable to compose special characters like the "at" sign. The startx output
649
  says something like "could not load keymap, falling back to default
723
says something like "could not load keymap, falling back to default
650
  keymap". What is wrong?
724
keymap". What is wrong?
651
</title>
725
</title>
652
<body>
726
<body>
653
727
Lines 661-668 Link Here
661
</section>
735
</section>
662
<section>
736
<section>
663
<title>
737
<title>
664
  When using OpenGL DRI or playing movies, the system sometimes freezes hard 
738
When using OpenGL DRI or playing movies, the system sometimes freezes hard 
665
  unexpectedly. What can I do?
739
unexpectedly. What can I do?
666
</title>
740
</title>
667
<body>
741
<body>
668
742
Lines 681-686 Link Here
681
extensions included with the newer X.org releases.  Please disable
755
extensions included with the newer X.org releases.  Please disable
682
these extensions if you're having problems. 
756
these extensions if you're having problems. 
683
</p>
757
</p>
758
684
</body>
759
</body>
685
</section>
760
</section>
686
<section>
761
<section>
Lines 688-698 Link Here
688
<body>
763
<body>
689
764
690
<p>
765
<p>
691
There are two approaches to sound on modern kernels either OSS or ALSA.  OSS 
766
There are two approaches to sound on modern kernels: OSS or ALSA.  OSS is the 
692
is the older of the two options and has been depreciated, but still functions
767
older of the two options and has been depreciated, but still functions well for
693
well for many older Macs.  ALSA is the newer method and will continue to be 
768
many older Macs.  ALSA is the newer method and will continue to be supported in 
694
supported in the future.  We recommend that you use ALSA unless you have
769
the future.  We recommend that you use ALSA unless you have problems.
695
problems.
696
</p>
770
</p>
697
771
698
<note>
772
<note>
Lines 714-728 Link Here
714
</p>
788
</p>
715
789
716
<note>
790
<note>
717
At this time, there is no support for the sound card provided with the G5.
791
If you are using a G5 or a mac-mini, you should follow the Gentoo ALSA
718
The Mac Mini is only supported with a hack.  See <uri link="http://forums.gentoo.org/viewtopic-t-297244.html">this</uri> forum thread for more details on sound
792
configuration guide to install the latest version of the ALSA drivers instead of
719
on the Mac Mini.
793
the versions supplied by the kernel.
720
</note>
794
</note>
795
721
</body>
796
</body>
722
</section>
797
</section>
723
<section>
798
<section>
724
<title>Sound setup with ALSA</title>
799
<title>Sound setup with ALSA</title>
725
<body>
800
<body>
801
726
<p>
802
<p>
727
For ALSA, we'll set up both the regular ALSA drivers and the OSS emulation
803
For ALSA, we'll set up both the regular ALSA drivers and the OSS emulation
728
layer so that we can still use legacy OSS only programs.  In <c>make 
804
layer so that we can still use legacy OSS only programs.  In <c>make 
Lines 733-739 Link Here
733
Device Drivers - Sound ---&gt;
809
Device Drivers - Sound ---&gt;
734
&lt;*&gt; Sound card support
810
&lt;*&gt; Sound card support
735
    Advanced Linux Sound Architecture ---&gt;
811
    Advanced Linux Sound Architecture ---&gt;
736
    &lt;*&gt;   PowerMac DMA sound support
812
    &lt;&nbsp;&gt;   PowerMac DMA sound support
737
      &lt;*&gt; Advanced Linux Sound Architecture
813
      &lt;*&gt; Advanced Linux Sound Architecture
738
      &lt;*&gt; Sequencer support
814
      &lt;*&gt; Sequencer support
739
      &lt;*&gt; Sequencer dummy client
815
      &lt;*&gt; Sequencer dummy client
Lines 755-764 Link Here
755
831
756
</body>
832
</body>
757
</section>
833
</section>
758
759
<section>
834
<section>
760
<title>Sound setup with OSS</title>
835
<title>Sound setup with OSS</title>
761
<body>
836
<body>
837
838
<note>Again, only use this if you're not using ALSA.</note>
839
762
<p>
840
<p>
763
In <c>make menuconfig</c> you'll need to select:
841
In <c>make menuconfig</c> you'll need to select:
764
</p>
842
</p>
Lines 841-864 Link Here
841
</body>
919
</body>
842
</section>
920
</section>
843
<section>
921
<section>
844
<title>Can I run Mac OS or Mac OS X under Gentoo Linux?</title>
922
<title>Can I run Mac OS 9 or Mac OS X under Gentoo Linux?</title>
845
<body>
923
<body>
846
924
847
<p>
925
<p>
848
Yes, as long as your are running Gentoo Linux/PPC on Apple hardware
926
Yes, as long as your are running Gentoo Linux on PPC hardware, you can use <uri
849
(or a Mac-clone). You will need to run <uri
927
link="http://www.maconlinux.org/">Mac-on-Linux</uri> which allows you to run an
850
link="http://www.maconlinux.org/">Mac-on-Linux</uri>. Just <c>emerge
928
instance of OS 9, OS X or Linux as a process on Linux. Simply <c>emerge mol</c>
851
mol</c>. MOL support Mac OS 7.5.2 to 9.2.2, as well as any version of OS X.
929
to install this package. MOL supports Mac OS 7.5.2 to 9.2.2, as well as any 
852
It can take over your full screen, or run in a window.
930
version OS X except Tiger (support is currently in progress). It can be run from
931
a console framebuffer or run in a window on X.
853
</p>
932
</p>
854
933
855
<note>
934
<note>
856
To run MOL fullscreen, you'll need to compile MOL with the fbcon use flag 
935
To run MOL fullscreen, you'll need to compile MOL with the fbcon use flag 
857
enabled.
936
enabled and run it in a console framebuffer.
858
</note>
937
</note>
859
938
860
<p>
939
<p>
861
For networking and sound you might install the drivers in the folder
940
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
941
<path>MOL-Install</path> on your Mac OS X-Desktop.  If errors with
863
networking occur, make sure you have the following kernel options
942
networking occur, make sure you have the following kernel options
864
enabled:
943
enabled:
Lines 891-920 Link Here
891
<section>
970
<section>
892
<title>Can I access my ext2/ext3 partitions from OSX?</title>
971
<title>Can I access my ext2/ext3 partitions from OSX?</title>
893
<body>
972
<body>
973
894
<p>
974
<p>
895
OSX can support the reading and writing of ext2/ext3 partitions by using the 
975
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>
976
kernel extension provided by the <uri link="http://sourceforge.net/projects/ext2fsx">ext2fsx project.</uri>
897
</p>
977
</p>
978
898
<note>
979
<note>
899
When using MOL, you cannot access a partition that is currently being used by
980
When using MOL, you cannot access a partition that is currently being used by
900
Linux.
981
Linux.
901
</note>
982
</note>
983
902
</body>
984
</body>
903
</section>
985
</section>
904
<section>
986
<section>
905
<title>Which Portage USE flags do not work on PowerPC machines?</title>
987
<title>Which Portage USE flags do not work on PowerPC machines?</title>
906
<body>
988
<body>
989
907
<p>
990
<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.
991
If you're using an old flat profile, (depreciated, pre 2005.0) look at 
992
<path>/etc/make.profile/use.mask</path> for a list.
909
</p>
993
</p>
994
910
<p>
995
<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.
996
If you're using a cascaded profile, (2005.0 and onwards) look at 
997
<path>/usr/portage/profiles/default-linux/ppc/use.mask</path> for a list.
912
</p>
998
</p>
999
913
</body>
1000
</body>
914
</section>
1001
</section>
915
<section>
1002
<section>
916
<title>How can I set up distcc with my x86 box?</title>
1003
<title>How can I set up distcc with my x86 box?</title>
917
<body>
1004
<body>
1005
918
<p>
1006
<p>
919
If you've got another faster computer, you can set up distcc to compile binaries
1007
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
1008
for your slower ppc processor.  It's better to do as much building as possible
Lines 923-933 Link Here
923
<uri>http://dev.gentoo.org/~vapier/CROSS-COMPILE-HOWTO</uri>
1011
<uri>http://dev.gentoo.org/~vapier/CROSS-COMPILE-HOWTO</uri>
924
<uri>http://www.sable.mcgill.ca/~dbelan2/crossdev/crossdev-powerpc-i686.html</uri>
1012
<uri>http://www.sable.mcgill.ca/~dbelan2/crossdev/crossdev-powerpc-i686.html</uri>
925
</p>
1013
</p>
1014
926
</body>
1015
</body>
927
</section>
1016
</section>
928
<section>
1017
<section>
929
<title>Why does gcc keep segfaulting during ebuilds?</title>
1018
<title>Why does gcc keep segfaulting during ebuilds?</title>
930
<body>
1019
<body>
1020
931
<p>
1021
<p>
932
If gcc segfaults during ebuilds, this probably isn't a bug with gcc and isn't
1022
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
1023
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">
1030
<pre caption="Check if preempt is enabled">
941
$ <i>grep PREEMPT /usr/src/linux/.config</i>
1031
$ <i>grep PREEMPT /usr/src/linux/.config</i>
942
</pre>
1032
</pre>
1033
943
<p>
1034
<p>
944
If returns: "# CONFIG_PREEMPT is not set", then you should report the 
1035
If returns: "# CONFIG_PREEMPT is not set", then you should report the 
945
segfault as a bug.
1036
segfault as a bug.
946
</p>
1037
</p>
1038
947
<p>
1039
<p>
948
If it returns: "CONFIG_PREEMPT=y", then you'll need to disable it and rebuild
1040
If it returns: "CONFIG_PREEMPT=y", then you'll need to disable it and rebuild
949
your kernel.
1041
your kernel.
Lines 968-974 Link Here
968
1060
969
</body>
1061
</body>
970
</section>
1062
</section>
971
972
<section>
1063
<section>
973
<title>This FAQ hasn't answered my question. What do I do now?</title>
1064
<title>This FAQ hasn't answered my question. What do I do now?</title>
974
<body>
1065
<body>

Return to bug 95800