Summary of Contents for HP c3700 - Workstation

The information contained in this document is subject to change without notice. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard. This document contains proprietary information that is protected by copyright.

preface The purpose of this document is to collect, in one place, all the information necessary to configure and administer graphics cards supported in HP-UX workstations and servers running the 11.00 and 11i version 1 (11.11) Operating Systems. Chapter 1...

preface NOTE Previous versions of this document contained information for 3D graphics Application Programming Interfaces (APIs) that are now obsolete. The following APIs were discontinued, then obsoleted, on the indicated dates: Table 1-1 Product Product Discontinued Obsoleted On Name Number Starbase B2374A October 1,...

preface document conventions document conventions Below is a list of the typographical conventions used in this document: ls /usr/include Verbatim computer literals are in computer font. Text in this style is letter-for-letter verbatim and, depending on the context, should be typed in exactly as specified, or is named exactly as specified.

configuring X Windows on HP-UX (HP Visualize graphics cards) on how to configure the X Server and includes a list of supported configurations. For each supported graphics device, device-dependent configuration information is provided. Information specific to a new release of the X Server, beyond the scope of the general information in this document, can be found in the HP-UX Release Notes located in /usr/share/doc.

configuring X Windows on HP-UX (HP Visualize graphics cards) X Server configuration The X Server delays loading of some X extensions until the first protocol request to the given extension is received. Specifying this server option forces all extensions to be loaded at X Server startup.

configuring X Windows on HP-UX (HP Visualize graphics cards) X Server configuration MinimumMonitorPowerSaveLevel <value> Specify the minimum power save level to be used by the monitor during screen blanking. You must specify a level of 0 -3 If the option is not used, the default is level 0.

configuring X Windows on HP-UX (HP Visualize graphics cards) X Server configuration Screen /dev/crt DefaultVisual Transparent The display diagram would be the same as that of the “Results of Minimal Legal X*screens File” configuration, above. • This sample X*screens file could be used on a system with a HP VISUALIZE-FXE graphics device.

configuring X Windows on HP-UX (HP Visualize graphics cards) X Server configuration Figure 2-3 Two physical displays, single logical screen (1x2) < host >:0.0 /dev/crt0 /dev/crt1 • These sample X*screens entries could be used on a system with four homogeneous graphics devices. Assuming the first device is associated with the device file “/dev/crt0”, the second device is associated with the device file “/dev/crt1”, etc.

configuring X Windows on HP-UX (HP Visualize graphics cards) X Server configuration determining swap performance The DBE API does not allow users to determine if double-buffering in a visual is through software or hardware. However, the API does provide a way to determine relative swapping performance on a per-visual basis.

configuring X Windows on HP-UX (HP Visualize graphics cards) X Server configuration The following table is a description of the states that are defined by VESA. The Power Savings column indicates (roughly) the level of power savings achieved in the given state. The Recovery Time is the amount of time that the screen takes to return to a usable state when the screen saver is turned off (by pressing a key or the moving the mouse).

configuring X Windows on HP-UX (HP Visualize graphics cards) X Server configuration stored in the shared memory segment. In all other respects, shared memory pixmaps behave the same as ordinary pixmaps and can be modified by the usual Xlib routines. In addition, it is possible to change the contents of these pixmaps directly without the use of Xlib routines merely by modifying the pixmap data.

configuring X Windows on HP-UX (HP Visualize graphics cards) X Server configuration Multi-Screen A configuration in which a single X Server with a mouse and keyboard drives multiple graphics devices (where each display is a different X Screen) concurrently while only allowing the cursor, not windows, to be moved between displays.

configuring X Windows on HP-UX (HP Visualize graphics cards) X Server configuration multi-screen support The list of supported multi-display configurations is rather large, and it changes whenever a new graphics device is introduced. Thus, if you are considering a Single Logical Screen or any other multi-display configuration, we recommend consulting your HP Sales Representative and inquiring whether the configuration you have in mind is indeed supported.

configuring X Windows on HP-UX (HP Visualize graphics cards) X Server configuration Note that if your machine has only one graphics device, the “Modify Multi-Screen Layout” menu option does not even appear, since multiple devices cannot occur in a single-device context. Note also that DHA (Direct Hardware Access) is supported in a window that spans multiple screens.

configuring X Windows on HP-UX (HP Visualize graphics cards) X Server configuration • The login screen. • The Front Panel. • Window move and resize boxes. • The screen lock dialog. This behavior is the result of HP CDE’s naive assumption that it is running against one large screen;...

