add directory docs
This commit is contained in:
gohigh
172
docs/Install-Guide/install-guide-2.2.2/node82.html
Normal file
172
docs/Install-Guide/install-guide-2.2.2/node82.html
Normal file
@@ -0,0 +1,172 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3O//DTD W3 HTML 2.0//EN">
|
||||
<!Converted with LaTeX2HTML 95.1 (Fri Jan 20 1995) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds >
|
||||
<HEAD>
|
||||
<TITLE>2.5.1 Problems with booting the installation media</TITLE>
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<meta name="description" value="2.5.1 Problems with booting the installation media">
|
||||
<meta name="keywords" value="gs">
|
||||
<meta name="resource-type" value="document">
|
||||
<meta name="distribution" value="global">
|
||||
<P>
|
||||
<BR> <HR><A NAME=tex2html2742 HREF="node83.html"><IMG ALIGN=BOTTOM ALT="next" SRC="next_motif.gif"></A> <A NAME=tex2html2740 HREF="node81.html"><IMG ALIGN=BOTTOM ALT="up" SRC="up_motif.gif"></A> <A NAME=tex2html2734 HREF="node81.html"><IMG ALIGN=BOTTOM ALT="previous" SRC="previous_motif.gif"></A> <A NAME=tex2html2744 HREF="node1.html"><IMG ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <A NAME=tex2html2745 HREF="node250.html"><IMG ALIGN=BOTTOM ALT="index" SRC="index_motif.gif"></A> <BR>
|
||||
<B> Next:</B> <A NAME=tex2html2743 HREF="node83.html">2.5.2 Hardware problems</A>
|
||||
<B>Up:</B> <A NAME=tex2html2741 HREF="node81.html">2.5 Running Into Trouble</A>
|
||||
<B> Previous:</B> <A NAME=tex2html2735 HREF="node81.html">2.5 Running Into Trouble</A>
|
||||
<BR> <HR> <P>
|
||||
<H2><A NAME=SECTION00451000000000000000>2.5.1 Problems with booting the installation media</A></H2>
|
||||
<P>
|
||||
<A NAME=secinstallprobsbooting> </A>
|
||||
<P>
|
||||
<A NAME=1544> </A>
|
||||
<A NAME=1545> </A>
|
||||
<P>
|
||||
When attempting to boot the installation media for the first time, you
|
||||
may encounter a number of problems. These are listed below.
|
||||
Note that the following problems are <em>not</em> related to booting your
|
||||
newly-installed Linux system. See
|
||||
Section <A HREF="node88.html#secinstallprobspostinstall">2.5.4</A>
|
||||
for information on these kinds of pitfalls.
|
||||
<P>
|
||||
<UL><LI> <b>Floppy or media error when attempting to boot.</b>
|
||||
<P>
|
||||
The most popular
|
||||
cause for this kind of problem is a corrupt boot floppy. Either the
|
||||
floppy is physically damaged, in which case you should re-create the
|
||||
disk with a <em>brand new</em> floppy, or the data on the floppy is bad,
|
||||
in which case you should verify that you downloaded and transferred the
|
||||
data to the floppy correctly. In many cases, simply re-creating the boot
|
||||
floppy will solve your problems. Retrace your steps and try again.
|
||||
<P>
|
||||
If you received your boot floppy from a mail order vendor or some other
|
||||
distributor, instead of downloading and creating it yourself, contact the
|
||||
distributor and ask for a new boot floppy---but only after verifying that
|
||||
this is indeed the problem.
|
||||
<P>
|
||||
<LI> <b>System ``hangs'' during boot or after booting.</b>
|
||||
<P>
|
||||
After the installation
|
||||
media boots, you will see a number of messages from the kernel itself,
|
||||
indicating which devices were detected and configured. After this, you will
|
||||
usually be presented with a login prompt, allowing you to proceed with
|
||||
installation (some distributions instead drop you right into an installation
|
||||
program of some kind). The system may appear to ``hang'' during several of
|
||||
these steps. During all of these steps, be patient; loading
|
||||
software from floppy is very slow. In many cases, the system has not
|
||||
hung at all, but is merely taking a long time. Verify that there is no
|
||||
drive or system activity for at least several minutes before assuming that
|
||||
the system is hung.
|
||||
<OL><A NAME=1553> </A>
|
||||
<LI> After booting from the <tt>LILO</tt> prompt, the system must load the
|
||||
kernel image from floppy. This may take several seconds; you will know
|
||||
that things are going well if the floppy drive light is still on.
|
||||
<P>
|
||||
<LI> While the kernel boots, SCSI devices must be probed for. If you do
|
||||
not have any SCSI devices installed, the system will ``hang'' for up to 15
|
||||
seconds while the SCSI probe continues; this usually occurs after the line
|
||||
<P><TT> lp_init: lp1 exists (0), using polling driver
|
||||
<P></TT>
|
||||
appears on your screen.
|
||||
<P>
|
||||
<LI> After the kernel is finished booting, control is transferred to the
|
||||
system bootup files on the floppy. Finally, you will be presented with
|
||||
a login prompt, or be dropped into an installation program. If you are
|
||||
presented with a login prompt such as
|
||||
<P><TT> Linux login:
|
||||
<P></TT>
|
||||
you should then login (usually as <tt>root</tt> or <tt>install</tt>---this varies
|
||||
with each distribution). After entering the username, the system may
|
||||
pause for 20 seconds or more while the installation program or shell is
|
||||
being loaded from floppy. Again, the floppy drive light should be on.
|
||||
Don't assume that the system is hung.
|
||||
<P>
|
||||
</OL>
|
||||
<P>
|
||||
Any of the above items may be the source of your problem. However,
|
||||
it is possible that
|
||||
the system actually may ``hang'' while booting, which can be due
|
||||
to several causes. First of all, you may not have enough available RAM
|
||||
to boot the installation media. (See the following item for information
|
||||
on disabling the ramdisk to free up memory.)
|
||||
<P>
|
||||
The cause of many system hangs is hardware incompatibility.
|
||||
Section <A HREF="node30.html#secintrohardware">1.8</A> in the last chapter presented an
|
||||
overview of
|
||||
supported hardware under Linux. Even if your hardware is supported, you may
|
||||
run into problems with incompatible hardware configurations which
|
||||
are causing the system to hang. See
|
||||
Section <A HREF="node83.html#secinstallprobshardware">2.5.2</A>, below, for a discussion of
|
||||
hardware incompatibilities.
|
||||
<P>
|
||||
<LI> <b>System reports out of memory errors while attempting to
|
||||
boot or install the software.</b>
|
||||
<P>
|
||||
This item
|
||||
deals with the amount of RAM that you have available. On systems
|
||||
with 4 megabytes of RAM or less, you may run into trouble booting the
|
||||
installation media or installing the software itself. This is because
|
||||
many distributions use a ``ramdisk'', which is a filesystem loaded
|
||||
directly into RAM, for operations while using the installation media.
|
||||
The entire image of the installation boot floppy, for example, may be
|
||||
loaded into a ramdisk, which may require more than a megabyte of RAM.
|
||||
<P>
|
||||
The solution to this problem is to disable the ramdisk option when
|
||||
booting the install media. Each release has a different procedure for
|
||||
doing this; on the SLS release, for example, you type ``<tt>floppy</tt>''
|
||||
at the LILO prompt when booting the <tt>a1</tt> disk.
|
||||
See your distribution's documentation for details.
|
||||
<P>
|
||||
You may not see an ``out of memory'' error when attempting to boot or install
|
||||
the software; instead, the system may unexpectedly hang, or
|
||||
fail to boot. If your system hangs, and none of the
|
||||
explanations in the previous section seem to be the cause, try disabling
|
||||
the ramdisk.
|
||||
<P>
|
||||
Keep in mind that Linux itself requires at least 2 megabytes of RAM to
|
||||
run at all; some distributions of Linux require 4 megabytes or more.
|
||||
<P>
|
||||
<LI> <b>The system reports an error such as ``<tt>permission denied</tt>''
|
||||
or ``<tt>file not found</tt>'' while booting.</b>
|
||||
<P>
|
||||
This is an indication that your installation bootup media is corrupt. If you
|
||||
attempt to boot from the installation media (and you're sure that you're
|
||||
doing everything correctly), you should not see any errors such as this.
|
||||
Contact the distributor of your Linux software and find out about the problem,
|
||||
and perhaps obtain another copy of the boot media if necessary. If you
|
||||
downloaded the bootup disk yourself, try re-creating the bootup disk, and
|
||||
see if this solves your problem.
|
||||
<P>
|
||||
<LI> <b>The system reports the error
|
||||
``<tt>VFS: Unable to mount root</tt>'' when booting.</b>
|
||||
<P>
|
||||
This error message means that the root filesystem (found on the boot
|
||||
media itself), could not be found. This means that either your boot
|
||||
media is corrupt in some way, or that you are
|
||||
not booting the system correctly.
|
||||
<P>
|
||||
For example, many CD-ROM distributions require that you have the CD-ROM
|
||||
in the drive when booting. Also be sure that the CD-ROM drive is on, and
|
||||
check for any activity. It's also possible that the system is not locating
|
||||
your CD-ROM drive at boot time; see
|
||||
Section <A HREF="node83.html#secinstallprobshardware">2.5.2</A> for more information.
|
||||
<P>
|
||||
If you're sure that you are booting the system correctly, then your
|
||||
bootup media may indeed be corrupt. This is a very uncommon problem, so
|
||||
try other solutions before attempting to use another boot floppy or tape.
|
||||
<P>
|
||||
</UL>
|
||||
<P>
|
||||
<A NAME=1572> </A>
|
||||
<A NAME=1573> </A>
|
||||
<P>
|
||||
<BR> <HR><A NAME=tex2html2742 HREF="node83.html"><IMG ALIGN=BOTTOM ALT="next" SRC="next_motif.gif"></A> <A NAME=tex2html2740 HREF="node81.html"><IMG ALIGN=BOTTOM ALT="up" SRC="up_motif.gif"></A> <A NAME=tex2html2734 HREF="node81.html"><IMG ALIGN=BOTTOM ALT="previous" SRC="previous_motif.gif"></A> <A NAME=tex2html2744 HREF="node1.html"><IMG ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <A NAME=tex2html2745 HREF="node250.html"><IMG ALIGN=BOTTOM ALT="index" SRC="index_motif.gif"></A> <BR>
|
||||
<B> Next:</B> <A NAME=tex2html2743 HREF="node83.html">2.5.2 Hardware problems</A>
|
||||
<B>Up:</B> <A NAME=tex2html2741 HREF="node81.html">2.5 Running Into Trouble</A>
|
||||
<B> Previous:</B> <A NAME=tex2html2735 HREF="node81.html">2.5 Running Into Trouble</A>
|
||||
<BR> <HR> <P>
|
||||
<BR> <HR>
|
||||
<P><ADDRESS>
|
||||
<I>Matt Welsh <BR>
|
||||
mdw@sunsite.unc.edu</I>
|
||||
</ADDRESS>
|
||||
</BODY>
|
||||
Reference in New Issue
Block a user