From owner-svn-doc-head@FreeBSD.ORG Fri May 23 16:24:37 2014 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 ESMTPS id 7C5F79A3; Fri, 23 May 2014 16:24:37 +0000 (UTC) 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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 694F52DF6; Fri, 23 May 2014 16:24:37 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s4NGObB5024528; Fri, 23 May 2014 16:24:37 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s4NGObig024527; Fri, 23 May 2014 16:24:37 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201405231624.s4NGObig024527@svn.freebsd.org> From: Dru Lavigne Date: Fri, 23 May 2014 16:24:37 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44918 - 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.18 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: Fri, 23 May 2014 16:24:37 -0000 Author: dru Date: Fri May 23 16:24:36 2014 New Revision: 44918 URL: http://svnweb.freebsd.org/changeset/doc/44918 Log: Finish editorial review of Dial-in Service chapter. Sponsored by: iXsystems 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 Fri May 23 16:04:57 2014 (r44917) +++ head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml Fri May 23 16:24:36 2014 (r44918) @@ -1367,11 +1367,11 @@ AT&B2&W Troubleshooting - Here are a few steps for troubleshooting a dial-up modem - on a &os; system. + This section provides a few tips for troubleshooting a + dial-up modem that will not connect to a &os; system. - Hook up the modem to the &os; system, boot the system, - and, if the modem has status indication lights, watch to see + Hook up the modem to the &os; system and boot the system. + If the modem has status indication lights, watch to see whether the modem's DTR indicator lights when the login: prompt appears on the system's console. If it lights up, that should mean that &os; @@ -1381,45 +1381,34 @@ AT&B2&W If the DTR indicator does not light, login to the &os; system through the console and type - ps ax to see if &os; is trying to run a + ps ax to see if &os; is running a getty process on the correct port: - 114 ?? I 0:00.10 /usr/libexec/getty V19200 ttyu0 - 115 ?? I 0:00.10 /usr/libexec/getty V19200 ttyu1 + 114 ?? I 0:00.10 /usr/libexec/getty V19200 ttyu0 - If something like this is displayed instead: - - 114 d0 I 0:00.10 /usr/libexec/getty V19200 ttyu0 - - and the modem has not accepted a call yet, this means + If the second column contains a d0 + instead of a ?? and the modem has not + accepted a call yet, this means that getty has completed its open on the communications port. This could indicate a problem with the - cabling or a misconfigured modem, because + cabling or a misconfigured modem because getty should not be able to open the - communications port until carrier detect has been asserted by + communications port until the carrier detect signal has been asserted by the modem. If no getty processes are waiting to - open the desired - ttyuN - port, double-check the entries in - /etc/ttys to see if there are any - mistakes. Also, check + open the port, double-check that the entry for the port is + correct in /etc/ttys. Also, check /var/log/messages to see if there are any log messages from init or - getty. If there are any messages, - triple-check /etc/ttys and - /etc/gettytab, as well as the - appropriate device special files, - /dev/ttyuN, for any mistakes, missing - entries, or missing device special files. + getty. 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 - there is still no login: prompt after a - while, try sending a BREAK. When using a + there is still no login: prompt, + try sending a BREAK. When using a high-speed modem, try dialing again after locking the dialing modem's interface speed. @@ -1452,9 +1441,8 @@ AT&B2&W DTR line is asserted by checking the modem's indicator lights. - If it still does not work, take a break and come back to - it later. If it still does not work, try sending an email - message to the &a.questions; describing the modem and the + If it still does not work, try sending an email + to the &a.questions; describing the modem and the problem.