Gentoo Archives: gentoo-doc-cvs

From: Joseph Jezak <josejx@×××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: gentoo-ppc-faq.xml
Date: Sat, 18 Feb 2006 18:09:06
Message-Id: 200602181808.k1II8lOs025847@robin.gentoo.org
1 josejx 06/02/18 18:08:46
2
3 Modified: xml/htdocs/doc/en gentoo-ppc-faq.xml
4 Log:
5 PPC FAQ Update.
6
7 Revision Changes Path
8 1.46 +210 -89 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.46&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.46&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.45&r2=1.46&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.45
18 retrieving revision 1.46
19 diff -u -r1.45 -r1.46
20 --- gentoo-ppc-faq.xml 4 Jan 2006 22:51:33 -0000 1.45
21 +++ gentoo-ppc-faq.xml 18 Feb 2006 18:08:45 -0000 1.46
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.45 2006/01/04 22:51:33 josejx Exp $ -->
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-ppc-faq.xml,v 1.46 2006/02/18 18:08:45 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.24</version>
35 -<date>2006-01-04</date>
36 +<version>1.25</version>
37 +<date>2006-02-18</date>
38
39 <chapter>
40 <title>Questions</title>
41 @@ -51,6 +51,12 @@
42
43 <ul>
44 <li>
45 + <uri link="#powerpc">
46 + What kind of PPC computer do I have and where can I find more information
47 + about it?
48 + </uri>
49 + </li>
50 + <li>
51 <uri link="#osxverify">How can I verify with OSX that the downloaded ISO
52 is not corrupted?</uri>
53 </li>
54 @@ -123,9 +129,7 @@
55 </uri>
56 </li>
57 <li>
58 - <uri link="#modem">
59 - Will the internal modem in an work?
60 - </uri>
61 + <uri link="#modem">Will the internal modem work?</uri>
62 </li>
63 <li>
64 <uri link="#sleep">Does sleep work on my iBook/PowerBook?</uri>
65 @@ -168,11 +172,17 @@
66 <uri link="#java">Does Gentoo/PPC have a Java plugin?</uri>
67 </li>
68 <li>
69 - <uri link="#xconf">Is there an easy way to configure X?</uri>
70 + <uri link="#xorg">
71 + Is there an easy way to configure X?
72 + </uri>
73 + </li>
74 + <li>
75 + <uri link="#drm">How do I configure DRM and OpenGL acceleration?</uri>
76 </li>
77 <li>
78 - <uri link="#drm">
79 - How can I enable Direct Rendering (DRM) on rage128 or radeon cards?
80 + <uri link="#glfreeze">
81 + When using OpenGL DRI or playing movies, the system sometimes locks up
82 + unexpectedly. What can I do?
83 </uri>
84 </li>
85 <li>
86 @@ -185,16 +195,10 @@
87 </uri>
88 </li>
89 <li>
90 - <uri link="#glfreeze">
91 - When using OpenGL DRI or playing movies, the system sometimes locks up
92 - unexpectedly. What can I do?
93 - </uri>
94 - </li>
95 - <li>
96 <uri link="#audiocd">How do I play Audio CDs?</uri>
97 </li>
98 <li>
99 - <uri link="#mol">Can I run Mac OS 9 or Mac OS X under Gentoo Linux?</uri>
100 + <uri link="#mol">Can I run Mac OS 9 or Mac OS X while running Linux?</uri>
101 </li>
102 <li>
103 <uri link="#ext">Can I access my ext2/ext3 partitions from OSX?</uri>
104 @@ -237,6 +241,52 @@
105
106 <chapter>
107 <title>Installation</title>
108 +<section id="powerpc">
109 +<title>
110 +What kind of PowerPC computer do I have and where can I find more information
111 +about it?
112 +</title>
113 +<body>
114 +
115 +<p>
116 +Welcome to Gentoo PPC! The PowerPC processor has been used in a number of
117 +popular computing devices, here are some links to help you figure out what
118 +type of hardware is in the machine on your desk.
119 +</p>
120 +
121 +<ul>
122 + <li>
123 + <uri link="http://www.info.apple.com/support/applespec.html">
124 + Apple Product Pages
125 + </uri>
126 + </li>
127 + <li>
128 + <uri link="http://lowendmac.com/profiles.htm">
129 + Apple Product History and Details
130 + </uri>
131 + </li>
132 + <li>
133 + <uri link="http://www.pegasosppc.com/products.php">
134 + Genesi Model Information
135 + </uri>
136 + </li>
137 + <li>
138 + <uri link="http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.pseries.doc/hardware_docs/selectbysystem.htm">
139 + IBM Documentation by Model
140 + </uri>
141 + </li>
142 + <li>
143 + <uri link="http://kurobox.com/">KuroBox</uri>
144 + </li>
145 + <li>
146 + <uri link="http://penguinppc.org/">
147 + PenguinPPC - Linux on PowerPC Information
148 + </uri>
149 + </li>
150 +</ul>
151 +
152 +</body>
153 +</section>
154 <section id="osxverify">
155 <title>How can I verify with OSX that the downloaded ISO is not corrupted?</title>
156 <body>
157 @@ -275,7 +325,7 @@
158 Yes you can! In fact, <e>yabootconfig</e> will automatically detect and setup
159 <path>/etc/yaboot.conf</path> with Linux, Mac OS X and even classic Mac OS (see
160 the <uri link="/doc/en/handbook/handbook-ppc.xml?part=1&amp;chap=10">Gentoo
161 -Handbook </uri> for details on yabootconfig). The trick is in how you partition
162 +Handbook</uri> for details on yabootconfig). The trick is in how you partition
163 your hard drive. Before installing Gentoo, startup with the Mac OS X Install
164 CD. Use the <c>Disk Utility</c> to partition the drive in your machine into two
165 or three partitions. Alternatively, use <c>parted</c> from a recent Gentoo
166 @@ -387,17 +437,17 @@
167 <section id="fstabboot">
168 <title>
169 My /etc/fstab file has /dev/BOOT in it. Do I need to setup this line for my
170 -bootstrap partition?
171 +Apple bootstrap partition?
172 </title>
173 <body>
174
175 <p>
176 -No. If you are not running a separate boot partition (<path>/boot</path>) then
177 +No. If you are not using a separate boot partition (<path>/boot</path>) then
178 you do not need this line and can safely just delete it from
179 -<path>/etc/fstab</path>. The bootstrap partition is <e>not</e>
180 -<path>/boot</path> and is not related in anyway. In general, PowerPC machines
181 -do not need a separate <path>/boot</path> partition, and the bootstrap
182 -partition should not be mounted.
183 +<path>/etc/fstab</path>. The Apple bootstrap partition is <e>not</e>
184 +<path>/boot</path> and is not related in any way. In general, Apple PowerPC
185 +machines do not need a separate <path>/boot</path> partition, and the bootstrap
186 +partition should not be mounted or referred to in your fstab.
187 </p>
188
189 </body>
190 @@ -442,23 +492,25 @@
191 <ul>
192 <li>
193 <e>pbbuttonsd</e> is a tool that enables the brightness and volume keys on
194 - most ppc laptops. The current versions also work as a powermanager.
195 + most ppc laptops as well as other apple laptop specific functionality. The
196 + current versions also work as a power manager and replace <e>pmud</e>.
197 </li>
198 <li>
199 - <e>gtkpbbuttons</e> gives you a gtk front end for pbbuttonsd (visual
200 + <e>gtkpbbuttons</e> provides a gtk frontend for pbbuttonsd (visual
201 feedback on button presses in X). <e>gtkpbbuttons</e> requires gtk and
202 - should be added to your X session file (<path>~/.Xsession</path>) for best
203 - results (so that it is always running while in X).
204 + should be started when X is started.
205 </li>
206 <li>
207 - <e>powerprefs</e> ties together with pbbuttonsd, and gives you the ability
208 - to edit settings such as power-management, trackpad options and various
209 - other preferences.
210 + <e>powerprefs</e> provides a graphical configuration editing tool for
211 + configuring pbbuttonsd including settings such as power-management, trackpad
212 + options and various other preferences.
213 </li>
214 <li>
215 <e>powernowd</e> allows cpu speed scaling for longer battery life. Other
216 packages also provide the same functionality, such as <e>cpudyn</e>,
217 - <e>cpufreqd</e> and <e>speedfreq</e>.
218 + <e>cpufreqd</e> and <e>speedfreq</e>. It doesn't really matter which you
219 + chose, just ensure that you have the <e>userspace</e> cpu frequency
220 + scaling governor enabled in your kernel.
221 </li>
222 </ul>
223
224 @@ -475,16 +527,16 @@
225 </pre>
226
227 <note>
228 -You should edit <path>/etc/pbbuttonsd.conf</path> to better suit your needs.
229 -The behaviour of the Fx-keys can be controlled here as well as many sleep
230 -options. To switch the Fx-keys to the OSX behaviour, set KBDMode to fkeyslast.
231 -You can turn off touchpad tapping by setting TPMode to notap. Many other
232 -options are available, see man pbbuttonsd.conf for details.
233 +You should edit <path>/etc/pbbuttonsd.conf</path> or use <e>powerprefs</e> to
234 +better suit your needs. The behaviour of the Fx-keys can be controlled here as
235 +well as many sleep options. To switch the Fx-keys to the OSX behaviour, set
236 +KBDMode to fkeyslast. You can turn off touchpad tapping by setting TPMode to
237 +notap. Many other options are available, see man pbbuttonsd.conf for details.
238 </note>
239
240 <p>
241 -It is useful to add pbbuttonsd and powernowd to your boot runlevel so that they're
242 -started when your computer starts. To do this:
243 +It is useful to add pbbuttonsd and powernowd to your boot runlevel so that
244 +they're started when your computer starts. To do this:
245 </p>
246
247 <pre caption="Adding pbbuttonsd and cpudyn to the boot runlevel">
248 @@ -549,8 +601,8 @@
249 <body>
250
251 <p>
252 -The Airport card is based on the Lucent Orinoco chipset. To use this card in
253 -Linux, enable these kernel options:
254 +The Airport card is an 802.11b device based on the Lucent Orinoco chipset. To
255 +use this card in Linux, enable these kernel options:
256 </p>
257
258 <pre caption="Wireless LAN">
259 @@ -574,7 +626,8 @@
260 </pre>
261
262 <p>
263 -For more details on iwconfig, refer to its man page.
264 +For a generic guide to setting up wireless with Gentoo, please see the
265 +<uri link="http://www.gentoo.org/doc/en/handbook/handbook-ppc.xml?part=4&amp;chap=4">Gentoo Wireless Guide</uri>.
266 </p>
267
268 </body>
269 @@ -584,17 +637,26 @@
270 <body>
271
272 <p>
273 -With the release of the native <uri link="http://bcm43xx.berlios.de">bcm43xx
274 -driver</uri>, using the Airport Extreme in Linux is now possible! Until the
275 -driver is added to the kernel, please see this
276 +The Airport Extreme is an 802.11b/g card that is included with modern Apple
277 +portable computers. It is based on the Broadcom 43xx chipset which is supported
278 +by the native <uri link="http://bcm43xx.berlios.de">bcm43xx driver</uri>
279 +project. Until this driver is added to the kernel, you can use the ebuild in
280 +portage.
281 +</p>
282 +
283 +<pre caption="Emerge the bcm43xx driver">
284 +# <i>emerge bcm43xx</i>
285 +</pre>
286 +
287 +<p>
288 +For additional information, please see this
289 <uri link="http://forums.gentoo.org/viewtopic-t-409194.html">forum post</uri>
290 for details.
291 </p>
292
293 <p>
294 -You can also use MOL and OSX to give Linux access to your Airport Extreme card,
295 -please see this <uri link="http://forums.gentoo.org/viewtopic-t-365647.html">
296 -forum post</uri> for details.
297 +For a generic guide to setting up wireless with Gentoo, please see the
298 +<uri link="http://www.gentoo.org/doc/en/handbook/handbook-ppc.xml?part=4&amp;chap=4">Gentoo Wireless Guide</uri>.
299 </p>
300
301 </body>
302 @@ -678,6 +740,11 @@
303 your kernel.
304 </note>
305
306 +<impo>
307 +If you compile in ALSA support, you need to also compile in i2c Keywest support.
308 +Failure to do this will result in kernel panics on boot!
309 +</impo>
310 +
311 </body>
312 </section>
313 <section id="alsa">
314 @@ -791,14 +858,22 @@
315 been tested on PPC or it has been tested, but hasn't yet been marked stable.
316 </p>
317
318 +<pre caption="The Package Hasn't Been Tested on PPC">
319 +!!! All ebuilds that could satisfy "bar" have been masked.
320 +!!! One of the following masked packages is required to complete your request:
321 +- app-foo/bar-1.0 (masked by: missing keyword)
322 +</pre>
323 +
324 <p>
325 If your package hasn't yet been tested on PPC, you'll need to first mark the
326 ebuild with the ppc keyword. This is done using the ekeyword tool which is part
327 -of the gentoolkit-dev package. To mark the ebuild ppc:
328 +of the gentoolkit-dev package. To mark the ebuild ppc and re-digest it to
329 +reflect the changes:
330 </p>
331
332 <pre caption="Adding the ppc keyword to app-foo/bar">
333 -$ <i>ekeyword ppc /usr/portage/app-foo/bar/bar-1.0.ebuild</i>
334 +# <i>ekeyword ppc /usr/portage/app-foo/bar/bar-1.0.ebuild</i>
335 +# <i>ebuild /usr/portage/app-foo/bar/bar-1.0.ebuild digest</i>
336 </pre>
337
338 <p>
339 @@ -810,13 +885,20 @@
340 <note>
341 This change will only last until the next sync. If you need a more permanent
342 fix, you can maintain a portage overlay. See the portage documentation for more
343 -information.
344 +information on maintaining an overlay.
345 </note>
346
347 +<pre caption="The Package Hasn't Been Marked Stable on PPC">
348 +!!! All ebuilds that could satisfy "bar" have been masked.
349 +!!! One of the following masked packages is required to complete your request:
350 +- app-foo/bar-1.0 (masked by: ~ppc keyword)
351 +</pre>
352 +
353 <p>
354 If your package already has the ~ppc keyword, you have two options. Either
355 follow the above instructions and replace the ~ppc keyword with ppc, or you can
356 -use /etc/portage to unmask the specific package.
357 +use /etc/portage to unmask the specific package. The second option is
358 +preferred simply because it won't be undone by an emerge sync.
359 </p>
360
361 <pre caption="Using /etc/portage to unmask app-foo/bar">
362 @@ -828,8 +910,8 @@
363 </note>
364
365 <p>
366 -Now emerge the package as normal. Once you're sure the app is stable, <b>please
367 -</b> report this as a bug so the developers can add the keyword.
368 +Now emerge the package as normal. Once you're sure the app is stable, i
369 +<b>please</b> report this as a bug so the developers can add the keyword.
370 </p>
371
372 </body>
373 @@ -840,14 +922,26 @@
374
375 <p>
376 Well, not really. Macromedia has not supplied a linux/ppc binary and open
377 -source implementations are incomplete and buggy at this time. Two projects that
378 -are working on this problem are <uri
379 -link="http://gplflash.sf.net">gplflash2</uri> and <uri
380 -link="http://swfdec.sf.net">swfdec</uri>, so check with these projects for more
381 -information. A possible workaround for now is to use qemu (an x86 emulator) to
382 -run the Macromedia Flash Player 6 stand alone player. This process was
383 -described on the forums:
384 -<uri>http://forums.gentoo.org/viewtopic.php?t=117774</uri>
385 +source implementations are incomplete and buggy at this time. Three projects
386 +that are working on this problem are:
387 +</p>
388 +
389 +<ul>
390 + <li>
391 + <uri link="http://www.gnu.org/software/gnash/">gnash</uri>
392 + </li>
393 + <li>
394 + <uri link="http://gplflash.sf.net">gplflash2</uri>
395 + </li>
396 + <li>
397 + <uri link="http://swfdec.sf.net">swfdec</uri>
398 + </li>
399 +</ul>
400 +
401 +<p>
402 +Another possible workaround for now is to use qemu (an x86 emulator) to run the
403 +Macromedia Flash Player 6 stand alone player. This process was described in the
404 +forums: <uri>http://forums.gentoo.org/viewtopic.php?t=117774</uri>
405 </p>
406
407 </body>
408 @@ -857,12 +951,13 @@
409 <body>
410
411 <p>
412 -Yes, a Java plugin is now available with IBM's Java 1.5 beta.
413 +Yes, a Java plugin is now available with IBM's Java 1.5. Note that not all
414 +Java applications work with Java 1.5 yet.
415 </p>
416
417 </body>
418 </section>
419 -<section id="xconf">
420 +<section id="xorg">
421 <title>Is there an easy way to configure X?</title>
422 <body>
423
424 @@ -877,30 +972,46 @@
425 </body>
426 </section>
427 <section id="drm">
428 -<title>
429 -How can I enable Direct Rendering (DRM) on rage128 or radeon cards?
430 -</title>
431 +<title>What kernel options are required for DRM?</title>
432 <body>
433
434 <p>
435 Make sure in your kernel config you have the following options set:
436 </p>
437
438 -<pre caption="DRM kernel configuration">
439 +<pre caption="Rage128 DRM kernel configuration">
440 Device Drivers - Character devices ---&gt;
441 &lt;*&gt; /dev/agpgart (AGP Support)
442 [*] Apple UniNorth support
443 [*] Direct Rendering Manager (DRI support)
444 &lt;*&gt; ATI Rage 128
445 - &lt;*&gt; ATI Radeon
446 Device Drivers - Graphics Support ---&gt;
447 &lt;*&gt; ATI Rage 128 display support
448 +</pre>
449 +
450 +<pre caption="Radeon DRM kernel configuration">
451 +Device Drivers - Character devices ---&gt;
452 + &lt;*&gt; /dev/agpgart (AGP Support)
453 + [*] Apple UniNorth support
454 + [*] Direct Rendering Manager (DRI support)
455 + &lt;*&gt; ATI Radeon
456 +Device Drivers - Graphics Support ---&gt;
457 &lt;*&gt; ATI Radeon display support
458 </pre>
459
460 +<pre caption="nVidia kernel configuration">
461 +Device Drivers - Graphics Support ---&gt;
462 + &lt;*&gt; nVidia Framebuffer Support
463 +</pre>
464 +
465 +<note>
466 +There is currently no support for DRM on nVidia cards since nVidia has not
467 +released any drivers for PPC and there are no open drivers for 3D acceleration.
468 +</note>
469 +
470 <p>
471 Rebuild and install the kernel if necessary. After this, make sure you
472 -have booted to the native framebuffer (i.e. radeonfb or atyfb and
473 +have booted to the native framebuffer (i.e. radeonfb or atyfb128 and
474 <e>not</e> from offb or ofonly video), and run <c>Xorgautoconfig</c>.
475 </p>
476
477 @@ -922,23 +1033,6 @@
478
479 </body>
480 </section>
481 -<section id="keymap">
482 -<title>
483 -I recently emerged Xorg, but when using it, my international keyboard layout
484 -does not work correctly. The main keys work fine but I am unable to compose
485 -special characters like the "at" sign. The startx output says something like
486 -"could not load keymap, falling back to default keymap". What is wrong?
487 -</title>
488 -<body>
489 -
490 -<p>
491 -Check that the permissions on <path>/var/tmp</path> are set to
492 -<path>drwxrwxrwx</path>. If not, change them by typing <c>chmod a+rwx
493 -/var/tmp</c>. This will allow Xorg to load keymaps properly again.
494 -</p>
495 -
496 -</body>
497 -</section>
498 <section id="glfreeze">
499 <title>
500 When using OpenGL DRI or playing movies, the system sometimes freezes hard
501 @@ -957,8 +1051,30 @@
502 </pre>
503
504 <p>
505 -Also, there are some known issues with the composite extensions included with the
506 -newer X.org releases. Please disable this extension if you're having problems.
507 +Also, there are some known issues with the composite extension, please disable
508 +this extension if you're having problems.
509 +</p>
510 +
511 +<p>
512 +Finally, if you are still having trouble, please try disabling dri in your
513 +xorg.conf and see if the problems go away.
514 +</p>
515 +
516 +</body>
517 +</section>
518 +<section id="keymap">
519 +<title>
520 +I recently emerged Xorg, but when using it, my international keyboard layout
521 +does not work correctly. The main keys work fine but I am unable to compose
522 +special characters like the "at" sign. The startx output says something like
523 +"could not load keymap, falling back to default keymap". What is wrong?
524 +</title>
525 +<body>
526 +
527 +<p>
528 +Check that the permissions on <path>/var/tmp</path> are set to
529 +<path>drwxrwxrwx</path>. If not, change them by typing <c>chmod a+rwx
530 +/var/tmp</c>. This will allow Xorg to load keymaps properly again.
531 </p>
532
533 </body>
534 @@ -1000,10 +1116,15 @@
535 link="http://www.maconlinux.org/">Mac-on-Linux</uri> which allows you to run an
536 instance of OS 9, OS X or Linux as a process on Linux. Simply <c>emerge mol</c>
537 to install this package. MOL supports Mac OS 7.5.2 to 9.2.2, as well as any
538 -version OS X. It can be run from a console framebuffer or run in a window on X.
539 +version of OS X. It can be run from a console framebuffer or run in a window on
540 +X.
541 </p>
542
543 <note>
544 +Currently, there is no support for running MOL on 64 bit PowerPC Processors.
545 +</note>
546 +
547 +<note>
548 To run MOL fullscreen, you'll need to compile MOL with the fbcon use flag
549 enabled and run it in a console framebuffer.
550 </note>
551
552
553
554 --
555 gentoo-doc-cvs@g.o mailing list