svn commit: r44918 - head/en_US.ISO8859-1/books/handbook/serialcomms

[Dru Lavigne]

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</programlisting>
     <sect2>
       <title>Troubleshooting</title>
 
-      <para>Here are a few steps for troubleshooting a dial-up modem
-	on a &os; system.</para>
+      <para>This section provides a few tips for troubleshooting a
+	dial-up modem that will not connect to a &os; system.</para>
 
-      <para>Hook up the modem to the &os; system, boot the system,
-	and, if the modem has status indication lights, watch to see
+      <para>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 <acronym>DTR</acronym> indicator lights
 	when the <prompt>login:</prompt> prompt appears on the
 	system's console.  If it lights up, that should mean that &os;
@@ -1381,45 +1381,34 @@ AT&B2&W</programlisting>
 
       <para>If the <acronym>DTR</acronym> indicator does not light,
 	login to the &os; system through the console and type
-	<command>ps ax</command> to see if &os; is trying to run a
+	<command>ps ax</command> to see if &os; is running a
 	<command>getty</command> process on the correct port:</para>
 
-      <screen>  114 ??  I      0:00.10 /usr/libexec/getty V19200 ttyu0
-  115 ??  I      0:00.10 /usr/libexec/getty V19200 ttyu1</screen>
+      <screen>  114 ??  I      0:00.10 /usr/libexec/getty V19200 <replaceable>ttyu0</replaceable></screen>
 
-      <para>If something like this is displayed instead:</para>
-
-      <screen>  114 d0  I      0:00.10 /usr/libexec/getty V19200 ttyu0</screen>
-
-      <para>and the modem has not accepted a call yet, this means
+      <para>If the second column contains a <literal>d0</literal>
+	instead of a <literal>??</literal> and the modem has not
+	accepted a call yet, this means
 	that <command>getty</command> 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
 	<command>getty</command> 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.</para>
 
       <para>If no <command>getty</command> processes are waiting to
-	open the desired
-	<filename>ttyu<replaceable>N</replaceable></filename>
-	port, double-check the entries in
-	<filename>/etc/ttys</filename> to see if there are any
-	mistakes.  Also, check
+	open the port, double-check that the entry for the port is
+	correct in <filename>/etc/ttys</filename>.  Also, check
 	<filename>/var/log/messages</filename> to see if there are
 	any log messages from <command>init</command> or
-	<command>getty</command>.  If there are any messages,
-	triple-check <filename>/etc/ttys</filename> and
-	<filename>/etc/gettytab</filename>, as well as the
-	appropriate device special files,
-	<filename>/dev/ttyuN</filename>, for any mistakes, missing
-	entries, or missing device special files.</para>
+	<command>getty</command>.</para>
 
       <para>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 <keycap>Enter</keycap> about once per second.  If
-	there is still no <prompt>login:</prompt> prompt after a
-	while, try sending a <command>BREAK</command>.  When using a
+	there is still no <prompt>login:</prompt> prompt,
+	try sending a <command>BREAK</command>.  When using a
 	high-speed modem, try dialing again after locking the
 	dialing modem's interface speed.</para>
 
@@ -1452,9 +1441,8 @@ AT&B2&W</programlisting>
 	<acronym>DTR</acronym> line is asserted by checking the
 	modem's indicator lights.</para>
 
-      <para>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
+      <para>If it still does not work, try sending an email
+	to the &a.questions; describing the modem and the
 	problem.</para>
     </sect2>
   </sect1>