Patch-ID# 101636-05 Keywords: turbo GX, qbasic, sun4m panics, check patches, ZX, multiprocessor, embedded keypad, Solaris 2.4, printing hangs Synopsis: SunPC 4.0.1: Jumbo patch for Solaris 2.3, 2.4 and sparc architectures Date: Oct/10/94 Solaris Release: 2.3, 2.4 SunOS Release: 5.3, 5.4 Unbundled Product: SunPC Unbundled Release: 4.0.1 Relevant Architectures: sparc BugId's fixed with this patch: 1153588 1155014 1155021 1155215 1156389 1156394 1156499 1157137 1159140 1161085 1170490 1174115 1175561 Changes incorporated in this version: 1153588 1155014 1156499 1159140 1161085 1170490 1174115 1175561 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Solaris 2.3 - 101318 (sun4m only), 101362, 101267, 101311 (GT frame buffer only) Solaris 2.4 - 101933, 102057, 101923 (A24 frame buffer only) Obsoleted by: Files included with this patch: /opt/SUNWsunpc/bin/check_patches /opt/SUNWsunpc/bin/spc.sva_svr4_prod /opt/SUNWsunpc/bin/sunpc /opt/SUNWsunpc/bin/sunpc_install /opt/SUNWsunpc/bin/sunpc_UNinstall /opt/SUNWsunpc/bin/ServerVersion /opt/SUNWsunpc/bin/sunpc_diag /opt/SUNWsunpc/drvr/sunpcmod.sun4c_53.o /opt/SUNWsunpc/drvr/sunpcmod.sun4c_54.o /opt/SUNWsunpc/drvr/sunpcmod.sun4m_53.o /opt/SUNWsunpc/drvr/sunpcmod.sun4m_54.o /opt/SUNWsunpc/drvr/storekernname.sun4c /opt/SUNWsunpc/drvr/storekernname.sun4m /opt/SUNWsunpc/drvr/S10storekernname /opt/SUNWsunpc/drvr/sunpcload /opt/SUNWsunpc/roms/sunpc.rom /opt/SUNWsunpc/roms/hwv7vga.rom /opt/SUNWsunpc/novell/lib/libnovell.so.1.1 Problem Description: 101636-05: 1153588 - SunPC hangs on multiprocessor system 1155014 - Text entered in SunPC window echoes in startup shelltool 1156499 - SunPC doesn't recognize the embedded keypad in the Compact1 keyboard 1159140 - Printing to parallel port from SunPC hardware session causes system to hang 1161085 - DOS application using sharing mode generates share_dos2unix: bad dosmode 0x82 1170490 - ICC78300 Compiler doesn't work on software sessions 1174115 - Can't use environment variables when mounting drives /ms. 1175561 - SunPC on a ZX (LEO) framebuffer does not show text Other fixes in this revision of the patch include: - Support for Solaris 2.4. - Bug fixes in the DOS window launched from MS-Windows. - SunPC properly receives keyboard focus on startup. - DVMA support for the cg14. - Support for the A24. 101636-04: 1155021 - Turbo GX and SunPC hardware card don't work together 1155215 - SunPC hardware card causes panics on sun4m 1156389 - SunPC -fp option doesn't work 1156394 - SunPC doesn't run on ZX frame buffer and Solaris 2.3 1157137 - Quick Basic BSAVE doesn't work on SunPC Known Problems: --------------- SunPC software sessions display extra vertical lines on systems with ZX (LEO) Framebuffers running Solaris 2.4 and this patch. Systems running Solaris 2.3 are not effected. When using the A24 frame buffer, you must either run SunPC with the '-visual pseudocolor' argument (ie: sunpc -visual pseudocolor) or start OpenWindows with a default depth of 8 (ie: openwin -dev /dev/fb defdepth 8). The sunpc_install script must be run outside of OpenWindows (see the Special Install Instructions) for the following reasons: - A conflict with the OpenWindows hardware cursor. - Sunpc_install on Solaris 2.3 Edition 4 has been observed to cause the drvconfig process to not exit properly. This problem is currently under investigation. As long as sunpc_install is run from the console (ie. outside of OpenWindows), no adverse effects should be seen. 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: ----------------------------- This patch is only for sun4c and sun4m systems running Solaris 2.3 or later. If you are running Solaris 2.4 or later, you must exit OpenWindows before running the sunpc_install script. After running the sunpc-install script, restart OpenWindows before running SunPC. Before installing this patch, exit any current SunPC session and verify that no SunPC process is running: 1) ps -ef |grep spc After installing the patch, do the following: 1) Become super-user. 2) Reinstall sunpc: cd /opt/SUNWsunpc/bin (or wherever SunPC is installed) ./sunpc_install 3) Exit super-user and run SunPC as before. Note: You do NOT need to reboot your system after installing this patch. 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. Any previously installed packages
in the patch should have been removed. See the log file
for the reason for failure. 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.
Patch Backout Errors:
---------------------
Error message:
Patch has not been successfully applied to this system.
Explanation and recommended action: The user has attempted to back
out a patch that was never applied to this system. It is
possible that the patch was applied, but that the patch
directory /var/sadm/patch/ was deleted somehow.
If this is the case, the patch cannot be backed out. The
user may have to restore the original files from the
initial installation CD.
Error message:
This patch was obsoleted by patch $1.
Patches must be backed out in the order in
which they were installed. Patch backout aborted.
Explanation and recommended action: The obsoleted contents of an
older patch rev that apparently still exists under /var/sadm/patch
should never be restored out of sequence. This could undermine
the integrity of the more current patch rev installed and the
restoration of the files it has saved.
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