Title: | AlphaServer 1000 (aka Mikasa) |
Moderator: | WRKSYS::HESCH G |
Created: | Mon Nov 14 1994 |
Last Modified: | Thu Jun 05 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 917 |
Total number of notes: | 3293 |
The information below maybe incorrect. The FE will try to clarify tomorrow. The customer has two brand new AS1000A 5/400 with a KZPSA in each. The systems run VMS 6.2xx. With the KZPSA on the primary PCI bus, system runs fine. If the customer installs the KZPSA on the secondary PCI bus, on POST the receive a messag about the IRQ not being correct. This happens on eith system and with multiple KZPSAs. Has anyone seen anything like this? Ed Burkhalter CSC Atlanta
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
853.1 | NT does not support the KZPSA behind the PPB only | KEIKI::WHITE | MIN(2�,FWIW) | Thu Mar 06 1997 21:17 | 44 |
Interesting that this is not noted in the ASRV1000 firmware release notes but is in the ASRV2100 firmware release notes. _________________________________________________________________________________ 1.2.1 Anomaly Seen on AlphaServer 2100A with KZPSA's Behind the | PCI-to-PCI Bridge | | The console may issue a message with older KZPSA's installed on | the PCI bus behind the PCI-to-PCI Bridge chip [PPB]. The message | may occur on power-up or after an INIT command. The message can be | ignored for OpenVMS and Digital UNIX systems. | Example output: | ... | | *** unable to assign PCI base address | *** bus 2, slot 9, function 0, size 00001000 (16 bit I/O) | ... | End of example output | | The message is informational for Windows NT systems because Window | NT systems currently do not support the KZPSA behind the PPB. The | KZPSA is supported when installed in front of the PPB. | | |||||
853.2 | Thanks, reply #1 was correct. | MSDOA::WILSON | Wed Mar 12 1997 14:15 | 6 | |
I went on-site and got the correct error message from the system and it is the same as listed in the first reply. (Unable to assign PCI base address). When we defined the boot device properly as dkb it booted into the cluster ok. f |