DOCUMENT ID:  1030-02

SYNOPSIS:     Resolving System Halts During Installation

OS RELEASE:   2.x

PRODUCT:      Solaris x86

KEYWORDS:     resolve system hang install


DESCRIPTION:

While installing Solaris on a PC, the installation hangs after the
copyright message on the second go-around of the spinner. 


SOLUTION:

The usual cause for the installation to seemingly stop cold is usually
due to a conflict with VGA controllers that are embedded on the
motherboard itself.  The installation may not actually stop, but instead
it may transfer its output at that particular point to the on-board chip
instead. 

Workaround -

Unless the on-board VGA controller is specifically listed on our
Hardware Compatibility List for Solaris x86 version 2.x, you will need
to completely disable the VGA controller on the motherboard and install
a plug-in VGA card that is on the compatibility list. 

Resolution -

In all cases where the system hangs during normal operation, the Solaris
Hardware Compatibility List (HCL) will be your most useful tool. 

The key items that specifically need to be on the list, and hence
supported, are the main computing platform, the hard- disk controller,
the VGA card, and any network host adapters.  If you experience a system
halt, all boards other than these need to be removed from the system for
troubleshooting purposes. 

If the system halt occurs at a place other than what is described above,
follow the procedures below to troubleshoot the problem. 

-------------------------------------------------------------

The first step is to rule out hardware conflicts...

1.) Remove all plug-in cards that are not absolutely necessary for the
installation.  You may also need to temporarily remove your network
card, which is often the problem variable. 

2.) Check addressing on the remaining cards for interrupt, DMA,
shared-memory and port address conflicts to make sure that each does not
overlap with any other device. 

3.) Check the SCSI sub-system.  Make sure that you have only one hard
drive (for now) on target ID 0 and a supported CD drive at TID 6.  Also
make sure that the devices are properly terminated and that 4.8 volts DC
(or greater) exists on pin 24 of the SCSI bus.  If not the SCSI host
adapter fuse may be blown.  Consult your hardware documentation for
instructions on how to set target jumpers, how to terminate the SCSI bus
properly (very important), and where the fuse/terminator power jumpers
and diodes are.  Also make sure that each SCSI device supplies the same
parity.  (i.e.  even, odd, or none) While installing, make sure that
SCSI BIOS is enabled, that synchronous negotiation is disabled, that
disconnect/reconnect protocol is disabled, and that BIOS TRANSLATION for
drives greater than 1024 cylinders is also disabled.  Lastly, make sure
that your hard-drive (SCSI only, NOT IDE) has been low-level formatted
for the controller you are using. 


The next step is to eliminate CMOS discrepancies...

1.) Insure that at least 16 MB of ram tests properly and is accessible,
and that all CMOS settings pertaining to the amount of RAM are
consistent. 

2.) If you have a 386 (which requires a math co-processor) make sure
that CMOS sees the co-processor. 

3.) Next, disable all ROM shadowing and external memory cache. 
(Usually, these can be turned back on when the installation is
complete.)


The final step deals with the motherboard itself...

1.) Motherboard problems are not for the faint-at-heart.  You may first
wish to run a complete diagnostic on the motherboard using a
commercially available DOS utility like Check-It, Norton, or QA Plus. 
Typically, Taiwanese clone motherboards, most of which are not
supported, may have timing problems caused by inferior chip-sets that
can be masked in BIOS and hence will not present problems under DOS but
will under UNIX which, after booting, does not typically use BIOS
services.  If you run into a problem that is timing or parity related,
slow down the processor, re-seat socketed chips, and make sure any 80486
or Pentium microprocessors have their own cooling fans.  If the POST
procedure reports memory or parity errors, you can also remove the SIMMS
and clean the memory contacts with a pencil eraser.  Remove excess
eraser particles completely. 

2.) Insure that all add-in boards are secured to the card cage with the
proper screws.  If not, a severe power short could be caused by plugging
in a network, SCSI, or monitor cable, etc. 

When inside the computer, OBSERVE AT ALL TIMES, the proper static
precautions and DO NOT make any hardware changes with power applied. 

The above procedures will identify any hardware problems.  The only
other possibility is that of media, i.e.  floppy errors or grease on the
CD.  If you suspect a defective floppy disk, call Technical Support for
a replacement.  If Solaris reports that it cannot find "ufsboot", clean
the shiny part of the CD with Freon TF (Miller-Stephenson Co) and a
polyester wipe.  (Cotton or other materials will scratch the CD
surface.) Isopropyl alcohol with a low water content may be used if
freon is not available. 


DATE APPROVED: 09/12/95