All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex deVries <alex@linuxcare.com>
To: n.wies@wanadoo.fr
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Help wanted on an 715/50 "old Box" 2
Date: Tue, 20 Feb 2001 18:36:06 -0500	[thread overview]
Message-ID: <3A92FF66.BB9B30C@linuxcare.com> (raw)
In-Reply-To: 01022023263600.01386@nw

WIES Nicolas wrote:
> I have an old Apollo, a 715/50 Scorpio with 64Mb Ram and a Tulip in the EISA
> port and my goal is to turn it into a firewall.

It seems very unlikely that's a Tulip chip, since that's a PCI chipset
that can't connect to EISA.  If it's another EISA ethernet chipset,
there's still some WAX work we need to get through.

> But I never have a commplete boot.
> 
> >From the beginnig of the year, I don't remenber exactly when, I have the same
> message with this last lines:
> 
> Entry 00100170 first 00100000 n 5
> 
> Segment 0 load 00100000 size 1453916 mediaptr 0x1000
> Segment 1 load 00264000 size 201128 mediaptr 0x164000
> Segment 2 load 00298000 size 214428 mediaptr 0x196000
> Segment 3 load 002d0000 size 8192 mediaptr 0x1cb000
> Segment 4 load 002fbda8 size 71328 mediaptr 0x1cdda8
> branching to kernel entry point 0x00100170
> 
> And nothing happen.

I've had this too with the exact same machine (without the EISA ethernet
card).  Then I decided to leave it for a LONG time, like 5 minutes, and
it did boot.  Could you try leaving it for something like an hour to see
if you get anything on the console?

- Alex

-- 
Alex deVries, Principal Solutions Architect, The Puffins at Linuxcare
613.562.2759 tel
alex@linuxcare.com, http://www.linuxcare.com/
Linuxcare, Putting open source to work.

  reply	other threads:[~2001-02-20 23:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-20 22:26 [parisc-linux] Help wanted on an 715/50 "old Box" 2 WIES Nicolas
2001-02-20 23:36 ` Alex deVries [this message]
2001-02-21 20:47   ` 5116
2001-02-22 22:01     ` WIES Nicolas
2001-02-20 23:36 ` Christoph Plattner

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=3A92FF66.BB9B30C@linuxcare.com \
    --to=alex@linuxcare.com \
    --cc=n.wies@wanadoo.fr \
    --cc=parisc-linux@lists.parisc-linux.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.