All of lore.kernel.org
 help / color / mirror / Atom feed
From: rick@dgii.com (Rick Richardson)
To: ultralinux@vger.kernel.org
Subject: Re: Worth attempting an Ultra 30 install with 1.1???u
Date: Sat, 21 Nov 1998 08:57:23 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-91168520928163@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-91142241707303@msgid-missing>

Rick Richardson writes...
> 
> OK, here's the status of this UP1.1 install on the Ultra 30.  This
> particular box has a broken onboard ethernet controller, so we used
> the one on the SCSI/HME PCI card to TFTP boot it.
> 
> The machines internal SCSI hard drive (with Solaris on it) was also
> removed, an an external drive (with terminators enabled) was connected.
> NOTE: I sure hope that the SUN SCSI controller is smart enough to enable
> termination for the now empty internal drive slot, and disable termination
> on the now connected external SCSI bus.

<snip>

> Unfortuantely, at this point I cannot get the thing to boot from the
> PROM monitor.  It just sits there.

OK, we seemed to have found a way around this issue.  It turns out
that if I plug the internal SCSI hard drive back in and set the
external hard drive to SCSI ID 1 I can get this thing to boot UP1.1
when I type "boot disk1".  No idea why the PROM monitor won't let me
boot the external drive with "boot disk" without the internal one
installed.  But thats not an UP1.1 problem.

Then we hit the "overwritting initrd" problem.  I then moved the SIMMs
from the first set of four slots to the third set of four slots,
as suggested by Jakub.  What a weird solution to a bug.  Whatever.

So after doing that, UltraPengiun 1.1 is finally booting on the Ultra
30.  Wow, what a day!!!!

Now the only issue left is the network.  Since the onboard ethernet
controller is broken, we are using the PCI hme board.  Unfortunately,
UP1.1 sees and configures that controller OK (as eth1), and will send
packets out on it, but is absolutely deaf when it comes to hearing
replies such as ARPs.

This smacks of an interrupt problem to me.  If the hme driver
isn't seeing interrupts from the board, this would explain the
behavior.

UltraPeniguin is *so* close to usable now.  I'm psyched.

-Rick


-- 
Rick "The Hack" Richardson  rick@dgii.com http://RickRichardson.freeservers.com

      parent reply	other threads:[~1998-11-21  8:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-18 10:03 Worth attempting an Ultra 30 install with 1.1???u Jakub Jelinek
1998-11-19 10:01 ` Rick Richardson
1998-11-19 10:58 ` Jakub Jelinek
1998-11-20 22:04 ` Rick Richardson
1998-11-21  8:57 ` Rick Richardson [this message]

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-91168520928163@msgid-missing \
    --to=rick@dgii.com \
    --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.