Sun Microsystems TurboGX, Руководство по установке

Страница: 46 / 82

B-12 TurboGX/TurboGXplus Installation Guide—November 1993
B
B.7 Device File Names
If you are using OpenWindows or SunView software on multiple monitors,
you should be familiar with the way frame buffer devices are assigned to
UNIX device file names. Multiple frame buffers used with OpenWindows and
SunView software require that UNIX device file names for frame buffers be
supplied on the command line when either is started.
The UNIX boot messages identifies the frame buffer as;
/dev/fb
(where fb is
the type of frame buffer). The
/dev/fb
usually has another device file name
such as;
/dev/cgsix0
,
/dev/bwtwo0
, or
/dev/cgthree0
depending on the
type of the frame buffer. When a second frame buffer is added, the system
decides which is
/dev/fb
based on the SBus slot number of each frame buffer
and an 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
.
Example: Assume that the
sbus-probe-list
on a SPARCstation 10 system
has the default value of f0123 and SBus slots 2 and 3 contain
TurboGX/TurboGXplus cards. The TurboGX/TurboGXplus card in slot 2 will
be known as
/dev/fb
and
/dev/cgsix0
; the TurboGX/TurboGXplus card in
slot 3 will be known as
/dev/cgsix1
.
#!/bin/sh
eeprom fcode-debug\?=true
eeprom nvramrc=’probe-sbus
: vsetup “ 64125000,48286,60,16,128,160,1024,2,6,29,768,COLOR” ;
vsetup 6
“/sbus/cgsix@2” “ override” execute-device-method drop
install-console
banner
‘
eeprom use-nvramrc\?=true