Before You Begin

This section contains critical installation issues that you need to be aware of before installing or upgrading to Solaris 10 OS. These issues might have an impact that would prevent installation or upgrades from completing successfully. If bugs in this section apply to your system, you might need to perform the recommended workarounds before you install or upgrade.

Installation Change for the Solaris Companion DVD

When you are installing the Solaris OS, the Companion DVD is not available to be installed with the Solaris installation program. Use the pkgadd(1M) command to install the Solaris Companion DVD. For detailed installation instructions, see the README file on the Companion DVD.

Solaris Live Upgrade and Solaris Zones

Using Solaris Live Upgrade in conjunction with Solaris zones is not supported. If you have installed non-global zones on a Solaris 10 system, you cannot upgrade to the Solaris 10 1/06 release by using Solaris Live Upgrade.

If you use the luupgrade command, the following error message is displayed:

Unable to upgrade boot environment.

Workaround: To upgrade such a system, use either the Solaris interactive installation program or the custom JumpStart program. These programs apply to your Solaris 10 OS all the patches and new packages that represent the differences between your current OS and the Solaris 10 1/06 software. The programs also apply the packages and patches to all the non-global zones.

Both programs have limitations. For example, you cannot customize your upgrade by installing additional software products or additional locale packages, or by modifying the disk layout. For details about these limitations, see the Upgrading the Solaris OS When Non-Global Zones Are Installed in Solaris 10 6/06 Installation Guide: Custom JumpStart and Advanced Installations.

Patching Miniroot on x86 Machines

The procedures for using patchadd with the -C destination specifier to patch a miniroot on an x86 machine have changed. You must now unpack the miniroot, apply patches, then repack the miniroot.

See the following for the detailed steps:

• Chapter 8, Preparing to Install From the Network With DVD Media (Tasks), in Solaris 10 6/06 Installation Guide: Network-Based Installations

• Chapter 9, Preparing to Install From the Network With CD Media (Tasks), in Solaris 10 6/06 Installation Guide: Network-Based Installations

Correct Solaris Data Encryption Supplement Required for Installation of Solaris 10 1/06 Release

When you install the Solaris 10 1/06 release, you must use the Solaris Data Encryption Supplement that corresponds to the release. The supplement is delivered in the SUNWcry and SUNWcryr packages. If you do not have the correct supplement version, upgrade the supplement by installing the appropriate patch:

• Patch ID 118562-05 or a later revision for SPARC based systems

• Patch ID 118563-04 or a later revision for x86 based systems

To determine your current supplement version, use showrev -p.

Additional Procedures Required When Installing Patches for Solaris 10 1/06 Release

The following patches are applied to resolve problems that were reported in CR 6277164 and CR 6214222:

• Patch ID 119366-05 for SPARC based systems

• Patch ID 119367-05 for x86 based systems

The sections that follow provide further steps that you must perform to completely resolve the reported problems.

Resolving Issues With the GNOME Display Manager (6277164)

When applying the patch, load new values into the GDM configuration files. Then restart the GDM application.

1. To load the new values into the configuration file, choose one of the following options.

   • Copy the /etc/X11/gdm/factory-gdm.conf file to the /etc/X11/gdm/gdm.conf file.

     Perform this step if you have not made any modifications to the gdm.conf file. Then you can start the GDM application.

   • Manually merge the differences in the factory-gdm.conf file into the gdm.conf file.

     Perform this step if you have modified the gdm.conf file and want to retain your modifications.

     When merging files, copy the values for the following commands from the factory-gdm.conf file to the gdm.conf file. These commands enable you to obtain the best OS performance.

     • RebootCommand

     • HaltCommand

     • SuspendCommand

     • DefaultPath

     • RootPath

     • GraphicalTheme

2. To restart GDM, perform the following steps:

   1. Become superuser.

   2. Issue the following command:

      # svcadm disable application/gdm2-login

   3. In the console that is now displayed, press Return to display a command prompt.

   4. To restart GDM, issue the following command:

      # svcadm enable application/gdm2-login

