aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce A. Mah <bmah@FreeBSD.org>2007-08-06 20:38:42 +0000
committerBruce A. Mah <bmah@FreeBSD.org>2007-08-06 20:38:42 +0000
commit798013c38a76cedaae8e98ad3d7e0025c351b94a (patch)
tree2af55b2ecb06554df2b3b03878df94df5dbb2f71
parent3d8da60ac53b17688f60aa6cd41a8ccfdaf50089 (diff)
Notes
-rw-r--r--en_US.ISO8859-1/books/handbook/install/chapter.sgml171
1 files changed, 0 insertions, 171 deletions
diff --git a/en_US.ISO8859-1/books/handbook/install/chapter.sgml b/en_US.ISO8859-1/books/handbook/install/chapter.sgml
index e52c57c5e0..34a401e5b6 100644
--- a/en_US.ISO8859-1/books/handbook/install/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/install/chapter.sgml
@@ -4066,29 +4066,6 @@ Please press any key to reboot.</screen>
</qandaentry>
<qandaentry>
<question>
- <para>My legacy ISA device used to be recognized in previous versions
- of &os;, but now it's not. What happened?</para>
- </question>
- <answer>
- <para>Some device drivers, like matcd, were removed over time due to
- lack of maintainership or other reasons. Others still exist but
- are disabled because of their intrusive hardware probe routines.
- The following ISA device drivers fall into this category and can
- re-enabled from the third stage boot loader: aha, ahv, aic, bt, ed,
- cs, sn, ie, fe, le, and lnc. To do this, stop the loader during
- it's 10 second countdown and enter the following at the
- prompt:</para>
-
- <screen>unset hint.foo.0.disabled</screen>
-
- <para>where <replaceable>foo</replaceable> is the name of the driver
- to re-enable. This can be set permanently by editing the file
- <filename>/boot/device.hints</filename> and removing the appropriate
- <quote>disabled</quote> entry.</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>
@@ -4191,23 +4168,6 @@ Please press any key to reboot.</screen>
</qandaentry>
<qandaentry>
<question>
- <para>The &man.mcd.4; driver keeps thinking that it has
- found a device and this stops my Intel EtherExpress card
- from working.</para>
- </question>
- <answer>
- <para>Set the hints
- <quote>hint.mcd.0.disabled="1"</quote> and
- <quote>hint.mcd.1.disabled="1"</quote>
- in the third stage boot loader to disable the probing
- of the <devicename>mcd0</devicename> and
- <devicename>mcd1</devicename> devices. Generally speaking,
- you should only leave the devices that you will be using
- enabled in your kernel.</para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
<para>The system finds my &man.ed.4; network card, but I
keep getting device timeout errors.</para>
</question>
@@ -4232,137 +4192,6 @@ Please press any key to reboot.</screen>
should not use IRQ 2 or 9 if at all possible.</para>
</answer>
</qandaentry>
- <qandaentry>
- <question>
- <para>I booted the install floppy on my IBM ThinkPad (tm)
- laptop, and the keyboard is all messed up.</para>
- </question>
- <answer>
- <para>Older IBM laptops use a non-standard keyboard
- controller, so you must tell the keyboard driver (atkbd0) to
- go into a special mode which works on the ThinkPads. Set the
- hint <quote>hint.atkbd.0.flags="4"</quote> and it should work
- fine.</para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>My system can not find my Intel EtherExpress 16 card.</para>
- </question>
- <answer>
- <para>You must set your Intel EtherExpress 16 card to be
- memory mapped at address 0xD0000, and set the amount of
- mapped memory to 32K using the Intel supplied
- <filename>softset.exe</filename> program.</para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>When installing on an EISA HP Netserver, my on-board
- AIC-7xxx SCSI controller isn't detected.</para>
- </question>
- <answer>
- <para>This is a known problem, and will hopefully be fixed
- in the future. In order to get your system installed at
- all, set the hint <quote>hw.eisa_slots="12"</quote> in the
- third stage loader.</para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>I have a Panasonic AL-N1 or Rios Chandler Pentium
- machine and I find that the system hangs before ever getting
- into the installation now.</para>
- </question>
- <answer>
- <para>Your machine doesn't like the new
- <literal>i586_copyout</literal> and
- <literal>i586_copyin</literal> code for some reason. To
- disable this, set the hint <quote>hint.npx.0.flags="1"</quote></para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>I have this CMD640 IDE controller that is said to be
- broken.</para>
- </question>
- <answer>
- <para>&os; does not support this controller.</para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>On a Compaq Aero notebook, I get the message <quote>No
- floppy devices found! Please check ...</quote> when trying to
- install from floppy.</para>
- </question>
- <answer>
- <para>With Compaq being always a little different from other
- systems, they do not announce their floppy drive in the CMOS
- RAM of an Aero notebook. Therefore, the floppy disk driver
- assumes there is no drive configured. Set the hint
- <quote>hint.fdc.0.flags="1"</quote>
- This pretends the existence of the first floppy drive (as a
- 1.44 MB drive) to the driver without asking the CMOS at
- all.</para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>When installing on a Dell Poweredge XE, Dell
- proprietary RAID controller DSA (Dell SCSI Array) isn't
- recognized.</para>
- </question>
- <answer>
- <para>Configure the DSA to use AHA-1540 emulation using EISA
- configuration utility. After that &os; detects the DSA
- as an Adaptec AHA-1540 SCSI controller, with irq 11 and port
- 340. Under emulation mode system will use DSA RAID disks,
- but you cannot use DSA-specific features such as watching
- RAID health.</para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>I have an IBM EtherJet PCI card, it is detected by the
- &man.fxp.4; driver correctly, but the lights on the card don't
- come on and it doesn't connect to the network.</para>
- </question>
- <answer>
- <para>We don't understand why this happens. Neither do IBM
- (we asked them). The card is a standard Intel EtherExpress
- Pro/100 with an IBM label on it, and these cards normally
- work just fine. You may see these symptoms only in some IBM
- Netfinity servers. The only solution is to install a
- different Ethernet adapter.</para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>When I configure the network during installation on an
- IBM Netfinity 3500, the system freezes.</para>
- </question>
- <answer>
- <para>There is a problem with the onboard Ethernet in the
- Netfinity 3500 which we have not been able to identify at
- this time. It may be related to the SMP features of the
- system being misconfigured. You will have to install
- another Ethernet adapter and avoid attempting to configure
- the onboard adapter at any time.</para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>When I install onto a drive managed by a Mylex PCI
- RAID controller, the system fails to boot (eg. with a
- <literal>read error</literal> message).</para>
- </question>
- <answer>
- <para>There is a bug in the Mylex driver which results in it
- ignoring the <quote>8GB</quote> geometry mode setting in the
- BIOS. Use the 2GB mode instead.</para>
- </answer>
- </qandaentry>
</qandaset>
</sect2>