SPARC : OpenSolaris 2009.06 Release Notes

Release Notes for the SPARC: OpenSolaris 2009.06 Release

This page lists the Release Notes for the *SPARC: OpenSolaris 2009.06* release. For additional information on the following issues, look up the bug number in Bugzilla.

Refer to the Release Notes for the x86: OpenSolaris 2009.06 release. For information about the new features in the OpenSolaris 2009.06 release, see What's New in OpenSolaris 2009.06.

For translations of this document, refer to Release Notes translated into non-English Languages

Installation Bugs

This section describes installation issues that apply to the OpenSolaris 2009.06 OS.

• #6616 platform/sun4u/dscp:default Service Failure Warnings Might be Displayed in sun4v Machines

  Description

  On some SPARC platforms, service failure warnings are generated during an Automated Install session. A warning similar to the following is displayed.

  Feb 19 16:07:43 svc.startd[7]: svc:/platform/sun4u/dscp:default: Method
  "/lib/svc/method/svc-dscp start" failed with exit status 96.
  Feb 19 16:07:43 svc.startd[7]: platform/sun4u/dscp:default misconfigured:
  transitioned to maintenance (see 'svcs -xv' for details)
  

  This issue occurs because architecture specific services are not enabled correctly. These service failure warnings are benign and install succeeds.

  Workaround

  The warning messages can be ignored.

• #7218 Convert Existing installadm Services

  Description

  The latest version of SUNWinstalladm-tools from http:pkg.opensolaris.org/release contains fixes for the following bug:

  #7218 - installadm needs to move service data into SMF

  If you update your automated install server with the versions of SUNWinstalladm-tools and SUNWinstall-libs packages that fix #7218, then you will need to convert any services previously created with installadm create-service.

  Workaround

  Use the following procedure to convert the services created with installadm create-service.

  1. Install the new SUNWinstalladm-tools and SUNWinstall-libs packages.
  2. Reboot the automated install server.
  3. Download and run the convert.sh script found at http://opensolaris.org/os/project/caiman/auto_install/convert.sh.
  4. Enable the service:

     svcadm enable svc:/system/install/server:default

  For more information, see the OpenSolaris Automated Installer Guide.

• #8575 Automated Installation Fails if Slice 0 is Configured on the Client With Lesser Than 8 GB Disk Space

  Description

  Automated Installation fails when the Automated Installation manifest points to a target device and the slice 0 on target device is configured with less than 8 GB of disk space. The following error message is displayed:

  Auto install failed

  The Automated Installation fails because it runs out of space in slice 0 of the target device.

  Workaround

  Choose one of the following workarounds:

  • Create slice 0 of the target device with more than 8 GB space.
  • If there is another slice with more than 8 GB space, change the Automated Installation manifest to use that slice. For example, if you want to use Slice 4 of your target device c0t0d0, add the following lines to your Automated Installation manifest:

    <ai_target_device>
       <target_device_name>c0t0d0</target_device_name>
       <target_device_install_slice_number>4</target_device_install_slice_number>
    </ai_target_device>
    

• #8661 Automated Installer Fails to Continue With Installation if Slices from the Previous Configuration Exist

  Description

  When a custom Automated Installation manifest is used to install a system and there are customizations in the manifest to create slices other than the root slice if those slices already exist on the disk in your system, then the automated installation fails. The following error message is seen in the install_log file:

  root@opensolaris:/tmp# tail -20 /tmp/install_log
  
   /tmp/ai_combined_manifest.xml is a valid manifest
   Auto reboot disabled
   Disk = c8t0d0 found on the system
   Disk name selected for installation is c8t0d0
   no manifest partition information found
   disk partition info not changed
   System reports enough physical memory for installation,
  swap is optional
   creating slice which already exists
   failed to modify slice(s) specified in the manifest
   Auto install failed
  

  Workaround

  Use the format(1M) command to remove the existing slices from your disk. Rerun the automated installation by rebooting your system back into the Automated Installer.

• #8773 installadm create-service Followed Quickly by installadm delete-service Causes installadm to Hang

  Description

  If you type installadm create-service followed immediately by installadm delete-service, the installadm command might hang. This command hangs because the installadm smf service, svc:/system/install/server:default, is not online when the installadm delete-service command is executed.

  Workaround

  Wait for the svc:/system/install/server:default service to be online. To determine whether this service is online, type svcs svc:/system/install/server:default and check whether the STATE is listed as online.

• #8884 Incorrect Backslash in Automated Installer Document Example

  Description

  The following SPARC example command in the OpenSolaris Automated Installer Guide section, How to Complete Server Setup (Advanced Instructions), contains an extra backslash:

  # installadm create-service -n sparc1 -s /root/Desktop/osol-0906-111a-ai-sparc.iso /export/aiserver/osol-0906-ai-sparc

  If you type the command with the backslash, the following error message is displayed:

  The installadm SMF service (svc:/system/install/server:default) is no longer
  online
  because the last install service has been disabled or deleted.
  
  

  Workaround

  The backslash should not be used in the command. Rerun the command without the backslash.

