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

103 lines
5.7 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.3 Problems with SCSI controllers and devices</TITLE>
</HEAD>
<BODY>
<meta name="description" value="2.5.2.3 Problems with SCSI controllers and devices">
<meta name="keywords" value="gs">
<meta name="resource-type" value="document">
<meta name="distribution" value="global">
<P>
<BR> <HR><A NAME=tex2html2791 HREF="node87.html"><IMG ALIGN=BOTTOM ALT="next" SRC="next_motif.gif"></A> <A NAME=tex2html2789 HREF="node83.html"><IMG ALIGN=BOTTOM ALT="up" SRC="up_motif.gif"></A> <A NAME=tex2html2785 HREF="node85.html"><IMG ALIGN=BOTTOM ALT="previous" SRC="previous_motif.gif"></A> <A NAME=tex2html2793 HREF="node1.html"><IMG ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <A NAME=tex2html2794 HREF="node250.html"><IMG ALIGN=BOTTOM ALT="index" SRC="index_motif.gif"></A> <BR>
<B> Next:</B> <A NAME=tex2html2792 HREF="node87.html">2.5.3 Problems installing the </A>
<B>Up:</B> <A NAME=tex2html2790 HREF="node83.html">2.5.2 Hardware problems</A>
<B> Previous:</B> <A NAME=tex2html2786 HREF="node85.html">2.5.2.2 Problems recognizing hard </A>
<BR> <HR> <P>
<H3><A NAME=SECTION00452300000000000000>2.5.2.3 Problems with SCSI controllers and devices</A></H3>
<P>
<A NAME=secinstallprobshardwarescsi>&#160;</A>
<P>
<A NAME=1649>&#160;</A>
<A NAME=1650>&#160;</A>
<P>
Presented here are some of the most common problems with SCSI controllers
and devices such as CD-ROMs, hard drives, and tape drives. If you are
having problems getting Linux to recognize your drive or controller,
read on.
<P>
The Linux SCSI HOWTO (see Appendix <A HREF="node225.html#appsourcesnum">A</A>) contains much useful
information on SCSI devices in addition to that listed here. SCSI can be
particularly tricky to configure at times.
<P>
<UL><LI> <b>A SCSI device is detected at all possible ID's.</b> This is caused
by strapping the device to the same address as the controller. You need to
change the jumper settings so that the drive uses a different address from
the controller itself.
<P>
<LI> <b>Linux reports sense errors, even if the devices are known to be
error-free.</b> This can be caused by bad cables, or by bad termination. If your
SCSI bus is not terminated at both ends, you may have errors accessing SCSI
devices. When in doubt, always check your cables.
<P>
<LI> <b>SCSI devices report timeout errors.</b> This is usually caused by
a conflict with IRQ, DMA, or device addresses. Also check that interrupts
are enabled correctly on your controller.
<P>
<LI> <b>SCSI controllers using BIOS are not detected.</b> Detection of
controllers using BIOS will fail if the BIOS is disabled, or if your
controller's ``signature'' is not recognized by the kernel. See the Linux
SCSI HOWTO for more information about this.
<P>
<LI> <b>Controllers using memory mapped I/O do not work.</b> This is caused
when the memory-mapped I/O ports are incorrectly cached. Either mark the
board's address space as uncacheable in the XCMOS settings, or disable
cache altogether.
<P>
<LI> <b>When partitioning, you get a warning that ``cylinders <b>&gt;</b> 1024'', or
you are unable to boot from a partition using cylinders numbered above 1023.</b>
BIOS limits the number of cylinders to 1024, and any partition using
cylinders numbered above this won't be accessible from the BIOS. As far as
Linux is concerned, this affects only booting; once the system has booted
you should be able to access the partition. Your options are to either
boot Linux from a boot floppy, or boot from a partition using
cylinders numbered below 1024. See Section <A HREF="node78.html#secinstalllinuxlilo">2.3.7</A>
for information on creating a boot diskette or installing LILO.
<P>
<LI> <b>CD-ROM drive or other removeable media devices are not recognized
at boot time.</b> Try booting with a CD-ROM (or disk) in the drive. This is
necessary for some devices.
<P>
</UL>
<P>
If your SCSI controller is not recognized, you may need to
force hardware detection at boot time. This is particularly important for
BIOS-less SCSI controllers. Most distributions allow you to
specify the controller IRQ and shared memory address when booting the
installation media. For example, if you are using a TMC-8xx controller,
you may be able to enter
<P><TT> boot: <em>linux tmx8xx=<IMG BORDER=0 ALIGN=BOTTOM ALT="" SRC="img78.gif">,<IMG BORDER=0 ALIGN=BOTTOM ALT="" SRC="img79.gif"></em>
<P></TT>
at the LILO boot prompt, where <IMG BORDER=0 ALIGN=BOTTOM ALT="" SRC="img80.gif"> is the IRQ of controller,
and <IMG BORDER=0 ALIGN=BOTTOM ALT="" SRC="img81.gif"> is the shared memory address. Whether or not
you will be able to do this depends on the distribution of Linux you are
using; consult your documentation for details.
<P>
<A NAME=1668>&#160;</A>
<A NAME=1669>&#160;</A>
<P>
<A NAME=1670>&#160;</A>
<A NAME=1671>&#160;</A>
<P>
<BR> <HR><A NAME=tex2html2791 HREF="node87.html"><IMG ALIGN=BOTTOM ALT="next" SRC="next_motif.gif"></A> <A NAME=tex2html2789 HREF="node83.html"><IMG ALIGN=BOTTOM ALT="up" SRC="up_motif.gif"></A> <A NAME=tex2html2785 HREF="node85.html"><IMG ALIGN=BOTTOM ALT="previous" SRC="previous_motif.gif"></A> <A NAME=tex2html2793 HREF="node1.html"><IMG ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <A NAME=tex2html2794 HREF="node250.html"><IMG ALIGN=BOTTOM ALT="index" SRC="index_motif.gif"></A> <BR>
<B> Next:</B> <A NAME=tex2html2792 HREF="node87.html">2.5.3 Problems installing the </A>
<B>Up:</B> <A NAME=tex2html2790 HREF="node83.html">2.5.2 Hardware problems</A>
<B> Previous:</B> <A NAME=tex2html2786 HREF="node85.html">2.5.2.2 Problems recognizing hard </A>
<BR> <HR> <P>
<BR> <HR>
<P><ADDRESS>
<I>Matt Welsh <BR>
mdw@sunsite.unc.edu</I>
</ADDRESS>
</BODY>