Chapter 1 Solaris Express Issues and Bugs

This chapter describes installation and runtime issues and bugs that are known to be problems in the current release. All of the following issues and bugs apply to the Solaris Operating System. Issues include information that you should know about, including prerequisites, tips, troubleshooting hints, and bugs. Bugs are a subset of issues, which have tracking numbers that are shown in parentheses. For updates on bugs published in these release notes, go to the SunSolve^SM web site. For the complete list of issues that apply to the Solaris 10 OS, see the Solaris 10 Release Notes at http://docs.sun.com.

This document includes descriptions of specific issues that you might encounter when performing upgrades. In general, problems might potentially occur if you use upgrade methods with Solaris Express releases. These problems might require you to perform an initial installation and reconfiguration of your system.

Solaris Express 12/06 Issues

The following issues apply to the Solaris Express 12/06 release.

Access to Removable Media (6488396)

Integration of HAL into Solaris causes removable media to be automatically mounted to the /media directory. Thus the functionality described in gnome-volcheck(1) and rmmount.conf(4) man pages is not available. Previously, removable media were mounted to the /vol/dev/aliases directory by vold. No error message is displayed.

Workaround: Users can access any removable media in the /media location on the filesystem.

Solaris Express 11/06 Issues

The following issues apply to the Solaris Express 11/06 release.

Using patchadd With the -R Option To Specify an Alternative Root Path From Systems That Are Not Zones Aware Should Be Restricted (6464969)

On systems running a Solaris release that is not zones aware, using patchadd -R, or any command that accepts the -R option to specify an alternate root path for a global zone that has non-global zones installed, will not work.

In contrast with the error message that is displayed by using the luupgrade [-t, -T, -p, -P] command, no error message regarding the use of appropriate command-level restrictions is displayed in this instance.

There is no indication that the -R option did not work. As a result of the failure of the command, Solaris Express packages or patches are not installed on any of the installed non-global zones.

This problem occurs while installing and uninstalling packages or patches.

The -R option works if the alternate boot environment has configured non-global zones, but no installed non-global zones. However, to avoid a potential problem, or if you are not sure whether there are any installed non-global zones used as the alternate root path, restrict the use of the -R option in all instances.

For more information, see the following man pages :

• patchadd(1M)

• patchrm(1M)

• pkgadd(1M)

• pkgrm(1M)

Workaround 1: Upgrade the OS to at least the Solaris Express 12/05 release.

Workaround 2: Restrict the use of the patchadd -R command or any command that accepts the -R option to create an alternate root path.

Instead, boot the alternate root, for example, the Solaris Express release, as the active OS.

Buffer Recycling Causes Long ARC Mutex Spins (6478928)

Significant performance regressions have been seen in ZFS SpecSFS runs. These performance regression issues are caused by the ZFS cache (ARC) holding a lock for an excessive length of time while trying to recycle buffers. No error message is displayed.

Workaround: None.

Panic Caused by Bad Trap ire_round_robin() (6478246)

When multiple default routes are managed by a dynamic routing scheme, as in.routed, the system may panic with the following stack:

000002a1004063b1 ire_round_robin+0x9c(60001ac1778, 0, 2a100406d50,
deadbeefdeadbeef, 0, 60001ac1780)
000002a100406481 ire_ftable_lookup+0x2b8(819911c1, 60001bd3bf0, 0, a, 0,
2a100406f88)
000002a1004065c1 ip_newroute+0x350(302882bde48, 60002535320, 0, 0, 0,
600177fcf90)
000002a1004067a1 ip_output+0x1d84(302527cd400, 600177fcf90, 1, 301596d6c80, 0,
302527cd400)
000002a100406891 tcp_rput_data+0x39e8(40000, 2018, 2018, 70461800, 302527cd880,
5c00)
000002a100406a81 squeue_enter_chain+0x1d0(600004b1d00, 30129545580, 302527cd400
, 2561caae75d0, 1, 1)
000002a100406b31 ip_input+0xa50(60000822728, 0, 0, 8192e41f, 7bb3cc00,
30129545580)
000002a100406c41 putnext+0x3ec(60000c577e8, 60000c57540, 60000c57730,
30129545580, 2a1004074f0, 0)
 :
 :

The following error message is displayed:

BAD TRAP: type=31 rp=2a100406b10 addr=deadbeefdeadbf34 mmu_fsr=0

Workaround: In feasible environments, manage the default routes through routing schemes as /etc/defaultrouter.

Solaris Express 10/06 Issues

The following issues apply to the Solaris Express 10/06 release.

DR: cfgadm -c Configuration of Slot on Starcat Fails (6452077)

Configuring an hba/nic with 64-bit BAR fails to map in the device register. The hot-plugged operation is aborted. The following error message is displayed:

interpreter[6879]: usr/lib/efcode/sparcv9/interpreter: 
FC_RUN_PRIV: Priv violation: map-in ( 2000 3000810 0 0 )
Jul 24 10:11:47 csst-15k-n interpreter[6879]: ABORT: pci:map-in: failed
Jul 24 10:11:47 csst-15k-n efdaemon[186]: Wait pid: 6878 status: 100

Workaround: None.

SPARC: Installing a Solaris Flash Archive Causes Sun4v System to Hang (6411690)

If you use the flarcreate command to create a Solaris Flash archive and use the default pax copy option, the installation of the archive fails on a Sun4v system. The archive failure occurs during the retrieval of the archive. This failure affects the T1000 model only.

The following error message is displayed.

Extracted  710.00 MB ( 33% of 2142.61 MB archive)
Extracted  711.00 MB ( 33% of 2142.61 MB archive)
Extracted  712.00 MB ( 33% of 2142.61 MB archive)
Extracted  713.00 MB ( 33% of 2142.61 MB archive)
Extracted  714.00 MB ( 33% of 2142.61 MB archive)
Extracted  715.00 MB ( 33% of 2142.61 MB archive)
Extracted  716.00 MB ( 33% of 2142.61 MB archive)
         (This hangs and will never complete)

Workaround: Create the archive by using the -L cpio option. See the following example:

# flarcreate -n test.flar.sun4v.cpio -L cpio -c
 /net/server/export1/rw/test.flar.sun4v.cpio

Keyboard Configuration in JumpStart Must Be Valid

A new sysidkdb tool is introduced in the Solaris Express 10/06 release, which configures the USB keyboard layout during installation. This new tool defines valid keyboard layout strings. Unknown is not a valid string. Therefore, during the JumpStart installation on SPARC systems, the keyboard=Unknown in the sysidcfg script is not valid.

The following error message is displayed:

keyboard=Unknown
Unknown is not a valid keyboard layout

Workaround: Remove the line Keyboard=Unknown from your sysidcfg script. Or, replace Unknown with a valid keyboard string. For more information about the new sysidkbd tool and for information about valid keyword options, see the sysidcfg(4) man page.

For serial keyboards with SPARC systems, omit the keyboard variable in your sysidcfg scripts for SPARC systems.

If a valid keyboard string is not provided in the sysidcfg script, you are prompted for a keyboard selection during the installation.

Solaris Express 9/06 Issues

The following issues apply to the Solaris Express 9/06 release.

Sound Juicer and Nautilus-CD-Burner Cannot Be Used Without HAL (6423748)

To work properly, the Sound Juicer and Nautilus-CD-Burner must have the hardware abstraction layer (HAL) present.

When you try to run the Sound Juicer or Nautilus-CD-Burner, an error message indicates that the particular functionality is unavailable.

Workaround:

• To play an audio track, perform these steps:

  • Run the following gst-launch command by replacing the 1 with the audio track number that you want to play:

    $ gst-launch cdda://1 ! sunaudiosink

  • To play a CD device that is not the default device, you need to specify the CD device name and audio track number. Replace “/dev/rdsk/” with the device name and replace 1 with the track number that you want to play. Then run the following gst-launch command:

    $ gst-launch cdiocddasrc device=/dev/rdsk/c1t0d0p0 track=1 ! sunaudiosink

• To write a CD:

  Use the cdrecord command. For more information about this command, see the cdrecord man page.

• To copy an audio track from a CD and save it as a file:

  Run the following gst-launch command by replacing the 1 with the audio track number that you want to play:

  gst-launch cdiocddasrc track=1 ! (decoder plugin for format desired) ! filesink location=filename

Solaris Express 8/06 Issues

The following issues apply to the Solaris Express 8/06 release.

Many GNOME Packages Fail to Install for Diskless Clients (6448317)

Because of incorrect postinstallation scripts, installing many GNOME packages for diskless clients fails.

Several error messages are displayed. The following is an example:

/export/root/clone/Solaris_11/sun4u/var/sadm/pkg/
SUNWgnome-base-libs-root/install/postinstall: 
/export/root/clone/Solaris_11/sun4u/usr/lib/postrun: not found
pkgadd: 
ERROR: postinstall script did not complete successfully

Workaround: None.

GNOME Panel Exits on Login (6452649)

After logging in to the Solaris OS, the following error dialog appears:

I've detected panel already running and will now exit

The error dialog prompts you to click OK. If OK is clicked, the dialog exits along with the bottom GNOME panel. The error dialog reappears after a while even though the GNOME panel is no longer displayed. The error dialog might reappear a few times. This behavior is seen mostly on dual-head systems.

Workaround: None.

Show Desktop, Window List, and Workspace Switcher Fail to Load on Login (6453340)

After logging in to the window system, the GNOME configuration appears to fail. This condition recurs.

The following error dialogs are displayed:

Show Desktop has quit unexpectedly, Don't Reload, Load
Window List has quit unexpectedly, Don't Reload, Load
Workspace Switcher has quit unexpectedly, Don't Reload, Load

If the window system is reloaded, it reboots under power management and the error dialogs reappear.

Workaround: None.

Solaris Express 7/06 Issues

The following issues apply to the Solaris Express 7/06 release.

Solaris Trusted Extensions Installation Issue (6440673)

Solaris Trusted Extensions do not get enabled correctly after installation. Additional steps must be performed before rebooting or the system will hang.

On x86 based systems, the Xorg X Window server does not work once the Solaris Trusted Extensions software has been installed. The Xsun X server must be enabled in order to use a window system.

The following error message is displayed:

NOTICE: template type for hme0 incorrectly configured. 
Change to CIPSO type for 192.029.075.008
NOTICE: hme0 failed: 
Cannot insert CIPSO template for local addr 192.029.075.008
ip_arp_done: init failed
Failed to configure IPv4 interface(s): hme0
Jun 19 11:44:51 svc.startd[7]: svc:/network/physical:default: 
Method "/lib/svc/method/net-physical" failed with exit status 96.
Jun 19 11:44:51 svc.startd[7]: network/physical:default misconfigured: 
transitioned to maintenance (see 'svcs -xv' for details) 

Workaround: Perform the following steps:

1. Become superuser.

2. Install the Solaris OS.

3. Reboot the system.

4. Install Solaris Trusted Extensions.

5. Run the following commands:

   # /usr/sbin/svccfg import /var/svc/manifest/network/tnctl.xml # /usr/sbin/svccfg import /var/svc/manifest/network/tnd.xml # /usr/sbin/svccfg import /var/svc/manifest/system/labeld.xml # /usr/sbin/svcadm mark -It maintenance tnctl # /usr/sbin/svcadm enable tnctl

6. Add the following line for your host in the /etc/security/tsol/tnrhdb file:

   <host IP address>:cipso

7. If the system architecture is x86, run the following command:

   # /usr/sbin/svccfg -s svc:/application/x11/x11-server \ 'setprop options/server = /usr/openwin/bin/Xsun'

8. Reboot the system.

9. Configure the Solaris Trusted Extensions software.

Issue Managing Solaris Trusted Extensions With SMC (6442319)

When running the SMC server in the “local connection mode” in Solaris Trusted Extensions, the hostname authentication sometimes fails. This failure occurs when the Solaris Trusted Extensions files scope toolbox is chosen from the top level toolbox.

