os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Finish editorial review of Dial-in Service chapter.

Browse source 
Sponsored by:	iXsystems
This commit is contained in:
Dru Lavigne 2014-05-23 16:24:36 +00:00
parent 2891dc042e
commit a0c5546f76
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=44918
1 changed files with 18 additions and 30 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

48
en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml
View file

@ -1367,11 +1367,11 @@ AT&amp;B2&amp;W</programlisting>
<sect2> <sect2>
<title>Troubleshooting</title> <title>Troubleshooting</title>
<para>Here are a few steps for troubleshooting a dial-up modem <para>This section provides a few tips for troubleshooting a
on a &os; system.</para> dial-up modem that will not connect to a &os; system.</para>
<para>Hook up the modem to the &os; system, boot the system, <para>Hook up the modem to the &os; system and boot the system.
and, if the modem has status indication lights, watch to see If the modem has status indication lights, watch to see
whether the modem's <acronym>DTR</acronym> indicator lights whether the modem's <acronym>DTR</acronym> indicator lights
when the <prompt>login:</prompt> prompt appears on the when the <prompt>login:</prompt> prompt appears on the
system's console. If it lights up, that should mean that &os; system's console. If it lights up, that should mean that &os;
@ -1381,45 +1381,34 @@ AT&amp;B2&amp;W</programlisting>
<para>If the <acronym>DTR</acronym> indicator does not light, <para>If the <acronym>DTR</acronym> indicator does not light,
login to the &os; system through the console and type 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> <command>getty</command> process on the correct port:</para>
<screen> 114 ?? I 0:00.10 /usr/libexec/getty V19200 ttyu0 <screen> 114 ?? I 0:00.10 /usr/libexec/getty V19200 <replaceable>ttyu0</replaceable></screen>
115 ?? I 0:00.10 /usr/libexec/getty V19200 ttyu1</screen>
<para>If something like this is displayed instead:</para> <para>If the second column contains a <literal>d0</literal>
instead of a <literal>??</literal> and the modem has not
<screen> 114 d0 I 0:00.10 /usr/libexec/getty V19200 ttyu0</screen> accepted a call yet, this means
<para>and the modem has not accepted a call yet, this means
that <command>getty</command> has completed its open on the that <command>getty</command> has completed its open on the
communications port. This could indicate a problem with 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 <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> the modem.</para>
<para>If no <command>getty</command> processes are waiting to <para>If no <command>getty</command> processes are waiting to
open the desired open the port, double-check that the entry for the port is
<filename>ttyu<replaceable>N</replaceable></filename> correct in <filename>/etc/ttys</filename>. Also, check
port, double-check the entries in
<filename>/etc/ttys</filename> to see if there are any
mistakes. Also, check
<filename>/var/log/messages</filename> to see if there are <filename>/var/log/messages</filename> to see if there are
any log messages from <command>init</command> or any log messages from <command>init</command> or
<command>getty</command>. If there are any messages, <command>getty</command>.</para>
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>
<para>Next, try dialing into the system. Be sure to use 8 bits, <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 no parity, and 1 stop bit on the remote system. If a prompt
does not appear right away, or the prompt shows garbage, try does not appear right away, or the prompt shows garbage, try
pressing <keycap>Enter</keycap> about once per second. If pressing <keycap>Enter</keycap> about once per second. If
there is still no <prompt>login:</prompt> prompt after a there is still no <prompt>login:</prompt> prompt,
while, try sending a <command>BREAK</command>. When using a try sending a <command>BREAK</command>. When using a
high-speed modem, try dialing again after locking the high-speed modem, try dialing again after locking the
dialing modem's interface speed.</para> dialing modem's interface speed.</para>
@ -1452,9 +1441,8 @@ AT&amp;B2&amp;W</programlisting>
<acronym>DTR</acronym> line is asserted by checking the <acronym>DTR</acronym> line is asserted by checking the
modem's indicator lights.</para> modem's indicator lights.</para>
<para>If it still does not work, take a break and come back to <para>If it still does not work, try sending an email
it later. If it still does not work, try sending an email to the &a.questions; describing the modem and the
message to the &a.questions; describing the modem and the
problem.</para> problem.</para>
</sect2> </sect2>
</sect1> </sect1>