• #8961 Specifying pkg Version Strings in the Automated Installation Manifest List of Packages causes Automated Installation to Fail

  Description

  Automated Installation might fail if version strings for packages are specified in the Automated Installation manifest. The following error message might be found in the Automated Installation SMF log at /var/svc/log/application-auto-installer:default.log.

  Unable to install SUNW in /a
  om_perform_install failed with error 114
  Auto install failed

  Workaround

  List the entire package first and specify version strings for the entire package only. For example:

  <ai_install_packages>
      <pkg name="entire@0.5.11,5.11-0.111"/>
      <pkg name="SUNWcsd"/>
      <pkg name="SUNWcs"/>
      <pkg name="SUNWj6rtx"/>
      <pkg name="SUNWgroff"/>
      <pkg name="SUNWgcc"/>
      <pkg name="babel_install"/>
      <pkg name="xvm"/>
  </ai_install_packages>
  
  
  #9026
   VTOC Partition Size Is Not Aligned to the Cylinder Boundary on Disks Larger Than 1.96 TB
  
  Description
  
  On disks larger than 1.96 TB, the installer creates VTOC slices which are not aligned on the cylinder boundary. 
  The installed OpenSolaris instance will boot successfully but the format(1M) tool cannot process the VTOC configuration.
  The tool will report that the disk does not contain a valid label.
  
  Workaround
  Use the Solaris format(1M) tools to create the required VTOC configuration outside the installer.
  Then install into the existing slice using the Automated Installer.
  For more information on how to configure and use the Automated Installer, see the OpenSolaris Automated Installer Guide.
  
  
  
  

Packaging Bugs

This section describes IPS-related issues that apply to the OpenSolaris 2009.06 OS.

