| 5.4. Resolución de problemas en el proceso de instalación | ||
|---|---|---|
 |
Capítulo 5. Arranque del sistema de instalación | 
|
| 5.4. Resolución de problemas en el proceso de instalación | ||
|---|---|---|
|
|
Capítulo 5. Arranque del sistema de instalación |
|
Sometimes, especially with older drives, the installer may fail to boot from an optical disc. The installer may also — even after booting successfully from such disc — fail to recognize the disc or return errors while reading from it during the installation.
Hay muchas causas posibles para estos problemas. Aquí sólo se pueden listar algunos problemas comunes y dar sugerencias generales de cómo tratarlos. Lo demás depende de usted.
Hay dos cosas muy sencillas que debería intentar primero.
If the disc does not boot, check that it was inserted correctly and that it is not dirty.
If the installer fails to recognize the disc, try just running the option a second time. Some DMA related issues with very old CD-ROM drives are known to be resolved in this way.
If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for CD-ROM and DVD.
If you cannot get the installation working from optical disc, try one of the other installation methods that are available.
Algunas unidades antiguas de CD-ROM no pueden leer discos que se grabaron a altas velocidades con grabadores de CD modernos.
Algunas unidades muy antiguas de CD-ROM no funcionan correctamente si se activa la función “direct memory access” (DMA).
If the optical disc fails to boot, try the suggestions listed below.
Check that your BIOS actually supports booting from optical disc (only an issue for very old systems) and that booting from such media is enabled in the BIOS.
If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the MD5SUMS file that should be present in the same location as where you downloaded the image from.
$ md5sumdebian-testing-i386-netinst.isoa20391b12f7ff22ef705cee4059c6b92debian-testing-i386-netinst.iso
Next, check that the md5sum of the burned disc matches as well. The following command should work. It uses the size of the image to read the correct number of bytes from the disc.
$ dd if=/dev/cdrom | \
> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \
> md5sum
a20391b12f7ff22ef705cee4059c6b92 -
262668+0 records in
262668+0 records out
134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s
If, after the installer has been booted successfully, the disc is not detected, sometimes simply trying again may solve the problem. If you have more than one optical drive, try changing the disc to the other drive. If that does not work or if the disc is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there.
Cambie al terminal virtual VT4 o consulte los contenidos de /var/log/syslog (utilice nano como editor) para comprobar si hay algún mensaje de error específico. Una vez lo haya hecho, compruebe también la salida de ejecutar dmesg.
Check in the output of dmesg if your optical drive was recognized. You should see something like (the lines do not necessarily have to be consecutive):
ata1.00: ATAPI: MATSHITADVD-RAM UJ-822S, 1.61, max UDMA/33 ata1.00: configured for UDMA/33 scsi 0:0:0:0: CD-ROM MATSHITA DVD-RAM UJ-822S 1.61 PQ: 0 ANSI: 5 sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray cdrom: Uniform CD-ROM driver Revision: 3.20
If you don't see something like that, chances are the controller your drive is connected to was not recognized or may be not supported at all. If you know what driver is needed for the controller, you can try loading it manually using modprobe.
Check that there is a device node for your optical drive under /dev/. In the example above, this would be /dev/sr0. There should also be a /dev/cdrom.
Use the mount command to check if the optical disc is already mounted; if not, try mounting it manually:
$ mount /dev/hdc /cdrom
Check if there are any error messages after that command.
Check if DMA is currently enabled:
$ cd /proc/ide/hdc$ grep using_dma settings using_dma 1 0 1 rw
A “1” in the first column after using_dma means it is enabled. If it is, try disabling it:
$ echo -n "using_dma:0" >settings
Make sure that you are in the directory for the device that corresponds to your optical drive.
If there are any problems during the installation, try checking the integrity of the installation media using the option near the bottom of the installer's main menu. This option can also be used as a general test if the disc can be read reliably.
En caso de que tenga problemas, el núcleo se bloquee durante el proceso de arranque, no reconozca los dispositivos que tiene o no se reconozcan correctamente las unidades, lo primero que debe verificar son los parámetros de arranque, como se explica en Sección 5.3, “Parámetros de arranque”.
En algunos casos, pueden aparecer errores de funcionamiento por un firmware de dispositivo faltante (consulte Sección 2.2, “Dispositivos que requieren Firmware” y Sección 6.4, “Carga de Firmware adicional”).
Durante la secuencia de arranque podría ver muchos mensajes de la forma can't find , o algoalgo not presentcan't initialize , o incluso algothis driver release depends on . Muchos de estos mensajes son inocuos. Los ve porque el sistema de instalación está programado para ejecutarse en ordenadores con diversos dispositivos. Obviamente, ningún ordenador tendrá todos y cada uno de los posibles dispositivos, de modo que el sistema operativo emite algunos mensajes de advertencia mientras intenta buscar dispositivos que usted no tiene. También podría observar que el sistema se detiene durante algunos momentos. Esto ocurre cuando se está esperando que un dispositivo responda y éste no está presente en su sistema. Podrá crear más adelante un núcleo a medida (lea Sección 8.5, “Compilar un nuevo núcleo”) si piensa que el tiempo que tarda en arrancar el sistema es muy largo. algo
If you get through the initial boot phase but cannot complete the install, the menu option may be helpful. It lets you store system error logs and configuration information from the installer on a storage medium, 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.
Puede encontrar otros mensajes de instalación pertinentes en /var/log/ durante la instalación, y en /var/log/installer/ después de que el ordenador ha sido arrancado con el sistema instalado.
Por favor, envíe un informe de su instalación si tiene problemas. Le animamos a hacerlo incluso si la instalación tiene éxito, de esta forma podremos obtener la mayor información posible sobre la mayor cantidad de configuraciones de hardware.
Tenga en cuenta que el informe de instalación se publicará en el sistema de seguimiento de fallos de Debian y que se reenviará a una lista de correo pública. Asegúrese que utiliza una dirección de correo electrónico que no le importa que se haga público.
If you have a working Debian system, the easiest way to send an installation report is to install the installation-report and reportbug packages (apt install installation-report reportbug), configure reportbug as explained in Sección 8.4.2, “Enviar correo electrónico fuera del sistema”, and run the command reportbug installation-reports.
Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the installation-reports pseudo package, by sending it to <submit@bugs.debian.org>.
Package: installation-reports
Boot method: <How did you boot the installer? CD/DVD? USB stick? Network?>
Image version: <Full URL to image you downloaded is best>
Date: <Date and time of the install>
Machine: <Description of machine (eg, IBM Thinkpad R32)>
Processor:
Memory:
Partitions: <df -Tl will do; the raw partition table is preferred>
Output of lspci -knn (or lspci -nn):
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [ ]
Detect network card: [ ]
Configure network: [ ]
Detect media: [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Install base system: [ ]
Clock/timezone setup: [ ]
User/password setup: [ ]
Install tasks: [ ]
Install boot loader: [ ]
Overall install: [ ]
Comments/Problems:
<Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.>
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.
|
|
 |
|
| 5.3. Parámetros de arranque |  |
Capítulo 6. Usar el instalador de Debian |