|
431.
|
|
|
We recommend to install such systems by netbooting the installer.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:3837
|
|
432.
|
|
|
Interpreting the Kernel Startup Messages
|
|
|
Tag: title
|
|
|
|
Interpretación das Mensaxes de Inicio do Kernel
|
|
Translated and reviewed by
Xosé
|
|
|
|
Located in
boot-installer.xml:3846
|
|
433.
|
|
|
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"/>).
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:3848
|
|
434.
|
|
|
Reporting Installation Problems
|
|
|
Tag: title
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:3873
|
|
435.
|
|
|
If you get through the initial boot phase but cannot complete the install, the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using a web browser. 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.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:3874
|
|
436.
|
|
|
Other pertinent installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/installer/</filename> after the computer has been booted into the installed system.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:3885
|
|
437.
|
|
|
Submitting Installation Reports
|
|
|
Tag: title
|
|
|
|
Envío de Informes de Instalación
|
|
Translated and reviewed by
Xosé
|
|
|
|
Located in
boot-installer.xml:3896
|
|
438.
|
|
|
If you still have problems, please submit an installation report. We also encourage installation reports to be sent even if the installation is successful, so that we can get as much information as possible on the largest number of hardware configurations.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:3897
|
|
439.
|
|
|
Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an e-mail address that you do not mind being made public.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:3904
|
|
440.
|
|
|
If you have a working Debian system, the easiest way to send an installation report is to install the <classname>installation-report</classname> and <classname>reportbug</classname> packages (<command>aptitude install installation-report reportbug</command>), configure <classname>reportbug</classname> as explained in <xref linkend="mail-outgoing"/>, and run the command <command>reportbug installation-reports</command>.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
boot-installer.xml:3910
|