diff options
Diffstat (limited to 'en/boot-installer/trouble.xml')
| -rw-r--r-- | en/boot-installer/trouble.xml | 57 |
1 files changed, 2 insertions, 55 deletions
diff --git a/en/boot-installer/trouble.xml b/en/boot-installer/trouble.xml index df8c51d55..6539fbe00 100644 --- a/en/boot-installer/trouble.xml +++ b/en/boot-installer/trouble.xml @@ -223,53 +223,6 @@ reliably. </sect3> </sect2> - <sect2 condition="supports-floppy-boot" id="unreliable-floppies"> - <title>Floppy Disk Reliability</title> - -<para> - -The biggest problem for people using floppy disks to install &debian; -seems to be floppy disk reliability. - -</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. - -</para><para> - -If you are having the installation stall at a particular floppy, the first -thing you should do is write the image to a <emphasis>different</emphasis> -floppy and see if that solves the problem. 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. - -</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. - -</para><para> - -Normally you should not have to download a floppy image again, but if you -are experiencing problems it is always useful to verify that the images -were downloaded correctly by verifying their md5sums. - -</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>Boot Configuration</title> <para> @@ -328,12 +281,6 @@ passing certain boot parameters to the installer. <!-- outdated <para> -Some systems have floppies with <quote>inverted DCLs</quote>. If you receive -errors reading from the floppy, even when you know the floppy is good, -try the parameter <userinput>floppy=thinkpad</userinput>. - -</para><para> - On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk drivers), the IDE drive may not be properly recognized. Again, try it first without the parameters and see if the IDE drive is @@ -513,7 +460,7 @@ custom kernel later <phrase arch="linux-any">(see <xref linkend="kernel-baking"/ 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. +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 @@ -564,7 +511,7 @@ installation reports, and file the report as a bug report against the <informalexample><screen> Package: installation-reports -Boot method: <How did you boot the installer? CD? floppy? network?> +Boot method: <How did you boot the installer? CD? USB stick? Network?> Image version: <Full URL to image you downloaded is best> Date: <Date and time of the install> |