1 files changed, 38 insertions, 2 deletions

diff --git a/share/doc/FAQ/FAQ.sgml b/share/doc/FAQ/FAQ.sgml
index 1ac4b9381b8d..3b2631135f5d 100644
--- a/share/doc/FAQ/FAQ.sgml
+++ b/share/doc/FAQ/FAQ.sgml
@@ -1,5 +1,5 @@
 <!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
-<!-- $Id: FAQ.sgml,v 1.14 1996/11/20 14:18:25 jfieber Exp $ -->
+<!-- $Id: FAQ.sgml,v 1.15 1996/12/06 18:19:31 jkh Exp $ -->
 
   <article>
 
@@ -7,7 +7,7 @@
 <author>Maintainer: Peter da Silva <tt><htmlurl url='mailto:pds@FreeBSD.ORG'
   name='&lt;pds@FreeBSD.ORG&gt;'></tt>
 
-<date>$Date: 1996/11/20 14:18:25 $
+<date>$Date: 1996/12/06 18:19:31 $
 <abstract>
 This is the FAQ for FreeBSD systems version 2.X  All entries are
 assumed to be relevant to FreeBSD 2.0.5+, unless otherwise noted.
@@ -1400,6 +1400,42 @@ options   PSM_NO_RESET       #don't reset mouse hardware (some laptops)
           the section <ref id="bigram" name="on 32 MB machines">. This is a
           problem that occurs with the Vesa-Local Buslogic SCSI cards.
 
+      <sect1>
+        <heading>FreeBSD does not recognise my on-board AIC-7xxx EISA SCSI in an HP Netserver</heading>
+        <p>
+	  This is basically a known problem.  The EISA on-board SCSI controller
+	  in the HP Netserver machines occupies EISA slot number 11, so all
+	  the ``true'' EISA slots are in front of it.  Alas, the address space
+	  for EISA slots >= 10 collides with the address space assigned to PCI,
+	  and FreeBSD's auto-configuration currently cannot handle this
+	  situation very well.
+
+	  So now, the best you can do is to pretend there were no address
+	  range clash :), go right ahead and edit the file
+	  <tt>/sys/i386/eisa/eisaconf.h</tt>.  Look for a line defining the
+	  macro <tt/EISA_SLOTS/, and bump the number it's defining to 12.
+	  Configure and compile a kernel, as described in the
+	  <url url="http://www.freebsd.org/handbook/kernelconfig.html"
+	  name="Handbook entry on configuring the kernel">.
+
+	  Of course, this does present you a chicken-and-egg problem when
+	  installing on such a machine.  In order to work around this
+	  problem, a special hack is available inside <em>UserConfig</em>.
+	  Do not use the ``visual'' interface, but the plain command-line
+	  interface there.  Simply type
+<verb>
+eisa 12
+quit
+</verb>
+
+	  at the prompt, and install your system as usual.  Don't forget
+	  to install the kernel source distribution, since you need to
+	  build a custom kernel, or otherwise you would have to repeat the
+	  described procedure at each boot!  <tt/dset(8)/ doesn't save this
+	  change for you.
+
+	  Hopefully, future version will have a proper fix for this problem.
+
     <sect>
       <heading>Commercial Applications</heading>