User manual EIZO RAPTOR 4000E

[. . . ] Raptor 4000/4000e Drivers Installation and Reference Solaris Manual Copyright © 2008 Tech Source, Inc. Altamonte Springs, FL 32701 (407) 262-7100 Publication: 65-0270-01 Rev. B March 25, 2008 Addendum Information Date Released Changes made to: REVISION NUMBER A B CHANGES Initial Release Added support for dual head March 25, 2008 DATE 9-12-07 3-25-08 The Tech Source logo and Tech Source Raptor are trademarks of Tech Source, Inc. Sun, Sun Microsystems, Sun Ultra, Sun Enterprise, Sun Blade, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. [. . . ] Connection to the monitor must occur during the boot process for the DDC/EDID protocol to be effective. For more information about the functionality of the DDC2B/EDID protocol with your Raptor card, please refer to Appendix A. 3. 4. 1 Resolution The resolution of the Raptor 4000/4000e card can be changed through the atcconfig utility. By using this utility, the user can select a resolution to be displayed, which will be written in the OWconfig file. If DDC is not used, or if the monitor doesn't report a valid resolution, then the software will check for a valid resolution specified in the /usr/openwin/server/etc/OWconfig file. If a valid resolution is specified and a reference for the timing numbers occurs in the rapafpresinfo file, then that resolution is used. If the timing numbers are not specified or there is no specific resolution in the OWconfig file, then the default resolution will be set to 2048x2048@60, analog. Note: The device number corresponding to rapafp# of your card is assigned by the operating system and could vary for each head. The following table lists the different Raptor cards and their device name locations. The device name will have the card's minor number appended to it. For example, the first instance of a Raptor 4000/4000e card will have a device name and number of rapafp0 for the first head and rapafp1 for the second head. The second instance will have a device name and number of rapafp2 for the first head and rapafp3 for the other head. Raptor Card 4000 (First Head) 4000 (Second Head) 4000e (First Head) 4000e (Second Head) Device Name /dev/fbs/rapafp0 /dev/fbs/rapafp1 /dev/fbs/rapafp2 /dev/fbs/rapafp3 4. 1. 1 Starting the X server Determine the device for your card(s) by running the command, dmesg | grep rapafp. For the examples below, we assume that the first head of your device is assigned as /dev/fbs/rapafp0 and the second head as /dev/fbs/rapafp1. To start the Xserver type: ©2008 Tech Source Inc. 13 Part #65-270-01 prompt# /usr/openwin/bin/X ­dev /dev/fbs/rapafp0 This will start the Xserver only on the first head. If you want to start the Xserver in multiscreen configuration on both heads, both device names should be specified on the command line. For example: prompt# /usr/openwin/bin/X ­dev /dev/fbs/rapafp0 \ ­dev /dev/fbs/rapafp1 4. 1. 2 xinit The xinit program can be directly used to start the X Window System server. The xinit format is as follows: xinit [[client] options] [ -- [server] [display] options ] If no specific client program is given on the command line, xinit will look for a file in the user's home directory called . xinitrc to run as a shell script to start up client programs. If no such file exists, xinit will use the following as a default: xterm -geometry +1+1 -n login \ -display :0 If no specific server program is given on the command line, xinit will look for a file in the user's home directory called . xserverrc to run as a shell script to start up the server. If no such file exists, xinit will use the following as a default: X :0 Note that the following example assumes that a program named X is in the current search path. To startup the server using xinit, type: prompt% xinit -- /usr/openwin/bin/X -dev \ /dev/fbs/rapafp0 14 You may also add any other command line arguments to the end of the line. For additional information on the use of xinit, refer to the man page for xinit. 4. 1. 3 Raptor as the Secondary Framebuffer The Raptor 4000/4000e card can work with other cards to display in multi-screen mode. In the following example, an Nvidia video card is assumed to be the console and a Raptor 4000/4000e is the secondary card. [. . . ] The video-mode method requires the output-device variable in NVRAM to be configured with the actual path of the desired Raptor 4000/4000e card. The path can be determined by searching for the string TSI in the / tree at the ok prompt. To find the path to the 4000/4000e device, type the following: ok show-devs At least one entry containing the string TSI will be displayed. For example, TSI, rapafp@#, where # will be a digit representing your Raptor's PCI slot number. [. . . ]