install-start.html

FreeBSD操作系统的详细使用手册

<p>Because of this, the first thing you have the opportunity to do when installing
FreeBSD is look at the list of drivers that are configured into the kernel, and either
disable some of them, if you do not own that device, or confirm (and alter) the driver's
configuration if you do own the device but the defaults are wrong.</p>

<p>This probably sounds much more complicated than it actually is.</p>

<p><a href="install-start.html#KERNEL-CONFIG">Figure 2-1</a> shows the first kernel
configuration menu. We recommend that you choose the <span class="GUIMENUITEM">Start
kernel configuration in full-screen visual mode</span> option, as it presents the easiest
interface for the new user.</p>

<div class="FIGURE"><a id="KERNEL-CONFIG" name="KERNEL-CONFIG"></a>
<p><b>Figure 2-1. Kernel Configuration Menu</b></p>

<p><img src="install/userconfig.png" /></p>
</div>

<p>The kernel configuration screen (<a href="install-start.html#FIG-USERCONFIG">Figure
2-2</a>) is then divided into four sections:</p>

<ol type="1">
<li>
<p>A collapsible list of all the drivers that are currently marked as ``active'',
subdivided into groups such as <var class="LITERAL">Storage</var>, and <var
class="LITERAL">Network</var>. Each driver is shown as a description, its two or three
letter driver name, and the IRQ and memory port used by that driver. In addition, if an
active driver conflicts with another active driver then <var class="LITERAL">CONF</var>
is shown next to the driver name. This section also shows the total number of conflicting
drivers that are currently active.</p>
</li>

<li>
<p>Drivers that have been marked inactive. They remain in the kernel, but they will not
probe for their device when the kernel starts. These are subdivided into groups in the
same way as the active driver list.</p>
</li>

<li>
<p>More detail about the currently selected driver, including its IRQ and memory port
address.</p>
</li>

<li>
<p>Information about the keystrokes that are valid at this point in time.</p>
</li>
</ol>

<div class="FIGURE"><a id="FIG-USERCONFIG" name="FIG-USERCONFIG"></a>
<p><b>Figure 2-2. The Kernel Device Configuration Visual Interface</b></p>

<p><img src="install/userconfig2.png" /></p>
</div>

<p>Do not worry if any conflicts are listed, it is to be expected; all the drivers are
enabled, and as has already been explained, some of them will conflict with one
another.</p>

<p>You now have to work through the list of drivers, resolving the conflicts.</p>

<div class="PROCEDURE">
<p><b>Resolving Driver Conflicts</b></p>

<ol type="1">
<li>
<p>Press <b class="KEYCAP">X</b>. This will completely expand the list of drivers, so you
can see all of them. You will need to use the arrow keys to scroll back and forth through
the active driver list.</p>

<p><a href="install-start.html#HARDWARE-CONFLICTS">Figure 2-3</a> shows the result of
pressing <b class="KEYCAP">X</b>.</p>

<div class="FIGURE"><a id="HARDWARE-CONFLICTS" name="HARDWARE-CONFLICTS"></a>
<p><b>Figure 2-3. Expanded Driver List</b></p>

<p><img src="install/hdwrconf.png" /></p>
</div>
</li>

<li>
<p>Disable all the drivers for devices that you do not have. To disable a driver,
highlight it with the arrow keys and press <b class="KEYCAP">Del</b>. The driver will be
moved to the <var class="LITERAL">Inactive Drivers</var> list.</p>

<p>If you inadvertently disable a device that you need then press <b
class="KEYCAP">Tab</b> to switch to the <var class="LITERAL">Inactive Drivers</var> list,
select the driver that you disabled, and press <b class="KEYCAP">Enter</b> to move it
back to the active list.</p>

<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> Do not disable <tt class="DEVICENAME">sc0</tt>. This controls the
screen, and you will need this unless you are installing over a serial cable.</p>
</blockquote>
</div>

<div class="WARNING">
<blockquote class="WARNING">
<p><b>Warning:</b> Only disable <tt class="DEVICENAME">atkbd0</tt> if you are using a USB
keyboard. If you have a normal keyboard then you must keep <tt
class="DEVICENAME">atkbd0</tt>.</p>
</blockquote>
</div>
</li>

<li>
<p>If there are no conflicts listed then you can skip this step. Otherwise, the remaining
conflicts need to be examined. If they do not have the indication of an ``allowed
conflict'' in the message area, then either the IRQ/address for device probe will need to
be changed, <span class="emphasis"><i class="EMPHASIS">or</i></span> the IRQ/address on
the hardware will need to be changed.</p>

<p>To change the driver's configuration for IRQ and IO port address, select the device
and press <b class="KEYCAP">Enter</b>. The cursor will move to the third section of the
screen, and you can change the values. You should enter the values for IRQ and port
address that you discovered when you made your hardware inventory. Press <b
class="KEYCAP">Q</b> to finish editing the device's configuration and return to the
active driver list.</p>

