os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Ooops, somehow the HP Netserver entry made it here twice.

Browse source
This commit is contained in:
Joerg Wunsch 1997-03-12 19:14:26 +00:00
parent 1e2515f400
commit 302d932d4a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=1289
1 changed files with 2 additions and 38 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

40
FAQ/FAQ.sgml
View file

@ -1,5 +1,5 @@
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
<!-- $Id: FAQ.sgml,v 1.35 1997-03-12 19:04:07 joerg Exp $ -->
<!-- $Id: FAQ.sgml,v 1.36 1997-03-12 19:14:26 joerg 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: 1997-03-12 19:04:07 $
<date>$Date: 1997-03-12 19:14:26 $
<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.
@ -1434,42 +1434,6 @@ quit
Hopefully, future version will have a proper fix for this problem.
<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="../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>