Page 1
TurboGX/TurboGXplus Hardware Installation Guide microsystems Sun Microsystems, Inc. 2500 Garcia Avenue Mountain View, CA 94043 U.S.A. Part No 801-5399-10 Revision A of November 1993...
Page 2
Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK® and Sun™ Graphical User Interfaces were developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry.
Page 3
Connections between the workstation and peripherals must be made using shielded cables in order to maintain compliance with FCC radio frequency emission limits. Modifications Modifications to this device, not approved by Sun Microsystems, Inc., may void the authority granted to the user by the FCC to operate this equipment. DOC Class B Notice — Canada This digital apparatus does not exceed the Class B limits for radio noise emission for a digital apparatus as set out in the Radio Interference Regulations of the Canadian Department of Communications.
Page 13
However, the installation of a TurboGX/TurboGXplus card into a SPARCsystem 600MP series, and SPARCcenter system should only be attempted by a qualified service provider.
Page 14
1. Unpack Peripheral Hardware Platform specific Hardware Installation Guide used 2.Verify Hardware Components with this guide 3. Shut Down the System 4. Install Peripheral Hardware 5. Start Up the System Platform Specific Handbooks 6. Configure the Device TurboGX/TurboGXplus Installation Guide—November 1993...
Page 15
After you perform these tasks, you will be ready to use the TurboGX/TurboGXplus card with your system. Before You Read This Book If you are installing a TurboGX/TurboGXplus card into a SPARCstation or SPARCserver, you should read the Installation Guide that came with your system for additional information.
Page 16
Appendix B describes how to configure your system using the TurboGX/TurboGXplus card and explains how to attach multiple monitors. In addition, it contains a list of monitors supported by the TurboGX/TurboGXplus card. Appendix C describes monitor cable signals. Appendix D describes the troubleshooting procedures.
Page 17
800-6366 SBus Card Installation Guide for Deskside and Data Center Cabinet SPARCsystems. Describes how to install an SBus card in a SPARCsystem. 800-6313 SPARCstation 10 Installation Guide. Describes how to install and power up a SPARCstation 10 workstation. In addition, it describes how to open and close the system unit and install monitors, and cables.
Page 18
Control key, and then press command. the lowercase c. Code samples are included in boxes and may display the following: UNIX C shell prompt system% UNIX Bourne shell prompt system$ Superuser prompt, either system# shell xviii TurboGX/TurboGXplus Installation Guide—November 1993...
Page 19
Notes, Cautions, and Warnings Observe all warning, cautions, and notes in this manual and in related manuals. The following warning, caution, and note are specifically related to all SPARCsystem 600MP series (630MP, 670MP, and 690MP), and SPARCcenter (1000 and 2000) hardware. Warning –...
SPARCservers, SPARCsystem 600MP series machines, and SPARCcenter 1000 and 2000 machines. This guide contains general installation instructions for both the TurboGX and TurboGXplus card. 1.1 TurboGX/TurboGXplus Specifications Table 1-1 lists the technical specifications for the TurboGX and TurboGXplus cards. Table 1-1 TurboGX/TurboGXplus Specifications...
Carefully read and follow the cautions below before beginning the installation procedure. Failure to comply may result in damage to the equipment. Caution – Do not open the antistatic envelope containing the TurboGX/TurboGXplus card until instructed to do so. TurboGX/Turbo GXplus Installation Guide—November 1993...
Page 23
To minimize risk of ESD damage, do the following: • Handle boards by the edges only. • Store boards in the antistatic envelope provided. • Use a wrist strap and antistatic envelope whenever you work on a board. (Instructions are included in the ESD kit.) TurboGX/TurboGXplus Introduction...
TurboGX/TurboGXplus installation instructions. ® Note – Only qualified Sun Microsystems service-trained maintenance providers should install a TurboGX/TurboGXplus card in a SPARCsystem and SPARCcenter series machine. 2.1 Tools Needed The TurboGX/TurboGXplus installation procedure for the SPARCstation does not require any special tools. You only need the following tools: 1.
TurboGX/TurboGXplus card into a particular SPARCcenter. 2.2 Software Requirements The TurboGX requires SunOS 4.0.3, the TurboGXplus requires SunOS 4.1.1 or higher or Solaris 1.x or higher to run a single TurboGX/TurboGXplus configuration. To run multiple TurboGX/TurboGXplus configurations, you need SunOS 4.1.1 or higher, or Solaris 2.0.
Users running Xlib applications will notice a higher level of performance running Solaris 2.0 with DXlib 2.0. If you need help with software or problems related to the TurboGX/TurboGXplus installation, call Sun Microsystems at 1-800-USA-4SUN. 2.4 System Requirements for TurboGX Note –...
See the Preface, “When You Need Help with UNIX,” for help with this command. This command is typically: cat etc/motd 2.7 Refresh Rate for Monitors The TurboGX/TurboGXplus card supports the following monitor resolutions and refresh rates: TurboGX/Turbo GXplus Installation Guide—November 1993...
Page 29
1280 x 1024 @ 76 Hz single double The TurboGX/TurboGXplus card uses the sense code bus to identify the monitor resolution and refresh rate for the monitor connected (see Table C-3 for a detailed description.) The sense code bus exists on the monitor cable and is driven by the monitor.
2.8 Changing the Refresh Rate for Monitors The TurboGX/TurboGXplus card supports a variety of monitors and refresh rates. In most cases, the user simply connects the monitor to the TurboGX/TurboGXplus card and the card automatically identifies the resolution and refresh rate for the monitor. There are two cases where you may wish to override the sense code bus: 1.
Page 31
This sets the resolution to 1280 x 1024 at 67 Hz. ok setenv output-device screen:r1280x1024x67 This is the default condition, resolution is set by the monitor (sense bus) ok setenv output-device screen <cr> ok reset <cr> General Installation Instructions...
The TurboGX/TurboGXplus card does not have any field replaceable components; rather the card assembly is a field replaceable unit (FRU). If the TurboGX/TurboGXplus card is defective, it should be replaced with a new one. If a unit is defective and under warranty, call 1-800-USA-4SUN if you are within the USA.
TurboGXplus Card F501-2253 A.4 Getting Help Sun Microsystems has service providers throughout the world. If you have a question about Sun software or hardware, contact your local service provider. When you call, please have your system’s model number, serial number, and operating system release number ready for the service provider.
Configuration Options This appendix describes how you can configure your system using a TurboGX/TurboGXplus card to suit your specific video/graphics requirements. B.1 Systems Supported • SPARCstation1, 1+ (TurboGX only) • SPARCstation 2 • SPARCstation 10 • SPARCclassic • SPARCstation IPC (TurboGX only) •...
B.2 TurboGX/TurboGXplus Supported Monitors Table B-1 shows the list of monitors supported by the TurboGX/TurboGXplus card. Table B-1 Monitors Supported TGX+ Model Sun Part Number Type/Size/FCC Resolution/Frequency GDM-1604A15 365-1079 Color 16” FCCA 1152 x 900 x 66 Hz US GDM-1604B15 365-1092 Color 16”...
Note – The monitors listed in Table B-1 are subject to change as Sun Microsystems announces new monitors. Contact your local Sun representative for a listing of supported monitors. B.3 Changing the Probing Order This section provides information about the SBus probing order and how to change it.
SBus slots to be probed. For example, in a SPARCclassic, SPARCstation IPX, and SPARCstation LX configuration, 0321 would cause SBus slot 3 (on-board frame buffer) to be probed first. After slot 3 is probed, SBus slots 1 and 2 will be probed, respectively. nevada# eeprom sbus-probe-list=0312 TurboGX/TurboGXplus Installation Guide—November 1993...
eeprom sbus-probe-list=0 3 1 2 Third SBus device Reserved for CPU Second SBus device Console device (if a frame buffer is installed in SBus slot 3) Figure B-1 SBus Probe List Explanation The leftmost character, except 0, in eeprom sbus-probe-list indicates the device that will be probed first.
B.6, Programming Multiple Monitor Configurations. Skip this section if you are not interested in running multiple monitors. Note – Sun Microsystems currently recommends upgrading to Version 3 of Open Windows running on Solaris 2.x to optimize the TurboGX/TurboGXplus card performance.
Page 41
When the system is booted, it looks for the sbus-probe-list which determines the order in which the SBus devices are addressed by the system. For the SPARCstation 10 system, SBus address f is reserved for the CPU and should always be the first address in the sbus-probe-list. The addressing numbers are 0, 1, 2, and 3.
Page 42
The line, , basically pushes the video string on the stack, the number 4 vsetup 4 defines the sense code of the monitor we want to change the resolution on. See Table B-3 for supported monitor codes. TurboGX/TurboGXplus Installation Guide—November 1993...
The next line, pushes the string /sbus/cgsix@1 onto the forth stack, the path for the device where the resolution is to be changed. The following example changes the framebuffer on Sbus slot 1. The string cgsix “override” is the actual entry point in the cgsix Fcode prom which reconfigures the resolution from the data present on the forth stack.
“ 216000000,101890,76,24,216,280,1600,2,8,50,1280,COLOR,0OFFSET” B.6.3 Setting up Multiple Monitors using a UNIX Script The following screen shows a UNIX script which sets up the TurboGX/TurboGXplus cards in slot 1 at 1152x900x76, and another r1600x1280x76 TurboGX/TurboGXplus card in slot 3 at 1280x1024x67 using two 19” monitors.
‘ eeprom use-nvramrc\?=true B.6.4 Setting up a single Monitor using the PROM method The following is an example of how to set up a TurboGX/TurboGXplus card in slot 2 to a 1024x768x60 resolution using a 16” monitor. ok nvedit 0: probe-sbus 1: : vsetup “...
EEPROM variable known as sbus-probe-list. The /dev/fb is the frame buffer in the first SBus slot defined in the sbus-probe-list. If a TurboGX/TurboGXplus card is added to the system that already has a GX product, the sbus-probe-list also determines which one is /dev/cgsix0 and which one is /dev/cgsix1.
file to start extra copies of the olwm window manager, one for each monitor. The OpenWindows Version 2 should already be installed. To run multiple monitors: 1. Edit the.xinitrc file under your home directory. example% vi ~/.xinitrc B-14 TurboGX/TurboGXplus Installation Guide—November 1993...
Page 49
Note – ~ indicates user’s home directory. 2. Edit these lines of your.xinitrc file if you wish to use two monitors: replace these lines: eval ‘svenv -env‘ # Sunview binary compatibility olwm -3 & # OpenLook Window Manager with these lines: ‘...
Page 50
0 Jan 10 1991 /dev/cgsix1 7. Exit the superuser mode. 8. Start the system using the -dev command-line option to openwin to specify the frame buffers for your monitors. For example: example openwin -dev /dev/fb -dev /dev/cgsix1 B-16 TurboGX/TurboGXplus Installation Guide—November 1993...
Page 51
Note – The order of the devices is important. The first device corresponds to the left screen. The second device corresponds to the right screen. The names of your devices (for example, /dev/cgsix1) may differ. Remember to use the device file name that is appropriate for your system. If you are running multiple screens, you should create a.openwin-init file in the home directory to specify the screen on which each tool is to be displayed.
Page 52
(The second frame buffer is assumed to be cgsix1.) example# cd /dev example# MAKEDEV cgsix1 This creates a device file for the second frame buffer. 4. Verify the newly created file by typing: B-18 TurboGX/TurboGXplus Installation Guide—November 1993...
example# ls -l /dev/cgsix1 The system will display a message similar to the following message indicating that the device file has been successfully created: crw-rw-rw- 1 root 0 Jan 10 1991 /dev/cgsix1 5. Exit the superuser mode. 6. Specify the screens that you wish to run by typing: example $OPENWINHOME/bin/openwin -dev /dev/fb -dev /dev/cgsix1 Note –...
Page 54
2. Save the file and exit your editor. 3. To start the OpenWindows environment on one frame buffer, execute the openwin command and specify the chosen frame buffer with the -dev option. For example: B-20 TurboGX/TurboGXplus Installation Guide—November 1993...
Page 55
example% openwin -dev /dev/fb 4. Reset your path so that the path for the SunView versions of the DeskSet tools appears before the path for the XView versions. For example, if you are using the C shell, use the following command: example% set path=(/usr/bin $path) If you are using the Bourne shell, use the following command: example$ PATH=/usr/bin:$PATH;...
Page 56
1 root 0 Jan 10 1991 /dev/cgsix1 8. Exit the superuser mode. 9. Start the SunView environment using the sunview command and specify the second frame buffer with the -d command-line option. For example: B-22 TurboGX/TurboGXplus Installation Guide—November 1993...
example% sunview -d /dev/cgsix1 & 10. Run the adjacentscreens command to provide alternating access to the two displays. For example, if the cgsix1 screen is to the left of the fb screen, type: example% adjacentscreens /dev/fb -l /dev/cgsix1 11. Check to make sure you can enter characters properly on the screen running the SunView environment.
Page 58
(The second frame buffer is assumed to be cgsix1 example# cd /dev example# MAKEDEV cgsix1 This creates a device file for the second frame buffer. 4. Verify the newly created file by typing: B-24 TurboGX/TurboGXplus Installation Guide—November 1993...
Page 59
example# ls -l /dev/cgsix1 The system will display a message similar to the one shown below indicating that the devicefile has been successfully created: crw-rw-rw- 1 root 0 Jan 10 1991 /dev/cgsix1 5. Exit the superuser mode. 6. To start the SunView environment on the second device, open a Shell Tool window and enter this command: example% sunview -d /dev/cgsix1 &...
Video Cable and Interface Signals This appendix describes the video cable and SBus interface signals. C.1 Video Cable Signals The Sun Class B monitor connector (13W3) is a D-type subminiature socket housing with coax cavities. Table C-1 describes the connectors. Table C-1 Monitor Connector Cable Parameter Description...
Troubleshooting This appendix describes the troubleshooting procedure. Some procedures are simple; others are complex and should be performed only by an experienced user of Sun hardware. D.1 Checking the fcode-debug Parameter Skip this information if you have not changed the fcode-debug parameter. Note –...
1. Make sure the power cord is attached, the power is on, and the SPARCstation LED and the monitor LED are lit. 2. Make sure the TurboGX/TurboGXplus card is installed properly and the cable is properly attached to the card and the monitor.
Note – This procedure should be performed only if the system fails to boot up after performing the procedure described in section D2 The TurboGX/TurboGXplus card does not have a fuse or a circuit breaker; it gets its power from the CPU board. If the system fails to boot and the system LED is not lit, this does not necessarily mean that the TurboGX/TurboGXplus card is defective;...
TurboGX/TurboGXplus installation process. 3. Close the system unit. 4. Wait for about 10 minutes and reboot the system. If the problem still exists, contact Sun Microsystems at 1-800-USA-4SUN (within the USA) or contact your Sun Sales Representative. D.7 Running Sundiag The Sundiag tool is available to every user under the SunOS or Solaris operating system.
Page 69
Refer to the Sundiag User’s Guide for details. Troubleshooting...
Temperature range: Between 32 and 104 degrees Fahrenheit (0 and 40 degrees Celsius) Humidity: Between 5% and 80% (relative noncondensing) Altitude: Between 0 and 10,000 feet (0 and 3048 meters) E.2 TurboGX Specifications Summary E.2.1 Physical Specifications Length: 146.70 mm (5.78 inches) Width: 83.82 mm (3.3 inches)
E.2.4 Interface Requirements Connector type: SBus (single slot) E.2.5 Agency Certification • FCC Class B • DOC Class B • VCCI Class 2 • VDE Class B (vfg243/1991) • • • TUV (EN60950/ISO9241-3) The FCC and VCCI approvals are board level approvals. All of the other approvals are system level;...
Installing an SBus Card Bracket Adapter and Handle This appendix provides installation instructions on how to install the bracket adapter, and card handle before installing the SBus card into the following systems: • SPARCstation 1 and 1+ • SPARCstation 2 •...
F.2 Removing an SBus Card If the SBus card is replacing an existing card, remove the card as shown in Figure F-1. Figure F-1 Removing an SBus Card TurboGX/TurboGXplus Installation Guide—November 1993...
F.3 Removing a Double-Wide SBus Card To remove a double-wide SBus card, grasp the card by the edge closest to the SBus connectors, and gently pull the card upward. When the card is free, disengage the tab from the back panel as shown in Figure F-2. Holes that receive mounting plate hooks SBus slot 1...
F.4 Installing the Card Handle Install the card handle on the card as shown in Figure F-3 Figure F-3 Installing the Card Handle TurboGX/TurboGXplus Installation Guide—November 1993...
F.5 Installing the Bracket Adapter Install the bracket adapter assembly on the SBus card as shown in Figure F-4 Figure F-4 Installing the Bracket Adapter Installing an SBus Card Bracket Adapter and Handle...
F.6 Installing an SBus Card When the SBus card is configured properly, install the card in the slot as shown in Figure F-5. Figure F-5 Installing an SBus Card TurboGX/TurboGXplus Installation Guide—November 1993...
Page 81
Index agency certification, E - 3 ESD kit, 1 -2 audience, xiii field replaceable units, A - 1 boot PROM CPU, D - 1 GFX Rev 2, 2 -2 cautions installation, 1 -2 handling internal components, F -1 Changing the Polling Order, B - 3 checking available frame buffers, B - 13 fcode-debug, D - 1...
Page 82
OpenWindows Version 3, B - 17 running, D - 4 SunView and OpenWindows system requirements, 2 -3 environments, B - 8 System Requirements, TurboGX, 2 -3 SunView environment, B - 23 System Requirements, TurboGXplus, 2 -4 systems covered, 1 -2 systems supported, B - 1...
Need help?
Do you have a question about the TurboGX and is the answer not in the manual?
Questions and answers