Document fins/I0618-1
FIN #: I0618-1
SYNOPSIS: A screen resolution of 1024x768x75 for Creator (FFB) and Elite (AFB)
Frame Buffers with any monitors is set incorrectly by the Open Boot
PROM.
DATE: Oct/20/00
KEYWORDS: A screen resolution of 1024x768x75 for Creator (FFB) and Elite (AFB)
Frame Buffers with any monitors is set incorrectly by the Open Boot
PROM.
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
SYNOPSIS: A screen resolution of 1024x768x75 for Creator (FFB) and
Elite (AFB) Frame Buffers with any monitors is set
incorrectly by the Open Boot PROM.
TOP FIN/FCO REPORT: No
PRODUCT_REFERENCE: Creator (FFB) and Elite (AFB) Frame Buffer
PRODUCT CATEGORY: Display / Frame Buffer
PRODUCTS AFFECTED:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
----------------
- A22 ALL Ultra 10 -
- A16 ALL Ultra 30 -
- A23 ALL Ultra 60 -
- A27 ALL Ultra 80 -
X-Options Affected
------------------
- - - - -
PART NUMBERS AFFECTED:
Part Number Description Model
----------- ----------- -----
501-4174 Creator series 2 FFB2/SB
501-4172 Creator3D series 2 FFB2/DB
501-4789 Creator series 3 FFB2+/SB
501-4788 Creator3D series 3 FFB2+/DB
501-5690 Creator3D series 3 FFB2+/DB
501-5484 Elite3D m3 AFB
540-3623 Elite3D m6 AFB
501-4860 Elite3D m3 FRU AFB
501-5268 Elite3D m3 FRU AFB
501-5574 Elite3D m3 FRU AFB
540-3902 Elite3D m6 FRU AFB
540-4313 Elite3D m6 FRU AFB
501-5201 Elite3D m3 (not a FRU) AFB
501-5575 Elite3D m3 (not a FRU) AFB
REFERENCES:
BugId: 4347705
PROBLEM DESCRIPTION:
A screen resolution of 1024x768x75 cannot be correctly set by the Open
Boot PROM for Creator and Elite Frame Buffers used with Any monitors.
The problem can be seen when either AFB or FFB frame buffers are
installed in one of the following systems:
. Ultra 10
. Ultra 30
. Ultra 60
. Ultra 80
If you use the following OBP command,
ok setenv output-device screen:r1024x768x75
the frame buffer outputs the 1024x768x80 resolution. This incorrect
resolution can be seen either in the boot messages or on the control
panel of some monitors.
The cause of this video resolution problem is an incorrect entry in the
OBP timing generation table. Note that the problem is not reproducible
with an FFB2+ frame buffer and a version 2.9 OBP.
A workaround is available. See the Corrective Action section below.
IMPLEMENTATION:
---
| | MANDATORY (Fully Pro-Active)
---
---
| | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---
CORRECTIVE ACTION:
There is an NVRAM workaround to patch the offending timing value for
Creator and Elite series frame buffers used with Any monitors. If a
resolution of 1024x768x75 is desired, perform one of the following two
procedures:
1) <At the ok prompt>
ok setenv fcode-debug? true
ok show-displays
a) /SUNW,ffb@1e,0
b) /pci@1f,4000/SUNW,m64B@2
q) NO SELECTION
Enter Selection, q to quit: a
/SUNW,ffb@1e,0 has been selected.
Type ^Y ( Control-Y ) to insert it in the command line
< select the AFB or FFB and make note of string for use in NVRAM script
>
ok nvedit
0: probe-all
1: dev < path_to_FFB > <=== example 1: dev
/SUNW,ffb@1e,0
2: base @ hex
3: patch 46 4b pclk78
4: base !
5: device-end
6: install-console banner
< CTRL-C >
ok nvstore
ok setenv use-nvramrc? true
ok reset-all
The system will now boot with 1024x768x75 resolution and the monitor
will display with the 75Hz refresh rate.
--- OR ---
2) An equivalent OS script can also be run to update the OBP:
---------------- Cut Here ----------------------------------
#!/bin/sh
eeprom fcode-debug?=true
eeprom nvramrc="probe-all
dev /SUNW,ffb@1e,0
# Note: Use correct path to frame buffer in previous line
base @ hex
patch 46 4b pclk78
base !
device-end
install-console banner"
eeprom use-nvramrc?=true
---------------- Cut Here ----------------------------------
COMMENTS:
----------------------------------------------------------------------------
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
support 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 "Enterprise Services Documenta-
tion" 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@Sun.COM
---------------------------------------------------------------------------
Copyright (c) 1997-2003 Sun Microsystems, Inc.