Sun Ultra 27 Workstation
 
Solaris Operating System
 

PLA-Support>Sun Systems>x86>Server>SN-x64: MISC-SERVER
 
_Old GCS Categories>Sun Microsystems>Servers>x64 Servers
 

There are three ways to go about providing this information to the install program:

Any of these will work; it is just a matter of getting the correct information to the install program. More than one method may be required to prevent the system from having to run the DCA (Device Configuration Assistant). For instance, you may need to create a hardware profile on the floppy to get right to the network as the boot device without all the interaction with the DCA and then also provide the hardware information in the profile so as to avoid the DCA during the install program running across the network.

For our examples we will use a jumpstart server named "gandalf" and an install client named "bilbo". For some activities described here you must be root. However, we will use a "username@machinename" prompt throughout so as to provide as much clarity as possible.

The first step is to gather the correct information for sysidcfg and bootparams. What information you need will depend on whether you are doing a hands-off local install or a hands-off jumpstart. If it is a local install, you will need to create a sysidcfg, rules, and profile, and update the hardware and boot properties in the DCA on the boot diskette. If you are doing a jumpstart, you will need to update the hardware and boot properties on the DCA on the boot diskette and create your rules, sysidcfg, profile, and bootparams data on the jumpstart server. The best way to collect the sysidcfg and bootparams hardware data is to use the kdmconfig command with the -d option for the sysidcfg data and the -s option for the bootparams data. Here are some examples:

root@bilbo# kdmconfig -d bilbo.sysidcfg
kdmconfig - View and Edit Window System Configuration
Current Window System Configuration:
Video Device: Cirrus Logic GD5480 (2MB)
Screen Size: 15-inch (38cm)
Resolution/Colors: 1024x768 - 256 colors @ 77Hz
Monitor Type: Plug and Play Mfreq 15 Inch SUN054A (up to 1024x768 @ >
Keyboard Type: Generic US-English(104-Key)
Pointing Device: Built-in PS/2 Mouse (2 Button)
7           Configure Devices
------------------------------------------
[X] No changes needed - Test/Save and Exit
[ ] Change Video Device/Monitor
[ ] Change Keyboard
[ ] Change Pointing Device

F2_Continue       F3_Quit Without Save       F6_Help

Select F2 and continue to the next screen:

 kdmconfig Window System Configuration Test
You can test the current window system configuration now by
pressing F2.   If the configuration is correct, you will see
the sample image, be able to move the pointer, and click on
a button.   If you see a blank or improper screen, press any
key.   If kdmconfig does not regain control within a minute,
you will have to reboot your system.
Press F4 to bypass the test.   If you bypass the test and you
have an incorrect or incomplete configuration, you will not
be able to use the window system.
F2_Continue       F4_Bypass       F6_Help

Select F4 to bypass the test. Then verify that the hardware entries are in the output file:

root@bilbo# cat bilbo.sysidcfg
display=bilbo:SUNWcirrus {
ddxHandler=ddxSUNWcirrus.so.1
ddxInitFunc=SUNWcirrusInit
}
pointer=bilbo:ps22b {
csize=0
buttons=2
strmod=vuid2ps2
ddxInitFunc=ddxSUNWmouseProc
ddxHandler=ddxSUNWx86mouse.so.1
dev=/dev/kdmouse
ptrfile=ps22b.ptr
PtrChksum=0x45cafda9
}
monitor=bilbo:5480-2 {
device=SUNWcirrus
res=1024x768
defdepth=8
size="15-inch (38cm)"
board=cirrus/5480-2.xqa
monitor=pnp/edidgen.vda
dpix=85
dpiy=85
DisplayChksum=0xcd0aba39
hz=77
dcm=Adapter
}
root@bilbo#

Once you have this data, you can then vi this file and create a sysidcfg with the remaining keywords you need as outlined in the Solaris[TM] "Advanced Installation Guide". This book is available at http://docs.sun.com in HTML and pdf formats. This sysidcfg file must be named "sysidcfg" and located in the root directory of the DCA floppy or in a file specified by bootparams on the jumpstart server. The server location is specified with the -p option to the add_install_client command. Once the sysidcfg file is created and placed in the correct location, you will need to create a rules file either on the root directory of the floppy or the jumpstart directory of the jumpstart server.

The rules file is covered in detail in the Advanced Installation Guide" and specifies the location of the begin script, finish script, and profile for each set of rules. Once you have created a rules file and a profile, you will need to validate them using the check script from the Tools directory; this will create the rules.ok file that the install looks for.

Once the sysidcfg (if applicable), rules, profile, and any scripts are on the DCA diskette, you then need to configure the DCA to boot automatically to the correct device. This is accomplished by booting to the DCA and allowing it to detect all the hardware in the system, then saving the hardware configuration and making it the default. Then you set the boot settings on the DCA to a default boot device and enable auto-booting. The steps for this are outlined below:

The procedure to install at this point is simple. Insert the DCA diskette into the machine to be installed. If you have configured for a jumpstart and the machine has been added to your jumpstart server using add_install_client, simply power on the box and walk away. If you are doing a hands-off install from cdrom, power on the box, insert the cdrom, and walk away.

This solution has no attachment