Linux MIPS Architecture development
 help / color / mirror / Atom feed
* Warning: persistent break condition on serial port 0.
@ 2002-03-07 19:59 Jan-Benedict Glaw
  2002-03-07 20:40 ` Jan-Benedict Glaw
  0 siblings, 1 reply; 3+ messages in thread
From: Jan-Benedict Glaw @ 2002-03-07 19:59 UTC (permalink / raw)
  To: Linux MIPS

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]

Hi!

I've got an Indy R4k6 some time ago (I managed to run Linux on it using
nfsroot) and now I attempted to really install it. However, I've now
got some problem with the serial port: I can read the boot-up messages,
but I cannot intercept the bootstrap (as I could do it some weeks
ago):

                         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>

So I get warnings about a "persistent break condition", but that's
not caused by the cable I use (I've used it weeks ago and it worked).

Did I manage to kill the serial port? Any other hint on this?

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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Warning: persistent break condition on serial port 0.
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Jan-Benedict Glaw @ 2002-03-07 20:40 UTC (permalink / raw)
  To: Linux MIPS

[-- Attachment #1: Type: text/plain, Size: 923 bytes --]

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...

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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Warning: persistent break condition on serial port 0.
  2002-03-07 20:40 ` Jan-Benedict Glaw
@ 2002-03-07 21:06   ` Jan-Benedict Glaw
  0 siblings, 0 replies; 3+ messages in thread
From: Jan-Benedict Glaw @ 2002-03-07 21:06 UTC (permalink / raw)
  To: Linux MIPS

[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-03-07 22:06 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox