From: Malcolm Beattie <mbeattie@sable.ox.ac.uk>
To: ultralinux@vger.kernel.org
Subject: Re: [mbeattie@sable.ox.ac.uk: oops booting ultrapenguin-1.0.9 on an
Date: Tue, 12 May 1998 13:21:46 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90222356531008@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90222356530980@msgid-missing>
Eddie C. Dost writes:
> > f008671c SUNW,isptwo@4
> > f007e438 SUNW,hme@0,1
> > f007e1e8 pci108e,1000@0
>
> Ahh, this 'pci108e,1000' is the second ebus bugging us...
>
> > clock_probe: Mostek not probed by EBUS
> > Program terminated
>
> Shit, another image...
Congratulations, this one gets through the entire boot stage
successfully and then gives the VFS "can't mount root" panic.
I assume this is intentional for these test images. It gives
539 BogoMIPS, sees both hme0 and hme1 ethernet cards, finds the
IDE disk partitions OK and generally looks fine. When mine
arrives and the fixes get merged into the UP dist, I can do a
proper install and take things from there. Many thanks for the
quick turnaround of fixes, Eddie.
I'll have access to an Enterprise 450 within the next few days
(destined to use Solaris but I can play with it for a while,
I should thing). Is ultralinux known to work fine with those or
is it worth me trying to boot it and see what happens?
--Malcolm
--
Malcolm Beattie <mbeattie@sable.ox.ac.uk>
Unix Systems Programmer
Oxford University Computing Services
next prev parent reply other threads:[~1998-05-12 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-07 10:10 [mbeattie@sable.ox.ac.uk: oops booting ultrapenguin-1.0.9 on an Malcolm Beattie
1998-05-08 9:40 ` Malcolm Beattie
1998-05-11 9:17 ` Malcolm Beattie
1998-05-12 13:21 ` Malcolm Beattie [this message]
1998-05-13 16:36 ` Malcolm Beattie
1998-05-25 17:57 ` Malcolm Beattie
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-90222356531008@msgid-missing \
--to=mbeattie@sable.ox.ac.uk \
--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.