test

Solaris 8 (SPARC Platform Edition) Online Release Notes Update

Chapter 1 Installation Issues

The following installation-related bug descriptions have been added in this chapter since this document was published on the Solaris 8 Documentation CD. A revised version of this chapter was published in the printed Solaris 8 (SPARC Platform Edition) Release Notes:

Issues You Need to Know About Before Starting an Interactive Installation From the Solaris 8 Software 1 of 2 CD

Locale Install Mechanism Change

The locale support installation mechanism has changed in the SolarisTM 8 operating environment. In the Solaris 2.5.1, 2.6, and 7 operating environments the level of locale support installed depended upon the software cluster chosen. The Solaris 8 operating environment includes a new install interface that prompts you to select specific geographic regions for which you require locale support. Therefore, you can customize the configuration of your system when you install the Solaris 8 operating environment more than was possible in the Solaris 2.5.1, 2.6, and 7 operating environments.

Pay special attention to the following behaviors:

Installation Bugs That Occur During an Interactive Installation

Installation Progress Bar May Be Inaccurate (1266156)

The Installing Solaris Software - Progress bar sometimes indicates that an installation is complete when it is still in progress. The install program may add packages for several minutes after the progress bar has indicated that the installation is complete.

Do not rely on the progress bar to indicate that the installation is complete. The installation displays the following message when the program has completed all installation operations.


Installation complete

Warnings May Occur When Creating a File System (4189127)

One of the following warning messages may be displayed when creating a file system during installation.


Warning: inode blocks/cyl group (87) >= data blocks (63) in last cylinder group. This implies 1008 sector(s) cannot be allocated.
or

Warning: 1 sector(s) in last cylinder unallocated
The warning occurs when the size of the file system being created does not map exactly to the space on the disk being used. This can result in unused space on the disk that is not incorporated into the indicated file system. This unused space is not available for use by other file systems.

Workaround: Ignore the warning message.

No Error Occurs If # Is Included In A Path (4294586)

If a # is included in the path of a JavaTM program, the following message is displayed when you execute the program.


Exception in thread "main" java.lang.NoClassDefFoundErrorVolume Management (vold) sometimes uses a pound sign in a pathwhen creating directory names:

Workaround: Delete the # from the path or do not use any Java installation wizards.

Custom JumpStart Does Not Prompt for the Solaris 8 Software 2 of 2 CD (4304912)

After installing the Solaris 8 Software 1 of 2 CD, a custom JumpStartTM installation does not prompt you to install the Solaris 8 Software 2 of 2 CD.

Workaround: If you are installing only the End User software group, you do not need to install the Solaris 8 Software 2 of 2 CD as the End User software and its basic locale support is contained on the Solaris 8 Software 1 of 2 CD.

Wizard Stops If You Insert the Solaris 8 Software 2 of 2 CD When the 1 of 2 CD Is Requested (4306752)

For some English-only versions of the Solaris 8 Installation CD, the installation program enables you to insert the Solaris 8 Software 2 of 2 CD at the point the installation program requested the Solaris 8 Software 1 of 2 CD.

If the incorrect CD has been inserted, the installation program attempts to use it even though it can no longer install the Solaris operating environment.

If you are performing a default installation, the following message is displayed in the summary panel's Details window:


ERROR: Could not load the media (/cdrom)" error message
If an Installation CD custom install had been selected, a blank panel would be displayed immediately after choosing Custom and selecting the Next Panel button.

Workaround: Insert the Solaris 8 Software 1 of 2 CD when requested. If you inserted the Solaris 8 Software 2 of 2 CD after a blank screen was displayed, you need to restart the installation by beginning with the "Boot CD-ROM" step.

An Arithmetic Exception Occurs When a Zip Drive is Attached With No Media in a Drive (4307035)

Solaris Web Start reports an arithmetic exception when a zip drive is attached and no disk has been inserted in the drive. The following message is displayed: 


Starting the Web Start 3.0 Solaris installer
./W00.findswap[1823]: 173 Arithmetic Exception
Could not get disk information.
Exiting
Workaround: Either disconnect the zip drive before you boot your system or insert the zip disk into the drive.

Cannot Perform a JumpStart Installation From a CD on the sun4us Platform (4309047)

The sun4us entry is missing from the servers_xlarge profile file.

Workaround: Set up a netinstall image using setup_install_server and modify the servers_xlarge file to include the client_arch entry for the sun4us platform. Then proceed with the JumpStart installation.

CD-ROM-Based Installation From the Solaris 8 Software 1 of 2 CD With Selection of DHCP Fails (4310705)

