14.1.12 DEC/VAX 7000 MOP booting problem
Current DEC/VAX 7000 consoles cannot handle MOP Protocol V4. If there is a server
anywhere on the network which supports V4 Protocol, the MOP boot may fail. Here is an
example, seen while booting from an Infoserver 1000:
>>>
Booting...
Connecting to boot device exa0
Created device: exa0.0.0.1.0
Requesting MOP Assistance Volunteer.
MOP Assistance Volunteer found.
Loading...
.Retrying MEM_LOAD...Retries exhausted.
bootstrap failure
The following workaround applies to DEC 7000 consoles V3.0 and earlier, or VAX 7000
consoles V3.3 and earlier. This forces the console to request a MOP Protocol V3 boot (which
it can handle).
>>> set mode advanced
>>> set mopv3_boot 1
>>> set mode basic
14.1.13 VAX 7000 MOP boot fails with RRD43
Current VAX 7000 consoles on CD fail to boot from an Infoserver, if the CD drive is an
RRD43. The ISL loads and runs correctly but when a service on the CD is selected the
system halts, thus:
CPU:0 Console entry reason : HALT instruction in kernel mode
Entry PC: 00147691 Entry PSL: 041F0600
boot failure
The failure occurs because the current ISL file (ISL_LVAX_V07) does not work with RRD43s.
OVMS Standalone Backup cannot be booted from CD either (as it uses the same ISL file).
Once OVMS is up however, the RRD43 can be used normally.
The only workaround, at present is to swap the RRD43 for an RRD42. The ISL file should
be fixed in Spring ’95.
Note: This means that some new VAX 7000 systems, as delivered, cannot be booted!
14.1.14 Boot fails due to suspected corrupt EEPROM on VAX 7000
This problem has been seen with V2.4 and V3.2 consoles, but probably applies to others too.
A MOP boot fails thus:
>>> boot -flag 0,0,0 -file VAX7000_V07_3 exa0
Too many strings
Fail to update eeprom env var on CPU 0
40
Komentarze do niniejszej Instrukcji