Dear Managers,
We have a DEC 2000/300 with 192MB that used to be with DU 3.2D-1. So, we decided to move to DU 4.0D boing a fresh install.
To begin, we planned to upgrade the firmware. And that's where the problem is.
First, we upgraded the firmware that resides on the CD V5.3. We followed the steps in the manual and ended up with Firmware revision V2.2. No problem with that.
At a certain point of the process, we were asked to insert the Eisa Config Utility floppy, after a power-cycle. That was done, and, after several messages it displays the existence of 3 errors:
- environment variable
- configuration tree
- EISA configuration
After that it showed the boot menu. From here we moved to supplementary menu->setup menu, where we got a list of options, with three in yellow (in this order):
- set default environment variables
- set default configuration
- run EISA configuration utility from floppy
The system forced us to correct these situations in order.
So, in the 1st, we told that the default boot partition was in SCSI 0 3. But, when it asked for the filesystem type, we just left it in blank. It is strange because the only to option available were FAT or NTFS, and we aren't using any of them.
On the 2nd we choosed first floppy 3.5" 2.88MBytes, second floppy none and us-101 keyboard. Actually the default options given by the system.
On the 3rd, the system send some messages NVRAM update, then says that the system will reboot, then asks for a power-cycle. And we do it.
The systems seems to power up fine.
Then we tried to do a normal boot from the default disk, and we get the following messages:
- Alpha boot: available memory from 0x92a000 to 0xc000000
- Digital UNIX V3.2D-1 (Rev. 41); Thu Jan 8 09:08:35 GMT 1998
- phisical memory = 192.00 megabytes
- available memory = 182.83 megabytes
- using 729 buffers containing 5.69 megabytes of memory
- DEC 2000 model 300 system
- Firmware revision: 2.2
- PALcode: OSF version 1.35
- ibus0 at nexus
- ace0 at ibus0
- gpc0 at ibus0
- panic (cpu0): e_get_config: no ECU data
Then sends a message stating that it was unable to dump to a device.
It seems to me that "run EISA utility" does nothing, since that, in all literature about it, a menu is refered, but it never appears.
Are we missing something ?
This description sums up sereral attempts that we already made. We also looked into the tru64-unix-managers archives.
This system is not vital for us, but as we already spent a week trying to figure out the problem, all the help will be apreciated.
Thanks in advance.
Yours sincerely
Antonio Urbano
--------------------------------
Tel.: +351-2-9953000 (ext. 1131)
Fax: +351-2-9955062
e-mail: a.urbano_at_mailcity.com
--------------------------------
Get your FREE Email at
http://mailcity.lycos.com
Get your PERSONALIZED START PAGE at
http://personal.lycos.com
Received on Wed Mar 17 1999 - 10:46:22 NZDT