From owner-svn-doc-head@FreeBSD.ORG Thu Oct 17 15:42:26 2013 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 781AB38D; Thu, 17 Oct 2013 15:42:26 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 54B722B7E; Thu, 17 Oct 2013 15:42:26 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id r9HFgQLV070679; Thu, 17 Oct 2013 15:42:26 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id r9HFgQEI070678; Thu, 17 Oct 2013 15:42:26 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201310171542.r9HFgQEI070678@svn.freebsd.org> From: Dru Lavigne Date: Thu, 17 Oct 2013 15:42:26 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r42984 - head/en_US.ISO8859-1/books/handbook/serialcomms X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Oct 2013 15:42:26 -0000 Author: dru Date: Thu Oct 17 15:42:25 2013 New Revision: 42984 URL: http://svnweb.freebsd.org/changeset/doc/42984 Log: Initial header tightening pass through this chapter, in prep for further work. Made sure not to create any orphaned links. Some headings were better suited as tables which were created. This is to be followed by a much needed white space fix. Modified: head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml Thu Oct 17 15:15:58 2013 (r42983) +++ head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml Thu Oct 17 15:42:25 2013 (r42984) @@ -57,13 +57,9 @@ - Introduction - - - - - Terminology + Serial Terminology and Hardware + The following terms are often used in serial commnications: bps @@ -76,16 +72,18 @@ DTE - An example of a Data Terminal EquipmentDTE - (DTE) is a computer. + Data Terminal EquipmentDTE + (DTE) is one of two endpoints in a + serial communication. An example would be a computer. DCE - An example of a Data Communications EquipmentDCE - (DTE) is a modem. + Data Communications EquipmentDCE + (DTE) is the other endpoint in a + serial communication. Typically, it is a modem. @@ -93,8 +91,8 @@ RS-232 - The original standard for hardware serial - communications. It is now usually referred to as + The original standard which defined hardware serial + communications. It has since been renamed to TIA-232RS-232C cables. @@ -105,10 +103,7 @@ number of electrical state transitions that may be made in a period of time, while bps is the correct term to use. - - - Cables and Ports To connect a modem or serial terminal to a &os; system, a serial port on the computer and the proper cable to connect to @@ -116,17 +111,14 @@ with serial hardware and cabling can safely skip this section. - - Cables + + Serial Cables and Ports There are several different kinds of serial cables. The two most common types are null-modem cables and standard RS-232 cables. The documentation for the hardware should describe the type of cable required. - - Null-modem Cables - null-modem cable @@ -431,10 +423,6 @@ another variation, SG connects to SG, TD connects to RD, RTS and CTS connect to DCD, DTR connects to DSR, and vice-versa. - - - - Standard RS-232C Cables RS-232C cables @@ -445,20 +433,12 @@ This is the type of cable used to connect a modem to the &os; system, and is also appropriate for some terminals. - - - - - Ports Serial ports are the devices through which data is transferred between the &os; host computer and the terminal. This section describes the kinds of ports that exist and how they are addressed in &os;. - - Kinds of Ports - Several kinds of serial ports exist. Before purchasing or constructing a cable, make sure it will fit the ports on the terminal and on the &os; @@ -471,10 +451,6 @@ See the documentation that accompanied the hardware for specifications on the kind of port or visually verify the type of port. - - - - Port Names In &os;, each serial port is accessed through an entry in /dev. @@ -508,9 +484,6 @@ terminal. If the terminal is on the second serial port (COM2), use /dev/ttyu1, and so forth. - - - @@ -642,16 +615,17 @@ + + --> Terminals terminals @@ -661,9 +635,6 @@ connected network. This section describes how to use terminals with &os;. - - Uses and Types of Terminals - The original &unix; systems did not have consoles. Instead, users logged in and ran programs through terminals that were connected to the computer's serial ports. @@ -681,13 +652,12 @@ otherwise be a single-user computer into a powerful multiple user system. - This section describes three kinds of terminals supported - by &os;: dumb terminals, computers acting as terminals, and X - terminals. - - - Dumb Terminals + &os; supports three types of terminals: + + + Dumb terminals + Dumb terminals are specialized hardware that connect to computers over serial lines. They are called dumb because they have only enough @@ -704,12 +674,13 @@ Dumb terminals are popular in work environments where workers do not need access to graphical applications. - + + - - Computers Acting as Terminals - - If a dumb terminal has + + Computers Acting as Terminals + + If a dumb terminal has just enough ability to display, send, and receive text, any spare computer can be a dumb terminal. All that is needed is the proper cable and some terminal @@ -750,11 +721,12 @@ through the Ports Collection, such as comms/minicom. - - - - X Terminals + + + + X Terminals + X terminals are the most sophisticated kind of terminal available. Instead of connecting to a serial port, they usually connect to a network like Ethernet. Instead of @@ -763,8 +735,9 @@ This chapter does not cover the setup, configuration, or use of X terminals. - - + + + Configuration @@ -995,10 +968,7 @@ ttyu5 "/usr/libexec/getty std.19200" Here is a list of common symptoms and some suggested fixes. - - No Login Prompt Appears - - Make sure the terminal is plugged in and powered up. If + If no login prompt appears, 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 port. @@ -1050,33 +1020,22 @@ ttyu5 "/usr/libexec/getty std.19200" software flow control enabled when using 3wire to prevent buffer overflows. - - - - If Garbage Appears Instead of a Login Prompt - - Make sure the terminal and &os; agree on the + If garbage appears instead of a login prompt, make sure the terminal and &os; agree on the bps rate and parity settings. Check the getty processes to make sure the correct getty type is in use. If not, edit /etc/ttys and run kill -HUP 1. - - - - Characters Appear Doubled and the Password Appears When - Typed - - Switch the terminal, or the terminal emulation software, + If characters appear doubled and the password appears when + typed, switch the terminal, or the terminal emulation software, from half duplex or local echo to full duplex. - - + Dial-in Service dial-in service Configuring a &os; system for dial-in service is similar to connecting terminals except that modems are used instead of - terminal devices. - - - External Versus Internal Modems + terminal devices. &os; supports both external and internal modems. External modems are more convenient for dial-up because they often can be semi-permanently configured via parameters @@ -1115,9 +1072,6 @@ ttyu5 "/usr/libexec/getty std.19200" internal modem has any signal indicator lights, they are difficult to view when the system's cover is in place. - - Modems and Cables - modem When using an external modem, a proper cable is needed. @@ -1196,8 +1150,6 @@ ttyu5 "/usr/libexec/getty std.19200" the modem after a call. &os; avoids sending commands to the modem or watching for status reports from the modem. - - Serial Interface Considerations @@ -1316,19 +1268,12 @@ ttyu5 "/usr/libexec/getty std.19200" information on the format of the file and the list of capabilities. - - Locked-speed Config - When locking a modem's data communications rate at a particular speed, no changes to /etc/gettytab should be needed. - - - Matching-speed Config - - Set up an entry in + However, a change is needed to create a matching-speed configuration. Create an entry in /etc/gettytab to give getty information about the speeds to use for the modem. For a 2400 bps modem, use the @@ -1402,7 +1347,6 @@ vq|VH57600|Very High Speed Modem at 5760 16550A-based serial ports, there may be sio silo errors at 57.6 Kbps. - @@ -1456,9 +1400,6 @@ vq|VH57600|Very High Speed Modem at 5760 Wait until the modem is properly configured and connected before signaling init. - - Locked-speed Config - For a locked-speed configuration, the ttys entry needs to have a fixed-speed entry provided to getty. @@ -1474,10 +1415,6 @@ vq|VH57600|Very High Speed Modem at 5760 instead of std.19200. Make sure to use a valid type listed in /etc/gettytab. - - - - Matching-speed Config In a matching-speed configuration, the ttys entry needs to reference the @@ -1489,7 +1426,6 @@ vq|VH57600|Very High Speed Modem at 5760 this: ttyu0 "/usr/libexec/getty V19200" dialup on - @@ -1627,9 +1563,6 @@ AT&C1&D2&H1&I0&R2&am conversation between getty and the modem. - - Locked-speed Config - For a locked-speed configuration, configure the modem to maintain a constant modem-to-computer data rate independent of the communications rate. On a &usrobotics; &sportster; @@ -1639,10 +1572,6 @@ AT&C1&D2&H1&I0&R2&am ATZ AT&B1&W - - - - Matching-speed Config For a variable-speed configuration, configure the modem to adjust its serial port data rate to match the incoming @@ -1654,7 +1583,6 @@ AT&B1&W ATZ AT&B2&W - Checking the Modem's Configuration @@ -1680,9 +1608,6 @@ AT&B2&W Here are a few steps for troubleshooting a dial-up modem on a &os; system. - - Checking Out the &os; System - Hook up the modem to the &os; system, boot the system, and, if the modem has status indication lights, watch to see whether the modem's DTR @@ -1728,12 +1653,8 @@ AT&B2&W appropriate device special files, /dev/ttyuN, for any mistakes, missing entries, or missing device special files. - - - - Try Dialing In - Try dialing into the system. Be sure to use 8 bits, no + Next, try dialing into the system. Be sure to use 8 bits, no parity, and 1 stop bit on the remote system. If a prompt does not appear right away, or the prompt shows garbage, try pressing Enter about once per second. If @@ -1776,9 +1697,7 @@ AT&B2&W it later. If it still does not work, try sending an email message to the &a.questions; describing the modem and the problem. - - @@ -2066,6 +1985,7 @@ raisechar=^^ + Setting Up the Serial Console serial console - - Introduction - &os; has the ability to boot a system with a dumb terminal on a serial port as a console. This configuration is useful for system administrators who wish to install &os; on @@ -2106,8 +2024,6 @@ raisechar=^^ boot block code, the boot loader code, and the kernel need to be configured. - - Quick Serial Console Configuration @@ -2160,7 +2076,7 @@ raisechar=^^ Use either a null-modem cable or a standard serial cable and a null-modem adapter. See for a discussion + linkend="term-cables-null"/> for a discussion on serial cables. @@ -2482,16 +2398,12 @@ boot: Summary - Here is the summary of the various settings discussed in - this section: + The following tables provide a summary of the various settings discussed in + this section. - - Case 1: Set the Flags to 0x10 for + <table frame="none" pgwide="1"> + <title>Case 1: Set the Flags to 0x10 for <devicename>sio0</devicename> - - device sio0 flags 0x10 - - @@ -2546,16 +2458,11 @@ boot: - - + - - Case 2: Set the Flags to 0x30 for + <table frame="none" pgwide="1"> + <title>Case 2: Set the Flags to 0x30 for <devicename>sio0</devicename> - - device sio0 flags 0x30 - - @@ -2610,8 +2517,7 @@ boot: - - +