[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[d-i doc] boot-installer 翻訳更新

鍋太郎です。

インストールマニュアルの
ja/boot-installer/trouble.xml
ja/boot-installer/powerpc.xml
の訳を更新しました。

更新をお願いします。

-- 
+-----------------------------------------------------+
 倉澤 望(鍋太郎) 
 KURASAWA Nozomu (nabetaro)
 nabetaro@xxxxxxxxxxxxx
 GnuPG FingerPrint: 
   C4E5 7063 FD75 02EB E71D  559B ECF6 B9D2 8147 ADFB
+-----------------------------------------------------+

<?xml version="1.0" encoding="EUC-JP"?>
<!-- retain these comments for translator revision tracking -->
<!-- original version: 15221 -->

 <sect1 id="boot-troubleshooting">
 <title>󥹥ȡץΥȥ֥륷塼ƥ</title>
<para>
</para>

  <sect2 id="unreliable-floppies">
  <title>եåԡǥο</title>

<para>

<!--
The biggest problem for people installing Debian for the first time
seems to be floppy disk reliability.
-->
 Debian 򥤥󥹥ȡ뤹ͤĤޤŤϡ
եåԡǥοȻפޤ

</para><para>

<!--
The boot floppy is the floppy with the worst problems, because it
is read by the hardware directly, before Linux boots.  Often, the
hardware doesn't read as reliably as the Linux floppy disk driver, and
may just stop without printing an error message if it reads incorrect
data. There can also be failures in the Driver Floppies most of which
indicate themselves with a flood of messages about disk I/O errors.
-->
ä˥֡ȥեåԡǤˤʤ褦Ǥ
 Linux ưˡϡɥľɤ߹ޤ뤫Ǥ礦
ϡɥ Linux Υեåԡǥɥ饤Фۤ
ι⤤ˡɤ߹ߤԤäƤʤȤ¿
ʤǡȡ
顼åɽñ˻ߤޤäƤޤޤ
ɥ饤Хեåԡ꤬뤳Ȥ⤢褦ǡ
ξ񡢥ǥ I/O 顼˴ؤå̤ɽޤ

</para><para>

<!--
If you are having the installation stall at a particular floppy, the
first thing you should do is re-download the floppy disk image and
write it to a <emphasis>different</emphasis> floppy. Simply
reformatting the old
floppy may not be sufficient, even if it appears that the floppy was
reformatted and written with no errors. It is sometimes useful to try
writing the floppy on a different system.
-->
󥹥ȡ뤬ΥեåԡߤƤޤϡ
ޤեåԡǥΥ᡼ɤľơ
 <emphasis>̤</emphasis> եåԡ˽ľƤߤ뤳ȤǤ
ŤեåԡեޥåȤľǤϽʬǤϤޤ
(ΥեåԡΥեޥåȤȽ񤭹߻˥顼ФʤäȤƤ⡢Ǥ)
եåԡ̤Υƥǽ񤭹Ǥߤȡ
ޤȤ⤢褦Ǥ

</para><para>

<!--
One user reports he had to write the images to floppy
<emphasis>three</emphasis> times before one worked, and then
everything was fine with the third floppy.
-->
桼ˤȡ᡼Υեåԡؤν񤭹ߤ
<emphasis>3 </emphasis>ľʤȡ
ޤư褦ˤʤʤäǤ
 3 ܤΥեåԡǤϡʤäǤ

</para><para>

<!--
Other users have reported that simply rebooting a few times with the
same floppy in the floppy drive can lead to a successful boot. This is
all due to buggy hardware or firmware floppy drivers.
-->
ޤ̤Υ桼Ǥϡ
Ʊեåԡɥ饤֤줿ޤ޿Ƶư򷫤֤ǡ
ޤưΤǤ
ϥϡɥե०Υեåԡɥ饤Ф
ǤäǤ礦

</para>
  </sect2>

  <sect2><title>ư</title>

<para>

<!--
If you have problems and the kernel hangs during the boot process,
doesn't recognize peripherals you actually have, or drives are not
recognized properly, the first thing to check is the boot parameters,
as discussed in <xref linkend="boot-parms"/>.
-->
֡ȥץκ˥ͥ뤬ϥ󥰤ꡢ
ܤƤյɥ饤֤Τǧʤʤɤ꤬ä顢
ޤ <xref linkend="boot-parms"/> ˽ä
֡ȥѥ᡼ǧƤ

</para><para>

<!--
If you are booting with your own kernel instead of the one supplied
with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in
your kernel.  The installer requires
<userinput>CONFIG_DEVFS</userinput>.
-->
󥹥ȡ餫Ϳ줿ͥǤϤʤ
ʬǺäͥ뤫鵯ưϡ
<userinput>CONFIG_DEVFS</userinput> ꤵƤ뤳ȤǧƤ
Υ󥹥ȡˤ <userinput>CONFIG_DEVFS</userinput> ɬפǤ

</para><para>

<!--
Often, problems can be solved by removing add-ons and peripherals, and
then trying booting again.  <phrase arch="i386">Internal modems, sound
cards, and Plug-n-Play devices can be especially problematic.</phrase>
-->
ޤߥɤյ곰ƺƵưƤߤȡ
Τ褦꤬Ǥ뤳Ȥ褯ޤ
<phrase arch="i386">¢ǥࡢɥɡ
Plug-n-Play ǥХʤɤäȤʤ꤬Ǥ</phrase>

</para><para>

<!--
There are, however, some limitations in our boot floppy set with
respect to supported hardware.  Some Linux-supported platforms might
not be directly supported by our boot floppies.  If this is the case,
you may have to create a custom boot disk (see
<xref linkend="rescue-replace-kernel"/>), or investigate network
installations.
-->
䤿εưեåԡ⡢
ݡȤƤϡɥˤϸ¤꤬ޤ
Linux ݡȤƤץåȥեǤ⡢
Υ֡ȥեåԡľܥݡȤƤʤȤϤǤ礦
ξϡ֡ȥǥʬǺ
(<xref linkend="rescue-replace-kernel"/> 򻲾) 
ͥåȥ󥹥ȡĴ٤뤫ɬפޤ

</para><para>

<!--
If you have a large amount of memory installed in your machine, more
than 512M, and the installer hangs when booting the kernel, you may
need to include a boot argument to limit the amount of memory the
kernel sees, such as <userinput>mem=512m</userinput>.
-->
ޥ˥꤬ (512M ʾ) ѤޤƤơ
󥹥ȡ餬ͥεư˥ϥ󥰤ϡ
<userinput>mem=512m</userinput> Τ褦ʥ֡ȰȤäơ
ͥ뤬̤¤ɬפ뤫⤷ޤ

</para>
  </sect2>

  <sect2 id="kernel-msgs">
  <title>ͥεưåΰ̣</title>

<para>

<!--
During the boot sequence, you may see many messages in the form
<computeroutput>can't find <replaceable>something</replaceable>
</computeroutput>, or <computeroutput>
<replaceable>something</replaceable> not present</computeroutput>,
<computeroutput>can't initialize <replaceable>something</replaceable>
</computeroutput>, or even <computeroutput>this driver release depends
on <replaceable>something</replaceable> </computeroutput>.
Most of these messages are harmless. You
see them because the kernel for the installation system is built to
run on computers with many different peripheral devices. Obviously, no
one computer will have every possible peripheral device, so the
operating system may emit a few complaints while it looks for
peripherals you don't own. You may also see the system pause for a
while. This happens when it is waiting for a device to respond, and
that device is not present on your system. If you find the time it
takes to boot the system unacceptably long, you can create a
custom kernel later (see <xref linkend="kernel-baking"/>).
-->
֡ȥ󥹤ǡ
<computeroutput>can't find <replaceable>something</replaceable>
</computeroutput> (Ĥʤ),
 <computeroutput><replaceable>something</replaceable> not present
</computeroutput> (¸ߤʤ),
<computeroutput>can't initialize <replaceable>something</replaceable>
</computeroutput> (Ǥʤ),
<computeroutput>this driver release depends on <replaceable>something
</replaceable></computeroutput> (Υɥ饤Фˤϡɬפ)
ʤɤΥåϤ뤳Ȥޤ
ΥåΤۤȤɤ̵Ǥ
餬Ϥͳϡ󥹥ȡ륷ƥΥͥ뤬
ʼեǥХΤǤ¿б褦ȤƤ뤫Ǥ
ΤᡢOS ºݤˤ¸ߤʤյõȤˤʤΤǡ
ʸǤ櫓Ǥ
ƥबФ餯ߤޤä褦˸뤳Ȥ⤢ޤ
ϥǥХȿΤԤäƤ뤿˵ΤǤ
(ºݤˤϤΥǥХ¸ߤʤΤǡߤޤäƤߤ櫓Ǥ)
ƥεưפ֤ۤĹϡ
ǼΥͥ뤳ȤǤޤ
(<xref linkend="kernel-baking"/> )

</para>
  </sect2>


  <sect2 id="problem-report">
  <title>Хݡ</title>
<para>

<!--
If you get through the initial boot phase but cannot complete the
install, the bug reporter menu choice may be helpful. It copies system
error logs and configuration information to a user-supplied floppy.
This information may provide clues as to what went wrong and how to
fix it.  If you are submitting a bug report you may want to attach
this information to the bug report.
-->
ǽεưʳ̲ᤷΤˡ󥹥ȡ뤬λǤʤäϡ
Хݡ˥塼򤹤Ȥ⤷ޤ
ϥ桼ΥեåԡˡƥΥ顼򥳥ԡޤ
ξϡְäƤƤɤΤ褦˽뤫
Ȥä꤬򼨤Ƥ뤫⤷ޤ
ХݤˡХˤξդ뤳ȤǤޤ

</para><para>

<!--
Other pertinent installation messages may be found in
<filename>/target/var/log/debian-installer/</filename> during the
installation, and <filename>/var/log/debian-installer/</filename>
after the computer has been booted into the installed system.
-->
¾Υ󥹥ȡåϡ󥹥ȡǤ
<filename>/target/var/log/debian-installer/</filename> ǡ
󥹥ȡ뤷ƥबưǤ
<filename>/var/log/debian-installer/</filename> ǸĤǤ礦

</para>
  </sect2>

  <sect2 id="submit-bug">
  <title>Х</title>
<para>

<!--
If you still have problems, please submit a bug report.  Send an email
to <email>submit@bugs.debian.org</email>.  You
<emphasis>must</emphasis> include the following as the first lines of
the email:
-->
ޤ꤬ϡХäƤ
<email>submit@bugs.debian.org</email>
Żҥ᡼äƤ
Żҥ᡼Ƭˤϡ
<emphasis>ɬ</emphasis> ʲεҤդäƤ

<informalexample><screen>

Package: installation-reports
Version: <replaceable>version</replaceable>

</screen></informalexample>

<!--
Be sure to fill in <replaceable>version</replaceable> with the
version of the debian-installer that you used. The version number can
be found if you press <keycap>F1</keycap> key on the
<prompt>boot:</prompt> prompt of your installation media. You should
also mention where did you download the installation media, or the
source of a CD you bought.
-->
<replaceable>version</replaceable> ΤȤˡ
Ѥ debian-installer ΥС񤯤Τ˺ʤ褦ˤƤ
СϤΥ󥹥ȡǥ <prompt>boot:</prompt> ǡ
<keycap>F1</keycap> 򲡤Ȥ狼ޤ
CD 丵Ǥ狼ޤ

</para><para>

<!--
You should also include the following information in your bug report.
If you use the program <command>reportbug</command> to submit your 
report, this information will be included automatically.
-->
ХˤϰʲΤ褦ʾźƤ
ݤ <command>reportbug</command> ץѤȡ
ưŪˤξɲäƤޤ

<informalexample><screen>

<!--
<phrase arch="i386">
flavor:        <replaceable>flavor of image you are using</replaceable>
</phrase>
architecture:  &architecture; 
model:         <replaceable>your general hardware vendor and model</replaceable>
memory:        <replaceable>amount of RAM</replaceable>
scsi:          <replaceable>SCSI host adapter, if any</replaceable>
cd-rom:        <replaceable>CD-ROM model and interface type, e.g., ATAPI</replaceable>
network card:  <replaceable>network interface card, if any</replaceable>
pcmcia:        <replaceable>details of any PCMCIA devices</replaceable>
-->
<phrase arch="i386">
flavor:        <replaceable>Ѥ᡼Υե졼С</replaceable>
</phrase>
architecture:  &architecture; 
model:         <replaceable>ϡɥΥ᡼ǥ̾</replaceable>
memory:        <replaceable>RAM </replaceable>
scsi:          <replaceable>() SCSI ۥȥץ</replaceable>
cd-rom:        <replaceable>CD-ROM Υǥ̾ȥ󥿡եμ (ATAPI )</replaceable>
network card:  <replaceable>() ͥåȥ󥿡ե</replaceable>
pcmcia:        <replaceable>PCMCIA ǥХξܺ</replaceable>

</screen></informalexample>

</para><para>

<!--
Depending on the nature of the bug, it also might be useful to report
whether you are installing to IDE or SCSI disks, other peripheral
devices such as audio, disk capacity, and the model of video card.
-->
ˤޤ
󥹥ȡΥǥ IDE ǥʤΤ SCSI ǥʤΤ
˥ǥΤ褦¾μյ
ǥ̡ӥǥɤΥǥ̾ʤɤξ
ź뤳ȤͭפǤ礦

</para><para>

<!--
In the bug report, describe what the problem is, including the last
visible kernel messages in the event of a kernel hang.  Describe the
steps that you did which brought the system into the problem state.
-->
Хκݤˤϡ
ͥ뤬ϥ󥰤ľɽ줿ͥåźơ
ʤΤƤ
ޤ꤬ޤǤ˥ƥФƹԤäȤ⵭ҤƤ

</para>

  </sect2>

 </sect1>

<?xml version="1.0" encoding="EUC-JP"?>
<!-- retain these comments for translator revision tracking -->
<!-- original version: 15220 -->

  <sect2 arch="powerpc"><title>CD-ROM εư</title>

&boot-installer-intro-cd.xml;

<para>

<!--
Currently, the only &arch-title; subarchitectures that support CD-ROM
booting are PReP and New World PowerMacs. On PowerMacs, hold the
<keycap>c</keycap> key, or else the combination of
<keycap>Command</keycap>, <keycap>Option</keycap>,
<keycap>Shift</keycap>, and <keycap>Delete</keycap>
keys together while booting to boot from the CD-ROM.
-->
ΤȤCD-ROM εư򥵥ݡȤƤ
&arch-title; Υ֥ƥ
PReP  New World PowerMac Ǥ
PowerMac Ǥϡ<keycap>c</keycap> 򲡤äѤʤˤ뤫
ޤ <keycap>Command</keycap>, <keycap>Option</keycap>,
<keycap>Shift</keycap>, <keycap>Delete</keycap> ưƱ˲С
CD-ROM 鵯ưǤޤ

</para><para>

<!--
OldWorld Powermacs will not boot a Debian CD, because OldWorld
computers relied on a MacOSROM CD boot driver to be present on the CD,
and a free-software version of this driver is not available. All
OldWorld systems have floppy drives, so use the floppy drive to launch
the installer, and then point the installer to the CD for the needed
files.
-->
OldWorld Powermac ǤϡDebian CD ưʤǤ礦ʤʤ OldWorld
ԥ塼ϡCD ѤΤ MacOSROM CD ֡ȥɥ饤Ф˰¸
Υɥ饤Фˤϥե꡼եȥǤ¸ߤʤǤ٤Ƥ
OldWorld ƥˤϡեåԡɥ饤֤Τǡ󥹥ȡ
Ϥ뤿˥եåԡɥ饤֤ȤɬפȤ줿եΤ CD 
ꤷƤ

</para><para>

If your system doesn't boot directly from CD-ROM, you can still use
the CD-ROM to install the system. On NewWorlds, you can also use an
OpenFirmware command to boot from the CD-ROM manually. Follow the
instructions in <xref linkend="boot-newworld"/> for booting from
the hard disk, except use the path to <command>yaboot</command> on the
CD at the OF prompt, such as

CD-ROM ľܵư򥵥ݡȤƤʤƥǤ⡢
󥹥ȡ CD-ROM Ѥ뤳ȤϲǽǤ
NewWorld ǤϡOpenFirmware ΥޥɤѤơ
ư CD-ROM 鵯ư뤳ȤǤޤ
ϡɥǥ鵯ư
<xref linkend="boot-newworld"/> λؼ˽äƤ
 OF ץץȤͿ CD  <command>yaboot</command> ؤΥѥȤƤϡ

<informalexample><screen>

0 > boot cd:,\install\yaboot

</screen></informalexample>
Τ褦ʤΤѤƤ
</para>
  </sect2>

  <sect2 arch="powerpc" id="install-drive">
  <title>ϡɥǥεư</title>

&boot-installer-intro-hd.xml;

  <sect3><title>OpenFirmware  CHRP εư</title>

<para>

<!--
  <emphasis>Not yet written.</emphasis>
-->
  <emphasis>ޤ񤤤Ƥޤ</emphasis>
</para>
   </sect3>

   <sect3><title>MacOS  OldWorld PowerMac εư</title>
<para>

<!--
If you set up BootX in <xref linkend="files-oldworld"/>, you can
use it to boot into the installation system. Double click the
<guiicon>BootX</guiicon> application icon. Click on the
<guibutton>Options</guibutton> button and select <guilabel>Use
Specified RAM Disk</guilabel>. This will give you the 
chance to select the <filename>ramdisk.image.gz</filename> file. You
may need to select the <guilabel>No Video Driver</guilabel> checkbox,
depending on your hardware. Then click the
<guibutton>Linux</guibutton> button to shut down MacOS and launch the
installer.
-->
<xref linkend="files-oldworld"/>  BootX Ѥߤʤ顢
Ȥäƥ󥹥ȡ륷ƥưǤޤ
<guiicon>BootX</guiicon> Υץꥱ󥢥֥륯åƤ
<guibutton>Options</guibutton> ܥ򥯥å
<guilabel>Use Specified RAM Disk</guilabel> Ǥ
 <filename>ramdisk.image.gz</filename> եǤ褦ˤʤޤ
ϡɥˤäƤϡ
<guilabel>No Video Driver</guilabel> åܥåФʤФʤʤ⤷ޤ
Ǹ <guibutton>Linux</guibutton> ܥ򥯥åȡMacOS åȥ󤷤ơ
󥹥ȡ餬ưޤ

</para>
   </sect3>


  <sect3 id="boot-newworld">
  <title>OpenFirmware  NewWorld Mac εư</title>
<para>

<!--
You will have already placed the <filename>linux.bin, yaboot,
yaboot.conf</filename>, and <filename>root.bin</filename> files at the
root level of your HFS partition in <xref linkend="files-newworld"/>. 
Restart the computer, and immediately (during the chime) hold down the
<keycap>Option</keycap>, <keycap>Command (cloverleaf/Apple)</keycap>,
<keycap>o</keycap>, and <keycap>f</keycap> keys all together. After 
a few seconds you will be presented with the Open Firmware prompt.
At the prompt, type
-->
 <xref linkend="files-newworld"/> ˤơ
<filename>linux.bin, yaboot, yaboot.conf, root.bin</filename> 
Ȥäե
HFS ѡƥ root ٥֤ȤȻפޤ
ԥ塼Ƶư (㥤बĤäƤ)
<keycap>Option</keycap>, <keycap>Command (С/Apple)</keycap>,
<keycap>o</keycap>, <keycap>f</keycap> γƥƱ˲ޤ
ô֤ĤȡOpenFirmware ΥץץȤɽޤ
ץץȤ鼡Τ褦Ϥޤ

<informalexample><screen>

0 > boot hd:<replaceable>x</replaceable>,yaboot

</screen></informalexample>

<!--
replacing <replaceable>x</replaceable> with the partition number of
the HFS partition where the
kernel and yaboot files were placed, followed by a &enterkey;. On some
machines, you may need to use <userinput>ide0:</userinput> instead of
<userinput>hd:</userinput>. In a few more seconds you will see a
yaboot prompt
-->
<replaceable>x</replaceable> ϥͥ yaboot ե֤
HFS ѡƥֹ֤Ƥ
Ϥ &enterkey; 򲡤ޤ
ĤΥޥǤϡ
<userinput>hd:</userinput>  <userinput>ide0:</userinput>
ꤹɬפ뤫⤷ޤ󡣤˲äԤĤȡ
yaboot ΥץץȤɽޤ

<informalexample><screen>

boot:

</screen></informalexample>

<!--
At yaboot's <prompt>boot:</prompt> prompt, type either
<userinput>install</userinput> or <userinput>install-safe</userinput>
followed by a &enterkey;.  The `safe' option uses the
<userinput>video=ofonly</userinput> argument for maximum
compatibility; you can try it if <userinput>install</userinput>
doesn't work. The Debian installation program should start.
-->
Yaboot  <prompt>boot:</prompt> ץץȤǡ
<userinput>install</userinput>  <userinput>install-safe</userinput> Ϥ&enterkey; 򲡤ޤ
`safe' ϸߴ⤯ʤ褦
<userinput>video=ofonly</userinput> Ȥޤ
<userinput>install</userinput> ޤʤȤϻƤߤƤ
 Debian Υ󥹥ȡץबϤϤǤ

</para>
   </sect3>
  </sect2>

  <sect2 arch="powerpc" id="boot-tftp"><title>TFTP Ǥεư</title>

&boot-installer-intro-net.xml;

<para>

<!--
Currently, PReP and New World PowerMac systems support netbooting. 
-->
ߡPReP  New World PowerMac ƥǤϥͥåȥ֡Ȥ򥵥ݡȤƤޤ

</para><para>

<!--
On machines with Open Firmware, such as NewWorld Power Macs, enter the
boot monitor (see <xref linkend="invoking-openfirmware"/>) and
use the command <command>boot enet:0</command>.  PReP and CHRP boxes
may have different ways of addressing the network.  On a PReP machine,
you should try 
<userinput>boot <replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>.
-->
NewWorld Power Mac Τ褦 OpenFirmware ΥޥǤϡ
֡ȥ˥
(<xref linkend="invoking-openfirmware"/> 򻲾)
<command>boot enet:0</command> ȤޥɤȤޤ
PReP  CHRP ΥޥǤϡͥåȥλ꤬ۤʤ뤫⤷ޤ
PReP ޥǤϡ
<userinput>boot <replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>
ƤߤƤ

</para>
  </sect2>


  <sect2 arch="powerpc">
  <title>եåԡεư</title>
<para>

<!--
Booting from floppies is supported for &arch-title;, although it is
generally only applicable for OldWorld systems. NewWorld systems are
not equipped with floppy drives, and attached USB floppy drives are 
not supported for booting.
-->
&arch-title; ϥեåԡεư򥵥ݡȤƤޤ
Ѥ뤳ȤǤΤ̾ OldWorld ƥǤ
NewWorld ƥϡ̽вٻˤϥեåԡɥ饤֤ĤƤޤ

</para><para>

<!--
You will have already downloaded the floppy images you needed and
created floppies from the images in <xref linkend="create-floppy"/>.
-->
餯 <xref linkend="create-floppy"/> 
ɬפʥեåԡ᡼ϴ˥ɤ
Υ᡼եåԡϺѤߤȻפޤ

</para><para>

<!--
To boot from the <filename>boot-floppy-hfs.img</filename> floppy,
place it in floppy drive after shutting the system down, and before
pressing the power-on button.
-->
<filename>boot-floppy-hfs.img</filename> եåԡ鵯ưˤϡ
ƥ򥷥åȥ󤷤Ȥ˥եåԡɥ饤֤졢
ѥܥ򲡤Ƥ

</para><note><para>
<!--
For those not familiar with Macintosh
floppy operations: a floppy placed in the machine prior to boot will
be the first priority for the system to boot from. A floppy without a
valid boot system will be ejected, and the machine will then check for
bootable hard disk partitions.
-->
Macintosh Υեåԡ˴Ƥʤ: 
եåԡƥεưǺͥˤϡ
ư˥եåԡƤ
ͭʥ֡ȥƥΤʤեåԡӽФƤޤ
֡ȲǽʥϡɥǥΥѡƥåޤ

</para></note><para>

<!--
After booting, the <filename>root.bin</filename> floppy is
requested. Insert the root floppy and press &enterkey;. The installer
program is automatically launched after the root system has been
loaded into memory.
-->
ưȡ<filename>root.bin</filename> եåԡ׵ᤵޤ
root եåԡ &enterkey; 򲡤Ƥ
root ƥब˥ɤȡ
󥹥ȡץबưŪ˵ưޤ

</para>
  </sect2>


  <sect2 arch="powerpc"><title>PowerPC ֡ȥѥ᡼</title>
<para>

<!--
Many older Apple monitors used a 640x480 67Hz mode. If your video
appears skewed on an older Apple monitor, try appending the boot
argument <userinput>video=atyfb:vmode:6</userinput> , which will
select that mode for most Mach64 and Rage video hardware. For Rage 128
hardware, this changes to
<userinput>video=aty128fb:vmode:6</userinput> .
-->
¿θŤ Apple ˥ϡ640x480 67Hz ⡼ɤѤޤ
Ť Apple ˥Dz̤椬硢
¿ Mach64Rage ӥǥϡɥǥ⡼ɤ򤹤ˤϡ
֡Ȱ <userinput>video=atyfb:vmode:6</userinput> ƤߤƤ
Rage 128 ϡɥʤ餳 <userinput>video=aty128fb:vmode:6</userinput> 
ѤƤ

</para>
  </sect2>