Resolving Issues With AccessKeyMouseListeners (6214222)

To further resolve problems that are reported in CR 6214222, perform these steps when applying the patch.

1. Change to the /etc/X11/gdm/modules directory.

2. Copy the files from factory-AccessDwellMouseEvents to AccessDwellMouseEvents.

3. Copy the files from factory-AccessKeyMouseEvents to AccessKeyMouseEvents.

4. Restart GDM by following the steps that are provided in the previous section.

Sun Fire V250 Server Installation

The SUNWCXall software metacluster must be installed on a Sun Fire V250 Server.

NFS Version 4 Introduces New Prompt at First System Boot

Solaris 10 OS uses NFS Version 4 (NFSv4) as the default distributed file system mechanism. In NFSv4, file user and group attributes are exchanged as strings of the form “user@domain” and “group@domain,” respectively.

The domain portion of the string should be common between client and server. This information is automatically derived from the system's name service domain name. However, in certain cases, the derived domain might not match between client and server. This mismatch might typically occur in environments where either of the following circumstances is true:

• The DNS TXT record is not used.

• Multiple administrative domain boundaries are crossed.

If domain information between client and server does not match, NFSv4-accessed files might appear to be owned by “nobody.”

To ensure proper configuration, on the first system boot the system now prompts you for a domain to use for NFSv4. Answer “no” to this prompt if one of the following configurations describes your deployment:

• Your deployment utilizes the DNS TXT record to configure the NFSv4 domain.

• Your deployment has a single (flat) administrative domain.

Custom JumpStart and Advanced Installations

Environments that use the Custom JumpStart method to perform unattended system installations require minimal tuning to suppress the first boot prompts.

A sample script, set_nfs4_domain, is provided in the Solaris 10 distribution media and is located in the ${CDrom_mnt_pt}/Solaris_10/Misc/jumpstart_sample directory. A copy of this script should be modified to set the NFS4_DOMAIN variable to site-specific needs and be called from within JumpStart's finish script. The target system's NFSv4 domain is therefore preconfigured as part of the JumpStart finish phase, and thus suppresses any first boot prompts.

Follow these steps to perform unattended installations:

1. Create a copy of the set_nfs4_domain script in the same directory as your JumpStart's finish.sh scripts.

2. Edit the script and set the NFS4_DOMAIN variable to your specific needs.

3. Edit your finish.sh script and append a call to set_nfs4_domain.

4. Perform the JumpStart installations as usual.

For further details, refer to the sysidconfig(1M), sysidtool(1M), nfsmapid(1M), and nfs(4) man pages. See also the System Administration Guide: Network Services.

x86: Systems With elx or pcelx NICs Fail Network Configuration

Systems with an elx or a pcelx network interface card (NIC) fail to install. During the configuration of the NIC, the following error message might be displayed:

WARNING: elx: transmit or jabber underrun: d0<UNDER, INTR, CPLT>

See the elxl(7D) or pcelx(7D) man page for more information.

Workaround: Install and run on systems that do not have elx or pcelx NICs.

Default Size of /var File System Inadequate for Extra Value Products

The default size of the /var file system might be insufficient for the Extra Value products in the following situations:

• If you install any of the Extra Value products that are provided on the Solaris 10 DVD or CDs

• If the /var file system is located on a separate slice

You must manually specify a larger slice size for the /var file system.

Workaround: Choose one of the following workarounds.

• If you are using the Solaris installation program GUI, follow these steps.

  1. Begin the installation.

  2. From Select Type of Install, select Custom Install.

     The Solaris installation program displays several screens that enable you to customize the software localizations, products, and disk layout that you want to install.

  3. From Lay Out File Systems, select Modify.

     The disk layout screen is displayed.

  4. Type /var in the File System column for a specific slice, then click Apply.

     The installation program suggests a default size for the /var file system.

  5. Edit the Size column entry for the /var file system to twice the disk space size.

     For example, if the installation program assigns 40 Mbytes of space, change the Size value to 80.

  6. Complete the installation.

