193 lines
3.1 KiB
HTML
193 lines
3.1 KiB
HTML
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>The console is unresponsive after connecting</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
|
REL="HOME"
|
|
TITLE="Remote Serial Console HOWTO"
|
|
HREF="index.html"><LINK
|
|
REL="UP"
|
|
TITLE="Bugs and annoyances"
|
|
HREF="bugs.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="init and
|
|
syslog output does not display on
|
|
secondary consoles"
|
|
HREF="bugs-monitor.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Modem hangs up during initialization"
|
|
HREF="bugs-setserial.html"></HEAD
|
|
><BODY
|
|
CLASS="SECTION"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
SUMMARY="Header navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>Remote Serial Console HOWTO</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="bugs-monitor.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
>Appendix A. Bugs and annoyances</TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="bugs-setserial.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="SECTION"
|
|
><H1
|
|
CLASS="SECTION"
|
|
><A
|
|
NAME="BUGS-WHEREAMI"
|
|
></A
|
|
>A.6. The console is unresponsive after connecting</H1
|
|
><P
|
|
>The terminal's screen may be blank after connecting to the
|
|
machine. Pressing <B
|
|
CLASS="KEYCAP"
|
|
>Enter</B
|
|
> will usually bring up a
|
|
<TT
|
|
CLASS="PROMPT"
|
|
>login:</TT
|
|
> request.</P
|
|
><P
|
|
>If no characters appear upon the screen after pressing
|
|
<B
|
|
CLASS="KEYCAP"
|
|
>Enter</B
|
|
> do not panic. The machine must have power
|
|
and the operating system must have booted: for our call to be
|
|
answered by the modem Data Terminal Ready must be active.</P
|
|
><P
|
|
>The most likely thing is that the machine booted and is
|
|
running a <B
|
|
CLASS="COMMAND"
|
|
>fsck</B
|
|
> filesystem check. These checks
|
|
can take some considerable time, all with no or very little
|
|
output.</P
|
|
><P
|
|
>It will help your peace of mind considerably to record in the
|
|
system log book the time <B
|
|
CLASS="COMMAND"
|
|
>fsck</B
|
|
> takes to check
|
|
each filesystem.</P
|
|
><P
|
|
>If you see garbled text after pressing <B
|
|
CLASS="KEYCAP"
|
|
>Enter</B
|
|
>
|
|
then there are mismatched bit rates or parity parameters. Correct
|
|
your terminal emulator's configuration.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
SUMMARY="Footer navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="bugs-monitor.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
ACCESSKEY="H"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="bugs-setserial.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><SPAN
|
|
CLASS="APPLICATION"
|
|
>init</SPAN
|
|
> and
|
|
<SPAN
|
|
CLASS="APPLICATION"
|
|
>syslog</SPAN
|
|
> output does not display on
|
|
secondary consoles</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="bugs.html"
|
|
ACCESSKEY="U"
|
|
>Up</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Modem hangs up during initialization</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |