Hi, and thanks again to all of you who helped me with the firmware-upgrade
question ! You really saved my weekend with your quick responds.
Some of you told me how I could mount the firmware CD and print out the
doc's, but my kernel was not configured with the "cdfs"-option, so this did
not work. Other of you told me what firmware-version would go with DU V3.2C,
and this solved my problem. I finally did this:
* Upgraded from OSF/1 V3.0 - DU V3.2
* Upgraded the firware to V6.0
* Upgraded from DU V3.2 - DU V3.2C, no need of another firmware-upgrade.
Here is the answers I got, and once more: THANK YOU ALL.
--Ingeborg Andreassen, Sys.adm. University of Tromsoe, Norway
=========================================================================
To: Ingeborg Andreassen <ingeborg.andreassen_at_adm.uit.no>
From: "Sheryl A. Campbell" <campbell_at_lvc.edu>
Subject: Re: Upgrading firmware.
Date: Fri, 28 Jun 1996 17:53:04 +0000
I'm pretty sure I read that the firmware is backwards-compatible for 3.2d to
3.2c.
I wish you luck! Upgrading the firmware for me was the biggest headacche I
had when moving from 2.0b to 3.2d. The documentation is simply too verbose!
Hope your upgrade doesn't take away too much of your weekend!
Regards,
Sheryl
-------------------------------------------------------------------
To: Ingeborg Andreassen <ingeborg.andreassen_at_adm.uit.no>
Subject: Re: Upgrading firmware.
Date: Fri, 28 Jun 1996 13:41:48 -0400
From: "S. Grant" <grant_at_psc.edu>
Mount the CD, making sure the '-t cdfs' flag is used, and look under the DOC
directory. You'll find the docs there and can more through it (or print it)
to get
the whole file name.
-Shirl
--------------------------------------------------------------------
Date: Fri, 28 Jun 96 10:09:45
From: ron.barrett_at_Cubic.COM
Subject: RE: Upgrading firmware.
To: Ingeborg Andreassen <ingeborg.andreassen_at_adm.uit.no>
Ingeborg,
Digital UNIX is VERY sensitive to firmware revisions. I had severe
compatibility problems (unreliable failures) when I didn't have the proper
firmware revision. I would strongly encourage that you get the proper
revisions and procedures before proceeding unless you have a lot of extra
time and patience to deal with the problems. I'm not sure where my firmware
instructions are, I am awaiting firmware along with Digital UNIX 4.0.
Ron
-----------------------------------------------------------------
From: Drew Kramer <kramer_at_pa.dec.com>
Subject: Re: Upgrading firmware.
Did you try just "boot -fl 0,80 dkb400"? I believe that has always worked for
me.
-drew
>> Yes this works, but you have to give the name of the bootfile later.
>>(Ingeborg's comment)
-------------------------------------------------------------------
Date: Fri, 28 Jun 1996 14:19:58 -0400
From: Joanna Lee Siegel <siegel_at_kara.zko.dec.com>
Organization: Digital Equipment Corporation
To: ingeborg.andreassen_at_adm.uit.no
Subject: firmware upgrade revision info
According to the following table you should be using:
[DEC3000]M400_V6_4.EXE
>I think I have the bootfile-name for firmware V3.4 that came with DU V3.2D,
>but can I upgrade to this version of firmware and still upgrade only to DU
>V3.2C ?
Yes, you can upgrade to the firmware on V3.4.
----------------------------------------------------------------
From: rioux_at_ip6480nl.ce.utexas.edu (Tom Rioux)
Subject: Re: Upgrading firmware.
To: ingeborg.andreassen_at_adm.uit.no (Ingeborg Andreassen)
Date: Fri, 28 Jun 96 13:35:43 CDT
I used firmware V6.0 from Alpha AXP Systems Firmware Update V3.1 CD 1/1
February 1995:
boot -fl 0,80 dka400
[dec3000]m400_v6_0.exe
update
verify
exit
Tom
-----------------------------------------------
Date: Fri, 28 Jun 1996 13:53:49 -0500 (UTC -05:00)
From: Bob Sloane <SLOANE_at_KUHUB.CC.UKANS.EDU>
Subject: Re: Upgrading firmware.
To: Ingeborg Andreassen <ingeborg.andreassen_at_adm.uit.no>
Cc: SLOANE_at_KUHUB.CC.UKANS.EDU
> I'm about to upgrade the OS on our DEC3000/600 from V3.2 to V3.2C, and need
> to upgrade the firmware first from V3.1 to V3.3. Unfortunately the
> firmware-upgrade doc's is lost, and I cant find the bootfilename to use.
> The boot-command is : >>> boot -fl 0,80 dkb400 <bootfile-name>
> I know the name is [DEC3000]M400_V?_?.EXE
You should be able to mount the CD using:
mount -t cdfs -r /dev/rzXc /mnt
and use ls to find out the file name. This assumes your kernel was
built to handle the cdfs file system. If not, then if you have any
other systems capable of mounting ISO CDs, like a PC or another usix
system you could mount it there. As it happens I have a V3.3 CD handy,
and it appears to contain firmware versions 5.2, 6.0 and 6.2.
Assuming you want to use 6.2, the file name is m400_v6_2.exe.
--
USmail: Bob Sloane, University of Kansas Computer Center, Lawrence, KS, 66045
E-mail: sloane_at_kuhub.cc.ukans.edu, Phone: (913) 864-0444, FAX: (913) 864-0485
--------------------------------------------------------------
Received on Sat Jun 29 1996 - 17:18:53 NZST