• If you are using the Solaris installation program's text installer, follow these steps.

  1. Begin the installation.

  2. From Select Type of Install, select Custom Install.

     The Solaris installation program displays several screens that enable you to customize the software localizations, products, and disk layout that you want to install.

  3. From Lay Out File Systems, select Auto Layout.

     The disk layout screen is displayed.

  4. Type /var in the File System column for a specific slice.

     The installation program suggests a default size for the /var file system.

  5. Press F4_Customize to customize the size of the /var file system.

  6. Edit the Size column entry for the /var file system to twice the disk space size.

     For example, if the installation program assigns 40 Mbytes of space, change the Size value to 80.

  7. Complete the installation.

• If you are using the custom JumpStart program, use the filesys profile keyword to set the size of the /var file system. The following example sets the size of the /var file system on slice 5 to 256 Mbytes.

  filesys  c0t0d0s5 256 /var

x86: Do Not Upgrade Hewlett-Packard (HP) Vectra XU Series Systems With BIOS Version GG.06.13

The Solaris 10 software includes a feature that enables you to install large partitions. The system BIOS must support logical block addressing (LBA). BIOS Version GG.06.13 does not support LBA access. The Solaris boot programs cannot manage this conflict. This issue can also affect other HP Vectra systems.

If you perform this upgrade, your HP system can no longer boot. Only a blank black screen with a flashing underscore cursor is displayed.

Workaround: Do not upgrade HP Vectra XU Series systems with the latest BIOS Version GG.06.13 to the Solaris 10 release. This version no longer supports these systems.

You can still boot your system by using the boot diskette or boot CD because the boot paths do not use the hard disk code. Then select the hard disk as your bootable device instead of the network or CD-ROM drive.

SPARC: Older Firmware Might Need Boot Flash PROM Update

On SPARC based systems, Solaris 10 OS runs in 64–bit mode only. Some Sun4U systems might need to be updated to a higher level of OpenBoot firmware in the flash PROM to run the OS in 64-bit mode. The following systems might require a flash PROM update:

• Ultra 2

• Ultra 450 and Sun Enterprise 450

• Sun Enterprise 3000, 4000, 5000, and 6000 systems

The following table lists the UltraSPARC systems and the minimum firmware versions that are required to run the 64–bit Solaris 10 OS. System type is the equivalent of the output of the uname -i command. You can determine which firmware version you are running by using the prtconf -V command.

Table 1-1 Minimum Firmware Versions Required to Run 64–Bit Solaris Software on UltraSPARC Systems

System Type From uname -i Minimum Firmware Version From prtconf -V SUNW,Ultra-2 3.11.2 SUNW,Ultra-4 3.7.107 SUNW,Ultra-Enterprise 3.2.16

See any edition of the Solaris 8 Sun Hardware Platform Guide at http://www.oracle.com/technetwork/indexes/documentation/index.html for instructions to perform a flash PROM update.

Additional Patches Are Needed to Run Solaris Live Upgrade

For Solaris Live Upgrade to operate correctly, a limited set of patch revisions must be installed for a given OS version. Make sure you have the most recently updated patch list by consulting http://sunsolve.sun.com. For additional information, search for the info Doc 72099 on the SunSolve web site.

Limitation When Installing Solaris Live Upgrade Packages

If you are running the Solaris 7 or Solaris 8 release, you might not be able to run the Solaris Live Upgrade installer. These releases do not contain the set of patches that is needed to run the Java 2 runtime environment.

The typical failure that results is a Java exception error. The following messages might be displayed:

InvocationTargetException in ArchiveReader constructornull
          java.lang.reflect.InvocationTargetException
                 at install.instantiateArchiveReader(Compiled Code)
                 at install.<init>(Compiled Code)
                 at install.main(Compiled Code)

To run the Solaris Live Upgrade installer and install the packages, you must have the Java 2 runtime environment recommended patch cluster.

