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

Copy the "Common Installation Problems" section from the installation

Browse source 
notes to the installation chapter of the handbook.  This is basically
a verbatim copy except for changes that were necessary to make the new
text build (consisted of removing a few entities and arch=
attributes).

Subsequent commits will remove questions that (in my opinion) are no
longer relevant or recent and adjust whitespace to match the rest of
this file.
This commit is contained in:
Bruce A. Mah 2007-08-06 20:25:31 +00:00
parent 1c63a89cba
commit 3d8da60ac5
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=30601
1 changed files with 331 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

331
en_US.ISO8859-1/books/handbook/install/chapter.sgml
View file

@ -4035,6 +4035,337 @@ Please press any key to reboot.</screen>
<para>NTFS partitions can also be mounted in a similar manner
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 <quote>hint.acpi.0.disabled</quote> 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 the &os; Handbook.</para>
</answer>
</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>
<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 &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>
<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>
<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>
</sect1>
<sect1 id="install-advanced">