• #7836 Warnings Are Displayed While Using pkg image-update

  Description

  While updating an image to build 111 or beyond, a warning message similar to the following might be displayed:

  driver (emlxs) upgrade (removal of minor perm '* 0600 root sys'') failed with
  return code 252
  command run was: /usr/sbin/update_drv -b /mnt -d -m * 0600 root sys' emlxs
  command output was:
  
  No entry found for driver (emlxs) in file (/mnt/etc/minor_perm).
  
  

  This bug occurs only when the SUNWemlxs package is manually added to the OpenSolaris 2008.11 OS and the system is updated to the OpenSolaris 2009.06 release. This warning message is displayed for many drivers including emlxs, afe, audio810, audiohd, audioixp, bnx, isa, ixgbe, nge, nv_sata, and qlc.

  Workaround

  The warning can be ignored.

Hardware-Related Bugs

This section describes hardware-related issues that apply to the OpenSolaris 2009.06 OS.

• #6831186 Sun Ultra 45 Workstation With XVR-300 Graphics Adapter Crashes While starting X Server

  Description

  Sun Ultra 45 Workstations with XVR-300 Graphics Adapter installed crash while starting the X Server. The system crashes just before the Gnome Display Manager (GDM) login page. JBUS-PCI error messages are displayed.

  Workaround

  None.

• #6831559 KFB and EFB Graphics Drivers have Initialization Issues with LCD Monitors

  Description

  The KFB and EFB drivers have initialization issues because of the failure to retrieve EDID support data from the LCD monitor. This causes the GNOME window system to hang or crash at GDM login or shortly after login. This issue is mainly seen with KFB drivers.

  Workaround

  Generate an /etc/X11/xorg.conf file. Perform the following steps:

  1. Disconnect the LCD monitor before you start.
  2. On the virtual-console, type the following command:

     # fbconfig -dev efb0 -res VESA_STD_1280x1024x60 now nocheck

  Note: For the XVR-2500 and KFB driver it is recommended that you use a SUN CRT type Monitor, Part numbers: 365-1399-01, 365-1418-01. Currently LCD Monitors with KFB are facing issues, even when the resolution and xorg.conf file is pre-created with resolution set at 1280x1024x60.

  See also, CRs 6841967, 6838784, and 6831186.

• #6835217 EFB Driver Shows Graphic Artefacts Even Under Supported Resolutions

  Description

  The screen displays noise while moving windows and the windows have rough borders.

  Workaround

  None.

• #6836612 GNOME Monitor Resolution Applet Locks Out User.

  Description

  When the user clicks on System -> Preferences -> Screen Resolution, the user is locked out of the system.

  Workaround

  None.

• #6836558 Window Display Fails to Return After Display Power Management

  Description

  When the display power management reaches the OFF state, pressing the mouse button, or keyboard tab, or the control key does not display the window system.

  Workaround

  Generate an /etc/X11/xorg.conf file. Perform the following procedure:

  1. Disconnect the LCD monitor before you start.
  2. On the virtual-console, type the following command:

     # fbconfig -dev efb0 -res VESA_STD_1280x1024x60 now nocheck

  3. Reboot your system.

• #6837629 Xorg Fails With Fatal Error

  Description

  Xorg Fails with a fatal error on XVR-2500 after the xhost is set. All applications and utilities close and the server crashes. This failure occurs when the XVR-2500 is connected to the SUN CRT Monitor. The following error message is seen:

  ddxDriverInit: Could not register as server

  This issue occurs when you type the following commands on the command-line:

  # /usr/X11/bin/Xorg& 
  
  /usr/X11/bin/xhost + 

The error message is displayed and the driver crashes. GDM is functional when the X Server is restarted.

Workaround

None.

• #6838784 EFB XVR-300 Ignores Resolution Set by fbconfig on Sun CRT Monitors

  Description

  The resolution on Sun CRT monitors remains the same regardless of the resolution set using fbconfig.

  Workaround

  None.

• #6838786 Xorg Receives Hardware Cursor Error While Initializing With EFB

  Description

  The Xorg standard output displays a hardware cursor error during initialization. The following error message is displayed:

  efb(0): Hardware cursor initialization failed

  Workaround

  None. Xorg and GNOME are not noticeably affected by this error.

• #6840893 Some Resolution Settings Produce an Incorrect Narrow Display Width on the LCD Monitor on EFB and NFB Drivers

  Description

  The VESA_STD_800x600x75, VESA_STD_1280x1024x75, SUNW_DIG_1920x1080x60, and SUNW_DIG_1920x1200x60 resolutions cannot be set on LCD monitors. These resolutions produce an incorrect narrow width display.

  Workaround

  Use the 1280x1024x60 and 1024x768x60 resolution sizes.

• #6841967 EFB with LCD Monitor Might Cause Powercycling of the System

  Description

  LCD Monitors that have higher than 1280x1024x60 preferred resolution settings might powercycle at GDM login.

  Workaround

  The recommended approach to the installation of a sun4v system is through the use of a service processor and virtual-console, or through ttya in the case of a sun4u system. Perform the following procedure:

  1. Unplug the monitor before you begin. This enables the smooth initialization of the graphics card when the system is rebooted.
  2. Install the system.
  3. At the end of the installation setup procedure through the virtual-console or through ttya create an /etc/X11/xorg.conf by setting the resolution:

     # fbconfig -dev efb0 -res VESA_STD_1280x1024x60 now nocheck
     New configuration file, /etc/X11/xorg.conf
     Video mode has been set to "VESA_STD_1280x1024x60"

  4. Reconnect the monitor.
  5. Type the following command on the virtual-console or ttya:

     # eeprom input-device=keyboard output-device=screen;

  6. Reboot the system.

• #6842468 EFB Console Is All Black on the Sun Ultra 45 Workstation

  Description

  The screen is black on a Sun Ultra 45 workstation until the GDM login page is displayed.

  Workaround

  Telnet to ttya for installation and setup because you might be unable to install locally .

Localization Bugs

This section describes localization issues that apply to the OpenSolaris 2009.06 OS.

• # 8880 Input Method Preference Editor Help Fails to Load

  Description

  iiim-properties(1) help fails to load with the XML parser error in some locales.

  Workaround

  1. Install SUNWgnome-xml from pkg.opensolaris.org.

     $ pfexec pkg install SUNWgnome-xml

  2. Manually execute the following script.

     $ pfexec /usr/share/sgml/docbook/docbook-catalog-install.sh

End-of-Software Support Statements

The following features might not be supported in a future release of the OpenSolaris software.

• xorgcfg and xorgconfig Utilities

  The xorg(1) server does not require an xorg.conf(4) file in many cases, and will autoconfigure itself if one is not present. If the default configuration does not meet your needs, you may use one of these alternative methods to generate an xorg.conf file for customization:
  • /usr/X11/bin/Xorg -configure, when the server is not already running will provide a sample configuration file for the currently detected hardware in the system.
  • When Xorg is started without a configuration file, the xorg.conf data it generates automatically is logged in /var/log/Xorg.0.log and may be copied to an xorg.conf file for customization.
  • Users of NVidia graphics devices may use the provided nvidia-settings(1) and nvidia-xconfig(1) utilities to generate or update device-specific configurations.
  • Users of Sun graphics devices for the SPARC platform may use the fbconfig(1) utility to generate or update device-specific configurations.

Additional Installation Troubleshooting Information

This section provides troubleshooting resources for the OpenSolaris 2009.06 OS.

• For general troubleshooting information, see the Getting Started Guide.
• For troubleshooting while installing the OpenSolaris release on your system, see Tips on Troubleshooting an OpenSolaris Startup and Troubleshooting Login and User Account Issues.
• For troubleshooting while installing the OpenSolaris release on multiple client systems, see Troubleshooting and FAQs for the Automated Installer.
• For troubleshooting while creating custom OpenSolaris images, see Troubleshooting for the Distribution Constructor.