Workaround: Complete the following workaround:

• Install the Solaris Live Upgrade packages by using the pkgadd command.

  For step-by-step instructions, refer to Chapter 8, Using Solaris Live Upgrade to Create a Boot Environment (Tasks), in Solaris 10 6/06 Installation Guide: Solaris Live Upgrade and Upgrade Planning.

• Install the Java 2 runtime environment recommended patch cluster. The patch cluster is available on http://sunsolve.sun.com. Then, you can use the Solaris Live Upgrade installer to install the packages.

Solaris Management Console 2.1 Software Is Not Compatible With Solaris Management Console 1.0, 1.0.1, or 1.0.2 Software

Solaris Management Console 2.1 software is not compatible with Solaris Management Console 1.0, 1.0.1, or 1.0.2 software. If you are upgrading to the Solaris 10 release, and you have Solaris Management Console 1.0, 1.0.1, or 1.0.2 software installed, you must first uninstall the Solaris Management Console software before you upgrade. Solaris Management Console software might exist on your system if you installed the SEAS 2.0 overbox, the SEAS 3.0 overbox, or the Solaris 8 Admin Pack.

Workaround: Choose one of the following workarounds:

• Before you upgrade, use the /usr/bin/prodreg command to perform a full uninstall of Solaris Management Console software.

• If you did not uninstall Solaris Management Console 1.0, 1.0.1, or 1.0.2 software before you upgraded to the Solaris 10 release, you must first remove all Solaris Management Console 1.0, 1.0.1, or 1.0.2 packages. Use the pkgrm command for package removal instead of the prodreg command. Carefully follow the order of package removal. Complete the following steps:

  1. Become superuser.

  2. Type the following command:

     # pkginfo | grep “Solaris Management Console“

     If the description does not start with “Solaris Management Console 2.1,” the package names in the output identify a Solaris Management Console 1.0 package.

  3. Use the pkgrm command to remove all instances of Solaris Management Console 1.0 packages in the following order:

     ---

     Note - Do not remove any package that has “Solaris Management Console 2.1” in its description. For example, SUNWmc.2 might indicate Solaris Management Console 2.1 software.

     If the pkginfo output displays multiple versions of Solaris Management Console 1.0 packages, use the pkgrm command to remove both packages. Remove the original package. Then, remove the package that has been appended with a number. For example, if the SUNWmcman and SUNWmcman.2 packages appear in the pkginfo output, first remove the SUNWmcman package and then remove the SUNWmcman.2 package. Do not use the prodreg command.

     ---

     # pkgrm SUNWmcman
     # pkgrm SUNWmcapp
     # pkgrm SUNWmcsvr# pkgrm SUNWmcsvu
     # pkgrm SUNWmc
     # pkgrm SUNWmcc
     # pkgrm SUNWmcsws

  4. In a terminal window, type the following command:

     # rm -rf /var/sadm/pkg/SUNWmcapp

  The Solaris Management Console 2.1 software should now function properly. For future maintenance, or if the Solaris Management Console 2.1 software does not function properly, remove the Solaris Management Console 2.1 software. Reinstall the software by completing the following steps:

  1. Use the pkgrm command to remove all Solaris Management Console 2.1 packages and dependent packages in the following order:

     ---

     Note - If your installation has multiple instances of Solaris Management Console 2.1 packages, such as SUNWmc and SUNWmc.2, first remove SUNWmc, and then SUNWmc.2 . Do not use the prodreg command.

     ---

     # pkgrm SUNWpmgr 
     # pkgrm SUNWrmui 
     # pkgrm SUNWlvmg 
     # pkgrm SUNWlvma 
     # pkgrm SUNWlvmr 
     # pkgrm SUNWdclnt 
     # pkgrm SUNWmga 
     # pkgrm SUNWmgapp 
     # pkgrm SUNWmcdev 
     # pkgrm SUNWmcex 
     # pkgrm SUNWwbmc 
     # pkgrm SUNWmc 
     # pkgrm SUNWmcc 
     # pkgrm SUNWmccom

  2. Insert the Solaris 10 Software - 4 CD into your CD-ROM drive. Type the following in a terminal window:

     # 
     # cd /cdrom/cdrom0/Solaris_10/Product
     # pkgadd -d . SUNWmccom SUNWmcc SUNWmc SUNWwbmc SUNWmcex SUNWmcdev \
       SUNWmgapp SUNWmga SUNWdclnt SUNWlvmr SUNWlvma SUNWlvmg SUNWpmgr \
       SUNWrmui

  All previous Solaris Management Console versions are removed. The Solaris Management Console 2.1 software is now functional.