configuring X Windows on HP-UX (HP Visualize graphics cards) hp Visualize- FXE, FX5 and FX10 device-dependent information visuals are simply duplicates of visuals that would normally appear in the X visual list. In case that the extra visuals cause problems with applications, a screen option can be used to disable them.

configuring X Windows on HP-UX (other graphics cards) section describes features unique to HP's implementation of the X Server, provides information on how to configure the X Server and includes a list of supported X configurations. For each supported graphics device, device-dependent configuration information is provided. NOTE This chapter deals with configuration requirements for graphics cards OTHER THAN HP Visualize cards (fxe, fx5, fx10, etc.).

configuring X Windows on HP-UX (other graphics cards) using SAM to configure X Windows using SAM to configure X Windows Configuration of the X Server is supported through SAM via an icon titled “X Server Configuration.” This icon resides either at SAM’s top-level or under the top-level “Display”...

configuring X Windows on HP-UX (other graphics cards) using SAM to configure X Windows other graphics cards. Running independent X Servers on an HP Visualize graphics device and any other device simultaneously is not supported. SLS is a mechanism for treating homogeneous multi-display configurations as a single logical screen.

configuring X Windows on HP-UX (other graphics cards) using SAM to configure X Windows The Modify Default Visual menu item lets you set the default visuals, depth and resolution on a graphics device. It lets you identify which of these should be the default settings. The Modify Screens Options item contains options that are specific to each graphics device.

configuring X Windows on HP-UX (other graphics cards) the XF86Config file the XF86Config file The XF86Config file is located in /etc/X11/XF86Config. It can be generated automatically or modified using SAM. A working configuration file is also delivered on the system. You must be root to create or edit this file.

configuring X Windows on HP-UX (other graphics cards) the XF86Config file Table 3-1 Option Value Default Description DontZap Boolean This disallows the use of the Ctrl+Shift+Break sequence. That sequence is normally used to terminate the X Server. When this option is enabled, that key sequence has no special meaning and is passed to clients.

configuring X Windows on HP-UX (other graphics cards) the XF86Config file Table 3-1 (Continued) CursorScaleFactor Integer See the section in “Features: ” for more details regarding these options. MaxCursorSize Integer See the section in “Features: Cursor Scaling” for more details regarding these options.

configuring X Windows on HP-UX (other graphics cards) the XF86Config file where <trans> is the transport type to use to connect to the font server (e.g., Unix for UNIX-domain sockets or tcp for a TCP/IP connection), <hostname> is the hostname of the machine running the font server, and <port-number>...

configuring X Windows on HP-UX (other graphics cards) the XF86Config file “Module” section The Module section is used to specify which X Server modules should be loaded. The types of modules normally loaded in this section are X Server extension modules, and font rasterizer modules. Most other module types are loaded automatically when they are needed via other mechanisms.

configuring X Windows on HP-UX (other graphics cards) the XF86Config file “InputDevice” section An InputDevice section is considered active if there is a reference to it in the active ServerLayout section. There may be multiple InputDevice sections. There will normally be at least two: one for the core (primary) keyboard, and one for the core pointer.

configuring X Windows on HP-UX (other graphics cards) the XF86Config file Table 3-2 (Continued) CoreKeyboard When this is set, the input device is to be installed as the core (primary) keyboard device. There must be no more than one core keyboard. If this option is not set here, or in the ServerLayout section, then the first input device that is capable of being used as a core keyboard will be selected as...

configuring X Windows on HP-UX (other graphics cards) the XF86Config file ServerLayout section. If neither of these is present, the first Screen section found in the configuration file is considered the active one. Screen sections have the following format: Section ìScreenî Identifier ìScreenIDî...

configuring X Windows on HP-UX (other graphics cards) the XF86Config file Various Option flags may be specified in the Screen section. Some are driver-specific and are described in the driver documentation. Driver-independent options are described here. Table 3-3 Entry Entry Description Position Accel...

configuring X Windows on HP-UX (other graphics cards) the XF86Config file The virtual screen allows you to have a “root window” larger than what can be displayed on the monitor. (e.g. the monitor may be 800x600 display, but have a 1280x1024 virtual size). The Virtual keyword is used to specify this size.

configuring X Windows on HP-UX (other graphics cards) the XF86Config file Option flags may be specified in the Display subsections. These may include driver-specific options or driver-independent options. The former are described in the driver-specific documentation. Some of the latter are described above in the section about the Screen section, and they may also be included here.

configuring X Windows on HP-UX (other graphics cards) the XF86Config file The data given here is used by the X Server to determine if video modes are within the specifications of the monitor. This information should be available in the monitor's handbook. If this entry is omitted, a default range of 28-33 kHz is used.