<p>If you are not sure what these figures should be then you can try using <var
class="LITERAL">-1</var>. Some FreeBSD drivers can safely probe the hardware to discover
what the correct value should be, and a value of <var class="LITERAL">-1</var> configures
them to do this.</p>

<p>The procedure for changing the address on the hardware varies from device to device.
For some devices you may need to physically remove the card from your computer and adjust
jumper settings or DIP switches. Other cards may have come with a DOS floppy that
contains the programs used to reconfigure the card. In any case, you should refer to the
documentation that came with the device. This will obviously entail restarting your
computer, so you will need to boot back into the FreeBSD installation routine when you
have reconfigured the card.</p>
</li>

<li>
<p>When all the conflicts have been resolved the screen will look similar to <a
href="install-start.html#USERCONFIG-DONE">Figure 2-4</a>.</p>

<div class="FIGURE"><a id="USERCONFIG-DONE" name="USERCONFIG-DONE"></a>
<p><b>Figure 2-4. Driver Configuration With No Conflicts</b></p>

<p><img src="install/probstart.png" /></p>
</div>

<p>As you can see, the active driver list is now much smaller, with only drivers for the
hardware that actually exists being listed.</p>

<p>You can now save these changes, and move on to the next step of the install. Press <b
class="KEYCAP">Q</b> to quit the device configuration interface. This message will
appear:</p>

<pre class="SCREEN">
Save these parameters before exiting? ([Y]es/[N]o/[C]ancel)
</pre>

<p>Answer <b class="KEYCAP">Y</b> to save the parameters to memory (it will be saved to
disk if you finish the install) and the probing will start. After displaying the probe
results in white on black text <b class="APPLICATION">sysinstall</b> will start and
display its main menu (<a href="install-start.html#SYSINSTALL-MAIN">Figure 2-5</a>).</p>

<div class="FIGURE"><a id="SYSINSTALL-MAIN" name="SYSINSTALL-MAIN"></a>
<p><b>Figure 2-5. Sysinstall Main Menu</b></p>

<p><img src="install/main1.png" /></p>
</div>
</li>
</ol>
</div>
</div>

<div class="SECT2">
<h2 class="SECT2"><a id="VIEW-PROBE" name="VIEW-PROBE">2.3.3 Reviewing the Device Probe
Results</a></h2>

<p>The last few hundred lines that have been displayed on screen are stored and can be
reviewed.</p>

<p>To review the buffer, press <b class="KEYCAP">Scroll Lock</b>. This turns on scrolling
in the display. You can then use the arrow keys, or <b class="KEYCAP">PageUp</b> and <b
class="KEYCAP">PageDown</b> to view the results. Press <b class="KEYCAP">Scroll Lock</b>
again to stop scrolling.</p>

<p>Do this now, to review the text that scrolled off the screen when the kernel was
carrying out the device probes. You will see text similar to <a
href="install-start.html#INSTALL-DEV-PROBE">Figure 2-6</a>, although the precise text
will differ depending on the devices that you have in your computer.</p>

<div class="FIGURE"><a id="INSTALL-DEV-PROBE" name="INSTALL-DEV-PROBE"></a>
<p><b>Figure 2-6. Typical Device Probe Results</b></p>

<pre class="SCREEN">
avail memory = 253050880 (247120K bytes) 
Preloaded elf kernel "kernel" at 0xc0817000.
Preloaded mfs_root "/mfsroot" at 0xc0817084.
md0: Preloaded image &lt;/mfsroot&gt; 4423680 bytes at 0xc03ddcd4

