Document Audience: | INTERNAL
Archive
| WARNING:Articles moved into the Archived collection were accurate at the "Last Update" date, but are not maintained from that date forward.
As such, Sun disclaims all implied or express warranties with respect to the information contained in such articles.
Document ID: | I0486-1 |
Title: | E450 banner may not appear when using banner command on systems with PGX32 cards installed. |
Copyright Notice: | Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved |
Last Updated Date: | 1999-04-17 |
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
FIN #: I0486-1
Synopsis: E450 banner may not appear when using banner command on systems with PGX32 cards installed.Create Date: Apr/16/99
Keywords:
E450 banner may not appear when using banner command on systems with PGX32 cards installed.
Top FIN/FCO Report: No
Products Reference: E450 banner command
Product Category: Server / System Board
Product Affected:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
----------------
- E450 ALL Ultra Enterprise 450 -
- E450 ALL Ultra 450 -
X-Options Affected
------------------
X3668A - - PGX32 CARD W/VIDEO ADAPTER -
Parts Affected:
Part Number Description Model
----------- ----------- -----
370-3753-02 PGX32 24Bit Low Cost Frame Buffer -
F370-3753-02 FRU, PGX32, Low Cost Frame Buffer -
References:
BugId: 4213767
ECO: ECR14855
WW StopShip: WW001#03560
MANUAL: 805-0429-10 Ultra Enterprise 450 Server Owner's guide
MANUAL: 805-0430-10 Sun Ultra 450 Workstation Owner's Guide
MANUAL: 805-7770-10 Sun PGX32 PCI Graphics Card Installation Guide
Issue Description:
Ultra Enterprise 450s configured with the PGX32 (370-37530-02) PCI
graphics card will not display the proper expected banner when the
"banner" command is invoked. This condition occurs after power up and
POST has run. Should anyone perform a "Stop+A", after bringing the
unit to the "ok>" prompt and try to execute "banner" command the will
not display the expected "RaptorGFX" logo. Additionally, the system
system may display either "Data Access Error" or "Insufficient Virtual
Memory" messages.
This problem has also been observed on Ultra Enterprise 450 systems
where customers purchased the X3668A option and install it themselves
or with the assistance of Enterprise Services.
The root cause has been identified as a bug within the FCODE of the
PGX32 card. The card will function without problems as long as the
"banner" command is not executed after power up.
The issue only results from running the "banner" command. The board
functions properly in all other cases.
Implementation:
---
| | MANDATORY (Fully Pro-Active)
---
---
| | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---
Corrective Action:
Customers and Field Service Representatives can avoid the above
mentioned problem with the "banner display" and the associated error
messages on Enterprise 450s by following the temporary workaround
provided below:
Should customers or Field Service Representatives who invoke the
"banner" command from OBP "OK prompt"; the system should be rebooted
in order to avoid any possible memory corruption. Once the E450 is
rebooted, the banner will appear as designed upon power up.
Comments:
The permanent corrective action is an ECO to dash roll the 370-3753-02
PGX32 to a -03 documenting the FCODE SW change which fixes this issue.
Worldwide stop ship for A25/A26 configurations with X3668A PGX32 option
was issued under WW001#03560 on 2/23/1999. Supplier, Tech-Source,
Inc. Spun the FCODE on the board and an emergency ECO is being drafted
to has rev the 370-3753-02 to a -03 to document the software change of
FCODE to v1.10. The ECR in process is ECR14855 out for approval as of
03/19/1999.
*NOTE: Swapping the X3668A board to the -03 level is NOT required for
proper function of the board.
--------------------------------------------------------------------------
Implementation Footnote:
________________________
i) In case of MANDATORY FINs, Enterprise Services will attempt to contact
all affected customers to recommend implementation of the FIN.
ii) For CONTROLLED PROACTIVE FINs, Enterprise Services mission critical sup-
port teams will recommend implementation of the FIN (to their respective
accounts), at the convenience of the customer.
iii) For REACTIVE FINs, Enterprise Services will implement the FIN as the need
arises.
-----------------------------------------------------------------------
All released FINs and FCOs can be accessed using your favorite network
browser as follows:
SunWeb Access:
______________
* Access the top level URL of http://sdpsweb.ebay/FIN_FCO/
* From there, select the appropriate link to query or browse the FIN and
FCO Homepage collections.
SunSolve Online Access:
_______________________
* Access the SunSolve Online URL at http://sunsolve.Corp/
* From there, select the appropriate link to browse the FIN or FCO index.
Supporting Documents:
____________________
Supporting documents for FIN/FCOs can be found on Edist. Edist can be
accessed internally at the following URL: http://edist.corp/.
* From there, follow the hyperlink path of "SunService Documentation" and
click on "FIN & FCO attachments", then choose the appropriate folder,
FIN or FCO. This will display supporting directories/files for FINs or
FCOs.
Internet Access:
_______________
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
________
Send questions or comments to finfco-manager@cte.EBay
---------------------------------------------------------------------------