SPARC: Upgrade Hangs on Sun Blade 1500 Workstations (6363365)

Upgrading to the Solaris 10 1/06 software might hang if you are installing or upgrading from a DVD media. The problem affects certain Sun Blade 1500 workstations that are equipped with the JLMS DVD drive. The error occurs when you use any of the following installation methods:

• Solaris interactive installation program

• Solaris Live Upgrade

When the system hangs, no error messages are displayed.

Workaround: To upgrade such a system, use a network installation image.

x86: Failure of BIOS Device Utility Prevents Installation or Upgrade From Being Completed (6362108)

On certain occasions, the utility for BIOS devices (/sbin/biosdev) might fail and prevent a successful installation or upgrade. The failure can occur under either of the following circumstances:

• Patch ID 117435-02 was applied, but the system was not rebooted.

• The system contains two or more identical disks that have identical fdisk partitions.

The following error message is displayed:

biosdev: Could not match any!!

Workaround: Make sure that you reboot the system after applying Patch ID 117435-02. Ensure that identical disks to be used in the installation or upgrade are configured with different fdisk-partition layouts.

The following example is based on a system that has two disks with identical fdisk-partition layouts. To change the layouts, perform the following steps.

1. Become superuser.

2. Start the disk maintenance utility.

   # format

   A list of available disks in the system is displayed.

3. To select the disk whose fdisk partition you want to change, type the disk's number.

4. From the list of Format options, select fdisk.

   The disk's partition information and a list of fdisk options are displayed.

5. To change the disk's layout, choose one of the following:

   • To specify a different active partition, press 2.

   • To add another disk partition, press 1.

   • To delete an unused partition, press 3.

6. To save your changes and exit the fdisk menu, press 5.

7. To exit the disk maintenance utility, select Quit from the Format options.

8. Reboot the system.

9. After the system reboots, verify that the error message no longer appears. As superuser, type the following command:

   # /sbin/biosdev

   If the error message is still generated, repeat the procedure but select a different option in Step 5.

10. If the system contains other identical disks with identical fdisk-partition layouts, repeat Steps 1-9 on these disks. Otherwise, you can proceed with your Solaris installation or upgrade.

Upgrade Option Unavailable if the Root (/) File System Is a RAID-1 Volume (Mirror) (6263122)

A problem occurs when you upgrade to the Solaris 10 1/06 software a system whose root (/) file system is a RAID-1 volume. This problem occurs when you perform the upgrade as follows:

• You use CD media or an network installation image.

• You use the Solaris interactive installation program or custom JumpStart.

One of the following problems occurs:

• If you are using the Solaris interactive program, you are not given the option of upgrading in the panel Select upgrade or initial install.

• If you use custom JumpStart to upgrade, the following error message is displayed:

  ERROR: No upgradeable root file systems were found.

Workaround: Perform Workaround 1 first. Proceed to Workaround 2 only if the first workaround did not resolve the issue.

