1 files changed, 169 insertions, 159 deletions

diff --git a/en_US.ISO8859-1/books/handbook/install/chapter.sgml b/en_US.ISO8859-1/books/handbook/install/chapter.sgml
index e095b163e3..34834637ea 100644
--- a/en_US.ISO8859-1/books/handbook/install/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/install/chapter.sgml
@@ -4036,165 +4036,175 @@ Please press any key to reboot.</screen>
 	using the &man.mount.ntfs.8; command.</para>
     </sect2>
 
-  <sect2>
-    <title>Troubleshooting Questions and Answers</title>
-
-    <qandaset>
-      <qandaentry>
-        <question>
-          <para>My system hangs while probing hardware during boot, or it
-            behaves strangely during install, or the floppy drive isn't
-            probed.</para>
-        </question>
-        <answer>
-          <para>&os; 5.0 and above makes extensive use of the system ACPI
-            service on the i386, amd64 and ia64 platforms to aid in system
-	    configuration if it's detected during boot.  Unfortunately,
-	    some bugs still exist in both the ACPI driver and within system
-	    motherboards and BIOS.  The use of ACPI can be disabled by setting
-	    the <literal>hint.acpi.0.disabled</literal> hint in the third stage
-	    boot loader:</para>
-
-          <screen>set hint.acpi.0.disabled="1"</screen>
-
-          <para>This is reset each time the system is booted, so it is
-            necessary to add <literal>hint.acpi.0.disabled="1"</literal>
-            to the file
-            <filename>/boot/loader.conf</filename>.  More information about the
-            boot loader can be found in <xref linkend="boot-synopsis">.</para>
-        </answer>
-      </qandaentry>
-      <qandaentry>
-        <question>
-          <para>I go to boot from the hard disk for the first time
-          after installing &os;, the kernel loads and probes my
-          hardware, but stops with messages like:</para>
-
-          <screen>changing root device to ad1s1a panic: cannot mount root</screen>
-          <para>What is wrong?  What can I do?</para>
-
-          <para>What is this
-          <literal>bios_drive:interface(unit,partition)kernel_name</literal>
-          thing that is displayed with the boot help?</para>
-        </question>
-        <answer>
-          <para>There is a longstanding problem in the case where the
-          boot disk is not the first disk in the system.  The BIOS
-          uses a different numbering scheme to &os;, and working
-          out which numbers correspond to which is difficult to get
-          right.</para>
-
-          <para>In the case where the boot disk is not the first disk
-          in the system, &os; can need some help finding it.  There
-          are two common situations here, and in both of these cases,
-          you need to tell &os; where the root filesystem is.  You
-          do this by specifying the BIOS disk number, the disk type
-          and the &os; disk number for that type.</para>
-
-          <para>The first situation is where you have two IDE disks,
-          each configured as the master on their respective IDE
-          busses, and wish to boot &os; from the second disk.  The
-          BIOS sees these as disk 0 and disk 1, while &os; sees
-          them as <devicename>ad0</devicename> and
-          <devicename>ad2</devicename>.</para>
-
-          <para>&os; is on BIOS disk 1, of type
-          <literal>ad</literal> and the &os; disk number is 2, so
-          you would say:</para>
-
-          <screen><userinput>1:ad(2,a)kernel</userinput></screen>
-
-          <para>Note that if you have a slave on the primary bus, the
-          above is not necessary (and is effectively wrong).</para>
-
-          <para>The second situation involves booting from a SCSI disk
-          when you have one or more IDE disks in the system.  In this
-          case, the &os; disk number is lower than the BIOS disk
-          number.  If you have two IDE disks as well as the SCSI disk,
-          the SCSI disk is BIOS disk 2, type <literal>da</literal> and
-          &os; disk number 0, so you would say:</para>
-
-          <screen><userinput>2:da(0,a)kernel</userinput></screen>
-
-          <para>To tell &os; that you want to boot from BIOS disk
-          2, which is the first SCSI disk in the system.  If you only
-          had one IDE disk, you would use '1:' instead.</para>
-
-          <para>Once you have determined the correct values to use,
-          you can put the command exactly as you would have typed it
-          in the <filename>/boot.config</filename> file using a
-          standard text editor.  Unless instructed otherwise, &os;
-          will use the contents of this file as the default response
-          to the <literal>boot:</literal> prompt.</para>
-        </answer>
-      </qandaentry>
-      <qandaentry>
-        <question>
-	  <para>I go to boot from the hard disk for the first time
-          after installing &os;, but the Boot Manager prompt just
-          prints <literal>F?</literal> at the boot menu each time but
-          the boot won't go any further.</para>
-	</question>
-	<answer>
-          <para>The hard disk geometry was set incorrectly in the
-          Partition editor when you installed &os;.  Go back into
-          the partition editor and specify the actual geometry of your
-          hard disk.  You must reinstall &os; again from the
-          beginning with the correct geometry.</para>
-
-          <para>If you are failing entirely in figuring out the
-	  correct geometry for your machine, here's a tip: Install a
-	  small DOS partition at the beginning of the disk and install
-	  &os; after that.  The install program will see the DOS
-	  partition and try to infer the correct geometry from it,
-	  which usually works.</para>
-
-	  <para>The following tip is no longer recommended, but is left here
-	  for reference:</para>
-
-	  <blockquote>
-            <para>If you are setting up a truly dedicated &os;
-	    server or workstation where you don't care for (future)
-	    compatibility with DOS, Linux or another operating system,
-	    you've also got the option to use the entire disk (`A' in
-	    the partition editor), selecting the non-standard option
-	    where &os; occupies the entire disk from the very first
-	    to the very last sector.  This will leave all geometry
-	    considerations aside, but is somewhat limiting unless
-	    you're never going to run anything other than &os; on a
-	    disk.</para>
-	  </blockquote>
- 	</answer>
-      </qandaentry>
-      <qandaentry>
-        <question>
-	  <para>The system finds my &man.ed.4; network card, but I
-          keep getting device timeout errors.</para>
-	</question>
-	<answer>
-	  <para>Your card is probably on a different IRQ from what is
-	  specified in the <filename>/boot/device.hints</filename> file.  The ed driver does
-	  not use the `soft' configuration by default (values entered
-	  using EZSETUP in DOS), but it will use the software
-	  configuration if you specify <literal>-1</literal> in the hints
-          for the interface.</para>
-
-	  <para>Either move the jumper on the card to a hard
-          configuration setting (altering the kernel settings if
-          necessary), or specify the IRQ as <literal>-1</literal>
-          by setting the hint <quote>hint.ed.0.irq="-1"</quote> 
-          This will tell the kernel to
-          use the soft configuration.</para>
-
-          <para>Another possibility is that your card is at IRQ 9,
-          which is shared by IRQ 2 and frequently a cause of problems
-          (especially when you have a VGA card using IRQ 2!).  You
-          should not use IRQ 2 or 9 if at all possible.</para>
-	</answer>
-      </qandaentry>
-    </qandaset>
-  </sect2>
-
+    <sect2>
+      <title>Troubleshooting Questions and Answers</title>
+
+      <qandaset>
+	<qandaentry>
+	  <question>
+	    <para>My system hangs while probing hardware during boot,
+	      or it behaves strangely during install, or the floppy
+	      drive isn't probed.</para>
+	  </question>
+	  <answer>
+	    <para>&os; 5.0 and above makes extensive use of the system
+	      ACPI service on the i386, amd64 and ia64 platforms to
+	      aid in system configuration if it's detected during
+	      boot.  Unfortunately, some bugs still exist in both the
+	      ACPI driver and within system motherboards and BIOS.
+	      The use of ACPI can be disabled by setting
+	      the <literal>hint.acpi.0.disabled</literal> hint in the
+	      third stage boot loader:</para>
+
+	    <screen>set hint.acpi.0.disabled="1"</screen>
+
+	    <para>This is reset each time the system is booted, so it
+	      is necessary to
+	      add <literal>hint.acpi.0.disabled="1"</literal> to the
+	      file
+	      <filename>/boot/loader.conf</filename>.  More
+	      information about the boot loader can be found
+	      in <xref linkend="boot-synopsis">.</para>
+	  </answer>
+	</qandaentry>
+	<qandaentry>
+	  <question>
+	    <para>I go to boot from the hard disk for the first time
+	      after installing &os;, the kernel loads and probes my
+	      hardware, but stops with messages like:</para>
+
+	    <screen>changing root device to ad1s1a panic: cannot mount root</screen>
+
+	    <para>What is wrong?  What can I do?</para>
+
+	    <para>What is this
+	      <literal>bios_drive:interface(unit,partition)kernel_name</literal>
+	      thing that is displayed with the boot help?</para>
+	  </question>
+	  <answer>
+	    <para>There is a longstanding problem in the case where
+	      the boot disk is not the first disk in the system.  The
+	      BIOS uses a different numbering scheme to &os;, and
+	      working out which numbers correspond to which is
+	      difficult to get right.</para>
+
+	    <para>In the case where the boot disk is not the first
+	      disk in the system, &os; can need some help finding it.
+	      There are two common situations here, and in both of
+	      these cases, you need to tell &os; where the root
+	      filesystem is.  You do this by specifying the BIOS disk
+	      number, the disk type and the &os; disk number for that
+	      type.</para>
+
+	    <para>The first situation is where you have two IDE disks,
+	      each configured as the master on their respective IDE
+	      busses, and wish to boot &os; from the second disk.  The
+	      BIOS sees these as disk 0 and disk 1, while &os; sees
+	      them as <devicename>ad0</devicename> and
+	      <devicename>ad2</devicename>.</para>
+
+	    <para>&os; is on BIOS disk 1, of type
+	      <literal>ad</literal> and the &os; disk number is 2, so
+	      you would say:</para>
+
+	    <screen><userinput>1:ad(2,a)kernel</userinput></screen>
+
+	    <para>Note that if you have a slave on the primary bus,
+	      the above is not necessary (and is effectively
+	      wrong).</para>
+
+	    <para>The second situation involves booting from a SCSI
+	      disk when you have one or more IDE disks in the system.
+	      In this case, the &os; disk number is lower than the
+	      BIOS disk number.  If you have two IDE disks as well as
+	      the SCSI disk, the SCSI disk is BIOS disk 2,
+	      type <literal>da</literal> and &os; disk number 0, so
+	      you would say:</para>
+
+	    <screen><userinput>2:da(0,a)kernel</userinput></screen>
+
+	    <para>To tell &os; that you want to boot from BIOS disk 2,
+	      which is the first SCSI disk in the system.  If you only
+	      had one IDE disk, you would use '1:' instead.</para>
+
+	    <para>Once you have determined the correct values to use,
+	      you can put the command exactly as you would have typed
+	      it in the <filename>/boot.config</filename> file using a
+	      standard text editor.  Unless instructed otherwise, &os;
+	      will use the contents of this file as the default
+	      response to the <literal>boot:</literal> prompt.</para>
+	  </answer>
+	</qandaentry>
+	<qandaentry>
+	  <question>
+	    <para>I go to boot from the hard disk for the first time
+	      after installing &os;, but the Boot Manager prompt just
+	      prints <literal>F?</literal> at the boot menu each time
+	      but the boot won't go any further.</para>
+	  </question>
+	  <answer>
+	    <para>The hard disk geometry was set incorrectly in the
+	      Partition editor when you installed &os;.  Go back into
+	      the partition editor and specify the actual geometry of
+	      your hard disk.  You must reinstall &os; again from the
+	      beginning with the correct geometry.</para>
+
+	    <para>If you are failing entirely in figuring out the
+	      correct geometry for your machine, here's a tip: Install
+	      a small DOS partition at the beginning of the disk and
+	      install &os; after that.  The install program will see
+	      the DOS partition and try to infer the correct geometry
+	      from it, which usually works.</para>
+
+	    <para>The following tip is no longer recommended, but is
+	      left here for reference:</para>
+
+	    <blockquote>
+	      <para>If you are setting up a truly dedicated &os;
+		server or workstation where you don't care for
+		(future) compatibility with DOS, Linux or another
+		operating system, you've also got the option to use
+		the entire disk (`A' in the partition editor),
+		selecting the non-standard option where &os; occupies
+		the entire disk from the very first to the very last
+		sector.  This will leave all geometry considerations
+		aside, but is somewhat limiting unless you're never
+		going to run anything other than &os; on a
+		disk.</para>
+	    </blockquote>
+	  </answer>
+	</qandaentry>
+	<qandaentry>
+	  <question>
+	    <para>The system finds my &man.ed.4; network card, but I
+	      keep getting device timeout errors.</para>
+	  </question>
+	  <answer>
+	    <para>Your card is probably on a different IRQ from what
+	      is specified in
+	      the <filename>/boot/device.hints</filename> file.  The
+	      ed driver does not use the `soft' configuration by
+	      default (values entered using EZSETUP in DOS), but it
+	      will use the software configuration if you
+	      specify <literal>-1</literal> in the hints for the
+	      interface.</para>
+
+	    <para>Either move the jumper on the card to a hard
+	      configuration setting (altering the kernel settings if
+	      necessary), or specify the IRQ as <literal>-1</literal>
+	      by setting the hint <quote>hint.ed.0.irq="-1"</quote>
+	      This will tell the kernel to use the soft
+	      configuration.</para>
+
+	    <para>Another possibility is that your card is at IRQ 9,
+	      which is shared by IRQ 2 and frequently a cause of
+	      problems (especially when you have a VGA card using IRQ
+	      2!).  You should not use IRQ 2 or 9 if at all
+	      possible.</para>
+	  </answer>
+	</qandaentry>
+      </qandaset>
+    </sect2>
   </sect1>
 
   <sect1 id="install-advanced">