d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Put the Troubleshooting chapter out of its misery.

Browse Source
This commit is contained in:
jfieber 1997-05-01 03:06:32 +00:00
parent f5455ee885
commit ce745e2533
4 changed files with 4 additions and 76 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
share/doc/handbook/Makefile
View File

@ -1,4 +1,4 @@
# $Id$
# $Id: Makefile,v 1.23 1997/02/22 12:58:05 peter Exp $
SRCS= authors.sgml basics.sgml bibliography.sgml boothelp.sgml
SRCS+= booting.sgml contrib.sgml crypt.sgml ctm.sgml current.sgml cvsup.sgml
@ -13,6 +13,6 @@ SRCS+= porting.sgml ports.sgml ppp.sgml printing.sgml
SRCS+= quotas.sgml relnotes.sgml routing.sgml
SRCS+= serial.sgml scsi.sgml sections.sgml sio.sgml skey.sgml slipc.sgml
SRCS+= slips.sgml stable.sgml submitters.sgml sup.sgml synching.sgml
SRCS+= term.sgml troubleshooting.sgml userppp.sgml uart.sgml linuxemu.sgml
SRCS+= term.sgml userppp.sgml uart.sgml linuxemu.sgml
.include <bsd.sgml.mk>

4
share/doc/handbook/handbook.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id: handbook.sgml,v 1.68 1997/02/22 12:58:34 peter Exp $ -->
<!-- $Id: handbook.sgml,v 1.69 1997/04/08 00:47:59 jfieber Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN" [
@ -133,7 +133,6 @@ name="FreeBSD FTP server"> or one of the numerous
&routing;
&nfs;
&diskless;
<sect><heading>* Yellow Pages/NIS</heading>
&isdn;
&mail;
@ -145,7 +144,6 @@ name="FreeBSD FTP server"> or one of the numerous
&stable;
&synching;
&submitters;
&troubleshooting;
&kerneldebug;
&kernelopts;
&linuxemu;

3
share/doc/handbook/sections.sgml
View File

@ -1,4 +1,4 @@
<!-- $Id$ -->
<!-- $Id: sections.sgml,v 1.22 1997/02/22 12:59:19 peter Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!-- Entities containing all the pieces of the handbook are -->
@ -57,6 +57,5 @@
<!ENTITY submitters SYSTEM "submitters.sgml">
<!ENTITY sup SYSTEM "sup.sgml">
<!ENTITY synching SYSTEM "synching.sgml">
<!ENTITY troubleshooting SYSTEM "troubleshooting.sgml">
<!ENTITY uart SYSTEM "uart.sgml">
<!ENTITY userppp SYSTEM "userppp.sgml">

69
share/doc/handbook/troubleshooting.sgml
View File

@ -1,69 +0,0 @@
<!-- $Id$ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Troubleshooting<label id="troubleshooting"></heading>
<p>The following tips and tricks may help you turn a
failing (or failed) installation attempt into a success.
Please read them carefully.
<sect>
<heading>Hardware conflict or misconfiguration</heading>
<p><descrip>
<tag>Problem:</tag> A device is conflicting with
another or does not match the kernel's compiled-in IRQ or
address.
<tag>Cause:</tag> While most device drivers in
FreeBSD are now smart enough to match themselves to your
hardware settings dynamically, there are a few that still
require fairly rigid configuration parameters to be
compiled in (and matched by the hardware) before they will
work. We are working hard to eliminate as many of these
last hold-outs as we can, but it is not always as easy as
it looks.
<tag>Solution:</tag> There are several possible
solutions. The first, and easiest, is to boot the kernel
with the <tt>-c</tt> flag. When you see the initial boot prompt
(from floppy or hard disk), type:
<tscreen><verb>
/kernel -c
</verb></tscreen>
This will boot just past the memory sizing code and then
drop into a dynamic kernel configuration utility. Type
`<tt>?</tt>' at the prompt to see a list of commands.
You can use this utility to reset the IRQ, memory
address, IO address or a number of other device
configuration parameters. You can also disable a device
entirely if it is causing problems for other devices you would
much rather have work.
Another solution is, obviously, to remove the offending
hardware or simply strip the system down to the bare
essentials until the problem (hopefully) goes away. Once
you are up, you can do the same thing mentioned
above---compile a kernel more suited to your hardware, or
incrementally try to figure out what it was about your
original hardware configuration that did not work.
</descrip>
<sect>
<heading>When I boot for the first time, it still looks for
/386bsd!</heading>
<p>Cause: You still have the old FreeBSD 1.x boot blocks on
your boot partition.
Solution: You should re-enter the installation process,
invoke the (F)disk editor and chose the (W)rite option.
This will not hurt an existing installation and will make
sure that the new boot blocks get written to the drive.
If you are installing for the first time, do not forget to
(W)rite out your new boot blocks! :-)