Files
oldlinux-files/docs/Install-Guide/install-guide-2.2.2/node85.html
2024-02-19 00:23:35 -05:00

110 lines
6.0 KiB
HTML

<!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.2.2 Problems recognizing hard drive or controller</TITLE>
</HEAD>
<BODY>
<meta name="description" value="2.5.2.2 Problems recognizing hard drive or controller">
<meta name="keywords" value="gs">
<meta name="resource-type" value="document">
<meta name="distribution" value="global">
<P>
<BR> <HR><A NAME=tex2html2781 HREF="node86.html"><IMG ALIGN=BOTTOM ALT="next" SRC="next_motif.gif"></A> <A NAME=tex2html2779 HREF="node83.html"><IMG ALIGN=BOTTOM ALT="up" SRC="up_motif.gif"></A> <A NAME=tex2html2773 HREF="node84.html"><IMG ALIGN=BOTTOM ALT="previous" SRC="previous_motif.gif"></A> <A NAME=tex2html2783 HREF="node1.html"><IMG ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <A NAME=tex2html2784 HREF="node250.html"><IMG ALIGN=BOTTOM ALT="index" SRC="index_motif.gif"></A> <BR>
<B> Next:</B> <A NAME=tex2html2782 HREF="node86.html">2.5.2.3 Problems with SCSI </A>
<B>Up:</B> <A NAME=tex2html2780 HREF="node83.html">2.5.2 Hardware problems</A>
<B> Previous:</B> <A NAME=tex2html2774 HREF="node84.html">2.5.2.1 Isolating hardware problems</A>
<BR> <HR> <P>
<H3><A NAME=SECTION00452200000000000000>2.5.2.2 Problems recognizing hard drive or controller</A></H3>
<P>
<A NAME=1618>&#160;</A>
<P>
When Linux boots, you should see a series of messages on your screen such
as:
<P><TT> Console: colour EGA+ 80x25, 8 virtual consoles <BR>
Serial driver version 3.96 with no serial options enabled <BR>
tty00 at 0x03f8 (irq = 4) is a 16450 <BR>
tty03 at 0x02e8 (irq = 3) is a 16550A <BR>
lp_init: lp1 exists (0), using polling driver <BR>
...
<P></TT>
Here, the kernel is detecting the various hardware devices present on your
system. At some point, you should see the line
<P><TT> Partition check:
<P></TT>
followed by a list of recognized partitions, for example:
<P><TT> Partition check: <BR>
hda: hda1 hda2 <BR>
hdb: hdb1 hdb2 hdb3
<P></TT>
If, for some reason, your drives or partitions are not recognized, then
you will not be able to access them in any way.
<P>
There are several things that can cause this to happen:
<UL><LI> <b>Hard drive or controller not supported.</b> If you are using a
hard drive controller (IDE, SCSI, or otherwise) that is not supported by
Linux, the kernel will not recognize your partitions at boot time.
<A NAME=1627>&#160;</A>
<P>
<LI> <b>Drive or controller improperly configured.</b>
Even if your controller is supported by Linux, it may not be configured
correctly. (This is particularly a problem for SCSI controllers; most
non-SCSI controllers should work fine without any additional configuration).
<P>
Refer to the documentation for your hard drive and/or controller for
information on solving these kinds of problems. In particular, many hard
drives will need to have a jumper set if they are to be used as a ``slave''
drive (for example, as the second hard drive). The acid test for this
kind of condition is to boot up MS-DOS, or some other operating system,
known to work with your drive and controller. If you can access the drive
and controller from another operating system, then it is not a problem with
your hardware configuration.
<P>
See Section <A HREF="node84.html#secinstallprobshardwareconflicts">2.5.2.1</A>, above, for
information on resolving possible device conflicts, and
Section <A HREF="node86.html#secinstallprobshardwarescsi">2.5.2.3</A>, below, for information on
configuring SCSI devices.
<P>
<LI> <b>Controller properly configured, but not detected.</b>
Some BIOS-less SCSI controllers require the user to specify information about
the controller at boot time.
Section <A HREF="node86.html#secinstallprobshardwarescsi">2.5.2.3</A>, below, describes how to
force hardware detection for these controllers.
<P>
<LI> <b>Hard drive geometry not recognized.</b> Some systems, such as
the IBM PS/ValuePoint, do not store hard drive geometry information in
the CMOS memory, where Linux expects to find it. Also, certain SCSI
controllers need to be told where to find drive geometry in order for
Linux to recognize the layout of your drive.
<P>
Most distributions provide a bootup option to specify the
drive geometry. In general, when booting the installation
media, you can specify the drive geometry at the LILO boot prompt with
a command such as:
<P><TT> boot: <em>linux hd=<IMG BORDER=0 ALIGN=BOTTOM ALT="" SRC="img72.gif">,<IMG BORDER=0 ALIGN=BOTTOM ALT="" SRC="img73.gif">,<IMG BORDER=0 ALIGN=BOTTOM ALT="" SRC="img74.gif"></em>
<P></TT>
where <IMG BORDER=0 ALIGN=BOTTOM ALT="" SRC="img75.gif">, <IMG BORDER=0 ALIGN=BOTTOM ALT="" SRC="img76.gif">, and <IMG BORDER=0 ALIGN=BOTTOM ALT="" SRC="img77.gif"> correspond
to the number of cylinders, heads, and sectors per track for your hard
drive.
<P>
After installing the Linux software, you will be able to install LILO,
allowing you to boot from the hard drive. At that time, you can specify the
drive geometry to the LILO installation procedure, making it unnecessary to
enter the drive geometry each time you boot. See Chapter <A HREF="node155.html#chapsysadmnum">4</A>
for more about LILO.
<P>
</UL>
<P>
<A NAME=1644>&#160;</A>
<P>
<BR> <HR><A NAME=tex2html2781 HREF="node86.html"><IMG ALIGN=BOTTOM ALT="next" SRC="next_motif.gif"></A> <A NAME=tex2html2779 HREF="node83.html"><IMG ALIGN=BOTTOM ALT="up" SRC="up_motif.gif"></A> <A NAME=tex2html2773 HREF="node84.html"><IMG ALIGN=BOTTOM ALT="previous" SRC="previous_motif.gif"></A> <A NAME=tex2html2783 HREF="node1.html"><IMG ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <A NAME=tex2html2784 HREF="node250.html"><IMG ALIGN=BOTTOM ALT="index" SRC="index_motif.gif"></A> <BR>
<B> Next:</B> <A NAME=tex2html2782 HREF="node86.html">2.5.2.3 Problems with SCSI </A>
<B>Up:</B> <A NAME=tex2html2780 HREF="node83.html">2.5.2 Hardware problems</A>
<B> Previous:</B> <A NAME=tex2html2774 HREF="node84.html">2.5.2.1 Isolating hardware problems</A>
<BR> <HR> <P>
<BR> <HR>
<P><ADDRESS>
<I>Matt Welsh <BR>
mdw@sunsite.unc.edu</I>
</ADDRESS>
</BODY>