* Reword some sentences for consistency
* Place an item in <note>, clarify PID 1 in a <note> * Place a set of questions into a <qandaset> * Minor markup changes
This commit is contained in:
Chern Lee
parent
a470682281
commit
186db00629
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10815
1 changed files with 89 additions and 69 deletions
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml,v 1.45 2001/08/22 05:37:50 murray Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml,v 1.46 2001/08/30 22:44:36 logo Exp $
|
||||
-->
|
||||
|
||||
<chapter id="serialcomms">
|
||||
|
|
@ -85,11 +85,11 @@
|
|||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<para>When talking about communications data rates, the authors
|
||||
do not use the term <quote>baud</quote>. Baud refers to the
|
||||
<para>When talking about communications data rates, this section
|
||||
does not use the term <quote>baud</quote>. Baud refers to the
|
||||
number of electrical state transitions that may be made in a
|
||||
period of time, while <quote>bps</quote> (bits per second) is
|
||||
the <quote>correct</quote> term to use (at least it does not
|
||||
the <emphasis>correct</emphasis> term to use (at least it does not
|
||||
seem to bother the curmudgeons quite a much).</para>
|
||||
</sect2>
|
||||
|
||||
|
|
@ -249,7 +249,7 @@
|
|||
|
||||
<para>See the documentation that accompanied the hardware for
|
||||
specifications on the kind of port in use. A visual inspection of
|
||||
the port often works, too.</para>
|
||||
the port often works too.</para>
|
||||
</sect4>
|
||||
|
||||
<sect4 id="term-portnames">
|
||||
|
|
@ -280,7 +280,7 @@
|
|||
</itemizedlist>
|
||||
|
||||
<para>If you have connected a terminal to the first serial port
|
||||
(<devicename>COM1</devicename> in MS-DOS parlance), then you want to
|
||||
(<devicename>COM1</devicename> in MS-DOS), then you want to
|
||||
use <filename>/dev/ttyd0</filename> to refer to the terminal. If
|
||||
it is on the second serial port (also known as
|
||||
<devicename>COM2</devicename>), it is
|
||||
|
|
@ -302,8 +302,8 @@
|
|||
<quote>dumb</quote> multiport serial interface cards, such as
|
||||
the BocaBoard 1008 and 2016, as well as more
|
||||
intelligent multi-port cards such as those made by Digiboard
|
||||
and Stallion Technologies. The default kernel only looks for
|
||||
the standard COM ports, though.</para>
|
||||
and Stallion Technologies. However, the default kernel only looks
|
||||
for the standard COM ports.</para>
|
||||
|
||||
<para>To see if your kernel recognizes any of your serial ports, watch
|
||||
for messages while the kernel is booting, or use the
|
||||
|
|
@ -412,7 +412,7 @@ device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr</programlisting>
|
|||
|
||||
<para><command>MAKEDEV</command> not only creates the
|
||||
<devicename>/dev/ttyd<replaceable>N</replaceable></devicename> device
|
||||
special files, but also creates the
|
||||
special files, but also the
|
||||
<devicename>/dev/cuaa<replaceable>N</replaceable></devicename>,
|
||||
<devicename>/dev/cuaia<replaceable>N</replaceable></devicename>,
|
||||
<devicename>/dev/cuala<replaceable>N</replaceable></devicename>,
|
||||
|
|
@ -459,8 +459,8 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen>
|
|||
the default set. To make changes to the default set, you can open and
|
||||
adjust the settings of the <quote>initial state</quote> device. For
|
||||
example, to turn on <option>CLOCAL</option> mode, 8 bit communication,
|
||||
and <option>XON/XOFF</option> flow control by default for ttyd5,
|
||||
type:</para>
|
||||
and <option>XON/XOFF</option> flow control by default for
|
||||
<devicename>ttyd5</devicename>, type:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>stty -f /dev/ttyid5 clocal cs8 ixon ixoff</userinput></screen>
|
||||
|
||||
|
|
@ -506,8 +506,8 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen>
|
|||
|
||||
<indexterm><primary>terminals</primary></indexterm>
|
||||
|
||||
<para>Terminals provide a convenient and low-cost way to access the power
|
||||
of your FreeBSD system when you are not at the computer's console or on
|
||||
<para>Terminals provide a convenient and low-cost way to access
|
||||
your FreeBSD system when you are not at the computer's console or on
|
||||
a connected network. This section describes how to use terminals with
|
||||
FreeBSD.</para>
|
||||
|
||||
|
|
@ -517,13 +517,13 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen>
|
|||
<para>The original Unix systems did not have consoles. Instead, people
|
||||
logged in and ran programs through terminals that were connected to
|
||||
the computer's serial ports. It is quite similar to using a modem and
|
||||
some terminal software to dial into a remote system to do text-only
|
||||
terminal software to dial into a remote system to do text-only
|
||||
work.</para>
|
||||
|
||||
<para>Today's PCs have consoles capable of high quality graphics, but
|
||||
the ability to establish a login session on a serial port still exists
|
||||
in nearly every Unix-style operating system today; FreeBSD is no
|
||||
exception. By using a terminal attached to a unused serial port, you
|
||||
exception. By using a terminal attached to an unused serial port, you
|
||||
can log in and run any text program that you would normally run on the
|
||||
console or in an <command>xterm</command> window in the X Window
|
||||
System.</para>
|
||||
|
|
@ -676,9 +676,11 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen>
|
|||
file also contains entries for the other virtual consoles, serial ports,
|
||||
and pseudo-ttys. For a hardwired terminal, just list the serial
|
||||
port's <filename>/dev</filename> entry without the
|
||||
<filename>/dev</filename> part.</para>
|
||||
<filename>/dev</filename> part (for example,
|
||||
<devicename>/dev/ttyv0</devicename> would be listed as
|
||||
<devicename>ttyv0</devicename>).</para>
|
||||
|
||||
<para>A default FreeBSD install includes a
|
||||
<para>A default FreeBSD install includes an
|
||||
<filename>/etc/ttys</filename> file with support for the first
|
||||
four serial ports: <filename>ttyd0</filename> through
|
||||
<filename>ttyd3</filename>. If you are attaching a terminal
|
||||
|
|
@ -790,7 +792,8 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
unprivileged accounts and then use &man.su.1; or a
|
||||
similar mechanism to gain superuser privileges.</para>
|
||||
|
||||
<para>It is highly recommended that you use "insecure"
|
||||
<para>It is highly recommended that you use
|
||||
<quote>insecure</quote>
|
||||
even for terminals that are behind locked doors. It
|
||||
is quite easy to login and use <command>su</command>
|
||||
if you need superuser privileges.</para>
|
||||
|
|
@ -810,6 +813,11 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
|
||||
<screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen>
|
||||
|
||||
<note>
|
||||
<para><command>init</command> is always the first process run
|
||||
on a system, therefore it will always have PID 1.</para>
|
||||
</note>
|
||||
|
||||
<para>If everything is set up correctly, all cables are in
|
||||
place, and the terminals are powered up, then a
|
||||
<command>getty</command> process should be running on each
|
||||
|
|
@ -825,11 +833,13 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
still go wrong while setting up a terminal. Here is a list of
|
||||
symptoms and some suggested fixes.</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>No login prompt appears</term>
|
||||
<qandaset>
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>No login prompt appears</para>
|
||||
</question>
|
||||
|
||||
<listitem>
|
||||
<answer>
|
||||
<para>Make sure the terminal is plugged in and powered up. If it
|
||||
is a personal computer acting as a terminal, make sure it is
|
||||
running terminal emulation software on the correct serial
|
||||
|
|
@ -865,33 +875,37 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
you have enabled the port in <filename>/etc/ttys</filename>.
|
||||
Also remember to run <command>kill -HUP 1</command>
|
||||
after modifying the <filename>ttys</filename> file.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>Garbage appears instead of a login prompt</term>
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Garbage appears instead of a login prompt</para>
|
||||
</question>
|
||||
|
||||
<listitem>
|
||||
<answer>
|
||||
<para>Make sure the terminal and FreeBSD agree on the bps rate and
|
||||
parity settings. Check the <command>getty</command> processes
|
||||
to make sure the
|
||||
correct <replaceable>getty</replaceable> type is in use. If
|
||||
not, edit <filename>/etc/ttys</filename> and run <command>kill
|
||||
-HUP 1</command>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>Characters appear doubled; the password appears when
|
||||
typed</term>
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Characters appear doubled; the password appears when
|
||||
typed</para>
|
||||
</question>
|
||||
|
||||
<listitem>
|
||||
<answer>
|
||||
<para>Switch the terminal (or the terminal emulation software)
|
||||
from <quote>half duplex</quote> or <quote>local echo</quote> to
|
||||
<quote>full duplex.</quote></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
|
|
@ -920,7 +934,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
modems instead of terminals.</para>
|
||||
|
||||
<sect2>
|
||||
<title>External v.s. Internal Modems</title>
|
||||
<title>External vs. Internal Modems</title>
|
||||
|
||||
<para>External modems seem to be more convenient for dial-up, because
|
||||
external modems often can be semi-permanently configured via
|
||||
|
|
@ -1026,7 +1040,8 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
<screen> 4850 ?? I 0:00.09 /usr/libexec/getty V19200 ttyd0</screen>
|
||||
|
||||
<para>When a user dials the modem's line and the modems connect, the
|
||||
<acronym>CD</acronym> line is asserted by the modem. The kernel
|
||||
<acronym>CD</acronym> (Carrier Detect) line is reported by the modem.
|
||||
The kernel
|
||||
notices that carrier has been detected and completes
|
||||
<command>getty</command>'s open of the port. <command>getty</command>
|
||||
sends a <prompt>login:</prompt> prompt at the specified initial line
|
||||
|
|
@ -1093,7 +1108,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
connection should receive better interactive response from full-screen
|
||||
programs.</para>
|
||||
|
||||
<para>The authors will try to give balanced configuration information,
|
||||
<para>This section will try to give balanced configuration information,
|
||||
but is biased towards having the modem's data rate follow the
|
||||
connection rate.</para>
|
||||
|
||||
|
|
@ -1185,8 +1200,9 @@ vp|VH9600|Very High Speed Modem at 9600,8-bit:\
|
|||
vq|VH57600|Very High Speed Modem at 57600,8-bit:\
|
||||
:nx=VH9600:tc=std.57600:</programlisting>
|
||||
|
||||
<para>If you have a slow CPU or a heavily loaded system and you do
|
||||
not have 16550A-based serial ports, you may receive sio
|
||||
<para>If you have a slow CPU or a heavily loaded system and do
|
||||
not have 16550A-based serial ports, you may receive
|
||||
<errorname>sio</errorname>
|
||||
<quote>silo</quote> errors at 57.6 Kbps.</para>
|
||||
</sect4>
|
||||
</sect3>
|
||||
|
|
@ -1240,7 +1256,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
|
|||
<screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen>
|
||||
|
||||
to send the signal. If this is your first time setting up the
|
||||
system, though, you may want to wait until your modem(s) are properly
|
||||
system, you may want to wait until your modem(s) are properly
|
||||
configured and connected before signaling <command>init</command>.
|
||||
</para>
|
||||
|
||||
|
|
@ -1370,7 +1386,7 @@ AT&C1&D2&H1&I0&R2&W</programlisting>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Switch 2: Do not care (Verbal Result Codes/Numeric Result
|
||||
<para>Switch 2: N/A (Verbal Result Codes/Numeric Result
|
||||
Codes)</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -1395,7 +1411,7 @@ AT&C1&D2&H1&I0&R2&W</programlisting>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Switch 8: Do not care (Smart Mode/Dumb Mode)</para>
|
||||
<para>Switch 8: N/A (Smart Mode/Dumb Mode)</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
|
@ -1505,7 +1521,8 @@ AT&B2&W</programlisting>
|
|||
<sect3>
|
||||
<title>Try Dialing In</title>
|
||||
|
||||
<para>Try dialing into the system; be sure to use 8 bits, no parity, 1
|
||||
<para>Try dialing into the system; be sure to use 8 bits, no parity,
|
||||
and 1
|
||||
stop bit on the remote system. If you do not get a prompt right
|
||||
away, or get garbage, try pressing <keycode>Enter</keycode>
|
||||
about once per second. If you still do not see a
|
||||
|
|
@ -1587,17 +1604,19 @@ AT&B2&W</programlisting>
|
|||
<para>Also, the dial timeout for <command>tip</command> is 60 seconds.
|
||||
Your modem should use something less, or else tip will think there is
|
||||
a communication problem. Try <command>ATS7=45&W</command>.</para>
|
||||
|
||||
<note>
|
||||
<para>As shipped, <command>tip</command> does not yet support
|
||||
Hayes modems fully. The solution is to edit the file
|
||||
<filename>tipconf.h</filename> in the directory
|
||||
<filename>/usr/src/usr.bin/tip/tip</filename>. Obviously you need the
|
||||
source distribution to do this.</para>
|
||||
|
||||
<para>Actually, as shipped <command>tip</command> does not yet support
|
||||
it fully. The solution is to edit the file
|
||||
<filename>tipconf.h</filename> in the directory
|
||||
<filename>/usr/src/usr.bin/tip/tip</filename> Obviously you need the
|
||||
source distribution to do this.</para>
|
||||
|
||||
<para>Edit the line <literal>#define HAYES 0</literal> to
|
||||
<literal>#define HAYES 1</literal>. Then <command>make</command> and
|
||||
<command>make install</command>. Everything works nicely after
|
||||
that.</para>
|
||||
<para>Edit the line <literal>#define HAYES 0</literal> to
|
||||
<literal>#define HAYES 1</literal>. Then <command>make</command> and
|
||||
<command>make install</command>. Everything works nicely after
|
||||
that.</para>
|
||||
</note>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="direct-at">
|
||||
|
|
@ -1621,7 +1640,7 @@ AT&B2&W</programlisting>
|
|||
this:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /dev</userinput>
|
||||
&prompt.root; <userinput>MAKEDEV cuaa0</userinput></screen>
|
||||
&prompt.root; <userinput>sh MAKEDEV cuaa0</userinput></screen>
|
||||
|
||||
<para>Or use <command>cu</command> as root with the following
|
||||
command:</para>
|
||||
|
|
@ -1632,7 +1651,7 @@ AT&B2&W</programlisting>
|
|||
(e.g.<filename>/dev/cuaa0</filename>) and
|
||||
<replaceable>speed</replaceable> is the speed
|
||||
(e.g.<literal>57600</literal>). When you are done entering the AT
|
||||
commands hit <command>~.</command> to exit.</para>
|
||||
commands hit <keycap>~.</keycap> to exit.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
|
|
@ -1701,7 +1720,7 @@ deep13:Gizmonics Institute terminal server:\
|
|||
:dv=/dev/cuaa2:br#38400:at=hayes:du:pa=none:pn=5551234:</programlisting>
|
||||
|
||||
<para>will let you type <command>tip pain</command> or <command>tip
|
||||
muffin</command> to connect to the hosts pain or muffin; and
|
||||
muffin</command> to connect to the hosts pain or muffin, and
|
||||
<command>tip deep13</command> to get to the terminal server.</para>
|
||||
</sect2>
|
||||
|
||||
|
|
@ -1876,7 +1895,7 @@ raisechar=^^</programlisting>
|
|||
<sect2 id="serialconsole-intro">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>FreeBSD boot on a system with only
|
||||
<para>FreeBSD has the ability to boot on a system with only
|
||||
a dumb terminal on a serial port as a console. Such a configuration
|
||||
should be useful for two classes of people: system administrators who
|
||||
wish to install FreeBSD on machines that have no keyboard or monitor
|
||||
|
|
@ -1930,7 +1949,7 @@ raisechar=^^</programlisting>
|
|||
<para>Setting the keyboard to <quote>Not installed</quote> in the
|
||||
BIOS setup does <emphasis>not</emphasis> mean that you will not
|
||||
be able to use your keyboard. All this does is tell the BIOS
|
||||
not to probe for a keyboard at power-on so that it will not
|
||||
not to probe for a keyboard at power-on, so it will not
|
||||
complain if the keyboard is not plugged in. You can leave the
|
||||
keyboard plugged in even with this flag set to <quote>Not
|
||||
installed</quote> and the keyboard will still work.</para>
|
||||
|
|
@ -1939,11 +1958,11 @@ raisechar=^^</programlisting>
|
|||
<note>
|
||||
<para>If your system has a PS/2 mouse, chances are very good that
|
||||
you may have to unplug your mouse as well as your keyboard.
|
||||
This is because PS/2 mice share some hardware with the keyboard,
|
||||
This is because PS/2 mice share some hardware with the keyboard
|
||||
and leaving the mouse plugged in can fool the keyboard probe
|
||||
into thinking the keyboard is still there. It is said that a
|
||||
Gateway 2000 Pentium 90MHz system with an AMI BIOS that behaves
|
||||
this way. In general this is not a problem since the mouse is
|
||||
this way. In general, this is not a problem since the mouse is
|
||||
not much good without the keyboard anyway.</para>
|
||||
</note>
|
||||
</step>
|
||||
|
|
@ -2097,8 +2116,8 @@ raisechar=^^</programlisting>
|
|||
detecting extended keyboards only. Keyboards with less
|
||||
than 101 keys (and without F11 and F12 keys) may not be
|
||||
detected. Keyboards on some laptop computers may not be
|
||||
properly found because of this limitation. If this is to
|
||||
be the case with your system, you have to abandon using
|
||||
properly found because of this limitation. If this is
|
||||
the case with your system, you have to abandon using
|
||||
the <option>-P</option> option. Unfortunately there is no
|
||||
workaround for this problem.</para>
|
||||
</note>
|
||||
|
|
@ -2226,7 +2245,8 @@ boot:</screen>
|
|||
and the console eventually selected.</para>
|
||||
|
||||
<sect3>
|
||||
<title>Case 1: You Set the flags to 0x10 for sio0</title>
|
||||
<title>Case 1: You Set the flags to 0x10 for
|
||||
<devicename>sio0</devicename></title>
|
||||
|
||||
<programlisting>device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4</programlisting>
|
||||
|
||||
|
|
@ -2358,8 +2378,8 @@ boot:</screen>
|
|||
<sect3>
|
||||
<title>Setting a Faster Serial Port Speed</title>
|
||||
|
||||
<para>By default the serial port settings are set to 9600 baud, 8
|
||||
bits, no parity, 1 stop bit. If you wish to change the speed, you
|
||||
<para>By default, the serial port settings are: 9600 baud, 8
|
||||
bits, no parity, and 1 stop bit. If you wish to change the speed, you
|
||||
need to recompile at least the boot blocks. Add the following line
|
||||
to <filename>/etc/make.conf</filename> and compile new boot
|
||||
blocks:</para>
|
||||
|
|
@ -2386,7 +2406,7 @@ boot:</screen>
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Get the kernel source.</para>
|
||||
<para>Get the kernel source. (See <xref linkend="cutting-edge">)</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
|
|
@ -2494,7 +2514,7 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
|
|||
<para>Previous sections described how to set up the serial console by
|
||||
tweaking the boot block. This section shows that you can specify the
|
||||
console by entering some commands and environment variables in the
|
||||
boot loader. As the boot loader is invoked as the third stage of the
|
||||
boot loader. As the boot loader is invoked at the third stage of the
|
||||
boot process, after the boot block, the settings in the boot loader
|
||||
will override the settings in the boot block.</para>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue