Solaris Express Developer Edition Release Notes
Previous Next

Document Information

Preface

1.  Solaris Express Developer Edition Issues and Bugs

Solaris Express Developer Edition 1/08 Issues

Solaris Express Developer Edition 9/07 Issues

Solaris Express Developer Edition 5/07 Issues

Solaris Express Developer Edition 2/07 Issues

Solaris Express 11/06 Issues

Solaris Express 10/06 Issues

Solaris Express 7/06 Issues

Solaris Express 6/06 Issues

Solaris Express 4/06 Issues

Solaris Express 3/06 Issues

Solaris Express 1/06 Issues

Solaris Express 12/05 Issues

Solaris Express 11/05 Issues

Solaris Express 6/05 Issues

Bugs Fixed and Integrated

2.  End-of-Software-Support Statements

Solaris Express Developer Edition 1/08 Issues

The following issues apply to the Developer 1/08 release.

x86: Solaris Installation Might Fail When Whole Disk Option Is Selected (6652417)

Installation of the Developer 1/08 release might fail when the whole disk option is selected. This failure occurs due to an fdisk error. The following error message is displayed:

ERROR: At least one 30 Mbyte Solaris fdisk partition is required on a selected drive
ERROR: System installation failed

Workaround: Perform the following steps:

  1. Restart the installation of the OS. Reboot the system or type install-solaris on the command line.

  2. Choose the default disk option or partition the disk option on the disk screen.

Installation of the Developer 1/08 OS Fails on Acer FR 5000/1000 (6643143)

Installation of the Developer 1/08 OS fails on Acer FR 5000/1000 machines. The following error message is displayed:

configuring /dev
ata_id_common: BUSY status 0x80 error 0x80
ata_id_common: BUSY status 0xfe error 0x0
ata_id_common: BUSY status 0x80 error 0x80
ata_id_common: BUSY status 0xfe error 0x0
atapi_start_cmd: drive select failed
WARNING: /pci@0,0/pci-ide@14,1/ide@0 (ata2):
timeout: early timeout, target=0 lun=0
atapi_start_cmd: drive select failed
WARNING: /pci@0,0/pci-ide@14,1/ide@0 (ata2):
timeout: early timeout, target=0 lun=0