The following error message is displayed:

Authentication failed

Workaround: Choose the Solaris Trusted Extensions files scope toolbox from the toolbox chooser window.

x86: Solaris Trusted Extensions Must Use Xsun X Server

In this release, Solaris Trusted Extensions on x86 based systems supports only the Xsun X server, not the Xorg X Window server.

Workaround: Install Solaris Trusted Extensions and before rebooting, run the following command:

# /usr/sbin/svccfg -s svc:/application/x11/x11-server \
'setprop options/server = /usr/openwin/bin/Xsun'

Installation Results Changed

Because of the new security features, the results of an installation are substantially different in this release. All network services, except ssh, are disabled or restricted to respond to local requests only.

For information about enabling services, see Network Services Startup in What’s New in Solaris Express

Solaris Express 6/06 Issues

The following issues apply to the Solaris Express 6/06 release.

Solaris Volume Manager Not Starting on Systems That Revert to Solaris OS Previous to Solaris Express 4/06 Release

You encounter problems with starting the Solaris Volume Manager if you perform the following procedures on your system:

1. Upgrade to the Solaris Express 4/06 OS or a subsequent release that contains the new Solaris Volume Manager support for descriptive names.

2. Create volumes and hot-spare pools, which Solaris Volume Manager automatically configures with descriptive names.

3. Without removing these components, revert to a Solaris OS previous to the Solaris Express 4/06 release currently in the system.

The Solaris Volume Manager in the previous Solaris OS does not recognize the components with descriptive names. Consequently, in the reverted Solaris release, the Solaris Volume Manager does not start. The following error message is displayed:

svc:/system/mdmonitor:default: Method "/lib/svc/method/svc-mdmonitor" 
failed with exit status 1.
   system/mdmonitor:default failed

The system also panics and displays a message similar to the following:

Cannot open mirrored root device, error 19
Cannot remount root on /pseudo/md@0:0,10,blk fstype ufs

panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root

000000000180b950 genunix:vfs_mountroot+344 (18831f0, 2021, 18831f0, 18621a8, 
18362c0, 185d760)
  %l0-3: 00000000018362c0 000000000185d400 000000000183b400 00000000011e6400
  %l4-7: 0000000000000001 0000000000008025 000000000185d518 00000000018831f0
000000000180ba10 genunix:main+98 (18141a0, 1013400, 18362c0, 18aa000, 
180e000, 1814000)
  %l0-3: 0000000070002000 0000000000000001 000000000180c000 000000000180e000
  %l4-7: 0000000000000001 0000000001074400 0000000000000060 0000000000000000

Workaround: All Solaris Volume Manager components that you created subsequent to the OS upgrade use descriptive names. Remove these components first before performing the OS reversion. Follow these steps:

1. Become superuser.

2. With the metastat -D command, list the metadevices and hot-spare pools that use descriptive names.

   You must issue the command separately for local and named metasets to acquire a complete list of these components. For further details about the metastat command, see the metastat(1M) man page.

   1. Issue the metastat -D command for local metasets. The command generates an output similar to the following:

      # metastat -D d21: Concat/Stripe Size: 208278 blocks (101 MB) Stripe 0: Device Start Block Dbase Reloc c1t1d0s1 0 No Yes swimming: 1 hot spare Device Status Length Reloc c1t2d0s1 Available 208278 blocks Yes

   2. Issue the metastat -D command for named metasets. The command generates an output similar to the following

      # metastat -s named -D named/alley: Concat/Stripe Size: 208278 blocks (101 MB) Stripe 0: Device Start Block Dbase Reloc c1t3d0s1 0 No Yes

3. With the metaclear command, remove these components that use descriptive names. You must issue this command separately for local and named metasets.

   1. From the local set, remove the component d21 and the hot-spare pool swimming.

      # metaclear d21 d21: Concat/Stripe is cleared # metahs -d swimming c1t2d0s1 swimming: Hotspare is deleted # metahs -d swimming swimming: Hotspare pool is cleared

   2. From the named metaset, remove the component alley.

      # metaclear -s named alley named/alley: Concat/Stripe is cleared

4. Proceed with reverting to the previous Solaris OS.

SMC Server Fails to Start (6430207)

In Build 40, the SMC server fails to start. The following error message is displayed:

Registration setup: 8/8 (Executing SUNWpmgr_reg.sh)
Registering components: 64/64 (Registering PatchMgrCli.jar)
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0xec2e2624, pid=1583, tid=1
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0_06-b05 mixed mode)
# Problematic frame:
# C  [libtsol.so.2+0x2624]  bsltos+0x10
#
# An error report file with more information is saved as hs_err_pid1583.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp

The error message is displayed only if the console is open.

Workaround: None.

smosservice add Command Does Not Install Designated ARCH=all Packages (4871256)

The smosservice add command does not install any packages that are designated ARCH=all in the root (/) or /usr file systems. No error message indicating that these packages were skipped is displayed. This behavior has existed since the Solaris 2.1 OS. The behavior applies to both SPARC based and x86 based clients.

Note that the list of missing packages varies, depending on the Solaris release that you are running.

Workaround:

Locate and install the missing ARCH=all packages.

For step-by-step instructions about locating and installing missing packages, see How to Locate and Install Missing ARCH=all Packages in System Administration Guide: Basic Administration.

Solaris Express 5/06 Issues

The following issues apply to the Solaris Express 5/06 release.

Solaris ZFS Administration Application Not Visible in Sun Java Web Console (6410632)

After logging in to the Sun Java^TM Web Console, the Solaris ZFS Administration application is not visible in the list of console applications.

Workaround: None.

Upgrade Fails When Upgrading to the Build 37 Release (6409425)

If you are upgrading the Solaris OS to the build 37 release, the upgrade fails. This failure occurs when you upgrade with any of the Solaris installation programs, including upgrading a new boot environment with Solaris Live Upgrade. The error occurs because of a problem in the libspmisvc.so.1 library.

The following error message is displayed:

