Patch-ID# 101311-08 Keywords: gt ow patch window DDX DGA SunPC xgl Synopsis: SunOS 5.3: GT os driver, openwindows server, xgl pipeline patch Date: Feb/22/95 Solaris Release: 2.3 SunOS Release: 5.3 Unbundled Product: Unbundled Release: Relevant Architectures: sun4c, sun4m BugId's fixed with this patch: 1135190 1138323 1138324 1138450 1138453 1138701 1138764 1138765 1138766 1138777 1138778 1138799 1139562 1139678 1139966 1140273 1140274 1141450 1141452 1143435 1131232 1132512 1135189 1136102 1138774 1138770 1147559 1138818 1141207 1149550 1149287 1149285 1149288 1149503 1138453 1149917 1149324 1147625 1143300 1138774 1138770 1135406 1135186 1148112 1151202 1151411 1152691 1152745 1152896 1152874 1151202 1153867 1141907 1148603 1159384 1159385 1159391 1159768 1130280 1176441 1192094 Changes incorporated in this version: 1192094 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Solaris 2.4 Files included with this patch: /kernel/drv/gt /etc/opt/SUNWgt/bin/gt.ucode /usr/openwin/server/modules/ddxSUNWgt.so.1 /opt/SUNWits/Graphics-sw/xgl-3.0/lib/pipelines/xglSUNWgt.so.3 Problem Description: (from 101311-08) 1192094 PDGS crashes on some GT systems upon startup (from 101311-07) 1176441 gcached polygon not displayed on GT (from 101311-06) 1130280: SS2/GT rendering "shudder" on sys_chassis GPC runs and picking hangs (from 101311-05) 1148603: GT system is being shutdown while running the Newton test suite 1159384: Anti-Aliasing not reenabled when changing draw mode goes to ROP_SRC 1159385: Z-buffering writes not disabled correctly 1159391: Memory freed incorrectly for patterns and markers 1159768: xgl_ctx_new_frame() doesn't work when window is offscreen (from 101311-04): Clean up the depend file of this patch package (from 101311-03): 1153867: GT can't handle LARGE (> 64K points) multi_simple_polygons 1141907: GT does not correctly model clip when supplied -w reference points (from 101311-02): 1152874: Gt renders cursor incorrectly sometimes 1148112: Incompatibility problem exist between GT OW and SunPC4.0 1151202: 8 bit dga dont work. Channel is not moved from over. to red on dga 1151411: Gt cursor colormap is not updated when cursor changes 1152691: AVS is unusable on Solaris 2.3 GT. 1152745: Window resizing does not use accelerated rendering 1152896: GT Warning and Error console messages should be removed (from 101311-01): 1135190: Unclear wether to use WLUT mode 4 or 6 for 24bit true color 1138323: DGA doesn't return a valid window id 1138324: GT's DDX needs to support all GT planegroups 1138450: horizontal full screen lines provoked occassionally 1138453: cursor trash left on screen intermittently 1138701: Allocated WIDS never de-allocated. 1138764: There is no 24 bit planegroup with double buffering and Z buffering 1138765: There is no 8 bit planegroup with double buffering and Z buffering 1138766: Need to write DBValidate( ) function for DGA on the GT 1138777: Need to implement 8 bit truecolor visual on the GT 1138778: Need to implement 8 bit directcolor visual on the GT 1138799: Server's cursor leaves garbage on screen 1139562: DGA window doesn't register new position until explicity "Refresh" 1139678: Cut and paste highlighting fails on GT- no inverse characters visible 1139966: highlight selection causes text to disappear on GT 1140273: on GT cursor does not appear in shelltools 1140274: cursor leaves shadow images on GT 1141450: 8-bit XGL DGA process crashes server 1141452: DGA-24 windows go black upon cursor entry (WID/WLUT problem?) 1143435: mailtool crashes on GT when composing mails w/ attachements 1131232: The gt does not support all the Solaris/mit visuals 1132512: wrong openwin logo color on gt (hawk) in 8bit mode 1135189: DGA - some functions not supported 1136102: mpg assumes that pixmap depth == bitsPerPixel (not true for 24bit) 1138774: Need t write CmapSetup( ) function ior DGA on th 1138770: Need to write DBSetup( ) function for DGA on the GT 1147559: denizen program arc8 leads to XGL not being abled to allocate WID 1138818: MPG initialized before DGA. Dga needs to be setup 1'st for DBValidate 1141207: server crashes when running an application in StaticColor or 1149550: Running program with mixed Xlib and XGL calls will render text 1149287: Local bus timeout error occur frequently with new ddx code 1149285: The closing icons for X tools are weird looking 1149288: Mysterious rendering in upper left corner 1149503: gt_wait_fe_hold_ack() gives timeouts halting server 1138453: cursor trash left on screen intermittently 1149917: openwindows goes down with signal 11 when starting up multiheaded 1149324: DGA & MPG are not compatible when using multibuffered rendering! 1147625: There is no Solaris logo displayed while GT openwindow starts 1143300: Unisoft Xtest core dumps 1138774: Need to write CmapSetup( ) function for DGA on the GT 1138770: Need to write DBSetup( ) function for DGA on the GT 1135406: Unisoft Xtest CH03/chngwdwatt - XChangeWindowAttributes-2 failed 1135186: fill/span too slow 1148112: Incompatibility problem exist between GT OW and SunPC4.0 1151202: 8 bit dga dont work. Channel is not moved from over. to red on 1151411: Gt cursor colormap is not updated when cursor changes Patch Installation Instructions: -------------------------------- Generic 'installpatch' and 'backoutpatch' scripts are provided within each patch package with instructions appended to this section. Other specific or unique installation instructions may also be necessary and should be described below. Special Install Instructions: ----------------------------- Instructions to install patch using "installpatch" -------------------------------------------------- 1. Become super-user. 2. Apply the patch by typing:
.
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
patch packages failed. Installpatch will backout the patch
to leave the system in its pre-patched state. See the log file
for the reason for failure. Correct the problem and
re-apply the patch.
Error message:
Pkgadd of package failed with error code .
Will not backout patch...patch re-installation.
Warning: The system may be in an unstable state!
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
the patch packages failed. Installpatch will NOT backout the
patch. You may manually backout the patch using backoutpatch,
then re-apply the entire patch. Look in the log file for the
reason pkgadd failed. Correct the problem and re-apply the
patch.
Patch Installation Messages:
---------------------------
Note: the messages listed below are not necessarily considered errors
as indicated in the explanations given. These messages are, however,
recorded in the patch installation log for diagnostic reference.
Message:
Package not patched:
PKG=SUNxxxx
Original package not installed
Explanation: One of the components of the patch would have patched a
package that is not installed on your system. This is not
necessarily an error. A Patch may fix a related bug for several
packages. Example: suppose a patch fixes a bug in both the
online-backup and fddi packages. If you had online-backup installed
but didn't have fddi installed, you would get the message
Package not patched:
PKG=SUNWbf
Original package not installed
This message only indicates an error if you thought the package
was installed on your system. If this is the case, take the
necessary action to install the package, backout the patch (if
it installed other packages) and re-install the patch.
Message:
Package not patched:
PKG=SUNxxx
ARCH=xxxxxxx
VERSION=xxxxxxx
Architecture mismatch
Explanation: One of the components of the patch would have patched a
package for an architecture different from your system. This is not
necessarily an error. Any patch to one of the architecture specific
packages may contain one element for each of the possible
architectures. For example, Assume you are running on a sun4m. If
you were to install a patch to package SUNWcar, you would see the
following (or similar) messages:
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4c
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4d
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4e
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
The only time these messages indicate an error condition
is if installpatch does not correctly recognize your architecture.
Message:
Package not patched:
PKG=SUNxxxx
ARCH=xxxx
VERSION=xxxxxxx
Version mismatch
Explanation: The version of software to which the patch is applied is
not installed on your system. For example, if you were running Solaris
5.3, and you tried to install a patch against Solaris 5.2, you would
see the following (or similar) message:
Package not patched:
PKG=SUNWcsu
ARCH=sparc
VERSION=10.0.2
Version mismatch
This message does not necessarily indicate an error. If
the version mismatch was for a package you needed patched, either
get the correct patch version or install the correct package version.
Then backout the patch (if necessary) and re-apply.
Message:
Re-installing Patch.
Explanation: The patch has already been applied, but there is
at least one package in the patch that could be added. For
example, if you applied a patch that had both Openwindows and
Answerbook components, but your system did not have Answerbook
installed, the Answerbook parts of the patch would not have
been applied. If, at a later time, you pkgadd Answerbook, you
could re-apply the patch, and the Answerbook components of the
patch would be applied to the system.
Message:
Installpatch Interrupted.
Installpatch is terminating.
Explanation: Installpatch was interrupted during execution
(usually through pressing ^C). Installpatch will clean up
its working files and exit.
Message:
Installpatch Interrupted.
Backing out Patch...
Explanation: Installpatch was interrupted during execution
(usually through pressing ^C). Installpatch will clean up
its working files, backout the patch, and exit.
Patch Backout Errors:
---------------------
Error message:
prebackout patch exited with return code .
Backoutpatch exiting.
Explanation and corrective action: the prebackout script
supplied with the patch exited with a return code other
than 0. Generate a script trace of backoutpatch to determine
why the prebackout script failed. Correct the reason for
failure, and re-execute backoutpatch.
Error message:
postbackout patch exited with return code .
Backoutpatch exiting."
Explanation and corrective action: the postbackout script
supplied with the patch exited with a return code other than
0. Look at the postbackout script to determine why it failed.
Correct the failure and, if necessary, RE-EXECUTE THE
POSTBACKOUT SCRIPT ONLY.
Error message:
Only one service may be defined.
Explanation and corrective action: You have attempted to specify
more than one service from which to backout a patch. Different
services must have their patches backed out with different
invocations of backoutpatch.
Error message:
The -S and -R arguments are mutually exclusive.
Explanation and recommended action: You have specified both a
non-native service to backout, and a package installation root.
These two arguments are mutually exclusive. If backing out a
patch from a non-native usr partition, the -S option should be
used. If backing out a patch from a client's root
partition (either native or non-native), the -R option
should be used.
Error message:
The service cannot be found on this system.
Explanation and recommended action: You have specified a non-
native service from which to backout a patch, but the
specified service is not installed on your system. Correctly
specify the service when backing out the patch.
Error message:
Only one rootdir may be defined.
Explanation and recommended action: You have specified more than
one package install root using the -R option. The -R option
may be used only once per invocation of backoutpatch.
Error message:
The directory cannot be found on this system.
Explanation and recommended action: You have specified a
directory using the -R option which is either not mounted,
or does not exist on your system. Verify the directory name
and re-backout the patch.
Error message:
Patch has not been successfully applied to this system.
Explanation and recommended action: You have attempted to backout
a patch that is not applied to this system. If you must
restore previous versions of patched files, you may have to
restore the original files from the initial installation CD.
Error message:
Patch has not been successfully applied to this system.
Will remove directory
Explanation and recommended action: You have attempted to back
out a patch that is not applied to this system. While the
patch has not been applied, a residual
/var/sadm/patch/ (perhaps from an unsuccessful
installpatch) directory still exists. The patch cannot be
backed out. If you must restore old versions of the patched
files, you may have to restore them from the initial
installation CD.
Error message:
This patch was obsoleted by patch .
Patches must be backed out in the order in
which they were installed. Patch backout aborted.
Explanation and recommended action: You are attempting to backout
patches out of order. Patches should never be backed-out out
of sequence. This could undermine the integrity of the more
current patch.
Error message:
Patch was installed without backing up the original
files. It cannot be backed out.
Explanation and recommended action: Either the -d option of
installpatch was set when the patch was applied, or the save
area of the patch was deleted to regain space. As a result, the
original files are not saved and backoutpatch cannot be used.
The original files can only be recovered from the original
installation CD.
Error message:
pkgrm of package failed return code .
See /var/sadm/patch//log for reason for failure.
Explanation and recommended action: The removal of one of
patch packages failed. See the log file for the reason for
failure. Correct the problem and run the backout script again.
Error message:
Restore of old files failed.
Explanation and recommended action: The backout script uses the
cpio command to restore the previous versions of the files
that were patched. The output of the cpio command should
have preceded this message. The user should take the
appropriate action to correct the cpio failure.
KNOWN PROBLEMS:
On client server machines the patch package is NOT applied
to existing clients or to the client root template space.
Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED
THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH
METHOD ON THE CLIENT. See instructions above for
applying patches to a client.
A bug affecting a package utility (eg. pkgadd, pkgrm, pkgchk)
could affect the reliability of installpatch or backoutpatch
which uses package utilities to install and backout the patch
package. It is recommended that any patch that fixes package
utility problems be reviewed and, if necessary, applied before
other patches are applied. Such existing patches are:
100901 Solaris 2.1
101122 Solaris 2.2
101331 Solaris 2.3
SEE ALSO
pkgadd, pkgchk, pkgrm, pkginfo, showrev, cpio