• Workaround 1:: Remove the RAID configurations before performing the upgrade. Rebuild your RAID configuration after the upgrade is completed. To remove the RAID configurations, follow these steps.

  1. Find the physical devices that are being used for the root partition's RAID-0 volumes or submirrors, as in the following example:

     # df -k /
     
     Filesystem         kbytes    used   avail capacity  Mounted on
     /dev/md/dsk/d0    4459950 3089180 1326171    70%    /
     
     # metastat -p d0
     
     d0 -m d10 d11 1
     d10 1 1 c1t0d0s0
     d11 1 1 c1t1d0s0

  2. Remove the mirror that is not being upgraded. In the example, if the disk to be upgraded is c1t0d0s0, you need to remove d11. Type the following:

     # metadetach d0 d11

  3. Revert to using the appropriate physical device to be upgraded. For the previous example, you issue the following command.

     # metaroot c1t0d0s0

  4. If necessary, verify that the /etc/vfstab has been updated with the required device.

     # grep c1t0d0s0 /etc/vfstab
     
     /dev/dsk/c1t0d0s0  /dev/rdsk/c1t0d0s0 /  ufs  1 no -

  5. Shut down the system.

  6. Boot the system from the DVD or CD media.

     In the panel Select upgrade or initial install, you can now choose to upgrade. You can also select the device to upgrade from the list of devices in the panel. Typically, the list contains the devices that comprise the original root subvolume.

     However, if the option to upgrade remains unavailable, then skip to the alternative workaround.

  7. To proceed with the upgrade, select the device.

  To rebuild your RAID configurations after the upgrade has been completed, follow these steps.

  1. Redefine the boot device.

     # metaroot d0

  2. Reboot the system.

  3. Add the subvolume.

     # metattach d0 d11

• Workaround 2: Use this workaround only if Workaround 1 was not successful. Do not perform this workaround without attempting the previous workaround first.

  1. Reboot the system.

     The system boots back to the existing Solaris release.

  2. Delete the active metadevices that comprise the root partition by using the metaclear command.

     # metaclear d0 d10 d11

  3. Shut down the system.

  4. Boot the system from the DVD or CD media.

  5. Proceed with the installation by following the installation or upgrade options that appear on the screen.

  6. After the upgrade is completed, reconfigure your metadevices by following the normal procedures.

  The following example shows the steps to configure the root (/) metadevice, set up the system files for the metadevice, and reattach the subvolume.

  # metainit d0 -m d10
  # metaroot d0
  # reboot
  
  # metainit d11 1 1 c1t1d0s0
  # metattach d0 d11

  ---

  Note - You reattach the old subvolume after the system boot is completed.

  ---

Cannot Create a Solaris Flash Archive When Solaris Zones Are Installed (6246943)

Starting with the current Solaris release, a Solaris Flash archive cannot be properly created when a non-global zone is installed. The Solaris Flash feature is not currently compatible with the Solaris containers (zones) feature.

Do not use the flar create command to create a Solaris Flash archive in these instances:

• In any non-global zone

• In the global zone if there are any non-global zones installed

If you create a Solaris Flash archive in such an instance, the resulting archive might not install properly when the archive is deployed.

Workaround: None.

Installation Fails When You Install Solaris Flash Archive on Empty Boot Environment With Solaris Live Upgrade (6222925)

If you use Solaris Live Upgrade to install a Solaris Flash archive on an empty alternate boot environment, the installation fails. Messages that are similar to the following errors are displayed.

sh:  /path_to_install_image/Solaris_10/Tools/Boot/usr/sbin/install.d
/mergescripts/merge_name_service:  not found

ERROR: Transfer list entry (/a/var/svc/profile/name_service.xml):
mergescript failed (/path_to_install_image/Solaris_10/Tools/
Boot/usr/sbin/install.d/mergescripts/merge_name_service)

ERROR: Unable to copy a temporary file to it's final location

ERROR: Flash installation failed

Extracting Flash Archive: 100% completed (of 4361.24 megabytes)
The Solaris flash install of the BE S10B74L2 failed.

In the previous example, path_to_install_image is the directory path to the network installation image you are using for the installation.

Workaround: Follow these steps.

1. Change directories to the mergescripts directory in the network installation image that you are using for the installation.

   # cd path_to_install_image/Solaris_10/Tools /Boot/usr/sbin/install.d/mergescripts

