Hello,
This is a follow-up to a previous thread
Subject: DEC 2000, Model 300 AXP Boot Error Message
There was one more step that was required to get to a DU installation
screen: Rerun the firmware upgrade, switch to boot NT, power cycle, run the
EISA config from the ECU diskette, and explicitly save the configuration.
Power cycle. Change boot to OSF. Power cycle. Boot from CD is now OK.
In case anyone wants the all the sordid details....
I had just succeeded in getting an Alpha 2000 Model 300 to get past the
83 BOOT SYS
INIT-S-CPU...
AUDIT_BOOT_STARTS...
without errors by attaching a Digital RRD43-DA external CD drive, which
shows up on >>>show dev
as dka500.
The next stage started fine, and it began with the Unix boot, but it
reached a certain point, quit, and started over again in an endless loop (I
watched it do this about 40 times transcribing this). I booted from the
Digital Unix 4.0B Operating System Volume 1 (Dec 1996, Part Number:
AG-QTM9C-BE). I upgraded the firmware using the Alpha Systems Firmware
Update V3.9 (March, 1997, Part Number: AG-PTMWW-BE) and it now says that I
have
ROM Version 2.2
Firmware Version 370
Here is the sequence that it goes through:
83 BOOT SYS...
AUDIT_BOOT_STARTS...
AUDIT_CHECKSUM_GOOD
AUDIT_LOAD_GEGINS
AUDIT_LOAD_DONE
Digital Unix boot Friday Nov 15 21:24:46 EST 1996
loading vmunix
loading at
Current PAL Revision <0x10530>
Switching to OSF PAL code succeeded
New PAL Revision <0x20123>
Sizes:
text = 4769280
data = 1253168
bss = 2497296
Starting at 0xfffffc0000404240
Alpha boot: available memory start 0xb98000 to 0x4000000
Digital Unix 4.0B Rev. 564 Sat Nov 16 ... 1996
physical memory = 64.0 megabytes
available memory = 52.45 megabytes
Using 79 buffers containing .61 megabytes of memory
There was a blink, and it began the boot cycle again.
I reran the firmware upgrade and did a verify, just to see if it would
really read something from a CD to completion, and it did. I then tried
booting from the DU 3.2C CD, which progressed in a similar fashion but
exited with the error message
DUMP: problem with specified dumdev 0x1000001, Status 19, not used
DUMP: primary swap not used, no explicit dumpdev.
Nowhere to put header, giving up
Thanks to Neil Dyce <Neil.Dyce_at_bristol.ac.uk> for the pointer to this message)
http://www.xray.mpe.mpg.de/mailing-lists/tru64-unix-managers/1999-04/msg0038
8.html
wherin I found the advice given by Dr. Tom in response to a query by
Antonio Urbano <a.urbano_at_mailcity.com>
Tue, 20 Apr 1999 01:56:26 -0800
to run the ECU configuration after the firmware upgrade and make sure to
explicitly save the configuration. Power cycle. Switch boot type to OSF.
Power cycle. And it now, finally, it booted from the CD at dka500 and I
have the Installation screen for 4.0B.
<----- oOo ----->
Bennet Fauber
Social Science Data Service
University of California, Davis
Received on Fri Oct 08 1999 - 18:07:12 NZDT