ERROR: Installation of the packages from this media of the media
   failed; pfinstall returned these diagnostics:

   Processing default locales
   - Specifying default locale (en_US.ISO8859-1)

   Processing profile
   Loading local environment and services
   Generating upgrade actions
   - Selecting locale (en_US.ISO8859-1)
   Space check complete.
   Building upgrade script
   Preparing system for Solaris upgrade

   ERROR: The upgrade script terminated abnormally
   sh: /sbin/install-finish: not found

Workaround:

To eliminate this problem, replace the build 37 libspmisvc.so.1 library with the build 36 library. You can find the libspmisvc.so.1 library in the following media directory:

<DVD/CD-Image>/Solaris_11/Tools/Boot/usr/snadm/lib/libspmisvc.so.1

pcie_error_init Enables Memory Access for Ranges 0x00000000-0x???????? (6401605)

On certain systems with faulty or empty PCIe bridge hardware, the Solaris OS fails to install. These “broken” bridges implement an invalid I/O space, which when accessed causes the system to hang.

Workaround: Perform the following steps:

1. Boot using the -kvd option.

2. At the debugger prompt, type:

   ::bp -d -n 1 attach_drivers :c npe`pcie_error_disable_flag/W 1 :c

Once the Solaris OS is installed, you can avoid using the workaround by adding the following variable to the /etc/system file:

set npe:pcie_error_disable_flag=1

bge Gets the checksum Wrong on IPv6 (6400907)

Starting with build 36, this error occurs if you are using IPv6 enabled on the bge with any of the following chipsets:

• BCM5700

• BCM5701

• BCM5702

• BCM5703

• BCM5704 Ax

• BCM5705

• BCM5782

To find information about the broadcom chip you are using, use the following command:

ls /etc/hostname.bge*

The following systems with the bge network interface might not be able to be contacted through IPv6:

• Sun Blade^TM 1500/2500

• Sun Fire^TM V20z/V40z/V250/V210/V240/V880/B100x/B200x/T1000

• Sun Java Workstation W1100z and W2100z

• Dell Power 2550 and 6500

• IBM xSeries 440

Workaround:

Add the following variable to the /etc/system file:

set ip:dohwcksum=0

Solaris Express 4/06 Issues

The following issues apply to the Solaris Express 4/06 release.

Wrong MAC Address is Displayed When There is More Than One Ethernet Card (6316245)

When you register to a Solaris Express 4/06 OS for remote update management using the Sun Update Connection, your system information is displayed. If your system has more than one Ethernet card, the same MAC address is displayed for all the Ethernet cards. No error message is displayed.

Workaround: None.

Solaris Express 3/06 Issues

The following issues apply to the Solaris Express 3/06 release.

x86: Upgrade Option Is Not Available When Upgrading to Solaris Express 3/06 OS (6386504 )

The upgrade operation fails when upgrading the OS to the Solaris Express 3/06 OS as follows:

• For the Solaris installation program, the upgrade option is unavailable.

• For the custom JumpStart^TM program, the upgrade fails.

This problem is due to an unused boot partition that must deleted. The problem occurs under the following circumstances:

• You have performed an initial installation from the Solaris 8, 9, or 10 3/05 release. An x86 boot partition was created during installation.

• You have performed an initial installation from the Solaris 10 1/06 release or Solaris Express release that supports GRUB. The x86 boot partition is preserved, but is not used.

• You try to upgrade to the Solaris Express 3/06 OS.

The following error will be in/tmp/install_log:

# more /tmp/install_log
kdmconfig:  The following warning was noted:
Error while executing loadkeys command.
Checking c1d0s0 for an upgradeable Solaris image.
The x86 Boot fdisk partition is missing /a/boot/solaris/bootenv.rc

Workaround:

• If you are upgrading with the Solaris installation program, delete the unused boot partition using the format or fdisk command. Repartition before you upgrade.

• If you are upgrading with JumpStart, specify the disk that contains the root (/) file system to be upgraded with the root_device keyword. For example, the profile would contain the following keywords.

  • install_type upgrade

  • root_device c1t0d0s0

Some Keyboard Layout Names in kdmconfig Have Changed (6372842)

Some of the keyboard layout names used by kdmconfig have changed. If one of these changed names is selected, the keyboard layout does not correctly set. The following error message is displayed:

From kdmconfig:
keyboard-layout-name> unknown layout name
Please refer to 'kbd -s' to get the supported layouts.
Error while executing loadkeys command.
Press Return to continue

The error occurs with the following keyboard layouts listed by kdmconfig:

• Czech

• French-Canadian

• Greek

• Hungarian

• Latvian

• Lithuanian

• Polish

• Russian

Workaround: After running kdmconfig and selecting one of the affected layouts, perform the following steps:

1. Log in as superuser.

2. Issue the command # kbd -s.

   The kbd -s command displays valid keyboard layouts.

3. Select the desired layout.

Solaris Express 2/06 Issues

The following issues apply to the Solaris Express 2/06 release.

Physical Distribution of Solaris Software is Now Only on DVD

Starting with the Solaris 10 1/06 release, Solaris software is only available on DVD media.

Solaris software was first distributed on DVD with the Solaris 8 release. Since then, DVDs have become the most preferred and visible distribution media. With the Solaris 10 3/05 release, a set of convenience CDs was still being provided. However, customers were also notified that the media kit would no longer include physical CDs.

Customers who still require CDs can download CD images from the Sun Download Center. In the future, the Sun Download Center might only offer Solaris software on DVD. At that time, distributions of Solaris Express will also be exclusively on DVD.

Solaris Express 1/06 Issues

The following issues apply to the Solaris Express 1/06 release.

x86: Graphics of Sun Java Desktop System Might Become Corrupted After Installation (6358446)

The graphics of the Sun Java Desktop System (Java DS) might become corrupted if you install the Solaris Express 1/06 software in the following manner:

• You install the software by using the DVD media or a DVD image on the network.

• You configure the system to use the Xorg X server.

The error is observed on systems that use certain Matrox graphics cards such as the Millennium G450, AGP, DualHead card, or the Millennium G400 card.

No error messages are displayed. However, you might observe the following symptoms on all GNOME applications:

• Icons and window titles exhibit unassigned colors.

• Buttons overlap.

• The positions of icons are unstable.

Workaround: None.

ZFS Administration Application Not Immediately Available After Installation (6356098)

The SUNWzfsg package, which contains the ZFS Administration Application, is installed by default together with the Solaris Express 1/06 software. After the installation, the Sun Web Console might not be enabled at the initial system boot. Consequently, the ZFS Administration Application becomes inaccessible. When you attempt to start the application by accessing the URL https://host:6789, the connection is refused.

The error occurs when you perform a Solaris installation by using a network installation image or DVD media. If you use Solaris Express Software CDs to install, no error occurs.

Workaround: Perform the following steps:

1. Become superuser.

2. Manually start the web server.

   # /usr/sbin/smcwebserver start

During subsequent system reboots, the Sun Web Console starts automatically.

x86: Adding Driver Updates Might Cause Failure of Network Configuration (6353146)

Installation of the Solaris Express 1/06 might fail while you are adding Driver Updates (DU), which are also known as Install Time Updates (ITU). This error occurs if you are using the GUI to install the Solaris Express 1/06 software.

The following message is displayed:

Unable to run cmd: /usr/sbin/sysidput

Workaround: Use either of the following workaround.

• Workaround 1: Configure the installation to use DHCP to gather network configuration information.

• Workaround 2: Use a text-based installation method.

  • If you are performing the text-based installation in a desktop session, follow these steps.

    1. After you have finished adding ITUs, type Ctrl-c instead of typing e.

    2. Choose option 3.

  • If you specify a serial console to use during the installation, follow these steps.

    1. After you have finished adding ITUs, type Ctrl-c instead of typing e.

    2. Choose option 4.

Solaris Express 12/05 Issues

The following issues apply to the Solaris Express 12/05 release.

x86: Cannot Configure Full-Screen Magnification on Systems With One Video Card

If your Solaris 10 system has a single physical video card, you cannot configure the system for full-screen magnification. For such a configuration, you must use a separate configuration file in which you define settings for a dummy driver. First, make sure that the Xserver is not running. Then perform the following steps:

1. Log in to a command-line session.

   • If you are using the GNOME Display Manager, follow these steps:

     1. Log in to a session as superuser.

     2. At the prompt, type svcadm disable application/gdm2-login.

     3. Log in again as superuser.

   • If you are using dtlogin, follow these steps:

     1. In the dtlogin window, click Options and select Command Line Login.

     2. Log in as superuser.

2. Create a new xorg.conf file.

   # /usr/X11/bin/Xorg -configure

   The command creates the file xorg.conf.new in the root (/) directory.

3. Copy the new configuration file to the /etc/x11 directory and rename the file xorg.conf.

   # cp /xorg.conf.new /etc/X11/xorg.conf

4. Modify the configurations in the file by using the following sample configurations:

   • Add a new monitor section.

     Section "Monitor" Identifier "monitor_dummy" ModelName "dummy" HorizSync 10-200 VertRefresh 20-90 EndSection

   • Add a new device section.

     Section "Device" BoardName "dummy" Driver "dummy" Identifier "device_dummy" VendorName "dummy" videoram 10000 EndSection

     ---

     Note –

     You might need to adjust the videoram value, depending on the screen width, height, and color depth of your particular graphics card. The value in Kbytes must be large enough for the intended screen. For example, you can compute the value by using the formula width * height * bpp/8

     ---

   • Add a new screen section.

     Section "Screen" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1280x1024" EndSubSection Device "device_dummy" Identifier "screen_dummy" Monitor "monitor_dummy" EndSection

     You might need to adjust the resolution value for your particular system setup.

5. Look for the following line under the ServerLayout section:

   Screen 0 "Screen0" 0 0

6. Insert the following line below the line in the previous step:

   Screen 1 "screen_dummy" RightOf "Screen0"

   This new line defines Screen1, a second dummy screen that is notionally to the right of Screen0, the physical and primary screen.

7. Save the changes.

8. Reboot the system from the appropriate command-line session:

   • If you are using GDM, perform the following:

     1. Type svcadm enable application/gdm2-login.

     2. Reboot the system.

   • If you are using dtlogin, reboot the system and log in.

9. Start the Gnopernicus screen reader.

10. Change the Startup Mode to Magnifier.

11. Click Preferences, then select Magnifier.

12. Click Add/Modify.

13. Assign the following values for Magnifier preferences:

    • For Source: 0.1

    • For Zoomer Placement:

      • Left and Top: 0

      • Bottom and Right: maximum

14. Click Apply.

    Because of the overlaying full-screen magnification zoomer, the Gnopernicus windows become invisible. However, full-screen magnification is now available.

x86: Problems Configuring USB Mouse Device as Extension Device for Use With GNOME On-Screen Keyboard

You cannot set up a USB mouse device as an extension device with the GNOME On-Screen Keyboard (GOK). The configuration fails when you are setting up the USB mouse device while using a PS2 mouse device as the core pointer. To properly set up the USB mouse, follow these steps.

1. Log in as superuser.

2. While the USB mouse device is unplugged, type the following in a terminal window:

   # ls -l /dev/usb/hid*

3. Connect the USB mouse and type the previous command again.

4. Record the path of the USB mouse that is displayed on the screen.

5. Log in to a command-line session.

   • If you are using the GNOME Display Manager, follow these steps:

     1. Log in to a session as superuser.

     2. At the prompt, type svcadm disable application/gdm2-login.

     3. Log in again as superuser.

   • If you are using dtlogin, follow these steps:

     1. In the dtlogin window, click Options and select Command Line Login.

     2. Log in as superuser.

6. Create a new xorg.conf file.

   # /usr/X11/bin/Xorg -configure

   The command creates the file xorg.conf.new in the root (/) directory.

7. Copy the new configuration file to the /etc/x11 directory and rename the file xorg.conf.

   # cp /xorg.conf.new /etc/X11/xorg.conf

8. Modify the configurations in the file:

   • In the ServerLayout section, add an input device for Mouse1 after the line InputDevice "Mouse0" "CorePointer". See the following example:

     InputDevice "Mouse0" "CorePointer" InputDevice "Mouse1"

   • In the InputDevice section that contains the line Identifier "Mouse0", apply the following changes:

     • Change Option "Device" "/dev/mouse" to Option "Device" "/dev/kdmouse"

     • Change Option "Protocol" "auto" to Option "Protocol" "VUID"

     • Add the following new Option:

       Option "StreamsModule" "vuid3ps2"

     After you have applied the changes, the section should appear similar to the following example:

     Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "VUID" Option "Device" "/dev/kdmouse" Option "StreamsModule" "vuid3ps2" EndSection

   • Create a new InputDevice section after the preceding InputDevice section:

     Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Device" "/dev/usb/hid1" EndSection

     ---

     Note –

     /dev/usb/hid1 is an example path for the USB mouse. Use the path in Step 4 to replace /dev/usb/hid1.

     ---

9. Save the file and exit.

10. Reboot the system from the appropriate command-line session:

    • If you are using GDM, perform the following:

      1. Type svcadm enable application/gdm2-login.

      2. Reboot the system.

    • If you are using dtlogin, reboot the system.

11. Log in to the accessible UI user's account.

12. Enable Assistive Technology Support by clicking Launch Menu => Preferences => Accessibility => Assistive Technology Support.

13. Log out of the system then log in to the accessible UI user's account again.

14. Open a terminal window and type the following command:

    % /usr/sfw/bin/gok --select-action=switch1

15. In the GOK window, click GOK and select Preferences.

16. If necessary, set up GOK to the accessible UI user's needs. Otherwise, to accept the current setup, click Apply then click OK in the GOK Preferences window.

17. Exit GOK and then restart it by clicking Launch Menu => Applications => Accessibility => On-Screen Keyboard. The following warning message might be displayed:

    The device you are using to control GOK is also controlling the system pointer.

18. Click OK.

19. Exit GOK and then repeat steps 14-17.

    The warning message is no longer displayed.

File System Creation Might Fail on Small Slices (6346510)

Creating a UFS file system with the newfs command might fail under the following conditions:

• The size of the slice is small, approximately less than 4 Mbytes.

• The size of the disk exceeds 8 Gbytes.

The error is caused by the large-size requirement of the file system for metadata. The following warning message is displayed:

Warning: inode blocks/cyl group (295) >= data blocks (294) in last
     cylinder group. This implies 4712 sector(s) cannot be allocated.
/dev/rdsk/c0t0d0s6:     0 sectors in 0 cylinders of 48 tracks, 128 sectors
         0.0MB in 0 cyl groups (13 c/g, 39.00MB/g, 18624 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
#

Workaround: As superuser, perform one of the following workarounds:

• Workaround 1: Specify the number of tracks when you use the newfs command. Follow these steps.

  1. Use the format command to find out the number of tracks to assign. For example:

     # format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t0d0 SUN18G 7506 alt 2 hd 19 sec 248 /pci@1f,4000/scsi@3/sd@0,0 Specify disk (enter its number):

     In the example, the number of tracks is 19.

  2. Assign the number to the file system that you create with the newfs command. For example:

     # newfs -v -t 19 /dev/dsk/c0t0d0s6 newfs: construct a new file system /dev/rdsk/c0t0d0s6: (y/n)? y mkfs -F ufs /dev/rdsk/c0t0d0s6 4712 -1 19 8192 1024 16 10 167 2048 t 0 -1 8 128 n mkfs: bad value for nsect: -1 must be between 1 and 32768 mkfs: nsect reset to default 32 Warning: 152 sector(s) in last cylinder unallocated /dev/rdsk/c0t0d0s6: 4712 sectors in 8 cylinders of 19 tracks, 32 sectors 2.3MB in 1 cyl groups (16 c/g, 4.75MB/g, 2304 i/g) super-block backups (for fsck -F ufs -o b=#) at: 32, #

• Workaround 2: Specify the number of bytes per inode (nbpi) in the newfs command to reduce the inode density in the file system. For example:

  # newfs -i 4096 /dev/dsk/c0t0d0s6 newfs: construct a new file system /dev/rdsk/c0t0d0s6: (y/n)? y Warning: 1432 sector(s) in last cylinder unallocated /dev/rdsk/c0t0d0s6: 4712 sectors in 1 cylinders of 48 tracks, 128 sectors 2.3MB in 1 cyl groups (16 c/g, 48.00MB/g, 11648 i/g) super-block backups (for fsck -F ufs -o b=#) at: 32, #

SPARC: Problems Configuring Preferences With the GNOME On-Screen Keyboard (6329929)

Software problems affect the use of extended devices such as a second mouse device or a USB head tracker with the GNOME On-Screen Keyboard (GOK). Consequently, the user preferences Dwell Selection and Direct Selection cannot be set by using GOK. Instead, you need to set these user preferences by using a physical keyboard and mouse device.

Workaround: After you have set the system to use an extended device, perform the following procedures in sequence. First, set GOK to ensure that the core pointer is controlled by the primary mouse device. Other extended devices are then reserved for use by AT applications. Follow these steps when starting GOK for the first time:

1. Start GOK.

2. In the window where Sticky Keys have been activated, press Enter.

3. In the window that prompts you to use core pointer mode, use the arrow keys to highlight Cancel, then press Enter.

4. To set user preferences, click GOK and select Preferences.

5. Configure Dwell Selection or Direct Selection.

   • To configure Dwell Selection, follow these steps:

     1. Click the Access Methods tab.

     2. Choose Dwell Selection from the Method drop-down menu.

     3. Click the Actions tab and perform the following:

        • Choose Dwell from the Name drop-down menu.

        • Check that Activate on Dwell is selected for Behavior.

        • Check that Other input device is selected for Event Source.

     4. Click Apply.

     5. In the Actions tab, perform the following:

        • Choose Mouse Pointer from the Name drop-down menu.

        • Check that Activate on Enter is selected for Behavior.

     6. Click Apply, then click OK.

     7. Exit the GOK window.

     8. Log out and log in again.

   • To configure Direct Selection, follow these steps:

     1. Click the Access Methods tab.

     2. Choose Direct Selection from the Method drop-down menu.

     3. From the Activate drop-down menu, choose Switch1 to use mouse button 1 on the second mouse.

     4. Click Apply, then click OK.

     5. Exit the GOK window.

     6. Log out and log in again.

SPARC: Error Messages Displayed During Dynamic Reconfiguration (6312424)

During dynamic reconfiguration (DR), error messages might be displayed. The messages are displayed if you perform DR while input and output operations are active on devices that are in the DR path. After the messages are displayed, the input and output operations are retried and eventually succeed. The following is a sample that is displayed:

Jul 28 12:23:19 qame10-a scsi: [ID 107833 kern.warning] WARNING:
/ssm@0,0/pci@19,700000/SUNW,qlc@2,1/fp@0,0/ssd@w2100000c5056fa13,0 (ssd6):
Jul 28 12:23:19 qame10-a 	transport rejected fatal error
Jul 28 12:22:08 qame10-a scsi: [ID 107833 kern.warning] WARNING:
/ssm@0,0/pci@19,700000/SUNW,qlc@2,1/fp@0,0/ssd@w2100000c5056f9a7,0 (ssd36):
Jul 28 12:22:08 qame10-a 	SCSI transport failed: reason 'timeout':
retrying command

Workaround: None. Ignore the error messages.

Full-Screen Magnification and Keyboard Accessibility Features Not Working (6273030)

On your Java DS, you cannot set up the following:

• Full-screen magnification

• Keyboard accessibility features

Workaround: Perform the following steps:

1. Open the /etc/X11/gdm/gdm.conf file.

2. Depending on your system's platform, perform the following:

   • On SPARC based systems:

     1. Look for the line in the file that begins as follows:

        command=/usr/openwin/bin/Xsun

     2. Append the following modification to the line:

        +kb +accessx -dev framebuffer1 -dev framebuffer2

        For example:

        +kb +accessx -dev /dev/fbs/pfb1 -dev /dev/fbs/pfb0

   • On x86 based systems:

     1. Look for the line in the file that begins as follows:

        command=/usr/X11R6/bin/Xorg

     2. Append the following modification to the line:

        +kb +accessx

Error Messages Displayed by pkgchk After You Remove Patches for Zones (6267966)

The patchadd and patchrm commands work improperly in non-global zones with inherited file systems. Consequently, in those zones, the pkgchk command might generate error messages about packages under the following circumstances:

1. In the global zone, you apply patches for the Solaris 10 zone system by using the patchadd command.

2. You use the patchrm command to remove patches that you just recently applied.

3. In a non-global zone with inherited file systems, you check with the pkgchk command for information about a package in any of the removed patches.

The following sample message is displayed when the pkgchk command is used on SUNWcsu under the circumstances previously listed.

# pkgchk SUNWcsu
ERROR: /usr/lib/inet/certdb
   modtime <04/26/05 10:55:26 PM> expected <01/23/05 01:48:24 AM> actual
   file size <36012> expected <42152> actual
   file cksum <37098> expected <19747> actual
ERROR: /usr/lib/inet/certlocal
   modtime <04/26/05 10:55:26 PM> expected <01/23/05 01:48:24 AM> actual
   file size <44348> expected <84636> actual

Workaround: None. The errors are harmless. Ignore the error messages.

Devices Not Immediately Available in Fabric Zones in a Storage Area Network (5077933)

When a fabric zone in a storage area network (SAN) is created dynamically, that zone's devices might be unavailable at the host side. If you use the command luxadm -e dump_map to display data for such devices or host bus adapters, an error message is displayed. See the following example:

# luxadm -e dump_map /dev/cfg/c5

Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type

ERROR: Unable to retrieve target port details (QLogic Corp-2312-3)ERROR

Listing the status of all the attachment points yields information similar to the following example. In this example, the fabric devices include a tape drive, but no device is indicated in c5.

# cfgadm -al

A-_ID         Type         Receptacle   Occupant     Condition 
: 
:
c5            fc-fabric    connected    unconfigured unknown
usb0/1        unknown      empty        unconfigured ok
:
:

Workaround: After configuring the fabric-connected devices, reinitialize the link to the devices by using the luxadm -e forcelip command. For the previous example, you would type the following:

# luxadm -e forcelip /dev/cfg/c5

Solaris Express 11/05 Issues

The following issues apply to the Solaris Express 11/05 release.

SPARC: Power Management in Sun Expert3D and Sun Elite3D Hardware Not Working Under Certain Circumstances (6321362)

Sun Expert3D or Sun Elite3D cards in Sun Blade 1000 or Sun Blade 2000 workstations normally switch to low-power mode after an idle period. However, if these cards are set as the primary head in the Xserver, power management does not work. The affected cards remain at full power and no power savings are realized. No error message is displayed.

Workaround: None.

x86: GNOME Applications Fail With dtremote (6278039)

GNOME applications do not start if you log in remotely and enable accessibility in gnome-at-properties. If you attempt to start a GNOME application, the following error message is displayed:

** ERROR **: Accessibility app error: exception during 
registry activation from id: 
IDL:Bonobo/GeneralError:1.0  aborting...

Workaround: None. Do not enable accessibility when you log in by using dtremote. To revert to the default desktop settings in which accessibility is disabled, close the GNOME session. Issue the following command:

% gnome-cleanup

Solaris Express 10/05 Issues

The following issues apply to the Solaris Express 10/05 release.

x86: New Minimum Memory Requirement

Beginning with the Solaris Express 10/05 release, all x86 based systems must now have at least 256 Mbytes of RAM to run the Solaris OS.

StarOffice Patch Application Requires Additional Steps

The following patches are applied to the Solaris OS to resolve StarOffice^TM problems that were reported in CR 6234855 and CR 6262830:

• For SPARC based systems

  • Patch ID 119412-06

  • Patch ID 119906-03

• For x86 based systems:

  • Patch ID 119413-06

  • Patch ID 119907-03

To completely resolve the reported problems, perform the following steps after applying the patches. These steps enable you to use StarOffice 7 Product Update 5 software to open, for example, those OpenDocument files that were created in StarOffice 8 software.

1. Become superuser.

2. Issue the following command:

   # update-mime-database /usr/share/mime

3. Log out of the system and then log in again.

SPARC: Loadkeys Warnings Appear When System Is Booted From Solaris OS DVD (6329642)

When you boot the system from the Solaris OS DVD to install the Solaris software, the following warning is displayed:

/sbin/install-discovery: /usr/bin/loadkeys: not found

Consequently, keyboard mappings for autodetected keyboards are not automatically loaded during the boot process.

Workaround: None. Ignore the warning message. You can continue to install the Solaris software on the system even without the keyboard mappings. After you have completed the installation, these mappings are automatically set when you reboot the system.

Solaris Express 9/05 Issues

The following issues apply to the Solaris Express 9/05 release.

SPARC: Using Suspend-and-Resume Functionality Might Cause Sun Blade 2500 Systems to Hang (6317659)

The checkpoint-resume (cpr) functionality might not work on a Sun Blade^TM 2500 workstation. The system hangs while resuming operations. No error message is displayed.

Workaround: Disable the workstation's cpr feature.

1. Open the /etc/system file.

2. Add the following line:

   exclude: misc/cpr

SPARC: Sun PGX Graphics Driver Not Working on Solaris Express 9/05 Release (6293801)

On the current Solaris Express release, the m64 Xsun DDX driver of the Sun PGX64 graphics accelerator card does not work. When the system boots after OS installation, the graphics driver attaches normally. However, after the text console messages have been displayed, the screen remains dark throughout the boot process and thereafter.

Workaround: Use a different graphics card.

x86: Default DMA Setting for CD and DVD Devices Might Cause Problems for Certain Systems (6227829)

In the current Solaris release, Direct Memory Access (DMA) for CD and DVD devices is enabled by default. On some older x86 hardware, drives and controllers might not function properly if DMA is enabled. Different systems might generate different error messages. A typical error message is similar to the following example:

WARNING: /pci@0,0/pci-ide@f,1/ide@0 (ata0)
timeout: abort request, target=0 lun=0
WARNING: /pci@0,0/pci-ide@f,1/ide@0 (ata0)
timeout: abort request, target=0 lun=0
WARNING: /pci@0,0/pci-ide@f,1/ide@0 (ata0)
timeout: abort request, target=0 lun=0
WARNING: /pci@0,0/pci-ide@f,1/ide@0 (ata0)
timeout: reset bus, target=0 lun=0

Note, however, that such messages are generic and might also apply to failures that are not related to the default DMA setting.

Workaround: Disable DMA for CD or DVD devices by using the eeprom system command. Perform the following steps.

1. Become superuser.

2. Issue the following command:

   # eeprom atapi-cd-dma-enabled=0

3. Reboot the system.

When you perform subsequent system boots, the DMA remains disabled until you enable the setting again.

If you are booting the system by using an optical device, do not use the eeprom command. Instead, edit the kernel command line by using the GRand Unifier Bootloader (GRUB) menu. Follow these steps.

1. Configure your system to boot from a DVD or CD.

2. Insert the appropriate media in your system.

3. Boot the system.

   After the memory test and hardware detection are completed, the GRUB menu is displayed.

4. Using the arrow keys, select the appropriate installation option and press e.

   A list of boot commands is displayed.

5. Select the boot command that begins with kernel and press e.

   The kernel command is displayed on the screen in edit mode, similar to the following example:

   grub edit>kernel /boot/multiboot kernel/unix -B install_media=cdrom

6. Using the arrow keys, navigate to the end of the command line and add the following argument:

   atapi-cd-dma-enabled=0

   The edited kernel command should be similar to the following example:

   grub edit>kernel /boot/multiboot kernel/unix -B install_media=cdrom atapi-cd-dma-enabled=0

7. After adding the argument, press Enter.

   The modified kernel command is displayed in the GRUB menu.

8. To boot the system, press b.

For more information about boot arguments you can use with command lines, see Chapter 8, Installing From the Network (Command Reference), in Solaris Express Installation Guide: Network-Based Installations. See also Chapter 11, GRUB Based Booting (Tasks), in System Administration Guide: Basic Administration.

Solaris Express 7/05 Issues

The following issues apply to the Solaris Express 7/05 release.

Upgrading From Solaris Express 6/05 Release to Current Release Requires Remounting of File Systems (6244945)

Directories might erroneously appear to be empty after you upgrade an NFSv4 server from the Solaris Express 6/05 release to the current release. Furthermore, your applications might encounter EACCESS errors.

Workaround: To prevent these errors, perform one of the following options.

• Unmount and then remount the client file system after upgrading. If unmounting fails, you might need to forcibly unmount the file system by using umount -f. For file systems that are mounted automatically, you can remount the client file system with the command automount -u.

• Reboot the client.

Remounting the file systems is not required if you directly upgraded to the current Solaris Express release, starting with Solaris Express 7/05, from either of the following releases:

• Solaris Express 4/05 or previous Solaris Express releases

• Solaris 10 OS

Solaris Express 6/05 Issues

The following issues apply to the Solaris Express 6/05 release.

Cannot Use Solaris Live Upgrade to Upgrade to Solaris Express 6/05

You cannot use Solaris Live Upgrade to upgrade your system to the Solaris Express 6/05 release. To upgrade your system to the Solaris Express 6/05 release, use the Solaris installation GUI or text installer or the Custom JumpStart program.

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.

Solaris Express 4/05 Issues

The following issues apply to the Solaris Express 4/05 release.

Bugs Fixed and Integrated

This table lists issues and bugs that have been fixed since the release of Solaris 10 Operating System.