From: Adam Agnew <agnew@missl.cs.umd.edu>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: "Trenton D. Adams" <tadams@extremeeng.com>,
"'Matthew M. DeLoera'" <code.bear@gte.net>,
<ecos-discuss@sources.redhat.com>, <waa@cs.umd.edu>,
<bdpayne@cs.umd.edu>, <usn01a@wam.umd.edu>
Subject: Re: [ECOS] Problems with RedBoot on x86 generic pc...
Date: Fri, 07 Sep 2001 11:25:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.33.0109071431090.34713-100000@www.missl.cs.umd.edu> (raw)
In-Reply-To: <3B66F138.309B7FFA@redhat.com>
Hi, I'm using the same image, getting the same results. Did anyone ever
have a solution to this problem?
On Tue, 31 Jul 2001, Jonathan Larmour wrote:
> "Trenton D. Adams" wrote:
> >
> > Since mine isn't working either, I figured I'd chime in.
> >
> > > "Matthew M. DeLoera" wrote:
> > > >
> > > > Anyway, my current problem is with RedBoot. I built the x86
> > version
> > > and
> > > > booted with the diskette. It seems to come up, and I see a RedBoot
> > > > prompt on my screen. I'm assuming that even though I can see it on
> > the
> > > > local console, the local console isn't active, right? So, I have
> > to
> > > use
> > > > a serial port or network, right?
> > >
> > > Yes it should be active. Is it not?
> > >
> >
> > Nope, mine isn't active.
> >
> > >
> > > On the console, what happens if you type "+$k#6b" (without the
> > quotes).
> > >
> >
> > I assume you mean the local console. If so, it does nothing for me.
> >
> > The redboot I'm using is the June 8th binary on the website, redboot.bin
>
> Although I tested this binary before, I just retested it just to be sure
> and it Works For Me(tm).
>
> One possibility is that there is noise on the serial line. RedBoot listens
> to all input channels, and as soon as it gets something on one, it uses
> that from then on. So if it got a glitch on the serial line, it might
> switch to that and stay there. How many serial ports does the machine have?
>
> > p.s.
> > I have the same problems as Matthew except I don't have a compatible
> > network card in the machine. I have an NE2000, but it's set to PNP mode
> > at the moment.
>
> If an i82559 card isn't detected it should still continue.
>
> Jifl
> --
> Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
> Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
>
next prev parent reply other threads:[~2001-09-07 11:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 12:07 Matthew M. DeLoera
2001-07-11 14:25 ` Jonathan Larmour
2001-07-31 7:59 ` Trenton D. Adams
2001-07-31 10:56 ` Jonathan Larmour
2001-07-31 12:01 ` Trenton D. Adams
2001-07-31 13:43 ` Jonathan Larmour
2001-07-31 14:20 ` Trenton D. Adams
2001-07-31 14:23 ` Jonathan Larmour
2001-09-07 11:25 ` Adam Agnew [this message]
2001-09-13 2:02 ` Adam Agnew
2001-09-13 3:56 ` [ECOS] RedBoot IDE access on x86 without BIOS Adam Agnew
2001-09-13 4:51 ` Mark Salter
2001-09-13 6:18 ` Adam Agnew
2001-09-13 6:24 ` Mark Salter
2001-09-13 6:53 ` Adam Agnew
2001-09-13 9:36 ` [ECOS] Problems with RedBoot on x86 generic pc Jonathan Larmour
2001-09-14 9:14 ` Adam Agnew
2001-09-14 12:43 ` Matthew DeLoera
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=Pine.BSF.4.33.0109071431090.34713-100000@www.missl.cs.umd.edu \
--to=agnew@missl.cs.umd.edu \
--cc=bdpayne@cs.umd.edu \
--cc=code.bear@gte.net \
--cc=ecos-discuss@sources.redhat.com \
--cc=jlarmour@redhat.com \
--cc=tadams@extremeeng.com \
--cc=usn01a@wam.umd.edu \
--cc=waa@cs.umd.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).