1
<?xml version="1.0" encoding="EUC-JP"?>
2
<!-- retain these comments for translator revision tracking -->
3
<!-- original version: 28997 -->
5
<sect1 id="boot-troubleshooting">
6
<title>���ȡ���ץ������Υȥ�֥륷�塼�ƥ���</title>
10
<sect2 condition="supports-floppy-boot" id="unreliable-floppies">
11
<title>�ե��åԡ��ǥ������ο�����</title>
16
The biggest problem for people using floppy disks to install Debian
17
seems to be floppy disk reliability.
19
�ե��åԡ��ǥ��������Ѥ��� Debian �ȡ��뤹��ͤ��ĤޤŤ����������ϡ�
20
�ե��åԡ��ǥ������ο��������Ȼפ��ޤ���
25
The boot floppy is the floppy with the worst problems, because it
26
is read by the hardware directly, before Linux boots. Often, the
27
hardware doesn't read as reliably as the Linux floppy disk driver, and
28
may just stop without printing an error message if it reads incorrect
29
data. There can also be failures in the Driver Floppies most of which
30
indicate themselves with a flood of messages about disk I/O errors.
32
�ä˥֡��ȥե��åԡ����Ǥ�����ˤʤ�褦�Ǥ���
33
����� Linux ����ư�������ˡ��ϡ��ɥ���������ľ���ɤ߹��ޤ�뤫��Ǥ��礦��
34
�ϡ��ɥ������� Linux �Υե��åԡ��ǥ������ɥ饤�Фۤ�
35
�������ι⤤��ˡ���ɤ߹��ߤ�ԤäƤ���ʤ����Ȥ�¿����
36
�������ʤ��ǡ�����������ȡ�
37
���顼��å�������ɽ��������ñ�˻ߤޤäƤ��ޤ��ޤ���
38
�ɥ饤�Хե��åԡ������꤬�����뤳�Ȥ⤢��褦�ǡ�
39
���ξ������ǥ����� I/O ���顼�˴ؤ����å����������̤�ɽ������ޤ���
44
If you are having the installation stall at a particular floppy, the
45
first thing you should do is re-download the floppy disk image and
46
write it to a <emphasis>different</emphasis> floppy. Simply
48
floppy may not be sufficient, even if it appears that the floppy was
49
reformatted and written with no errors. It is sometimes useful to try
50
writing the floppy on a different system.
52
���ȡ��뤬����Υե��åԡ�����ߤ��Ƥ��ޤ����ϡ�
53
�ޤ��ե��åԡ��ǥ������Υ���������������ɤ�ľ���ơ�
54
����� <emphasis>�̤�</emphasis> �ե��åԡ��˽�ľ���Ƥߤ뤳�ȤǤ���
55
�Ť��ե��åԡ���ե����ޥåȤ�ľ�������ǤϽ�ʬ�ǤϤ���ޤ���
56
(���Υե��åԡ��Υե����ޥåȤȽ����˥��顼���Фʤ��ä��Ȥ��Ƥ⡢�Ǥ�)��
57
�ե��åԡ����̤Υ����ƥ�ǽ���Ǥߤ�ȡ�
58
���ޤ��������Ȥ⤢��褦�Ǥ���
63
One user reports he had to write the images to floppy
64
<emphasis>three</emphasis> times before one worked, and then
65
everything was fine with the third floppy.
67
����桼�������ˤ��ȡ�������Υե��åԡ��ؤν��ߤ�
68
<emphasis>3 ��</emphasis>���ľ���ʤ��ȡ�
69
���ޤ�ư���褦�ˤʤ�ʤ��ä������Ǥ���
70
���� 3 ���ܤΥե��åԡ��Ǥϡ���������ʤ����ä������Ǥ���
75
Other users have reported that simply rebooting a few times with the
76
same floppy in the floppy drive can lead to a successful boot. This is
77
all due to buggy hardware or firmware floppy drivers.
80
Ʊ���ե��åԡ���ɥ饤�֤����줿�ޤ���Ƶ�ư���֤������ǡ�
81
���ޤ���ư�����Τ������Ǥ���
82
����ϥϡ��ɥ��������ե����०�����Υե��åԡ��ɥ饤�Ф�
83
�Ǥ��������ä�����Ǥ��礦��
88
<sect2><title>��ư����</title>
93
If you have problems and the kernel hangs during the boot process,
94
doesn't recognize peripherals you actually have, or drives are not
95
recognized properly, the first thing to check is the boot parameters,
96
as discussed in <xref linkend="boot-parms"/>.
98
�֡��ȥץ������κ���˥����ͥ뤬�ϥ����ꡢ
99
��ܤ���Ƥ�����յ����ɥ饤�֤����Τ�ǧ������ʤ��ʤɤ����꤬�����ä��顢
100
�ޤ� <xref linkend="boot-parms"/> �������˽��ä�
101
�֡��ȥѥ������ǧ���Ƥ���������
106
If you are booting with your own kernel instead of the one supplied
107
with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in
108
your kernel. The installer requires
109
<userinput>CONFIG_DEVFS</userinput>.
111
���ȡ��餫��Ϳ����줿�����ͥ�ǤϤʤ���
112
��ʬ�Ǻ�ä������ͥ뤫�鵯ư�������ϡ�
113
<userinput>CONFIG_DEVFS</userinput> �����ꤵ��Ƥ��뤳�Ȥ��ǧ���Ƥ���������
114
���Υ��ȡ���ˤ� <userinput>CONFIG_DEVFS</userinput> ��ɬ�פǤ���
119
Often, problems can be solved by removing add-ons and peripherals, and
120
then trying booting again. <phrase arch="i386">Internal modems, sound
121
cards, and Plug-n-Play devices can be especially problematic.</phrase>
123
�ޤ������ߥ����ɤ���յ�����곰���ƺƵ�ư���Ƥߤ�ȡ�
124
���Τ褦�����꤬���Ǥ��뤳�Ȥ�褯����ޤ���
125
<phrase arch="i386">��¢��ǥࡢ������ɥ����ɡ�
126
Plug-n-Play �ǥХ����ʤɤ��ä�����Ȥʤ꤬���Ǥ���</phrase>
131
If you have a large amount of memory installed in your machine, more
132
than 512M, and the installer hangs when booting the kernel, you may
133
need to include a boot argument to limit the amount of memory the
134
kernel sees, such as <userinput>mem=512m</userinput>.
136
�ޥ���˥��꤬�������� (512M �ʾ�) �Ѥޤ�Ƥ��ơ�
137
���ȡ��餬�����ͥ�ε�ư���˥ϥ�����ϡ�
138
<userinput>mem=512m</userinput> �Τ褦�ʥ֡��Ȱ�������Ȥäơ�
139
�����ͥ뤬����������̤����¤���ɬ�פ����뤫�⤷��ޤ���
144
<sect2 arch="i386" id="i386-boot-problems">
146
<title>Common &arch-title; Installation Problems</title>
148
<title>&arch-title; �ؤΥ��ȡ���˶��̤�����</title>
152
There are some common installation problems that can be solved or avoided by
153
passing certain boot parameters to the installer.
155
���ȡ���κݤζ��̤����꤬�����Ĥ����ꡢ
156
����ϥ��ȡ�����Ϥ���ư�ѥ����Dz�褷���ꡢ
157
�μ¤˥Х��ѥ����Ʋ�����Ǥ��ޤ���
162
Some systems have floppies with <quote>inverted DCLs</quote>. If you receive
163
errors reading from the floppy, even when you know the floppy is good,
164
try the parameter <userinput>floppy=thinkpad</userinput>.
166
�����ƥ�ˤ�äƤ� ``inverted DCLs''
167
�Ĥ��Υե��åԡ��ɥ饤�֤�����������Τ�����ޤ���
168
�ե��åԡ��ǥ��������Τˤ����꤬�ʤ��Ϥ��ʤΤˡ�
169
�ɤ߹�����˥��顼���Ф����ˤϡ�
170
<userinput>floppy=thinkpad</userinput> �Ȥ����ѥ������Ƥ���������
175
On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506
176
disk drivers), the IDE drive may not be properly recognized. Again,
177
try it first without the parameters and see if the IDE drive is
178
recognized properly. If not, determine your drive geometry
179
(cylinders, heads, and sectors), and use the parameter
180
<userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>.
182
IBM PS/1 �� (ST-506 �ǥ������ɥ饤�Ф���������) ValuePoint
183
�ʤɤΥ����ƥ�Ǥϡ�IDE �ɥ饤�֤�������ǧ������ʤ����Ȥ�����ޤ���
184
�����֤��ˤʤ�ޤ������ޤ��ѥ����ʤ��ǥ����ͥ��ư����
185
IDE �ɥ饤�֤�������ǧ������뤫�ɤ����Ƥ���������
187
�ɥ饤�֤Υ�����ȥ� (���������إå���������) ��Ĵ�٤ơ�
188
<userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>
189
�Ȥ����ѥ�����ȤäƤ���������
194
If you have a very old machine, and the kernel hangs after saying
195
<computeroutput>Checking 'hlt' instruction...</computeroutput>, then
196
you should try the <userinput>no-hlt</userinput> boot argument, which
200
<computeroutput>Checking 'hlt' instruction...</computeroutput>
201
��ɽ�����줿���Ȥ˥����ͥ뤬�ϥ��Ƥ��ޤ����ϡ�
202
�֡��Ȱ��� <userinput>no-hlt</userinput> ��Ȥäơ�
203
���Υ����å���̵���ˤ��Ƥߤ�Ȥ褤�Ǥ��礦��
208
If your screen begins to show a weird picture while the kernel boots,
209
eg. pure white, pure black or colored pixel garbage, your system may
210
contain a problematic video card which does not switch to the
211
framebuffer mode properly. Then you can use the boot parameter
212
<userinput>debian-installer/framebuffer=false</userinput> or
213
<userinput>video=vga16:off</userinput> to disable the framebuffer
214
console. Only the English
215
language will be available during the installation due to limited
216
console features. See <xref linkend="boot-parms"/> for details.
218
�����ͥ�ε�ư���˲��̤��ԻĤʳ� (��: �������ù������դ��ԥ������)
219
��ɽ�����Ϥ���硢���ʤ��Υ����ƥ�ϡ�
220
�ե졼��Хåե��⡼�ɤ�Ŭ�ڤ��Ѥ��ʤ�����Τ���ӥǥ������ɤ��Ĥ��Ƥ��뤫�⤷��ޤ���
221
���ξ�硢�ե졼��Хåե��������̵���ˤ��뤿�ᡢ
222
�֡��ȥѥ����� <userinput>debian-installer/framebuffer=false</userinput>
223
�� <userinput>video=vga16:off</userinput> ����ѤǤ��ޤ���
224
������ε�ǽ�����¤���Ƥ��뤿�ᡢ���ȡ�����ˤϱѸ줷���Ȥ��ޤ���
225
�ܺ٤� <xref linkend="boot-parms"/> ��������������
231
<title>System Freeze During the PCMCIA Configuration Phase</title>
233
<title>PCMCIA ������Υ����ƥ�ե��</title>
237
Some laptop models produced by Dell are known to crash when PCMCIA device
238
detection tries to access some hardware addresses. Other laptops may display
239
similar problems. If you experience such a problem and you don't need PCMCIA
240
support during the installation, you can disable PCMCIA using the
241
<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can
242
then configure PCMCIA after the installation is completed and exclude the
243
resource range causing the problems.
245
DELL �Υ�åץȥåץ�ǥ�Τ����Ĥ��ϡ�
246
PCMCIA �ǥХ������ФǤ����Ĥ��ϡ��ɥ��������ɥ쥹���������褦�Ȥ���ȡ�
247
����å��夹�뤳�Ȥ��Τ��Ƥ��ޤ���
248
¾�Υ�åץȥåץ���ԥ塼���Ǥ⡢Ʊ�ͤ����꤬�����뤫�⤷��ޤ���
249
���Τ褦��������������Ƥ⡢PCMCIA ���ݡ��Ȥ�ɬ�פǤʤ���С�
250
<userinput>hw-detect/start_pcmcia=false</userinput> �Ȥ����֡��ȥѥ����ǡ�
251
PCMCIA ��̵���ˤǤ��ޤ���
252
���ȡ��뤬��λ�����塢PCMCIA �����ꤷ��
253
���꤬�����������ϰϤ�������뤳�Ȥ��Ǥ��ޤ���
258
Alternatively, you can boot the installer in expert mode. You will
259
then be asked to enter the resource range options your hardware
260
needs. For example, if you have one of the Dell laptops mentioned
261
above, you should enter <userinput>exclude port
262
0x800-0x8ff</userinput> here. There is also a list of some common
263
resource range options in the <ulink
264
url="http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12">System
265
resource settings section of the PCMCIA HOWTO</ulink>. Note that you
266
have to omit the commas, if any, when you enter this value in the
269
����¾�����ȡ�������ѡ��ȥ⡼�ɤǵ�ư���뤳�Ȥ��Ǥ��ޤ���
270
���θ塢�ϡ��ɥ�������ɬ�פȤ��������ϰϥ��ץ�����
272
�㤨�С��嵭�� Dell �Υ�åץȥåץ���ԥ塼������äƤ���С�
273
������ <userinput>exclude port 0x800-0x8ff</userinput> �����Ϥ���Ȥ����Ǥ���
274
����ˤ����Ĥ��ζ��̤Υ�����ϰϥ��ץ����Υꥹ�Ȥ�<ulink
275
url="http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12">
276
PCMCIA HOWTO �Υ����ƥ�����������</ulink> �ˤ���ޤ���
277
���ȡ���ˤ����ͤ����Ϥ����硢
278
�⤷����Х���ޤ��ά���ʤ���Фʤ�ʤ����Ȥ����դ��Ƥ���������
285
<title>System Freeze while Loading the USB Modules</title>
287
<title>USB �⥸�塼���������Υ����ƥ�ե��</title>
291
The kernel normally tries to install USB modules and the USB keyboard driver
292
in order to support some non-standard USB keyboards. However, there are some
293
broken USB systems where the driver hangs on loading. A possible workaround
294
may be disabling the USB controller in your mainboard BIOS setup. Another option
295
is passing the <userinput>debian-installer/probe/usb=false</userinput> parameter
296
at the boot prompt, which will prevent the modules from being loaded.
298
�����ͥ�ϡ���ɸ�� USB �����ܡ��ɤݡ��Ȥ���褦�ˡ�
299
�̾� USB �⥸�塼��� USB �����ܡ��ɥɥ饤�Фȡ��뤷�褦�Ȥ��ޤ���
300
���������ɥ饤�Ф���������˻ߤޤ�褦�ʡ�
301
�����줿 USB �����ƥब�ޤ�ˤ���ޤ���
302
����ϥޥ����ܡ��ɤ� BIOS ���åȥ��åפǡ�
303
USB ����ȥ������̵���ˤǤ��뤫�⤷��ޤ���
305
�֡��ȥץ���ץȤ� <userinput>debian-installer/probe/usb=false</userinput>
307
����ˤ�� USB �ϡ��ɥ����������Τ���Ƥ⡢
308
�⥸�塼�뤬�����ɤ����Τ��ɤ����Ȥ��Ǥ��ޤ���
314
<sect2 id="kernel-msgs">
315
<title>�����ͥ�ε�ư����å������ΰ�̣</title>
320
During the boot sequence, you may see many messages in the form
321
<computeroutput>can't find <replaceable>something</replaceable>
322
</computeroutput>, or <computeroutput>
323
<replaceable>something</replaceable> not present</computeroutput>,
324
<computeroutput>can't initialize <replaceable>something</replaceable>
325
</computeroutput>, or even <computeroutput>this driver release depends
326
on <replaceable>something</replaceable> </computeroutput>.
327
Most of these messages are harmless. You
328
see them because the kernel for the installation system is built to
329
run on computers with many different peripheral devices. Obviously, no
330
one computer will have every possible peripheral device, so the
331
operating system may emit a few complaints while it looks for
332
peripherals you don't own. You may also see the system pause for a
333
while. This happens when it is waiting for a device to respond, and
334
that device is not present on your system. If you find the time it
335
takes to boot the system unacceptably long, you can create a
336
custom kernel later (see <xref linkend="kernel-baking"/>).
339
<computeroutput>can't find <replaceable>something</replaceable>
340
</computeroutput> (�������Ĥ���ʤ�),
341
<computeroutput><replaceable>something</replaceable> not present
342
</computeroutput> (����¸�ߤ��ʤ�),
343
<computeroutput>can't initialize <replaceable>something</replaceable>
344
</computeroutput> (���������Ǥ��ʤ�),
345
<computeroutput>this driver release depends on <replaceable>something
346
</replaceable></computeroutput> (���Υɥ饤�Фˤϡ���ɬ�פ�)
347
�ʤɤΥ�å�����������������Ϥ���뤳�Ȥ�����ޤ���
348
�����Υ�å������ΤۤȤ�ɤ�̵���Ǥ���
349
����餬���Ϥ������ͳ�ϡ����ȡ��륷���ƥ�Υ����ͥ뤬��
350
���������ʼ��եǥХ����ΤǤ������¿�����б����褦�Ȥ��Ƥ��뤫��Ǥ���
351
���Τ��ᡢOS ���ºݤˤ�¸�ߤ��ʤ����յ����õ�����Ȥˤʤ�Τǡ�
353
�����ƥब���Ф餯�ߤޤä��褦�˸����뤳�Ȥ⤢��ޤ���
354
����ϥǥХ�����ȿ������Τ��ԤäƤ��뤿��˵������ΤǤ�
355
(�ºݤˤϤ��ΥǥХ�����¸�ߤ��ʤ��Τǡ��ߤޤäƤߤ���櫓�Ǥ�)��
356
�����ƥ�ε�ư���פ�����֤������������ۤ�Ĺ�����ϡ�
357
��Ǽ����Υ����ͥ���뤳�Ȥ�Ǥ��ޤ�
358
(<xref linkend="kernel-baking"/> ����)��
364
<sect2 id="problem-report">
365
<title>�Х���ݡ���</title>
369
If you get through the initial boot phase but cannot complete the
370
install, the bug reporter menu choice may be helpful. It copies system
371
error logs and configuration information to a user-supplied floppy.
372
This information may provide clues as to what went wrong and how to
373
fix it. If you are submitting a bug report you may want to attach
374
this information to the bug report.
376
�ǽ�ε�ư�ʳ����̲ᤷ���Τˡ����ȡ��뤬��λ�Ǥ��ʤ��ä����ϡ�
377
�Х���ݡ�����˥塼������Ȥ������⤷��ޤ���
378
����ϥ桼���Υե��åԡ��ˡ������ƥ�Υ��顼�������������ԡ����ޤ���
379
���ξ���ϡ������ְ�äƤ��ƤɤΤ褦�˽������뤫��
380
�Ȥ��ä��꤬������Ƥ��뤫�⤷��ޤ���
381
�Х���������ݤˡ��Х����ˤ��ξ�����դ��뤳�Ȥ��Ǥ��ޤ���
386
Other pertinent installation messages may be found in
387
<filename>/var/log/</filename> during the
388
installation, and <filename>/var/log/debian-installer/</filename>
389
after the computer has been booted into the installed system.
391
����¾�Υ��ȡ����å������ϡ����ȡ�����Ǥ�
392
<filename>/var/log/</filename> �ǡ�
393
���ȡ��뤷�������ƥब��ư������Ǥ�
394
<filename>/var/log/debian-installer/</filename> �Ǹ��Ĥ���Ǥ��礦��
399
<sect2 id="submit-bug">
400
<title>���ȡ����ݡ��Ȥ�����</title>
404
If you still have problems, please submit an installation report. We also
405
encourage installation reports to be sent even if the installation is
406
successful, so that we can get as much information as possible on the largest
407
number of hardware configurations. Please use this template when filling out
408
installation reports, and file the report as a bug report against the
409
<classname>installation-reports</classname> pseudo package, by sending it to
410
<email>submit@bugs.debian.org</email>.
412
�ޤ����꤬������ˤϡ����ȡ����ݡ��Ȥ����꤯��������
413
�ޤ������ȡ��뤬���������Ȥ��Υ��ȡ����ݡ��Ȥ⤪���꤯��������
414
��������ȡ���������Υϡ��ɥ�������������������뤳�Ȥ��Ǥ��ޤ���
415
���ȡ����ݡ��Ȥ�������ݤˤϡ��ʲ��Υƥ�ץ졼�ȤȤ�����������
416
���Υե������<classname>installation-reports</classname> �����ѥå������ΥХ����Ȥ��ơ�
417
<email>submit@bugs.debian.org</email> ���ˤ����꤯��������
419
<informalexample><screen>
420
Package: installation-reports
422
Debian-installer-version: <����������������������>
424
uname -a: <������ץ���ץȤ� uname -a ��¹Ԥ������>
425
Date: <���ȡ��뤷������>
426
Method: <�ɤΤ褦�˥��ȡ��뤷����? �ɤΤ褦�˵�ư������?
427
�ͥåȥ�����ȡ���ʤ�ɤ����餫? �ץ�������?>
429
Machine: <�ޥ�������� (�� IBM Thinkpad R32)>
432
Root Device: <IDE? SCSI? �ǥХ���̾��?>
433
Root Size/partition table: <�ɤ��˥ޥ���Ȥ�����������Ĥ��ơ�
434
���ѡ��ƥ������ơ��֥��ͳ��ĥ���դ��Ƥ���������>
435
Output of lspci and lspci -n:
437
Base System Installation Checklist:
438
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
440
Initial boot worked: [ ]
441
Configure network HW: [ ]
444
Load installer modules: [ ]
445
Detect hard drives: [ ]
446
Partition hard drives: [ ]
447
Create file systems: [ ]
448
Mount partitions: [ ]
449
Install base system: [ ]
450
Install boot loader: [ ]
455
<��ñ�ʥ��ȡ����������������ȡ���ιͻ��������ȡ������ǥ��ʤ�>
456
</screen></informalexample>
459
In the bug report, describe what the problem is, including the last
460
visible kernel messages in the event of a kernel hang. Describe the
461
steps that you did which brought the system into the problem state.
464
�����ͥ뤬�ϥ���ľ����ɽ�����줿�����ͥ��å�������ź���ơ�
465
��������ʤΤ����������Ƥ���������
466
�ޤ������꤬������ޤǤ˥����ƥ���Ф��ƹԤä����Ȥ�Ҥ��Ƥ���������