Kill whitespace.
This commit is contained in:
Tom Rhodes
parent
4e1ba4d813
commit
52da88130a
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=17008
1 changed files with 62 additions and 67 deletions
|
|
@ -846,92 +846,87 @@ 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>
|
||||
|
||||
<sect3>
|
||||
<title>No Login Prompt Appears</title>
|
||||
<sect3>
|
||||
<title>No Login Prompt Appears</title>
|
||||
|
||||
<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
|
||||
port.</para>
|
||||
|
||||
<para>Make sure the cable is connected firmly to both the terminal
|
||||
and the FreeBSD computer. Make sure it is the right kind of
|
||||
cable.</para>
|
||||
<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
|
||||
port.</para>
|
||||
|
||||
<para>Make sure the terminal and FreeBSD agree on the bps rate and
|
||||
parity settings. If you have a video display terminal, make
|
||||
sure the contrast and brightness controls are turned up. If it
|
||||
is a printing terminal, make sure paper and ink are in good
|
||||
supply.</para>
|
||||
<para>Make sure the cable is connected firmly to both the terminal
|
||||
and the FreeBSD computer. Make sure it is the right kind of
|
||||
cable.</para>
|
||||
|
||||
<para>Make sure that a <command>getty</command> process is running
|
||||
and serving the terminal. For example, to get a list of
|
||||
running <command>getty</command> processes with
|
||||
<command>ps</command>, type:</para>
|
||||
<para>Make sure the terminal and FreeBSD agree on the bps rate and
|
||||
parity settings. If you have a video display terminal, make
|
||||
sure the contrast and brightness controls are turned up. If it
|
||||
is a printing terminal, make sure paper and ink are in good
|
||||
supply.</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>ps -axww|grep getty</userinput></screen>
|
||||
<para>Make sure that a <command>getty</command> process is running
|
||||
and serving the terminal. For example, to get a list of
|
||||
running <command>getty</command> processes with
|
||||
<command>ps</command>, type:</para>
|
||||
|
||||
<para>You should see an entry for the terminal. For
|
||||
example, the following display shows that a
|
||||
<command>getty</command> is running on the second serial
|
||||
port <literal>ttyd1</literal> and is using the
|
||||
<literal>std.38400</literal> entry in
|
||||
<filename>/etc/gettytab</filename>:</para>
|
||||
|
||||
<screen>22189 d1 Is+ 0:00.03 /usr/libexec/getty std.38400 ttyd1</screen>
|
||||
|
||||
<para>If no <command>getty</command> process is running, make sure
|
||||
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>
|
||||
<screen>&prompt.root; <userinput>ps -axww|grep getty</userinput></screen>
|
||||
|
||||
<para>If the <command>getty</command> process is running
|
||||
but the terminal still does not display a login prompt,
|
||||
or if it displays a prompt but will not allow you to
|
||||
type, your terminal or cable may not support hardware
|
||||
handshaking. Try changing the entry in
|
||||
<filename>/etc/ttys</filename> from
|
||||
<literal>std.38400</literal> to
|
||||
<literal>3wire.38400</literal> remember to run
|
||||
<command>kill -HUP 1</command> after modifying
|
||||
<filename>/etc/ttys</filename>). The
|
||||
<literal>3wire</literal> entry is similar to
|
||||
<literal>std</literal>, but ignores hardware
|
||||
handshaking. You may need to reduce the baud rate or
|
||||
enable software flow control when using
|
||||
<literal>3wire</literal> to prevent buffer
|
||||
overflows.</para>
|
||||
<para>You should see an entry for the terminal. For
|
||||
example, the following display shows that a
|
||||
<command>getty</command> is running on the second serial
|
||||
port <literal>ttyd1</literal> and is using the
|
||||
<literal>std.38400</literal> entry in
|
||||
<filename>/etc/gettytab</filename>:</para>
|
||||
|
||||
</sect3>
|
||||
<screen>22189 d1 Is+ 0:00.03 /usr/libexec/getty std.38400 ttyd1</screen>
|
||||
|
||||
<sect3>
|
||||
<title>If Garbage Appears Instead of a Login Prompt</title>
|
||||
<para>If no <command>getty</command> process is running, make sure
|
||||
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>
|
||||
|
||||
<para>If the <command>getty</command> process is running
|
||||
but the terminal still does not display a login prompt,
|
||||
or if it displays a prompt but will not allow you to
|
||||
type, your terminal or cable may not support hardware
|
||||
handshaking. Try changing the entry in
|
||||
<filename>/etc/ttys</filename> from
|
||||
<literal>std.38400</literal> to
|
||||
<literal>3wire.38400</literal> remember to run
|
||||
<command>kill -HUP 1</command> after modifying
|
||||
<filename>/etc/ttys</filename>). The
|
||||
<literal>3wire</literal> entry is similar to
|
||||
<literal>std</literal>, but ignores hardware
|
||||
handshaking. You may need to reduce the baud rate or
|
||||
enable software flow control when using
|
||||
<literal>3wire</literal> to prevent buffer
|
||||
overflows.</para>
|
||||
|
||||
<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>
|
||||
</sect3>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<sect3>
|
||||
<title>If Garbage Appears Instead of a Login Prompt</title>
|
||||
|
||||
<title>Characters Appear Doubled; the Password Appears when
|
||||
Typed</title>
|
||||
<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>
|
||||
|
||||
|
||||
</sect3>
|
||||
|
||||
<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>
|
||||
<sect3>
|
||||
<title>Characters Appear Doubled; the Password Appears when Typed</title>
|
||||
|
||||
<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>
|
||||
|
||||
</sect3>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="dialup">
|
||||
<sect1info>
|
||||
<authorgroup>
|
||||
|
|
|
|||
Loading…
Reference in a new issue