If a system is installed with the Solaris 8 Software 1 of 2 CD, you may be prompted to configure the system using the Dynamic Host Configuration Protocol (DHCP). If you select DHCP, the installation fails. The following message is displayed:


The IP address previously set on the network interface is no longer available.
This problem does not occur if you install the system:

Workaround: Configure the system to use DHCP after the installation has completed, use the Web Start installation program, or install the system using a Net Install server.

Upgrade Issues

Solaris Easy Access Server (SEAS)

The applications in Solaris Easy Access Server are not certified to run in the Solaris 8 operating environment. If you are running applications from SEAS, you must install the Solaris 8 Admin Pack to ensure that those applications will run properly in the Solaris 8 operating environment.

Several of the applications that are included in SEAS releases are now part of the Solaris 8 operating environment:

The following SEAS applications have not been certified to run in the Solaris 8 operating environment:

Priority Paging Is Not Needed With the New Solaris 8 Caching Architecture

The Solaris 8 operating environment introduces a new file system caching architecture, which subsumes the Solaris 7 Priority Paging functionality. The system variable priority_paging should not be set in the Solaris 8 operating environment, and should be removed from the directory /etc/system when systems are upgraded to the Solaris 8 operating environment.

The new caching architecture removes most of the pressure on the virtual memory system that resulted from file system activity. As a result, the new caching architecture changes the dynamics of the memory paging statistics, which makes observing system memory characteristics simpler. However, several of the statistics report significantly different values, which should be considered when analyzing memory behavior or setting performance monitoring thresholds. The most notable differences are:

Installation Bugs That Occur During an Upgrade

When Using Already Installed Patches for Sun Microelectronics Platforms During an Upgrade to the Solaris 8 Operating Environment (4240147), the System Fails to Boot

When you upgrade to the Solaris 8 operating environment using already installed patches for Sun Microelectronics platforms, the system fails to boot.

Workaround: If you plan to upgrade to the Solaris 8 operating environment and you have either patch IDs 107258-02 or 107258-01 installed on your system that is running the Solaris 7 operating environment, type:


# patchrm 107258-02
# patchrm 107258-01
Then start the upgrade. Otherwise, the system fails to boot after you have completed the upgrade. After the system has been rebooted, type:

# patchadd 107258-02
# patchadd 107258-01

Relocated CDE from the Solaris 2.5.1 Operating Environment Orphaned By An Upgrade to the Solaris 8 Operating Environment (4260819)

This problem affects systems running the Solaris 2.5.1 and the Solaris 2.5.1 unbundled CDE operating environments. However, these systems are only affected if the unbundled CDE has been relocated to a directory other than /usr/dt. The CDE relocation on these systems has been accomplished by creating a symbolic link in /usr/dt that points to the relocated CDE.

When you upgrade to the Solaris 8 operating environment, CDE is also reinstalled in /usr/dt, and the link to the relocated version is removed. The relocated CDE itself is not removed and is therefore orphaned.

If the upgrade involves the reallocation of file systems, the upgrade may fail because the reallocation mechanism does not account for the extra space needed in /usr/dt for the new version of CDE. This failure is not visible until the upgrade has been completed. If this failure occurs, the upgrade log will include a number of messages indicating that more space is needed for an upgrade.

Workaround: Uninstall the relocated CDE before you start upgrading to the Solaris 8 operating environment. This can be accomplished by using the install-cde script from the Solaris 2.5.1 CDE CD. This script should be run with the -uninstall flag to remove CDE.

Upgrading the Solaris 7 Operating Environment With Web-Based Enterprise Management (WBEM) 1.0 to the Solaris 8 Operating Environment Causes WBEM 2.0 to Not Work (4274920)

If you installed WBEM 1.0 from the Solaris Easy Access Server (SEAS) 3.0 CD-ROM on a system running the Solaris 7 operating environment, you must remove the WBEM 1.0 packages before upgrading to the Solaris 8 operating environment. The Solaris WBEM Services 2.0 do not start after upgrading the Solaris 7 operating environment with WBEM 1.0 to the Solaris 8 operating environment. The Common Information Model (CIM) Object Manager fails to start. The following error message is displayed: 


File not found: /opt/sadm/lib/wbem/cimom.jar

Workaround: Use the pkgrm command to remove the WBEM 1.0 packages before upgrading to the Solaris 8 operating environment.

  1. Use the pkginfo command to check if the WBEM 1.0 packages are installed by typing:


    % pkginfo | grep WBEM

  2. Become superuser.

  3. Use the pkgrm command to remove all WBEM 1.0 packages by typing:


    # pkgrm SUNWwbapi