2. Create the merge_name_service file.

   # touch merge_name_service

3. Make the merge_name_service file executable.

   # chmod a+x merge_name_service

4. On the system you want to install, install the Solaris Flash archive on the alternate boot environment with Solaris Live Upgrade.

   For instructions about how to install a Solaris Flash archive with Solaris Live Upgrade, see Installing Solaris Flash Archives on a Boot Environment in Solaris 10 6/06 Installation Guide: Solaris Live Upgrade and Upgrade Planning.

5. Mount the file systems in the alternate boot environment you installed in step 4.

   # lumount alt_boot_env mount-point

   In the previous command, alt_boot_env is the boot environment you installed in step 4. mount-point is the mount point for the alternate boot environment.

6. Change directory to the /var/svc/profile directory in the alternate boot environment.

   # cd mount-point/var/svc/profile

7. Remove the name_service.xml profile.

   # rm name_service.xml

8. Create a symbolic link for the name service profile to the name_service.xml file.

   # ln -s ns_name-service.xml name_service.xml

   In the previous example, name-service is the name service you want to use for the system. Use one of the following strings for this value.

   • nis

   • nisplus

   • dns

   • ldap

   • files

x86: Sun Java Workstations 2100Z Might Panic When Booting From Solaris 10 Operating System DVD (6214356)

The DVD combo-drive firmware in a Sun Java Workstation 2100Z might cause a system panic. The panic occurs when you boot the workstation from the Solaris 10 Operating System DVD. After the kernel banner is displayed, the following message is very quickly flashed:

panic[cpu0]/thread=fec1be20: mod_hold_stub: 
Couldn't load stub module sched/TS_DTBL
fec25cb0 genunix:mod_hold_stub+139 (fec04088, 63, fea11)
fec25cc4 unix:stubs_common_code+9 (1, 8, fec026e4)
fec25ce4 unix:disp_add+3d (fec026dc)
fec25d00 genunix:mod_installsched+a4 (fef01530, fef01518)
fec25d20 genunix:mod_install+2f (fef01518, fec25d3c,)
fec25d2c TS:_init+d (0, d6d89c88, fec25d)
fec25d3c genunix:modinstall+d9 (d6d89c88)
fec25d50 genunix:mod_hold_installed_mod+2e (d6d77640, 1, fec25d)
fec25d7c genunix:modload+ac (fec026c4, fec26c4)
fec25d98 genunix:scheduler_load+3d (fec026c4, fec026dc)
fec25db4 genunix:getcid+50 (fec026c4, fec28514)
fec25dcc unix:dispinit+df (fec25ddc, fe814ba9)
fec25dd4 unix:startup_modules+d5 (fec25dec, fe8cac37)
fec25ddc unix:startup+19 (fe800000, 166130, 7)
fec25dec genunix:main+16 ()

Then the system automatically resets.

Workaround: Choose one of the following options:

Workaround 1: Modify some BIOS configuration settings. This temporary workaround enables a Solaris 10 installation to be completed. However, this method might cause poor read-DVD performance. Follow these steps:

1. During system boot, press F2 at the prompt to enter the setup.

   The screen displays attachment-type options similar to the following example:

   Primary Master [ ]
   Primary Slave [ ]
   Secondary Master [CD-ROM]
   Secondary Slave [ ]

2. Choose the DVD drive's attachment type by selecting the attachment type for CD-ROM.

   ---

   Note - The screen might display more than one attachment type for CD-ROM, for example, if your system has multiple optical drives. In such cases, you might need to open the system case to determine the DVD drive's point of attachment. Make sure that you select the correct attachment type that applies to the DVD drive.

   ---

3. After selecting the correct CD-ROM attachment type, press Enter.

   The next screen appears with Type:[Auto] automatically selected.

4. Press the spacebar twice to change the selection to Type:[CD-ROM].

5. Use the arrow keys to select Transfer Mode.

