[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[d-i doc] boot-installer 翻訳更新
鍋太郎です。
en/boot-installer/trouble.xml が更新されていましたので、
訳を更新してお送りします。
ja/boot-installer/trouble.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 -->
<!-- $Id: trouble.xml 11648 2004-03-22 00:37:46Z joeyh $ -->
<!-- original version: 14602 -->
<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 not set in
your kernel. The installer is not compatible with
<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>