Workaround: Perform the following steps:

  1. Boot your system using the -k option so that kmdb is loaded at the boot process. Use the -d boot option to request a debugger breakpoint prior to starting the kernel.

    ok boot -kd

  2. Set a breakpoint at the [0]>kmdb debugger prompt:

    ::bp ata`ata_init_controller+0x165

  3. Once the breakpoint is hit, print the general-purpose register $r and verify that the $eax, or the $ebx, contains a valid ata_ctl_t structure:

    <address>::print -a ata_ctl_t

  4. Take the address of the ac_timing_flags and set the value from 0x0 to 1:

    <address>/W 1

    You might hit the breakpoint more than once, but it is sufficient if you set the ac_timing_flags value once.

  5. Resume upgrading your OS.

For more information on these commands, see the Solaris Modular Debugger Guide.

x86: Xorg Does Not Use the RadeonHD Driver Without the xorg.conf File (6642276)

The Developer 1/08 release includes a video driver for ATI Radeon X1000 and ATI Radeon HD2000 series graphics cards and chipsets. Xorg will not detect and use the new driver unless it is specified in the xorg.conf configuration file. Xorg attempts to use the VESA driver instead, which might not work on all Radeon graphics devices. No error message is displayed.

Workaround: Type the /usr/X11/bin/Xorg -configure command to generate a /etc/X11/xorg.conf file after installation. Verify that the xorg.conf configuration file specifies the RadeonHD driver.

Empty negative_sign in en_US Locale (6618050)

The locale data for existing European and Middle East and African (EMEA), Central and South American, and Oceania locales are migrated to Common Locale Data Repository (CLDR) to achieve maximum compatibility across platforms. Existing applications might see different formats for locale sensitive data when you upgrade from Solaris 10 to the Solaris Express release.

Workaround: Customize the Solaris locales. For instructions on how to customize Solaris locales, see the tech tips at http://developers.sun.com/dev/gadc/techtips/locale_customization.html.

PRODRM Has Problems Deleting prodreg Entry For Solaris Trusted Extensions (6616592)

While upgrading Solaris Trusted Extensions from the Solaris 10 11/06 or Solaris 10 8/07 release to the current Developer 1/08 release, the prodreg entry for Solaris Trusted extensions will not be removed. No error message is displayed.

Workaround: After upgrading Solaris Trusted Extensions to the current release, remove the prodreg entry manually as follows:

# prodreg unregister -f -r -u "Solaris Trusted Extensions" -i 1

Solaris Trusted Extensions Upgrade Issues (6616585)

While upgrading Solaris Trusted Extensions from the Solaris 10 11/06 or Solaris 10 8/07 release to the current Developer 1/08 release, unwanted localized Solaris Trusted Extensions packages are installed on your system. This bug occurs because the Solaris Trusted Extensions installer in the Solaris 10 11/06 or Solaris 10 8/07 releases installs localized packages by default. No error message is displayed.

Workaround: Before upgrading Solaris Trusted Extensions to the current release, remove the following localized Solaris Trusted Extensions packages:

SUNWjdtts

SUNWkdtts

SUNWjmgts

SUNWkmgts

SUNWjtsman

SUNWktsu

SUNWjtsu

SUNWodtts

SUNWtgnome-l10n-doc-ja

SUNWtgnome-l10n-ui-ko

SUNWtgnome-l10n-ui-it

SUNWtgnome-l10n-ui-zhHK

SUNWtgnome-l10n-ui-sv

SUNWtgnome-l10n-ui-es

SUNWtgnome-l10n-doc-ko

SUNWtgnome-l10n-ui-ptBR

SUNWtgnome-l10n-ui-ja

SUNWtgnome-l10n-ui-zhTW

SUNWtgnome-l10n-ui-zhCN

SUNWtgnome-l10n-ui-fr

SUNWtgnome-l10n-ui-de

SUNWtgnome-l10n-ui-ru

Remote Multilevel Login From the Login Screen Is Not Supported in Solaris Trusted Extensions (6616030)

The Remote Login item on the Options menu on the login screen cannot be used to remotely log in to a multilevel Solaris Trusted Extensions system. When the label of your system is the same as the label that has been assigned to an unlabeled system, you can log in remotely to that unlabeled system.

Workaround: To log in remotely, see the instructions in Chapter 14, Remote Administration in Trusted Extensions (Tasks), in Solaris Trusted Extensions Administrator’s Procedures.

gDesklets Fails to Start (6608943)

When you log in to the system as a new user, gDesklets fails to start. The following error message is displayed:

bash-3.00$ gdesklets shell

You're running gDesklets for the first time.
gDesklets will start a requirements check now...

Checking requirements:
 - sys ... found
 - xml.parsers.expat ... found
 - xml.sax ... found
 - gtk ... found
 - ORBit ... found
 - bonobo.ui ... missing
Version check failed.

bonobo python bindings are required.

Workaround: Perform the following steps:

  1. Change to your home directory:

    cd <home_directory>

  2. Type the following command:

    mkdir .gdesklets

Reboot Now Button Is Unresponsive (6270371)

After installation of the Solaris OS, the Reboot Now button does not work.

Workaround: Perform the following steps:

  1. Open a terminal window.

  2. Type the following commands:

    # touch /tmp/.instsuccess
# pkill -9 java

The system reboots and does not require CDs.

SPARC: NFS/RDMA Connection Errors (6229077)

There might be connection errors between an NFS server and client while using Remote Direct Memory Access (RDMA). Because of these errors the buffer pool resources are exhausted and the system panics. The following error message is displayed:

rpcib: WARNING: rib_rbuf_alloc: No free buffers!

Workaround: Choose one of the following workarounds:

  • Configure the NFS server to enable TCP. In the /etc/default/nfs file, change (NFSD_PROTOCOL=tcp).

  • Mount the NFS file system from the client side with the proto=tcp mount option.

For more information, see the mount_nfs(1M) and nfs(4) man pages.

NetBeans Dynamic Tracing GUI Plug-in

The NetBeansTM Dynamic Tracing (DTrace) GUI plug-in is installed during the installation of the NetBeans 6.0 and Sun Studio software. The plug-in should be configured manually before using it.

Workaround: To use the DTrace GUI plug-in, copy the DTrace scripts from the /opt/dtrace-gui to your home directory:

cp -r /opt/dtrace-gui/DTraceScripts $HOME/
chmod -R 755 $HOME/DTraceScripts

The installation of the Dtrace GUI plug-in is now complete.

For more information about this plug-in, see the /opt/dtrace-gui/doc/NetBeans_DTrace_GUI_Plugin.html file. This file describes how to set privileges in the /etc/user_attr file, and how to start the Dtrace GUI. Ensure that you start NetBeans or Sun Studio IDE from a different shell than the shell you use to set privileges.

Build Number Mismatch Between uname -a Output and /etc/release Contents

The uname -a command displays the build number of the kernel as Build 79a. However, the contents of /etc/release is Build 79b which is the build number of the final assembly of the Developer 1/08 OS.

Workaround: None.

x86: Solaris JumpStart Fails

Solaris JumpStartTM goes to interactive mode if the netmask value in the sysidcfg script is defined. No error message is displayed. The sysidtool starts due to missing network data.

Workaround: Do not specify the netmask value in the sysidcfg script.

GTK+ Issues With JDK

The Sun Studio IDE might have display problems while loading GTK look and feel libraries. These problems are due to a JDKTM 6 Update 3 bug. Following are examples of the display problems faced:

  • Icons in the Run menu item partly hide the labels

  • The Debug toolbar is twice as big as the Build toolbar

Workaround: Use an alternate version of JDK. For example:

% sunstudio --jdkhome /usr/jdk/jdk1.5.0_13
Previous Next