6. Press Enter to display a list of other Transfer Mode options.

7. Use the arrow keys to select Standard, then press Enter to accept your selection.

8. Press F10 to save the configuration changes and exit BIOS setup.

   The system restarts.

Workaround 2: Update the DVD combo drive's firmware to v1.12. This option requires your DVD combo drive to be attached to a system that is running Microsoft Windows. Follow these steps.

1. Remove your DVD combo drive from the Sun Java Workstation 2100z. See the workstation's user's guide for steps to remove the drive properly.

2. Connect the drive to a system that is running Microsoft Windows. Make sure to change the drive's master and slave jumper settings, if needed.

3. Go to AOpen's download center at http://download.aopen.com.tw/default.aspx.

4. Search for your DVD drive's firmware by using the following information:

   • Product: Combo drives

   • Model: COM5232/AAH

   • Categories: Firmware

5. Download and install the firmware version R1.12.

6. Reinstall the drive on the workstation. If needed, restore the original master and slave jumper settings.

x86: Serial Consoles of Some Sun Fire Systems Do Not Work (6208412)

The serial console (ttya) on the following Sun Fire systems does not work by default:

• Sun Fire V20z

• Sun Fire V40z

• Sun Fire V60x

• Sun Fire V65x

To use the serial console, you must manually configure the system's BIOS.

Workaround: This workaround requires your system to have a Sun keyboard and a display monitor. Follow these steps:

1. Boot the machine.

2. During system boot, press F2 at the prompt to access the Phoenix BIOS.

3. Under Peripherals, change the comm port from disabled to enabled.

4. Save the configuration and boot the system.

5. Use the eeprom command to change input-device and output-device to ttya.

Solaris Installation GUI Program Might Fail on Systems With Existing x86 fdisk Boot Partitions (6186606)

The Solaris installation GUI program might fail on a system with an existing x86 boot partition. The failure occurs if the existing x86 boot partition was created with the Solaris text-based installer. The following error message is displayed.

Default layout will not work on this system.
Error:
Error: ERROR: Could not create explicit fdisk partition on c0t0d0,
requested cylinders 14581 - 14597 in use by fdisk partition 1
Error:
Error: ERROR: System installation failed
Pfinstall failed. Exit stat= java.lang.UNIXProcess@a89ce3 2 
artition on c0t0d0, requested cylinders 14581 - 14597 in use by fdisk
partition 1  ERROR: System installation failed

Workaround: Choose one of the following workarounds.

Workaround 1: When the installation program prompts you to select an installation type, select 3 Solaris Interactive Text (Desktop Session).

Workaround 2: If you use the Solaris installation GUI program, follow these steps.

1. Begin the installation.

2. At the prompt to select an installation type, select Custom Install.

   The custom installation panels prompt you for information about the locales, software, and disks that you want to install.

3. Answer the questions on the screens as appropriate for your system.

4. On the Fdisk Selection screen, check the disk that contains the x86boot partition.

5. Remove the x86boot partition by changing it to UNUSED in the pull-down menu.

6. Add the x86boot partition back by changing UNUSED back to x86boot.

7. Continue the installation.

x86: X Server Unable to Open Mouse Device in Sun LX50 Servers (5027771)

On a Sun LX50 system, the X server might be unable to open a PS/2 mouse device. The error might occur either during installation or when the system reboots. When the problem occurs, the following error message is displayed:

ddxSUNWmouse: Error opening mouse device '/dev/kdmouse;
     /dev/kdmouse: No such device or address

Consequently, the Solaris installation program can proceed only in command-line interface mode. After installation, the problem might persist during Solaris runtime.

Workaround: On the Y-cable that connects to the server's PS/2 connector, switch the connections between the PS/2 keyboard and mouse.

If the PS/2 mouse remains unrecognized after a system reboot, press the LX50 server's Reset button. Alternatively, use the reconfigure option (b -r) when the following boot prompt appears:

Select (b)oot or (i)nterpreter: