Patch-ID# 102058-10 Keywords: ATI Boca Cirrus Compaq Diamond Matrox Oak P9100 S3 Stealth STB Trio Synopsis: OpenWindows 3.4_x86: New video card support for Solaris 2.4 X86 Date: May/13/96 Solaris Release: 2.4_x86 SunOS Release: 5.4_x86 Unbundled Product: OpenWindows Unbundled Release: 3.4_x86 Relevant Architectures: i386 BugId's fixed with this patch: 1161494 1172443 1173469 1173503 1173773 1173985 1174387 1174477 1174561 1176285 1179339 1183990 1193138 1200058 1200644 1200858 1210704 1210745 1211889 Changes incorporated in this version: Support has been added for the following video cards: Board Model Chipset ----------------------------------------------------------- Acer ET4000/W32 | ET4000/W32 ----------------------------------------------------------- AST Manhanttan 5090P | Cirrus Logic GD5424 ----------------------------------------------------------- ATI Mach64 | ATI Mach64 ----------------------------------------------------------- ATI Mach64CT | ATI Mach64CT ----------------------------------------------------------- ATI Graphics ProTurbo | ATI Mach64 ----------------------------------------------------------- ATI Graphics Ultra Plus | ATI Mach32 ----------------------------------------------------------- ATI Graphics Ultra Pro | ATI Mach32 ----------------------------------------------------------- ATI Graphics WinTrubo | ATI Mach64 ----------------------------------------------------------- ATI Graphics Xpression | ATI Mach64 ----------------------------------------------------------- Boca Voyager 64 | S3 Trio64 ----------------------------------------------------------- Cirrus 5420 W/512K | Cirrus Logic GD5420 ----------------------------------------------------------- Cirrus 5424 W/512K | Cirrus Logic GD5424 ----------------------------------------------------------- Cirrus 5428 W/512K | Cirrus Logic GD5428 ----------------------------------------------------------- Cirrus 5430 | Cirrus Logic GD5430 ----------------------------------------------------------- Cirrus 5434 | Cirrus Logic GD5434 ----------------------------------------------------------- Compaq QVision 1024 | Triton ----------------------------------------------------------- Compaq QVision 1280 | QVision1280 ----------------------------------------------------------- Compaq QVision 2000 | Matrox MGA-2 ----------------------------------------------------------- Compaq ProLiant | Cirrus Logic GD5420 ----------------------------------------------------------- Compaq ProSignia Series | Cirrus Logic GD5420 ----------------------------------------------------------- Compaq ProSignia 300 Series | Cirrus Logic GD5424 ----------------------------------------------------------- DEC DECpc XL 590 | Cirrus Logic GD5428 ----------------------------------------------------------- Dell OptiPlex DGX 590 | ATI Mach64 ----------------------------------------------------------- Dell OptiPlex XMT 590 | S3 Vision864 ----------------------------------------------------------- Dell PowerEdge SP 5XX | ATI Mach32 ----------------------------------------------------------- Diamond SpeedStar 64 | Cirrus Logic GD5434 ----------------------------------------------------------- Diamond Stealth 32 | Tseng Labs W32P ----------------------------------------------------------- Diamond Stealth 64 DRAM | S3 Vision864 ----------------------------------------------------------- Diamond Stealth 64 DRAM | S3 Trio64 ----------------------------------------------------------- Diamond Stealth 64 VRAM | S3 Vision964 ----------------------------------------------------------- Diamond Stealth 64 Video DRAM| S3 Vision868 ----------------------------------------------------------- Diamond Stealth 64 Video VRAM| S3 Vision968 ----------------------------------------------------------- Diamond Stealth 64 Graphics | S3 Trio64 2000 Series | S3 Vision864 ----------------------------------------------------------- Diamond Stealth 64 Video | S3 Vision868 2000 Series | ----------------------------------------------------------- Diamond Stealth 64 Video | S3 Trio64V+ 2001 Series | ----------------------------------------------------------- Diamond Stealth 64 Video | S3 Vision968 3000 Series | ----------------------------------------------------------- Diamond Viper VLB/PCI | Weitek Power 9000 ----------------------------------------------------------- Diamond Viper SE | Weitek Power 9100 ----------------------------------------------------------- Diamond Viper Pro | Weitek Power 9100 ----------------------------------------------------------- Elsa Winner 1000 | S3 928 ----------------------------------------------------------- Elsa Winner 2000 | S3 928 ----------------------------------------------------------- Elsa Winner 1000 Pro | S3 Vision864 ----------------------------------------------------------- Elsa Winner 2000 Pro | S3 Vision964 ----------------------------------------------------------- Everex FIC 864P | S3 Vision864 ----------------------------------------------------------- Everex VGA Trio64 | S3 Trio64 ----------------------------------------------------------- Everex ViewPoint 64P | S3 Vision864 ----------------------------------------------------------- Ergo Power Brick | Western Digital 90C24 See Laptop Notes | ----------------------------------------------------------- HP NetServer LC/LE/LF | TVGA 9000i ----------------------------------------------------------- HP Vectra VL2 | Cirrus Logic GD5428 ----------------------------------------------------------- HP Vectra XM2i | S3 Vision864 ----------------------------------------------------------- HP Vectra XU | S3 Vision864 with | ATT 21C498 RAMDAC ----------------------------------------------------------- HP Vectra XU | S3 Vision864 with | STG 1702 RAMDAC ----------------------------------------------------------- IBM Personal Computer | Cirrus Logic GD5430 300-486 Series | ----------------------------------------------------------- IBM Personal Computer | S3 Vision864 300 Series | ----------------------------------------------------------- IBM Personal Computer | S3 Vision864 700 Series | ----------------------------------------------------------- IBM PS/Value Point | S3 Vision864 Performance Series | ----------------------------------------------------------- Intel Professional/GX | ATI Mach32 High Resolution | ----------------------------------------------------------- Intergraph TD1 | S3 928 ----------------------------------------------------------- Intergraph G91 | Weitek Power 9100 ----------------------------------------------------------- Matrox MGA Impression | Matrox MGA-1 ----------------------------------------------------------- Matrox MGA Impression Plus | Matrox MGA-3 ----------------------------------------------------------- Matrox MGA Millenum | Matrox STORM ----------------------------------------------------------- Matrox MGA Ultima | Matrox MGA-2 ----------------------------------------------------------- Matrox MGA Ultima Plus | Matrox MGA-2 ----------------------------------------------------------- Matrox MGA Ultima Plus 200 | Matrox MGA-2 ----------------------------------------------------------- Micronics Mpower 4 Plus | ATI Mach64 (Mother board) | ----------------------------------------------------------- Miro Crystal 20SD | S3 Vision864 with | ATT 20C498 RAMDAC ----------------------------------------------------------- Miro Crystal 20SD | S3 Vision864 with | S3 SDAC ----------------------------------------------------------- Miro Crystal 40SV | S3 Vision964 ----------------------------------------------------------- NANAO EizoAccel AA51 | F82C480 ----------------------------------------------------------- NANAO HA50/HL50 | S3 928 ----------------------------------------------------------- NANAO HA60 | S3 928 ----------------------------------------------------------- NEC Versa M75C | Chips & Technology 65540 See Laptop Notes | ----------------------------------------------------------- NEC Versa M75HC | Chips & Technology 65545 See Laptop Notes | ----------------------------------------------------------- Number Nine 9FX Motion 531 | S3 Vision868 ----------------------------------------------------------- Number Nine 9FX Motion 771 | S3 Vision968 ----------------------------------------------------------- Number Nine #9GXE | S3 928 ----------------------------------------------------------- Number Nine #9GXE64 | S3 Vision864 ----------------------------------------------------------- Number Nine #9GXE64 | S3 Trio64 ----------------------------------------------------------- Number Nine #9GXE64 Pro | S3 Vision964 ----------------------------------------------------------- Number Nine Imagine 128 | S3 Imagine128 ----------------------------------------------------------- Oak OTI107 | Oak OTI107 ----------------------------------------------------------- Orchid Fahrenheit 1280 Plus | S3 928 ----------------------------------------------------------- Orchid Kelvin 64 | Cirrus Logic GD5434 ----------------------------------------------------------- S3 928 | S3 928 ----------------------------------------------------------- S3 Trio64V | S3 Trio64V ----------------------------------------------------------- S3 Trio64V+ | S3 Trio64V+ ----------------------------------------------------------- S3 Vision864 | S3 Vision864 ----------------------------------------------------------- S3 Vision864 | S3 Vision864 with | S3 SDAC ----------------------------------------------------------- S3 Vision868 | S3 Vision868 ----------------------------------------------------------- SPEA V7-Mirage P-64 | S3 Vision868 ----------------------------------------------------------- STB Lightspeed VL | Tseng Labs W32P ----------------------------------------------------------- STB Nitro PCI | Cirrus Login GD5434 ----------------------------------------------------------- STB Powergraph 64 | S3 Trio64 ----------------------------------------------------------- STB Powergraph 64 Video | S3 Trio64V+ ----------------------------------------------------------- STB Powergraph Pro | S3 Vision864 ----------------------------------------------------------- STB Velocity 64V | S3 Vision968 ----------------------------------------------------------- Toshiba J3100 | WD 90C31A ----------------------------------------------------------- Toshiba 4900 CT | Chips & Technology 65545 See Laptop Notes | ----------------------------------------------------------- Trident TVGA 9000i | Trident TVGA 9000i ----------------------------------------------------------- NOTE: To avoid user-level program core dumps after installing any Solaris 2.4 x86 Video Driver Update, it is recommended that you install the latest revision of the Solaris 2.4 x86 jumbo kernel patch, ID 101946. See "Solaris 2.4 x86 Jumbo Kernel Pateh" on page 7 for information on how to obtain the patch. NOTE: The #9GXE support in this driver update obsoletes the one available in the Solaris X86 2.4 release. If you have any of these boards in your machine, you must run "kdmconfig" to reconfigure your window system. Please refer to the "Special Install Instructions" section for further detail. NOTE: The ATI Mach64 support includes cards with the following RAMDACs: ATI68860, ATT20C408, ATT20C491, ATTC498, and STG1702. NOTE: Gateway ATI GX Mach 64 PCI Video card is the same as ATI WinTurbo video card. Configure this card as "ATI WinTurbo". NOTE: Boca Voyager 64 uses a S3 Trio64. Configure this card as "S3 Trio64 (2MB)". NOTE: Generic support for video cards with Chips & Technologies 65540 Chips & Technologies 65545 Cirrus Logic 5420 w/512k Cirrus Logic 5424 w/512k Cirrus Logic 5428 w/512k S3 928 S3 Trio64 S3 Trio64V+ S3 Vision864 S3 Vision864 and S3 SDAC RAMDAC S3 Vision868 Trident TVGA9000i (512k) are provided. If user has a video card with above chip set but is not included in the hardware support list then user should use the generic entry. NOTE: Support has also been added for the following monitors. Intergraph InterVue 20 Intergraph InterVue 21 Intergraph InterVue 27 NEC 5FGe NEc 6FGp LAPTOP NOTES: ------------- WARNING: Laptop Users must read this section before starting windowing system CAUTION: Even though many notebook computers are capable of supporting external monitors at a resolution highre than 640x480, you should not change the default video resolution on a notebook computer to be anything other than what the internal monitor can support. Higher resolution video modes do not work on the integrated LCD screen; if you happen to start up the window system without an external monitor, you may not be able to see anything on the LCD screen. In some cases, this may even damage your LCD screen. Support for Panning in 8-bit mode Added This Video Driver Update adds support for panning on the following laptop systems: NEC Versa M75C NEC Versa M75HC Toshiba 4900ct in 8-bit mode. Previously, this was only supported in 4-bit mode. Configuring Secondary Display Following instructions allow you to configure a secondary display for notebook computers that have an external monitor. The external monitor will be configured for 1024x768, 256 colors. 1. Become the superuser. 2. Change to directory /etc/openwin/server/etc. 3. Copy appropriate OpenWindows configuration file for your notebook, a. Toshiba 4900 CT cp /usr/openwin/server/etc/OWconfig.4900ct OWconfig b. NEC Versa M75 C cp /usr/openwin/server/etc/OWconfig.vm75c OWconfig c. NEC Versa M75 HC cp /usr/openwin/server/etc/OWconfig.vm75hc OWconfig 4. Exit from superuser status. 5. Start the OpenWindows software, indicating which display to use. a. To use the internal display, type "openwin -display :0" b. To use the internal display, type "openwin -display :1" Note: Panning is set to 1024x768 in these OWconfig sample files for LCD display. Note: The Openwindows configuration file that is being installed assumes you are using a built-in PS/2 style mouse. For more information about notebook computer configuration, see the Solaris 2.4 Notebook Supplement Guide ( part number 801-6619-14). Patches accumulated and obsoleted by this patch: 101860-01. Patches which conflict with this patch: Patches required with this patch: 102059-10 Obsoleted by: Files included with this patch: openwin/server/etc/OWconfig.4900ct openwin/server/etc/OWconfig.vm75c openwin/server/etc/OWconfig.vm75hc openwin/server/lib/libaccel.so.1 openwin/server/modules/ddxNANAO928.so.1 openwin/server/modules/ddxSUNWati.so.1 openwin/server/modules/ddxSUNWchips.so.1 openwin/server/modules/ddxSUNWcirrus.so.1 openwin/server/modules/ddxSUNWcompaq.so.1 openwin/server/modules/ddxSUNWmatrox.so.1 openwin/server/modules/ddxSUNWnumber9.so.1 openwin/server/modules/ddxSUNWoak.so.1 openwin/server/modules/ddxSUNWp9000.so.1 openwin/server/modules/ddxSUNWp9100.so.1 openwin/server/modules/ddxSUNWs3.so.1 openwin/server/modules/ddxSUNWtrident.so.1 openwin/server/modules/ddxSUNWtseng.so.1 openwin/share/etc/devdata/SUNWaccel/boards/ati/mach64-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/ati/mach64ct-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/ati/mach64ct-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/ati/mpower4+.xqa openwin/share/etc/devdata/SUNWaccel/boards/ati/turbo2.xqa openwin/share/etc/devdata/SUNWaccel/boards/ati/turbo4.xqa openwin/share/etc/devdata/SUNWaccel/boards/ati/ultra+.xqa openwin/share/etc/devdata/SUNWaccel/boards/ati/ultrapro1.xqa openwin/share/etc/devdata/SUNWaccel/boards/ati/ultrapro2.xqa openwin/share/etc/devdata/SUNWaccel/boards/ati/winturbo.xqa openwin/share/etc/devdata/SUNWaccel/boards/ati/xpression.xqa openwin/share/etc/devdata/SUNWaccel/boards/ati/xpression1.xqa openwin/share/etc/devdata/SUNWaccel/boards/chips/65540.xqa openwin/share/etc/devdata/SUNWaccel/boards/chips/65545.xqa openwin/share/etc/devdata/SUNWaccel/boards/cirrus/5090p.xqa openwin/share/etc/devdata/SUNWaccel/boards/cirrus/5420-0.5.xqa openwin/share/etc/devdata/SUNWaccel/boards/cirrus/5424-0.5.xqa openwin/share/etc/devdata/SUNWaccel/boards/cirrus/5428.xqa openwin/share/etc/devdata/SUNWaccel/boards/cirrus/5430-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/cirrus/5430-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/cirrus/5434-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/cirrus/5434-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/cirrus/5434-4.xqa openwin/share/etc/devdata/SUNWaccel/boards/compaq/proliant.xqa openwin/share/etc/devdata/SUNWaccel/boards/compaq/prosignia.xqa openwin/share/etc/devdata/SUNWaccel/boards/compaq/prosignia300.xqa openwin/share/etc/devdata/SUNWaccel/boards/compaq/qvis1024.xqa openwin/share/etc/devdata/SUNWaccel/boards/compaq/qvis1280-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/compaq/qvis1280-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/compaq/qvis2000.xqa openwin/share/etc/devdata/SUNWaccel/boards/dec/xl590.xqa openwin/share/etc/devdata/SUNWaccel/boards/dell/optiplex.xqa openwin/share/etc/devdata/SUNWaccel/boards/dell/optiplex_dgx.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/p9100-pci.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/p9100pro-pci.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/ss64-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/ss64-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st32-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st32-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64-1b.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64-1c.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64-2b.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64-2c.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64-4.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64v-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64v-4.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64v2000-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64v2000-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64v2001-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64v2001-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64v3000-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64v3000-4.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64v3000ibm-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64v3000ibm-4.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64vd-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond/st64vd-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/diamond2/p9100-vlb.xqa openwin/share/etc/devdata/SUNWaccel/boards/elsa/win1000-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/elsa/win1000-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/elsa/win1000p-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/elsa/win1000p-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/elsa/win2000-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/elsa/win2000p-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/elsa/win2000p-4.xqa openwin/share/etc/devdata/SUNWaccel/boards/everex/864p-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/everex/864p-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/everex/ev64p-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/everex/ev64p-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/everex/trio64p-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/everex/trio64p-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/hp/netsvr.xqa openwin/share/etc/devdata/SUNWaccel/boards/hp/vectravl2.xqa openwin/share/etc/devdata/SUNWaccel/boards/hp/vectraxm2i-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/hp/vectraxu.xqa openwin/share/etc/devdata/SUNWaccel/boards/hp/vectraxu_att21c498.xqa openwin/share/etc/devdata/SUNWaccel/boards/ibm/pc300GD5430-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/ibm/pc300S3864-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/ibm/pc300S3864-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/ibm/pc700S3864-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/ibm/pc700S3864-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/ibm/rocket864-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/ibm/rocket864-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/intel/profgx-hires.xqa openwin/share/etc/devdata/SUNWaccel/boards/intergraph/g91-4.xqa openwin/share/etc/devdata/SUNWaccel/boards/intergraph/td1-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/intergraph/td1-4.xqa openwin/share/etc/devdata/SUNWaccel/boards/matrox/mga-imp.xqa openwin/share/etc/devdata/SUNWaccel/boards/matrox/mga-mil2.xqa openwin/share/etc/devdata/SUNWaccel/boards/matrox/mga-mil4.xqa openwin/share/etc/devdata/SUNWaccel/boards/matrox/mga-mil8.xqa openwin/share/etc/devdata/SUNWaccel/boards/matrox/mga-plus2.xqa openwin/share/etc/devdata/SUNWaccel/boards/matrox/mga-ult1.xqa openwin/share/etc/devdata/SUNWaccel/boards/matrox/mga-ult2+.xqa openwin/share/etc/devdata/SUNWaccel/boards/matrox/mga-ult2.xqa openwin/share/etc/devdata/SUNWaccel/boards/matrox/mga-ult4h.xqa openwin/share/etc/devdata/SUNWaccel/boards/miro/miro20sd-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/miro/miro20sd-1b.xqa openwin/share/etc/devdata/SUNWaccel/boards/miro/miro20sd-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/miro/miro20sd-2b.xqa openwin/share/etc/devdata/SUNWaccel/boards/miro/miro40sv-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/miro/miro40sv-4.xqa openwin/share/etc/devdata/SUNWaccel/boards/nec/vm75c.xqa openwin/share/etc/devdata/SUNWaccel/boards/nec/vm75hc.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/gxe-1a.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/gxe-1b.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/gxe-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/gxe-3.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/gxe64-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/gxe64-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/gxe64p-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/gxe64p-4.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/gxetrio64-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/gxetrio64-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/im128.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/motion531-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/motion531-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/motion771-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/number9/motion771-4.xqa openwin/share/etc/devdata/SUNWaccel/boards/oak/oti107-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/orchid/f1280+.xqa openwin/share/etc/devdata/SUNWaccel/boards/orchid/kelvin-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/orchid/kelvin-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/s3/864-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/s3/864-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/s3/864sdac-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/s3/864sdac-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/s3/868-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/s3/868-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/s3/928-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/s3/928-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/s3/928-4.xqa openwin/share/etc/devdata/SUNWaccel/boards/s3/trio64-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/s3/trio64-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/s3/trio64v+1.xqa openwin/share/etc/devdata/SUNWaccel/boards/s3/trio64v+2.xqa openwin/share/etc/devdata/SUNWaccel/boards/spea/mirage64-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/stb/lightspeed.xqa openwin/share/etc/devdata/SUNWaccel/boards/stb/nitro-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/stb/nitro-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/stb/nitro-4.xqa openwin/share/etc/devdata/SUNWaccel/boards/stb/pg64-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/stb/pg64-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/stb/pg64v+2.xqa openwin/share/etc/devdata/SUNWaccel/boards/stb/pgpro-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/stb/pgpro-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/stb/velocity-2.xqa openwin/share/etc/devdata/SUNWaccel/boards/stb/velocity-4.xqa openwin/share/etc/devdata/SUNWaccel/boards/toshiba/4900ct.xqa openwin/share/etc/devdata/SUNWaccel/boards/trident/tvga9000i.xqa openwin/share/etc/devdata/SUNWaccel/boards/tseng/vga1600.xqa openwin/share/etc/devdata/SUNWaccel/boards/tseng/w32p-1.xqa openwin/share/etc/devdata/SUNWaccel/boards/tseng/w32p-2.xqa openwin/share/etc/devdata/SUNWaccel/etc/Xmessages openwin/share/etc/devdata/SUNWaccel/etc/Xtimings openwin/share/etc/devdata/SUNWaccel/monitors/hitachi/20mvx.vda openwin/share/etc/devdata/SUNWaccel/monitors/ibm/vgacolor.vda openwin/share/etc/devdata/SUNWaccel/monitors/ibm/vgamono.vda openwin/share/etc/devdata/SUNWaccel/monitors/ingr/mdsp1260a.vda openwin/share/etc/devdata/SUNWaccel/monitors/ingr/mdsp1270a.vda openwin/share/etc/devdata/SUNWaccel/monitors/ingr/mdsp1280a.vda openwin/share/etc/devdata/SUNWaccel/monitors/lcd/nbcolor.vda openwin/share/etc/devdata/SUNWaccel/monitors/lcd/nbmono.vda openwin/share/etc/devdata/SUNWaccel/monitors/lcd/nbsvga.vda openwin/share/etc/devdata/SUNWaccel/monitors/mfreq/mfreq38.vda openwin/share/etc/devdata/SUNWaccel/monitors/mfreq/mfreq48.vda openwin/share/etc/devdata/SUNWaccel/monitors/mfreq/mfreq56.vda openwin/share/etc/devdata/SUNWaccel/monitors/mfreq/mfreq64.vda openwin/share/etc/devdata/SUNWaccel/monitors/mfreq/mfreq76.vda openwin/share/etc/devdata/SUNWaccel/monitors/mfreq/mfreq80.vda openwin/share/etc/devdata/SUNWaccel/monitors/mfreq/mfreq85.vda openwin/share/etc/devdata/SUNWaccel/monitors/mfreq/svga.vda openwin/share/etc/devdata/SUNWaccel/monitors/nec/nec2a.vda openwin/share/etc/devdata/SUNWaccel/monitors/nec/nec3d.vda openwin/share/etc/devdata/SUNWaccel/monitors/nec/nec4d.vda openwin/share/etc/devdata/SUNWaccel/monitors/nec/nec5d.vda openwin/share/etc/devdata/SUNWaccel/monitors/nec/nec5fge.vda openwin/share/etc/devdata/SUNWaccel/monitors/nec/nec6gp.vda openwin/share/etc/devdata/SUNWaccel/monitors/sni/mcm1701-90.vda openwin/share/etc/devdata/SUNWaccel/monitors/sni/mcm2102-15.vda openwin/share/etc/devdata/SUNWaccel/monitors/sni/mcm2102-90.vda openwin/share/etc/keytables/J3100_x86.kt.Z Problem Description: (Bug numbers are given where applicable) o The Diamond Viper VLB adapter does not work on some systems that have both PCI and VESA Local Bus support on the motherboard. The OpenWindows software will fail with an error message when you attempt to start it. The Solaris P9000 driver expects a PCI version of the Diamond Viper board if the system support PCI. Workaround: Use the Diamond Viper PCI adapter on those systems that support both bus types. o The Diamond Viper Pro VLB adapter does not work on some systems that have both PCI and VESA Local Bus support on the motherboard. The OpenWindows software will fail with an error message when you attempt to start it. The Solaris driver expects a PCI version of the Diamond Viper board if the system support PCI. Workaround: Use the Diamond Viper PCI adapter on those systems that support both bus types. o Some VESA Local Bus motherboards do not properly support the default address range used by the Diamond Viper VLB adapter. To find a workable address for a particular system may require some experimentation. See "Enabling Video Support for the Diamond Viper Accelerator Boards", below, for further information. o Due to hardware conflicts, on some VESA Local Bus (VLB) systems, Diamond Viper Pro VLB card will not function when configured at the default memory address (0xa0000000). If your system appears hung with a blank screen after starting the OpenWindows software, you will need to reboot your system, edit the file /etc/openwin/ server/etc/OWconfig, and change the address on the line that con- tains XSCREENCONFIG to 0xc0000000. o Some versions of the Orchid Kelvin 64 VLB video card have memory addressing limitations that may cause problems if your system contains 32 Mbytes or more of RAM. A newer revision of this board addresses these problems. Unfortunately, there is no obvious distinction made between revisions of this card. Therefore, if your system has 32 Mbytes or more of RAM and you observe symptoms such as a fuzzy display or random vertical lines in your OpenWindows environment, contact Orchid Technology to request a newer revision of this card. o The Number Nine Imagine128, Number Nine #9GXE64 and Number Nine #9GXE64 Pro video cards do not support interlaced mode. Consequently, configuring the window system using a monitor type of "MultiFrequency-38kHZ(up to 1024x768 interlaced)" or "MultiFrequency-56kHZ(up to 1280x1024 interlaced)" will cause the window system to fail. Workaround: Use a monitor that can support 1024x768 or 1280x1024 in non-interlaced mode. 1161494 Under the Solaris operating environment, the Diamond Viper card is not compatible with motherboard that has a VEGA Symphony chipset. This combination may cause the system to panic or reboot. If the VEGA Symphony chipset is present on the motherboard, do not use the Diamond Viper video card. 1176285 Users should be careful when setting the XGLHOME shell environment variable prior to starting openwindows. If XGLHOME points to a non-existent path (or one that doesn't contain the XGL run-time binaries), then any program that uses the PEX extension (including XGL programs on most display adaptors) will cause the server to abort. Prior to to running the 'openwin' command, make sure your XGLHOME enironment variable is either not set, or points to a valid XGL path for the system you are using. 1173503 On Systems with video cards that use the S3 Vision 864 or S3 Vision 964 chipset, windows sometimes appear to "wrap" from one side of the monitor screen to the other. The number of pixels that wrap varies from 2 to 8 pixels depending on the color depth. Workaround: Avoid placing windows within a few pixels of the edge of the screen. 1173469 On systems with Diamond Stealth 64 video card installed, occasionally the mouse cursor will appear as two images that move in unison when the cursor is moved, this may last for a short period of time before the two images become one again. These same symptoms occur on system with the Number Nine #9GXE, Number Nine #9GXE64, Number Nine #9GXE64 Pro and the Elsa Winner2000Pro cards. 1173773 After running xlock, a white border may be seen around the screen on systems with video cards that use the Tseng Lab W32P chipset. The white border disappears after the user unlocks the screen. 1174387 On systems with the Diamond Stealth 32 VLB/PCI card, you may lose control of the mouse pointer when xfontsel is used to select a font with a font family of lucida, and a point size of 180 or above. If this occurs, reset the system. 1174477 Systems with the ATI Graphics Turbo video adapter may fail when used with a resolution of 1600x1200. According ATI, the ATI Graphics Turbo does not support 1600x1200 mode. Workaround: Use a lower resolution. 1179339 The ATI Ultra Pro VLB video card with a Mach32 graphic chip, a TI68875 BFN RAMDAC, and 2 Mbytes of DRAM may not work properly if the "ATI Graphic Ultro Pro (2MB)" entry is selected when configuring the window system. Vertical bars get displayed on the screen. Workaround: If you have this version of the card, choose the "ATI Graphic Ultra Pro (1MB)" entry when configuring the window system but note that you will not be able to use a resolution of 1280x1024. Note also that the ATI Graphic Ultra Pro VLB video card with VRAM does not have this problem. 1183990 Matrox Impression Plus fails at 1280x1024, 8-bit color mode with "MultiFrequency-64kHz" monitor. Workaround: Use different resolution or monitor. 1193138 QVision 1024/E:black lines appear along a client's title bar at input focus If the window manager is olwm and the resource OpenWindows.SetInput is set to "followmouse" in the .Xdefaults or .OWdefaults file you will notice black rectangular bars extending outward from the title bar of every client, everytime it gets input focus. Performing a refresh operation can cause the bars to disappear, however, on a temporary basis only. The workaround is to set the input focus to be "Click to Type". In other words the OpenWindows.SetInput resource should be changed to "select" instead of "followmouse". The Properties selection in the Workspace menu allows you to change the type of input focus without manually editing any files. Use the Miscellaneous Category in the Workspace Properties and make sure the "Set Active Window" property has "Click Mouse" highlighted instead of "Move Pointer". 1200644 On NEC VERSA M/75HC, only a quarter of the normal screen is displayed on the LCD screen. This happens when user select 800x600, 256 color resolution for LCD monitor or executing "openwin -display :0" with /usr/openwin/server/etc/OWconfig.vm75hc copied to /etc/openwin/server/etc/OWconfig, as described in Laptop Note section. Workaround: press Fn-LCD/CRT Keys three times then the display on LCD will be corrected. 1200058 NEC Versa M75 may show white screen after invoking kdmconfig, user will not be able to configure the system when this happen. Workaround: Do not run kdmconfig and use the sample OWconfig file in the release, see Laptop Note for more information. 1200858 The Diamond Viper SE adapter will not run with a refresh rate above 75 kHz in 1024x768 resolution. (See the manufacturer's manual to verify the maximum horizontal refresh rates.) In the current release, it also does not work with a refresh rate of 56 kHz in 1280x1024 resolution. Workaround: Use a refresh rate of 64 kHz with 1280x1024 resolution. 1211889,1210704 The Matrox Millenium card may exhibit problems with some high resolutions, color depths, and refresh rates. 1210745 The Matrox MGA Impression (VLB) video card does not support 1600x1200 resolution in the current release. The following problems only apply to 24-bit depth color: 1172443 Applications using XIL display the wrong colors when used with 24 bit display adapter. Imagetool is an example of such an application. The problem is that XIL does not handle the byte ordering of 24-bit image correctly, thus the colors are wrong in the displayed image. Workaround: Use an application that does not use XIL and can display 24-bit images correctly. xv is an example of a shareware application that is available over the Internet. 1173985 iconedit dies when saving a 24-bit image to a file. 1174561 The STB LIGHTSPEED VL video card used in 800x600 resolution, 24-bit color mode does not work properly with the Sony CPD 1604S monitor. Workaround: Do not use this particular monitor type at that resolution and color depth. o Wabi will not run under 24-bit depth mode. o The IslandPaint application does not work properly under 24-bit mode. All of the button icons on the left-hand side of the window are either missing images or have incorrect ones displayed. Note: Please refer to "Changes incorporated in this version:" for chipset information. Patch Installation Instructions: -------------------------------- Generic 'installpatch' and 'backoutpatch' scripts are provided within each patch package with instructions appended to this section. After you complete the 'installpatch' procedure, additional configuration steps are necessary and are described below. Special Install Instructions: ----------------------------- NOTE: New software in this Driver Update replaces the support for the Number Nine #9GXE ISA and VLB display adapters included in the Solaris 2.4 release. If you have one of these video boards, you will need to reconfigure your window system as described in this section to enable the new Number Nine #9GXE support. If, for some reason you do not want to use the new Number Nine #9GXE video support in this release, you must back two patches. See the README file in /var/sadm/patch/102058-10 and /var/sadm/patch/102059-10 for instructions on how to back out these two patches. You must install patch 102059-10 to make this patch work. Patch 102059-10 provides kernel drivers for new video drivers and new kdmconfig to configure systems with new video drivers. In order to enable the new hardware support, you must reconfigure the window system. The kdmconfig program will allow you to do this. To do this, as superuser, run: # kdmconfig -u This will complete silently; then run: # kdmconfig -cf The kdmconfig program will now ask you to configure your keyboard, mouse, and display adapter. The list of display adapters will appear alphabetically by vendor. To quickly scroll through the list, type the first letter of the vendor name. For example, type `M' to get to the first Matrox MGA entry. (This short cut can only be done to scroll down the list, not up.) Some of the names of video adapters on the list may be followed by the amount of video memory on the card. For example, `Diamond Stealth 64 (2MB)' indicates 2 MBytes of memory on the card. Be sure to select one that matches your configuration. Note - In order to choose one of The Diamond Viper video card entries displayed by kdmconfig, you will need to select an entry that matches your monitor. After you have selected your display adapter, you may be asked additional questions regarding screen size, color depth, display resolution, and monitor type. Select the Correct Monitor Size, Color Depth, Resolution, and Monitor from the list displayed by kdmconfig. For all the Intergraph monitors listed above please choose 19-inch as the screen size. Selecting `8' for color depth means your adapter is capable of 8-bit color (256 colors); `24' is equivalent to 16,777,216 colors. After choosing monitor size, color depth, and resolution, you will be shown a list of supported monitors (unless you have already chosen one of the Diamond Viper card entries). If you have a multisync/multifrequency monitor, be sure to check the manufacturer's documentation to find out the maximum horizontal synchronization rate supported by the monitor. For example, if you have a ViewSonic 17 monitor, which has a maximum horizontal sync rate of 82kHz, select `MultiFrequency-80KHz (up to 1600x1200@60 Hz)' as the monitor type. If your system contains one of the newly supported Diamond Viper video cards, there are additional steps you must take to enable the Solaris p9000 device driver. This driver is disabled by default and must be enabled before it can be used under the Solaris environment. Proceed to "Enabling Video Support for the Diamond Viper Accelerator Boards" below. If your system does not have one of the Diamond Viper cards, the installation of the Solaris 2.4 x86 Driver Update 2 (Video) is complete and you can now run the openwin command to start the window system. Enabling Video Support for the Diamond Viper, Viper Pro and Viper SE Boards --------------------------------------------------------------- Warning - Diamond Viper video card user must reconfigure the windowing system after installing Solaris 2.4 Driver Update 6, this is not necessary for Diamond Viper SE or Diamond Viper Pro user if 2.4 Solaris Driver Updated 5 is installed on the system. Diamond Viper cards are graphics accelerator boards. The Diamond Viper VLB and Diamond Viper PCI are based on the Weitek p9000 accelerator chip. The Diamond Viper SE, and Diamond Viper Pro are based on the Weitek p9100 accelerator chip. Resolutions at which graphics operations are accelerated with these boards range from 800x600 to 1280x1024, all with an 8-bit color depth (256 colors). The Diamond Viper card can also emulate a standard VGA at 640x480, although in this configuration, the board does not accelerate graphics operations. When running the kdmconfig configuration program for the Diamond Viper VLB card, you will be asked to assign its memory address. The default address range, 0xa0000000 to 0xa03fffff, should be acceptable for most systems, but if it conflicts with any other device, then user must select a different address range, 0x20000000 to 0x203fffff or 0x80000000 to 0x803fffff. Instructions to install patch using "installpatch" -------------------------------------------------- 1. Become super-user. 2. Apply the patch by typing: //installpatch / where is the directory containing the patch and is the patch number. must be a full path name. Example: # /tmp/123456-01/installpatch /tmp/123456-01 3. If any errors are reported, see "Patch Installation Errors" in the Command Descriptions section below. Rebooting the system or restarting the application after a successful patch installation is usually necessary to utilize patch. NOTE: 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 the next section for instructions for installing a patch on a client. Instructions for installing a patch on a diskless or dataless client -------------------------------------------------------------------- 1. Before applying the patch, the following command must be executed on the server to give the client read-only, root access to the exported /usr file system so that the client can execute the pkgadd command: share -F nfs -o ro,anon=0 /export/exec/Solaris_2.1_sparc.all/usr The command: share -F nfs -o ro,root= \ /export/exec/Solaris_2.1_sparc.all/usr accomplishes the same goal, but only gives root access to the client specified in the command. 2. Login to the client system and become super-user. 3. Continue with step 2 in the "Instructions to install patch using installpatch" section above. Instructions for backing out patch using "backoutpatch" ------------------------------------------------------- 1. Become super-user. 2. Change directory to /var/sadm/patch: cd /var/sadm/patch 3. Backout patch by typing: /backoutpatch where is the patch number. Example: # 123456-01/backoutpatch 123456-01 4. If any errors are reported, see "Patch Backout Errors" in the Command Descriptions section below. Instructions for identifying patches installed on system: ---------------------------------------------------------- Type: installpatch -p This command produces a list of the patch IDs of the patches that are currently applied to the system. When executed with the -p option, the installpatch command does not modify the system in any way. Command Descriptions -------------------- NAME installpatch - apply patch package to Solaris 2.x system backoutpatch - remove patch package from Solaris 2.x system SYNOPSIS installpatch [-u] [-d] backoutpatch DESCRIPTION These installation and backout utilities apply only to Solaris 2.x associated patches. They do not apply to Solaris 1.x associated patches. These utilities are currently only provided with each patch package and are not included with the standard Solaris 2.x release software. OPTIONS installpatch -u unconditional install, do not verify file attributes -d do not save original files being replaced -p print a list of the patches currently applied on the system DIAGNOSTICS Patch Installation Errors: -------------------------- Error message: Patch has already been applied. Explanation and recommended action: This patch has already been applied to the system. If the patch has to be reapplied for some reason, backout the patch and then reapply it. Error message: This patch is obsoleted by a patch which has already been applied to this system. Application of this patch would leave the system in an inconsistent state. Patch installation is aborted. Explanation and recommended action: Occasionally, a patch is replaced by a new patch which incorporates the bug fixes in the old patch and supplies additional fixes also. At this time, the earlier patch is no longer made available to users. The second patch is said to "obsolete" the first patch. However, it is possible that some users may still have the earlier patch and try to apply it to a system on which the later patch is already applied. If the obsoleted patch were allowed to be applied, the additional fixes supplied by the later patch would no longer be available, and the system would be left in an inconsistent state. This error message indicates that the user attempted to install an obsoleted patch. There is no need to apply this patch because the later patch has already supplied the fix. Error message: The packages to be patched are not installed on this system. Explanation and recommended action: None of the packages to be updated by this patch are installed on the system. Therefore, this patch cannot be applied to the system. Error message: This patch is not applicable to client systems. Explanation and recommended action: The patch is only applicable to servers and standalone machines. Attempting to apply this patch to a client system will have no effect on the system. Error message: The /usr/sbin/pkgadd command is not executable. Explanation and recommended action: The /usr/sbin/pkgadd command cannot be executed. The most likely cause of this is that installpatch is being run on a diskless or dataless client and the /usr file system was not exported with root access to the client. See the section above on "Instructions for installing a patch on a diskless or dataless client". Error message: Patch directory is not of expected format. Explanation and recommended action: The patch directory supplied as an argument to installpatch did not contain any patch packages. Verify that the argument supplied to installpatch is correct. Error message: The following validation errors were found: Explanation and recommended action: Before applying the patch, the patch application script verifies that the current versions of the files to be patched have the expected fcs checksums and attributes. If a file to be patched has been modified by the user, the user is notified of this fact. The user then has the opportunity to save the file and make a similar change to the patched version. For example, if the user has modified /etc/inet/inetd.conf and /etc/inet/inetd.conf is to be replaced by the patch, the user can save the locally modified /etc/inet/inetd.conf file and make the same modification to the new file after the patch is applied. After the user has noted all validation errors and taken the appropriate action for each one, the user should re-run installpatch using the "-u" (for "unconditional") option. This time, the patch installation will ignore validation errors and install the patch anyway. Error message: Insufficient space in /var/sadm to save old files. Explanation and recommended action: There is insufficient space in the /var/sadm directory to save old files. The user has two options for handling this problem: (1) generate additional disk space by deleting unneeded files, or (2) override the saving of the old files by using the "-d" (do not save) option when running installpatch. However if the user elects not to save the old versions of the files to be patched, backoutpatch CANNOT be used. One way to regain space on a system is to remove the save area for previously applied patches. Once the user has decided that it is unlikely that a patch will be backed out, the user can remove the files that were saved by installpatch. The following commands should be executed to remove the saved files for patch xxxxxx-yy: cd /var/sadm/patch/xxxxxx-yy rm -r save/* rm .oldfilessaved After these commands have been executed, patch xxxxxx-yy can no longer be backed out. Error message: Save of old files failed. Explanation and recommended action: Before applying the patch, the patch installation script uses cpio to save the old versions of the files to be patched. This error message means that the cpio failed. The output of the cpio would have been preceded this message. The user should take the appropriate action to correct the cpio failure. A common reason for failure will be insufficient disk space to save the old versions of the files. The user has two options for handling insufficient disk space: (1) generate additional disk space by deleting unneeded files, or (2) override the saving of the old files by using the "-d" option when running installpatch. However if the user elects not to save the old versions of the files to be patched, the patch CANNOT be backed out. Error message: Pkgadd of package failed. 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. Error message: error while adding patch to root template Explanation and recommended action: The install script determined this system to be a client server. The attempt to apply the patch package to the appropriate root template space located under /export/root/templates failed unexpectedly. Check the log file for any failure messages. Correct the problem and re-apply the patch. Patch Backout Errors: --------------------- Error message: Patch has not been 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: 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. 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. After a patch package has been installed pkginfo(1) will not recognize the SUNW_PATCHID macro in the patch package pkginfo file. Instead, to identify patches installed on the system use the grep command method described in the patch README. The pkgadd command shipped with Solaris 2.1 fails (drops core without any error message) when there are more than 100 entries in the /etc/mnttab file. This means that installpatch can fail, because it uses pkgadd. Since this is very likely on any big system with lots of automounts, ANY patch could fail. Applying patch 100901-01 fixes this problem (the README for patch 100901 mentions shutting down the automounter while applying it). SEE ALSO pkgadd(1), pkgchk(1), pkgrm(1), pkginfo(1)