From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Linux MIPS <linux-mips@oss.sgi.com>
Subject: Re: Warning: persistent break condition on serial port 0.
Date: Thu, 7 Mar 2002 22:06:09 +0100 [thread overview]
Message-ID: <20020307210609.GG25044@lug-owl.de> (raw)
In-Reply-To: <20020307204020.GF25044@lug-owl.de>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
On Thu, 2002-03-07 21:40:20 +0100, Jan-Benedict Glaw <jbglaw@lug-owl.de>
wrote in message <20020307204020.GF25044@lug-owl.de>:
> On Thu, 2002-03-07 20:59:48 +0100, Jan-Benedict Glaw <jbglaw@lug-owl.de>
> wrote in message <20020307195948.GE25044@lug-owl.de>:
> > Running power-on diagnostics...
> > Warning: persistent break condition on serial port 0.
> > Warning: persistent break condition on serial port 0.
> > Starting up the system...
> > To perform system maintenance instead, press <Esc>
>
> I've now modified the cable: it's only signal ground and the receiving
> wire, so I really can only receive the Indy's messages. I cannot
> send anything anymore, but I still get those messages. I think this
> means that the box is now a paperweight: no way to access it, because
> I cannot even set console to ttyS1...
Things are getting better: I am root on that machine through a telnet
login (Irix 6.2 is running). Is there a way to set the console
device to ttyd1? Maybe that could work...
MfG, JBG
--
Jan-Benedict Glaw . jbglaw@lug-owl.de . +49-172-7608481
-- New APT-Proxy written in shell script --
http://lug-owl.de/~jbglaw/software/ap2/
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
prev parent reply other threads:[~2002-03-07 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 19:59 Warning: persistent break condition on serial port 0 Jan-Benedict Glaw
2002-03-07 20:40 ` Jan-Benedict Glaw
2002-03-07 21:06 ` Jan-Benedict Glaw [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020307210609.GG25044@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-mips@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox