Document fins/I0416-1


FIN #: I0416-1

SYNOPSIS: Ultra 5/10/30/60 2.5.1/2.6 AutoClients or Diskless Clients May Not
          Boot or Run a Window System After Installation.

DATE:  Aug/26/98

KEYWORDS: Ultra 5/10/30/60 2.5.1/2.6 AutoClients or Diskless Clients May Not
          Boot or Run a Window System After Installation.


---------------------------------------------------------------------
        - Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------  
                        FIELD INFORMATION NOTICE
                  (For Authorized Distribution by SunService)




 
SYNOPSIS: Ultra 5/10/30/60 2.5.1/2.6 AutoClients or Diskless Clients
          May Not Boot or Run a Window System After Installation.


TOP FIN/FCO REPORT: No


PRODUCT_REFERENCE:  autoclient, diskless client patch support


PRODUCT CATEGORY:   Desktop / Software / Unbundled  


PRODUCTS AFFECTED: 
	          
Mkt_ID   Platform   Model   Description   Serial Number
------   --------   -----   -----------   -------------

Systems Affected
----------------

   -     A21        All      Ultra 5            -
   -     A22        All      Ultra 10           -
   -     A16        All      Ultra 30           -
   -     A23        All      Ultra 60           -

X-Options Affected
------------------
SOLS-2.5.1NOV97   -   -      Solaris 2.5.1 HW 11/97 Server Media Kit   -
SOLS-2.6          -   -      Solaris 2.6 Server Media Kit              -
SOLS-2.6MAR98     -   -      Solaris 2.6 HW 3/98 Server Media Kit      -
SOLMS-26EW9999    -   -      Solaris 2.6 HW 5/98 Server Media Kit      -  

*The Solaris Media Kits (shown above) include Solstice AdminSuite 2.3 
 and AutoClient 2.1.


REFERENCES:	

BugId: 4150243,  4136400,  4124194,  4108393,  4146505
ESC: 514712
PatchId: 104628,  105654    
 
	
PROBLEM DESCRIPTION:

Problem #1

Ultra 5/10/30/60 Solaris 2.5.1 HW 11/97 and Solaris 2.6 AutoClients 
and Diskless Clients may hang or crash during boot.  This may be   
caused by missing patches and/or packages, especially if the OS   
Service that was used to create the client did NOT contain OEM support.  
Shown below is an example of an error message encountered by an
improperly configured AutoClient or Diskless Client during the boot
process: 

No entry for SUNW,Ultra-5_10 under "/export/root/hostname/platform".
No entry for SUNW,Ultra-5_10 under
"/export/root/hostname/usr/platform".

In addition to the error messages shown above, the following symptoms
will be encountered by the affected AutoClient or Diskless Client.

i)   Unable to complete boot sequence.
ii)  Hangs after "SunOS Release ..." banner.
iii) The AutoClient or Diskless Client must be powered off.
     (L1-A does not work).


Problem #2

If an autoclient or diskless client was installed from an OS Service  
that did not include OEM support your system may NOT have the proper  
packages to run OpenWindows or CDE.  The symptom of this problem is   
an error message similar the following, when attempting to start a  
windowing system:

 	
	/dev/fb: No such file or directory
	Graphics Adapter device /dev/fb is of unknown type

	Fatal server error:
	InitOutput: Error loading module for /dev/fb



IMPLEMENTATION: 
 
         ---
        |   |   MANDATORY (Fully Pro-Active)
         ---    
         
  
         ---
        |   |   CONTROLLED PRO-ACTIVE (per Sun Geo Plan) 
         --- 
         
                                
         ---
        | X |   REACTIVE (As Required)
         ---


 
CORRECTIVE ACTION:


In order to avoid the above stated problems with Ultra 5/10/30/60 
Solaris 2.5.1 HW11/97 and Solaris 2.6 AutoClients and Diskless 
Clients, The following recommendations for client configuration must 
be applied:

1. For each affected 2.5.1 HW11/97 Autoclient or Diskless Client add  
   the following packages to each client from the server to correct  
   the boot problem:

	SUNWevc.u   SUNWffb.u   SUNWhmd   SUNWide	
	SUNWm64.u   SUNWpci.u   SUNWpd	  SUNWvplr.u

Also, install patch 104628 to each client from the server to correct
the boot problem.


a. For each affected 2.6 HW 3/98 or 5/98 Autoclient or Diskless Client  
   add the following packages to each client from the server to correct  
   the boot problem:

	SUNWafb.u   SUNWafbr   SUNWffb.u   SUNWhmd		
	SUNWide	    SUNWm64.u  SUNWpci.u   SUNWpd		
        SUNWw250.u  SUNWvplr.u SUNWxfb.u

Also, install patch 105654 to each client from the server to correct
the boot problem.
 

2. To provide windowing support for new framebuffers (AFB, FFB, and M64)
   you will need to add the following packages to the server's Service 
   Area for Solaris 2.5.1 and for Solaris 2.6:

	SUNWvplu.u  SUNWvplxw  SUNWafbcf  SUNWafbw
        SUNWafbxg   SUNWffbcf  SUNWffbw   SUNWffbxg 
        SUNWm64w    SUNWm64cf


Note: Reference the Comments section below for important information  
      on where to find packages and patches on your OS CD and for  
      instructions on how to add packages and patches to your client  
      and to your Service Area.
 

COMMENTS:

1. On the Solaris 2.5.1 HW11/97 CD all packages referenced above are
   in the /cdrom/cdrom0/s0/Solaris_2.5.1 directory.

2. On the Solaris 2.6 HW3/98 and HW5/98 CDs all packages referenced 
   above are in the /cdrom/cdrom0/s0/Solaris_2.6/Product directory.

3. The Solaris 2.6 HW3/98 and HW5/98 CD contain patch 105654  
   in the /cdrom/cdrom0/s0/Solaris_2.6/Patches/105654-03 directory.

4. The Solaris 2.5.1 HW 11/97 CD contains patch 104628 in the
   /cdrom/cdrom0/s0/MU/Solaris_2.5.1MU5/sparc/Patches/104628-05 directory.

5. To apply a patch from the server to an Autoclient or Diskless client:

   # cd <patch_directory>
   # ./installpatch -R /export/root/<client_name> .

6. To add a package from the server to an Autoclient or Diskless client:

   # cd <package_top_level_directory>
   # pkgadd -R /export/root/<client_name> -d . <package_name>	

7. To add a package to a server's Solaris 2.5.1 Service Area:

   # cd <package_top_level_directory>
   # pkgadd -R /export/exec/Solaris_2.5.1_sparc.all -d .<package_name>

8. To add a package to a server's Solaris 2.6 Service Area:

   # cd <package_top_level_directory>
   # pkgadd -R /export/exec/Solaris_2.6_sparc.all -d .<package_name>


--------------------------------------------------------------------------

Implementation Footnote:
________________________

i)   In case of MANDATORY FINs, Enterprise Services will attempt to contact   
     all affected customers to recommend implementation of the FIN. 
        

ii)  For CONTROLLED PROACTIVE FINs, Enterprise Services mission critical sup-  

     port teams will recommend implementation of the FIN (to their respective 
     accounts), at the convenience of the customer. 


iii) For REACTIVE FINs, Enterprise Services will implement the FIN as the need 

     arises.
----------------------------------------------------------------------------

All released FINs and FCOs can be accessed using your favorite network 
browser as follows:

SunWeb Access: 
______________

* Access the top level URL of http://cte.corp/FIN_FCO/

* From there, select the appropriate link to query or browse the FIN and
  FCO Homepage collections.

Supporting documents for FIN/FCOs can be found on Edist.  Edist can be 
accessed internally at the following URL: http://edist.corp/.
 
* From there, follow the hyperlink path of "SunService Documentation"
and 
  click on "FIN & FCO attachments", then choose the appropriate
folder, FIN or 
  FCO.  This will display supporting directories/files for FINs or FCOs.
  
Internet Access:
_______________

* Access the top level URL of https://infoserver.Sun.COM

--------------------------------------------------------------------------
General:
________

Send questions or comments to finfco-manager@cte.Corp

---------------------------------------------------------------------------






Copyright (c) 1997-2003 Sun Microsystems, Inc.