configuring X Windows on HP-UX (other graphics cards) sample XF86Config file sample XF86Config file # This is a sample XF86Config file. It can be cut from this document # and placed in the /etc/X11/XF86Config file. # The config file has a hierarchical ìSectionî structure along # with some standalone ìSections.î...

configuring X Windows on HP-UX (other graphics cards) sample XF86Config file Option "Protocol" "PS/2" EndSection # There may be multiple Monitor sections. The purpose of this section is # is to specify the range of operation of a monitor. For a Monitor to be # in use the Identifier must match the Monitor line in an active Screen.

configuring X Windows on HP-UX (other graphics cards) display power management signaling (DPMS) display power management signaling (DPMS) Monitors constitute a large percentage of the power used by a workstation even when not actively in use (i.e. during screen blanking). In order to reduce the power consumption, the Video Electronic Standards Association (VESA) has defined a Display Power Management Signaling (DPMS) standard which can be used to greatly reduce the...

configuring X Windows on HP-UX (other graphics cards) display power management signaling (DPMS) Option Value Default Description SuspendTime time Suspend Time sets the inactivity timeout for the “suspend” phase of DPMS mode. Time is in minutes, and the value can be changed at run-time with xset(1).

configuring X Windows on HP-UX (other graphics cards) features features cursor scaling There are times when the standard X11 cursors are difficult to see on the screen. The effect is compounded on large displays. Two options are available in the X Server that instruct the X Server to scale all X11 cursors (both user-defined and built-in cursors) by a user-defined value.

configuring X Windows on HP-UX (other graphics cards) features Option ìSuppressVisualsî ìPseudoColorî EndSection technical print service (TPS) The Technical Print Service, tps(5), is a network transparent printing system that allows X applications to render to non screen devices in the same manner they render to displays.

configuring X Windows on HP-UX (other graphics cards) features starting the X Server from the command line Command line options for the X Server are described in Xf86(1). mapping options from the previous hp X Server to the current hp X Server The purpose of this section is to provide the user, who is familiar with the X* screens files or the HP X Server, a method of setting the equivalent options in the XF86Config file, in the current release of the HP X Server.

configuring X Windows on HP-UX (other graphics cards) features Depth The default depth of the visual can be set in the Screen section of the XF86Config file using the DefaultDepth option. The following example sets the default depth to 24. X*screens File Example: Screen /dev/crt DefaultVisual...

configuring X Windows on HP-UX (other graphics cards) output devices supported monitor configurations All FireGL cards support multiple monitors. The FireGL X1 and X3 have dual DVI-I connectors, which will drive either digital or analog monitors. The FireGL T2 has one DVI-I and one VGA connector. When using a single monitor, the monitor can be attached to either connector.

configuring X Windows on HP-UX (other graphics cards) hp Fire GL-UX configuration hints This may cause problems with some applications. Setting "CountTransI- nOvlyVis" causes the server to reserve the transparent pixel index. In this case, the server reports that 255 colormap entries are available for allocation in the PseudoColor visual.

configuring X Windows on HP-UX (other graphics cards) ATI FireGL X1/T2/X3 configuration hints gamma correction Gamma correction can be applied to windows in the image planes explicitly with the gamma tool (/opt/graphics/common/bin/gamma) or implicitly by running a direct rendering OpenGL application. If no default gamma has been set with the gamma tool, the OpenGL libraries will apply a gamma of 1.7 when starting an OpenGL application.

X Windows configuration details making an x*.hosts file making an x*.hosts file The /etc/X0.hosts file is an ASCII text file containing the hostnames of each remote host permitted to access your local server. • If you are running as a stand-alone system, you must have your system’s name in this file.

X Windows configuration details making an x*.hosts file • The user must have a valid login (username and password) and home directory on the remote host. stopping the X Window system After stopping all application programs, stop the window system by holding down the keys, and then pressing the Ctrl...

X Windows configuration details making an x*.hosts file xmodmap -e “pointer = 1 3 2 4 5" 3-button mouse modifying modifier key bindings with xmodmap To change the meaning of a particular key for a particular X11 session, or to initialize the X Server with a completely different set of key mappings, use the xmodmap client.

<modifier > Specifies one of the eight modifier names: Shift, Control, Lock, Mod1, Mod2, Mod3, Mod4, and Mod5. On Hewlett-Packard keyboards, the lock modifier is set to the key. Caps However, any of the modifiers can be associated with any valid key symbol.

X Windows configuration details making an x*.hosts file examples Suppose you frequently press the key at the most inopportune Caps moments. You could remove the lock key from the lock modifier, Caps swap it for the key, then map the key to the lock modifier.