md1: Malloc disk
Using $PIR table, 4 entries at 0xc00fde60
npx0: &lt;math processor&gt; on motherboard   
npx0: INT 16 interface   
pcib0: &lt;Host to PCI bridge&gt; on motherboard
pci0: &lt;PCI bus&gt; on pcib0
pcib1:&lt;VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge&gt; at device 1.0 on pci0
pci1: &lt;PCI bus&gt; on pcib1
pci1: &lt;Matrox MGA G200 AGP graphics accelerator&gt; at 0.0 irq 11
isab0: &lt;VIA 82C586 PCI-ISA bridge&gt; at device 7.0 on pci0
isa0: &lt;iSA bus&gt; on isab0
atapci0: &lt;VIA 82C586 ATA33 controller&gt; port 0xe000-0xe00f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0 &lt;VIA 83C572 USB controller&gt; port 0xe400-0xe41f irq 10 at device 7.2 on pci
0
usb0: &lt;VIA 83572 USB controller&gt; on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr1
uhub0: 2 ports with 2 removable, self powered
pci0: &lt;unknown card&gt; (vendor=0x1106, dev=0x3040) at 7.3
dc0: &lt;ADMtek AN985 10/100BaseTX&gt; port 0xe800-0xe8ff mem 0xdb000000-0xeb0003ff ir
q 11 at device 8.0 on pci0
dc0: Ethernet address: 00:04:5a:74:6b:b5
miibus0: &lt;MII bus&gt; on dc0
ukphy0: &lt;Generic IEEE 802.3u media interface&gt; on miibus0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ed0: &lt;NE2000 PCI Ethernet (RealTek 8029)&gt; port 0xec00-0xec1f irq 9 at device 10.
0 on pci0
ed0 address 52:54:05:de:73:1b, type NE2000 (16 bit)
isa0: too many dependant configs (8)
isa0: unexpected small tag 14
orm0: &lt;Option ROM&gt; at iomem 0xc0000-0xc7fff on isa0
fdc0: &lt;NEC 72065B or clone&gt; at port 0x3f0-0x3f5,0x3f7 irq 6 drq2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: &lt;1440-KB 3.5" drive&gt; on fdc0 drive 0
atkbdc0: &lt;Keyboard controller (i8042)&gt; at port 0x60,0x64 on isa0
atkbd0: &lt;AT Keyboard&gt; flags 0x1 irq1 on atkbdc0
kbd0 at atkbd0
psm0: &lt;PS/2 Mouse&gt; irq 12 on atkbdc0
psm0: model Generic PS/@ mouse, device ID 0
vga0: &lt;Generic ISA VGA&gt; at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: &lt;System console&gt; at flags 0x100 on isa0
sc0: VGA &lt;16 virtual consoles, flags=0x300&gt;
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: &lt;Parallel port&gt; at port 0x378-0x37f irq 7 on isa0
pppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/15 bytes threshold
plip0: &lt;PLIP network interface&gt; on ppbus0
ad0: 8063MB &lt;IBM-DHEA-38451&gt; [16383/16/63] at ata0-master UDMA33
acd0: CD-RW &lt;LITE-ON LTR-1210B&gt; at ata1-slave PIO4
Mounting root from ufs:/dev/md0c
/stand/sysinstall running as init on vty0
</pre>
</div>

<p>Check the probe results carefully to make sure that FreeBSD found all the devices you
expected. If a device was not found, then it will not be listed. If the device's driver
required configuring with the IRQ and port address then you should check that you entered
them correctly.</p>

<p>If you need to make changes to the UserConfig device probing, it is easy to exit the
<b class="APPLICATION">sysinstall</b> program and start over again. It is also a good way
to become more familiar with the process.</p>

<div class="FIGURE"><a id="SYSINSTALL-EXIT" name="SYSINSTALL-EXIT"></a>
<p><b>Figure 2-7. Select Sysinstall Exit</b></p>

<p><img src="install/sysinstall-exit.png" /></p>
</div>

<p>Use the arrow keys to select <span class="GUIMENUITEM">Exit Install</span> from the
Main Install Screen menu. The following message will display:</p>

<pre class="SCREEN">
                      User Confirmation Requested 
         Are you sure you wish to exit? The system will reboot 
           (be sure to remove any floppies from the drives).

                            [ Yes ]    No
</pre>

<p>The install program will start again if the CDROM is left in the drive and <span
class="GUIBUTTON">[&nbsp;Yes&nbsp;]</span> is selected.</p>

<p>If you are booting from floppies it will be necessary to remove the <tt
class="FILENAME">mfsroot.flp</tt> floppy and replace it with <tt
class="FILENAME">kern.flp</tt> before rebooting.</p>
</div>
</div>

<div class="NAVFOOTER">
<hr align="LEFT" width="100%" />
<table summary="Footer navigation table" width="100%" border="0" cellpadding="0"
cellspacing="0">
<tr>
<td width="33%" align="left" valign="top"><a href="install-pre.html"
accesskey="P">Prev</a></td>
<td width="34%" align="center" valign="top"><a href="index.html"
accesskey="H">Home</a></td>
<td width="33%" align="right" valign="top"><a href="using-sysinstall.html"
accesskey="N">Next</a></td>
</tr>

<tr>
<td width="33%" align="left" valign="top">Pre-installation Tasks</td>
<td width="34%" align="center" valign="top"><a href="install.html"
accesskey="U">Up</a></td>
<td width="33%" align="right" valign="top">Introducing Sysinstall</td>
</tr>
</table>
</div>

<p align="center"><small>This, and other documents, can be downloaded from <a
href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/</a>.</small></p>

<p align="center"><small>For questions about FreeBSD, read the <a
href="http://www.FreeBSD.org/docs.html">documentation</a> before contacting &#60;<a
href="mailto:[e-mail]">[e-mail]</a>&#62;.<br />
For questions about this documentation, e-mail &#60;<a
href="mailto:[e-mail]">[e-mail]</a>&#62;.</small></p>
</body>
</html>