All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Preslan <kpreslan@lcse.umn.edu>
To: ultralinux@vger.kernel.org
Subject: UltraPenguin109 + Ultra5 = Bad
Date: Tue, 07 Jul 1998 02:22:02 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-90222358531001@msgid-missing> (raw)

Hi,

I'm trying to get Ultra Penguin 1.0.9 to work on a Ultra 5.  The prom says
it's a UltraSPARC-IIi 270MHz.  OpenBoot version 3.11.6.  (What other info do
you guys need?)

I have rarp and tftp setup up and it's booting the latest image from
ultra.linux.cz.  Here's what it prints out:

PROMLIB: Sun IEEE Boot Prom 3.11.6 1997/12/08 10:42
Linux version 2.1.99 (root@manka) (gcc driver version 2.7.2 snapshot 970621 executing gcc version 2.7.2) #1 Sat may 2 18:35:38 1998
ARCH: SUN4U
Ethernet address: 08:00:20:90:c4:ea
Found CPU 0 <nodeð06ca38,mid=0>
Found 1 CPU prom device tree node(s).
CENTRAL: no central found.
Memory 60224k available (1574k kernel code, 1624k data, 152k init) [fffff80000000000,fffff80013f26000]
SBUS: No SBUS's found.
Console: Colour SUNPCI 128x64, 16 point font, 864 scans
PCI: Probing for controllers.
PCI: Found SABRE, main regs at fffff9fe00000000
SABRE: PCI config space at fffff9fe01000000
SABRE: DVMA at c0000000 [20000000]
PCI: Probing PCI hardware.
ebus0: fffff9ff00000000[1000000] fffff9ff00000000[800000]
ebus1: fffff9fff0000000[1000000] fffff9fff1000000[800000]
mach64_init: IOBASE[fffff9fe02c00100] MEMBASE[fffff9ffe1000000]
mach64_init: chip_type[4754], total_vram[00200000]

And it just stops there.

Anybody have a hunch as to what's wrong?

Thanks,

Ken Preslan
kpreslan@lcse.umn.edu

             reply	other threads:[~1998-07-07  2:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-07  2:22 Kenneth Preslan [this message]
1998-07-07  3:04 ` UltraPenguin109 + Ultra5 = Bad David.Andrew
1998-07-07  6:38 ` Jakub Jelinek
1998-07-07  7:39 ` Stephan van Hienen
1998-07-07 10:46 ` Jakub Jelinek
1998-07-07 14:55 ` David Andrew - Sun MDE

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=marc-linux-ultrasparc-90222358531001@msgid-missing \
    --to=kpreslan@lcse.umn.edu \
    --cc=ultralinux@vger.kernel.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.