# pkgrm SUNWwbcor
# pkgrm SUNWwbdev
# pkgrm SUNWwbdoc
# pkgrm SUNWwbm

Disk Space Requirements Can Be Exaggerated by the Upgrade Process (4041733)

The upgrade program can exaggerate by as much as 30 percent the amount of space required for upgrades to systems with Solaris software. Systems affected by this problem cannot be upgraded without deselecting packages or finding more space.

Workaround: You can manually reallocate disk space among file systems or use the Software Customization menu to remove software packages that are not needed.

SUNWeeudt Partially Fails to Install During an Upgrade (4304305)

The upgrade log may state that the SUNWeeudt package was only partially installed.


     Doing pkgadd of SUNWeeudt to /.
     ERROR: attribute verification of 
     </a/usr/dt/appconfig/types/ru_RU.KOI8-R/datatypes.dt> 
     failed pathname does not exist ...

     Installation of <SUNWeeudt> partially failed.
     pkgadd return code = 2

Workaround: Perform the following steps after the upgrade has been completed.

  1. Remove the SUNWeeudt package by typing:


    # pkgrm SUNWeeudt

  2. Add the SUNWeeudt package by typing:


    # pkgadd SUNWeeudt

64-Bit Solaris Issues

Sun UltraSPARC System (sun4u) May Need Boot Flash PROM Upgrade

Note -

If your system is already running 64-bit ready firmware, then the flash PROM upgrade is not required.

If you want to run the 64-bit Solaris operating environment on an UltraSPARCTM system, you may need to upgrade its flash PROM firmware. The Solaris 8 installation programs have a checkbox for adding 64-bit support. This 64-bit support is selected by default when installing on Sun UltraSPARC systems. A 64-bit system only boots in the 64-bit mode by default if it has a CPU speed of 200 Mhz or greater.

Note -

If you choose to run the 32-bit Solaris operating environment on any SunTM or UltraSPARC system, the flash PROM upgrade is not needed.

The following table lists the UltraSPARC (sun4u) systems that are affected and the minimum firmware versions needed. System type is the equivalent of the output of the uname -i command. You can tell what firmware version you are running by using the prtconf -V command.

System Type from uname -i

Minimum Firmware Version from prtconf -V

SUNW,Ultra-1-Engine 

3.10.0 

SUNW,Ultra-1 

3.11.1 

SUNW,Ultra-2 

3.11.2 

SUNW,Ultra-4 

3.7.107 

SUNW,Ultra-Enterprise 

3.2.16 

Note -

If a system is not listed in the above table, it does not need a flash PROM upgrade.

For instructions on performing the flash PROM update using the Solaris CD, refer to the Solaris 8 on Sun Hardware Collection. If you do not have this manual, it can be obtained at http://docs.sun.com.

Localization Bugs

Some Error Messages and Dialogs Are Not Localized and Display Only in English (4283839)

French, Italian, German, Spanish, and Swedish locales have some unlocalized dialogs, a few unlocalized dialogs in help files, and help files not found during an installation.

Installation Of European Software (4299758)

If you install a European locale, additional software for windowing, installation, 64-bit support, and fonts are installed on your system. The impact of this bug is negligible because only minimal additional space is needed to support this extra software.

Swedish Locale: Unlocalized Dialogs Are Displayed During Installation (4300655)

The Solaris interactive install dialog has not been localized except for the title. The section that has not been localized begins with:


You'll be using the initial option .....

French and Italian Install Wizards May Display {0} Instead of the CD Title (4302549)

{0} is occasionally displayed in French and Italian where a CD title should appear.

Motif suninstall Fails in de_AT.ISO8859-15 and fr_BE.ISO8859-15 Locales (4305420)

Installing the operating environment by using the two languages specified causes parts of the installation process to be displayed in English. In addition, not all localization packages are installed. The following message is displayed:


XView warning: "de" kann nicht als Sprachumgebungs-Kategorie 
Ausgabesprache (gesetzt über Umgebungsvariable(n)) verwendet 
werden, wenn Standardspracheauf"de_AT.ISO8859-15" gesetzt ist 
(Server Package)
XView warning: Requested input method style not supported. 
(Server package)

Workaround: Install the Solaris operating environment using the German or French ISO8859-1 locales.

German Locale: Add and Cancel Buttons in the Proxy Kiosk Screen are Labeled as Undefined (4306260)

The German Web Start Kiosk proxy information dialog has the OK and Cancel buttons labeled as Undefined. The button on the left should be OK and the button on the right should be Cancel.