Subject: UDB boot failing on secondary bootloader
To: 'port-alpha' <port-alpha@netbsd.org>
From: Lindgren, Jon <jlindgren@SLK.com>
List: port-alpha
Date: 02/09/1999 12:54:34
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01BE5455.552B9D00
Content-Type: text/plain;
charset="iso-8859-1"
After going through what looks like a dead battery/lost firmware problem on
my Multia, I finally have it up and running on firmware 3.8-3. NetBSD 1.3.3
installed fine, but the boot fails during the secondary bootloader's attempt
to open netbsd. There is no disk activity, and no baton twirling (it
doesn't look like it's even loading the kernel - it's just hanging). When
it fails, it spews out a bunch of debug, then drops me into what looks to be
a sort of debugger which prompts "Eh?" at most of my attempts to drop back
to prom. The disk is on the NCR SCSI bus as device 0. No boot flags or
default boot devices are set in the prom.
With the update to the 3.8-3 firmware, I also started getting a single poll
error on pka0 during the firmware initialization. I've ignored them since
the disk works (I've tested it in another machine), the install went fine,
the primary and secondary bootloaders load and execute, and I didn't get the
error before updating the firmware.
I'm clueless on this one. Has anyone run into this before?
Hmmm... maybe I shouldn't try to replace my alphastation 200 with a
multia...
Thanks.
-Jon Lindgren
Spear, Leeds & Kellogg
(201) 332-3577, x4391
jlindgren@slk.com
------_=_NextPart_001_01BE5455.552B9D00
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2232.0">
<TITLE>UDB boot failing on secondary bootloader</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>After going through what looks like a dead =
battery/lost firmware problem on my Multia, I finally have it up and =
running on firmware 3.8-3. NetBSD 1.3.3 installed fine, but the =
boot fails during the secondary bootloader's attempt to open =
netbsd. There is no disk activity, and no baton twirling (it =
doesn't look like it's even loading the kernel - it's just =
hanging). When it fails, it spews out a bunch of debug, then =
drops me into what looks to be a sort of debugger which prompts =
"Eh?" at most of my attempts to drop back to prom. The =
disk is on the NCR SCSI bus as device 0. No boot flags or default =
boot devices are set in the prom.</FONT></P>
<P><FONT SIZE=3D2>With the update to the 3.8-3 firmware, I also started =
getting a single poll error on pka0 during the firmware =
initialization. I've ignored them since the disk works (I've =
tested it in another machine), the install went fine, the primary and =
secondary bootloaders load and execute, and I didn't get the error =
before updating the firmware.</FONT></P>
<P><FONT SIZE=3D2>I'm clueless on this one. Has anyone run into =
this before?</FONT>
</P>
<P><FONT SIZE=3D2>Hmmm... maybe I shouldn't try to replace my =
alphastation 200 with a multia...</FONT>
</P>
<P><FONT SIZE=3D2>Thanks.</FONT>
</P>
<P><FONT SIZE=3D2> -Jon Lindgren</FONT>
<BR><FONT SIZE=3D2> Spear, Leeds & Kellogg</FONT>
<BR><FONT SIZE=3D2> (201) 332-3577, x4391</FONT>
<BR><FONT SIZE=3D2> jlindgren@slk.com</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01BE5455.552B9D00--