Chapter 3 Solaris Runtime Issues

This chapter describes runtime issues that are known to be problems.

Some of the issues and bugs in this chapter have been fixed in subsequent Solaris 10 releases. If you have upgraded your Solaris software, certain issues and bugs in this chapter might no longer apply. To see which bugs and issues no longer apply to your specific Solaris 10 software, refer to Appendix A, Table of Integrated Bugs in the Solaris 10 Operating System.

Common Desktop Environment

The following bugs in Solaris 10 OS apply to the Common Desktop Environment (CDE).

x86: Support for Intel Integrated i810 and i815 Graphics Chipsets

Intel Integrated i810 and i815 Graphics Chipsets are not supported by the Xorg X Window System server. Support is available with the Xsun server. To configure the Xsun server to use these chipsets, follow these steps:

1. Become superuser.

2. Run the program to configure keyboard, display, and mouse.

   # kdmconfig

3. On the Introduction and X Server Selection screen, select the Xsun server.

   On the View and Edit Window System Configuration screen, Intel i810/i815 (4MB) should be automatically selected and displayed as the Video Device.

4. If the Intel i810 and i815 Chipsets are not automatically selected, select the Change Video Device/Monitor option.

5. On the Video Device Selection screen, select the Intel i810/i815 (4MB) option.

6. Continue to select other kdmconfig options.

Arabic Text Not Appearing in ar Locales

If your x86 system is using Xorg as the default Xserver, the Arabic font (iso7759-6) does not appear in the ar locale. This error does not occur if you are using XSun instead of XOrg.

Workaround: Follow these steps.

1. As superuser, edit /usr/dt/config/Xservers.

   • Uncomment or add the following line:

     :0 Local local_uid@console root /usr/openwin/bin/Xsun :0 -nobanner -defdepth 24

   • Comment out the following line:

     :0 Local local_uid@console root /usr/X11/bin/Xorg :0

2. Reboot the system.

Alternatively, you can log in to ar_EG.UTF-8 or other UTF-8 locales.

Compose Key Sequences Might Not Work When You Use X Keyboard Extension in Some Locales (6219932)

Some Compose key sequences might not work in locales that do not use keyboard input methods, such as the C locale. The error occurs if either of the following system configurations is used in those locales:

• System using Xorg X server on Solaris 10 for x86

• System using Xsun X server with X Keyboard Extension (XKB) enabled on Solaris 10 for both SPARC and x86

Specifically, Compose sequences in these systems fail if the sequence requires the use of the Shift key to type one of the characters.

Workaround: Choose one of the following options:

• Use an alternate Compose sequence that does not include the Shift key.

  For more information, see Appendix C, Compose Key Sequences, in Solaris Common Desktop Environment: User’s Guide. The appendix provides a list of available sequences, some of which have alternate sequences that do not use the Shift key.

• Log in by using a locale that uses keyboard input methods, such as any of the available UTF-8 locales.

x86: kdmconfig Command Does Not Create System Identification Configuration File for Xorg X Server (6217442)

If you use the JumpStart installation method, the process might use a system identification configuration (sysidcfg) file. This file is used to generate a specific Xsun configuration file for a system. The Xsun configuration portion of a sysidcfg file is created by the command kdmconfig -d filename. However, on systems that use the default Xorg server, the command does not create a file with any Xorg configuration information. Consequently, you cannot use the JumpStart method on these systems without some additional preparatory steps.

Workaround: Before using the JumpStart installation method on a system that uses the Xorg server, perform the following steps.

1. Prepare a specific xorg.conf file to be used on the system. Store this file in the JumpStart directory of the JumpStart server.

   For instructions to create an xorg.conf file and to access Xorg information, see x86: Program That Configures Keyboard, Display, and Mouse Not Working for X Server (6178669).

2. Create a finish script that copies the xorg.conf file to the /etc/X11 directory in the system that you want to install. For example, the script might include the following line:

   cp ${SI_CONFIG_DIR}/xorg.conf /etc/X11/Xorg.conf

3. In the custom JumpStart rules file, include the finish script in the rules entry for systems of the type that you want to install.

4. Perform the custom JumpStart installation.

For instructions about how to perform a custom JumpStart installation, see the Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations. Chapter 4 includes information about the JumpStart rules file, while Chapter 5 contains a section about finish scripts.

x86: kdmconfig Instructions to Configure Xorg X Server Are Incomplete (6205881)

Instructions that are provided in the kdmconfig program to configure the Xorg server are incomplete. The program lists basic instructions to generate an xorg.conf file. However, some relevant information is unavailable. For example, options in the xorg.conf file can be overridden in several places:

• Command-line options

• Information that is detected by the Xorg server when the server starts

• The startup scripts for the Xorg server, which might include passing overriding arguments

Thus, for more information about Xorg configuration, refer to the following sources:

• Xorg(1x) man page in the /usr/X11/man directory

• Man pages for the desktop systems that use the X server, such as the following:

  • dtlogin(1X) in the /usr/dt/man directory

  • gdm(1) in the /usr/share/man directory

If these directories are not in your man path, use one of these options:

• Add the directory to the MANPATH environment variable setting.

• Use the -M directory option of the man command.

Some scripts that start the Xorg server use smf(5) repository properties. In particular, the FMRI svc:/applications/x11/x11-server is used for storing X server properties. The following properties are relevant to the Xorg server:

• options/xserver

• options/default_depth

• options/server_args

You can set and retrieve these properties by becoming superuser and using the svccfg command, as shown in the following example:

# svccfg 
svc:> select application/x11/x11-server 
svc:/application/x11/x11-server> listprop options/default_depth 
options/default_depth integer 24


 
svc:/application/x11/x11-server> setprop options/default_depth = 8 
svc:/application/x11/x11-server> listprop options/default_depth 
options/default_depth integer 8


 
svc:/application/x11/x11-server> end
#

x86: Program That Configures Keyboard, Display, and Mouse Not Working for X Server (6178669)

In this current Solaris 10 release, the default X server has changed from Xsun to Xorg. The program that configures keyboard, display, and mouse ( kdmconfig ) applies only to the Xsun server. The program has no effect on Xorg server configuration. Consequently, you cannot use kdmconfig to configure the Xorg server. While kdmconfig allows you to select which server to use, kdmconfig only configures the Xsun server.

Workaround: To configure the Xorg server, perform the following steps:

1. Create an xorg.conf file with one of these commands:

   • /usr/X11/bin/Xorg -configure

   • /usr/X11/bin/xorgconfig

   • /usr/X11/bin/xorgcfg

2. Edit the resultant xorg.conf file with the necessary changes.

3. Move the xorg.conf file to /etc/X11/xorg.conf.

For more details about Xorg configuration, refer to the Xorg man pages in /usr/X11/man. This directory is not in the default man page path. To view these man pages, use one of the following options:

• Add the path to the settings of the environment variable MANPATH .

• Use the syntax man -M /usr/X11/man.

Xorg command line options can override xorg.conf settings. See the man pages for more details about options to use with Xorg.

SPARC: Some UTF-8 Locales Are Unavailable in the Common Desktop Environment Login Service (5042573)

The following UTF-8 locales are missing when the login server starts and the Common Desktop Environment (CDE) login service is launched:

• ar_SA.UTF-8

• el_GR.UTF-8

• nl_BE.UTF-8

• nl_NL.UTF-8

• pt_PT.UTF-8

Workaround: To use these locales, log in to any other UTF-8 locale. Then, set the LC_ALL variable at the command line. For example:

export LC_ALL=ar_SA.UTF-8

The workaround applies only to SPARC based systems. These locales are unavailable in x86 based systems.

CDE Removable Media Auto Run Capability Removed (4634260)

The Removable Media auto run capability in the CDE desktop environment has been temporarily removed from the Solaris 10 software.

Workaround: To use the auto run function for a CD-ROM or another removable media volume, you must do one of the following:

• Run the volstart program from the top level of the removable media file system.

• Follow the instructions that are included with the CD for access from outside of CDE.

Solaris PDASync Cannot Delete Last Entry From the Desktop (4260435)

After you delete the last item from the desktop, the item is restored from the handheld device to the desktop when you synchronize your handheld device. Examples of items that you might delete, and then have restored, are the last appointment in your Calendar or the last address in the Address Manager.

Workaround: Manually delete the last entry from the handheld device prior to synchronization.

Solaris PDASync Does Not Support Data Exchange With the Multibyte Internationalized PDA Device (4263814)

If you exchange multibyte data between a PDA device and Solaris CDE, the data might be corrupted in both environments.

Workaround: Back up your data on your personal computer with the PDA backup utility before you run the Solaris PDASync application. If you accidentally exchange multibyte data and corrupt that data, restore your data from the backup.

Documentation DVD

The following Documentation DVD bugs apply to the Solaris 10 release.

SUNWsdocs Package Needed to Remove Other Documentation Packages

If you remove the SUNWsdocs package, then try to remove other documentation packages, the removal fails. This problem occurs because the SUNWsdocs package is installed with any collection and provides the browser entry point.

Workaround: If you removed the SUNWsdocs package, reinstall the SUNWsdocs package from the documentation media and then remove the other documentation packages.

European Locale PDF Documents Available Only Through C Locale (4674475)

On systems that are running the current Solaris 10 release, PDF documents on the Solaris 10 Documentation DVD are not accessible in the following European locales:

• de (German)

• es (Spanish)

• fr (French)

• it (Italian)

• sv (Swedish)

Workaround: Choose one of the following workarounds.

• On x86 based platforms, set the environment variable LC_ALL to C acroread. For example, in the C shell, type the following command in a terminal window:

  % env LC_ALL=C acroread

• On SPARC based systems, upgrade to Adobe Acrobat Reader 5.0 or a later version.

File Systems

The following file system bugs apply to the Solaris 10 release.

Upgrading From Some Solaris Express or Solaris 10 Releases Requires Remounting of File Systems

After you upgrade an NFSv4 server from Solaris Express 11/04 or earlier Solaris 10 releases, your programs might encounter EACCES errors. Furthermore, directories might erroneously appear to be empty.

To prevent these errors, unmount and then remount the client file systems. In case unmounting fails, you might need to forcibly unmount the file system by using umount -f. Alternatively, you can also reboot the client.

NFSv4 Access Control List Functions Might Work Incorrectly

NFSv4 Access Control List (ACL) functions might work improperly if clients and servers in the network are installed with different previous Solaris 10 releases. The affected ACL functions and command-line utilities that use these functions are the following:

• acl()

• facl()

• getfacl

• setfacl

For more information about these functions and utilities, see their respective man pages.

For example, errors might be observed in a network that includes the following configuration:

• A client that is running Solaris 10 Beta software

• A server that is running Solaris 10 software

The following table illustrates the results of the ACL functions in client-server configurations with different Solaris 10 releases.

Workaround: For the NFSv4 ACL functionality to work properly, perform a full installation of the Solaris 10 OS on both the server and the client.

Access Problems Between Solaris NFSv4 Clients and NFSv4 Servers

In the current Solaris 10 version, Solaris implementation of NFSv4 Access Control Lists (ACL) is now compliant with RFC 3530 specifications. However, errors occur for NFSv4 clients that use the Solaris 10 Beta 2 or Beta 1 versions. These clients cannot create files in the NFSv4 servers that are using the current Solaris 10 release. The following error message is displayed:

NFS getacl failed for server_name: error 9 (RPC: Program/version mismatch)

Workaround: None.

System Crash Dump Fails on Devices Greater Than 1 TByte (6214480)

The system cannot generate a dump on a partition that is equal to or greater than 1 Tbyte in size. If such a device is on a system, the following might occur after the system boots subsequent to a system panic:

• The system does not save the dump.

• The following message is displayed:

  0% done: 0 pages dumped, compression ratio 0.00, dump failed: error 6

Workaround: Configure the size of your system's dump device to less than 1 Tbyte.

Using smosservice Command to Add OS Services Results in Insufficient Disk Space Message (5073840)

If you use the smosservice command to add OS services to a UFS file system, a message that there is insufficient disk space available is displayed. This error is specific to UFS file systems on EFI-labeled disks.

Workaround: Complete the following workaround.

1. Apply the SMI VTOC disk label.

2. Re-create the file system.

3. Rerun the smosservice command.

Hardware–Related Issue and Bugs

The following hardware–related issue and bugs apply to the Solaris 10 release.

SPARC: Sun Crypto Accelerator 4000 Board Versions 1.0 and 1.1 Not Supported in Solaris 10 OS

A new cryptographic framework is provided in Solaris 10 OS. However, versions 1.0 and 1.1 of the Sun Crypto Accelerator 4000 board's software and firmware do not utilize this framework. Consequently, these versions are not supported in the Solaris 10 OS.

The 2.0 release uses the new framework. This release is available as a free upgrade to current Sun Crypto Accelerator 4000 users who plan to use Solaris 10 OS. Because the Sun Crypto Accelerator 4000 is an export-controlled product, you must contact Sun Enterprise Services or your local sales channel to obtain the free upgrade. Additional information is available on the Sun Crypto Accelerator 4000 web page at Sun's products site.

Certain USB 2.0 Controllers Are Disabled

Support for certain USB 2.0 controllers has been disabled because of incompatibilities between these devices and the EHCI driver. The following message is displayed:

Due to recently discovered incompatibilities with this 
USB controller, USB2.x transfer support has been disabled. 
This device will continue to function as a USB1.x controller. 
If you are interested in enabling USB2.x support please refer 
to the ehci(7D) man page. 
Please refer to www.sun.com/io for Solaris Ready products 
and to www.sun.com/bigadmin/hcl for additional compatible 
USB products.

For the latest information about USB devices, see http://www.sun.com/io_technologies/USB-Faq.html.

Supported USB Devices and Corresponding Hub Configurations

This Solaris release supports both USB 1.1 and USB 2.0 devices. The following table is a summary of USB devices that work in specific configurations. Connection types can either be direct to the computer or through a USB hub. Note that USB 1.1 devices and hubs are low speed or full speed. USB 2.0 devices and hubs are high speed. For details about ports and speeds of operation, see the System Administration Guide: Devices and File Systems.

x86: Limitations Exist With Certain Device Drivers in Solaris 10 OS

The following list describes limitations with certain drivers and interfaces in this release of Solaris 10 for x86 platforms:

Checkpoint Resume

This functionality is turned off for all device types. In the DDI_SUSPEND code in your detach() function, you should return DDI_FAILURE.

Power Management

This functionality is unavailable to USB devices. Do not create power management components. Write your driver so that pm_raise_power() and pm_lower_power() are called only when power management components are created.

DVD-ROM/CD-ROM Drives on Headless Systems

Power management of interactive devices such as removable media is linked with power management of your monitor and the graphics card that drives your monitor. If your screen is active, devices such as the CD-ROM drive and diskette remain at full-power mode. These devices might switch to low-power mode on a system without a monitor. To restore power to the CD or diskette, type volcheck to obtain the latest status from each removable device.

Alternatively, you can disable power management on your system by using the Dtpower GUI. By disabling power management, these devices are constantly at full power.

x86: Manual Configuration Required to Specify Non-US English Keyboards

By default, the kdmconfig program specifies Generic US-English(104-Key) as the keyboard type that is connected to the system. If the system's keyboard is not a US-English keyboard, you must manually specify the keyboard type during installation. Otherwise, installation continues by using the default keyboard specification that is inconsistent with the system's actual keyboard type.

Workaround 1: If the system's keyboard is not a US-English keyboard, perform the following steps during installation:

1. When the Proposed Window System Configuration For Installation is displayed, press Esc.

   ---

   Note –

   The information on the Proposed Window System Configuration For Installation, which includes the keyboard type, is displayed only for 30 seconds. If you want to change configuration settings, you must press Esc before the 30 seconds lapse. Otherwise, the installation continues by using the displayed settings.

   ---

2. Change the keyboard type to the type that corresponds to your system's keyboard.

3. Press Enter to accept the changes and continue with the installation.

Workaround 2: If you want to change the keyboard type in a system that is already running Solaris 10 OS, use the kdmconfig program. Choose the option that applies to the type of X server your system is running.

• If your system is running the Xsun server, follow these steps:

  1. Run kdmconfig.

  2. Use the Change Keyboard option to change the keyboard type.

  3. Save the configuration.

• If your system is running the default Xorg server, follow these steps:

  1. Run kdmconfig.

  2. Select the Xsun server.

  3. Use the Change Keyboard option to change the keyboard type.

  4. Save the configuration.

  5. Run kdmconfig again to switch to the Xorg server.

SPARC: jfca Driver for Certain Host Bus Adapters That Are Connected to Tape Devices Might Cause Errors (6210240)

The jfca driver for the following host bus adapters (HBAs) might cause system panics or I/O failures when these HBAs are connected to tape devices:

• SG-PCI1FC-JF2

• SG-PCI2FC-JF2

The jfca driver for these HBAs is prone to race conditions when certain operations are being run, and thus causes the errors. The operations are the following:

• Link reset

• Loop reset

• Switch reset

• Repeated link failures

Error messages similar to the following examples might be displayed:

• I/O failure messages

  jfca: [ID 277337 kern.info] jfca4: Sequencer-detected error. Recover immediately. last message repeated 18376 times jfca: [ID 716917 kern.notice] jfca4: ExgWarning: SendVerify(1): SHOULD ABORT THE ORIG I/O PKG=30007520bd8! scsi: [ID 107833 kern.warning] WARNING: /pci@1e,600000/SUNW,jfca@3,1/fp@0,0/st@w2100001086108 628,1 (st3): SCSI transport failed: reason 'timeout': giving up

• System panic message

  panic[cpu1]/thread=2a100497cc0: BAD TRAP: type=31 rp=2a1004978d0 addr=a8 mmu_fsr=0 occurred in module "jfca" due to a NULL pointer dereference

Workaround: Do not connect tape devices to either the SG-PCI1FC-JF2 or SG-PCI2FC-JF2 HBA.

Using USB 2.0 Hubs With USB 1.x Devices Might Cause System Panic (6209619)

If you use USB 1.x devices downstream from a USB 2.0 hub, the system might panic. The following might be one of the error messages that is displayed:

BAD TRAP: type=31 rp=2a100f8d6a0 addr=38 mmu_fsr=0 occurred 
in module "usba" due to a NULL pointer

Workaround: Do not use any of the following connection configurations with USB 1.x devices:

• USB 1.x devices with a connection to a USB 2.0 hub that is connected to a USB 2.0 system port

• USB 1.x devices that are connected to a USB 2.0 PCI card's ports

Instead, connect the USB 1.x devices directly to the system's USB 1.1 ports. Alternatively, you can use a USB 1.1 external hub that is connected to a USB 2.0 system port or a PCI card's port.

For appropriate information, see the following:

• http://www.sun.com/io for Solaris Ready products

• http://www.sun.com/bigadmin/hcl for additional compatible USB products

• http://www.sun.com/io_technologies/USB-Faq.html for the latest information about USB devices

x86: EHCI Driver Unusable in Certain Motherboards (6204987)

The system software in the ICH5R controller in certain motherboards fails to take control of EHCI hardware from the BIOS. The following error message is displayed:

ehci_init_ctrl: Unable to take control from BIOS. EHCI support disabled.

Consequently, you cannot use the EHCI driver.

For appropriate information, see the following:

• http://www.sun.com/io for Solaris Ready products

• http://www.sun.com/bigadmin/hcl for additional compatible USB products

• http://www.sun.com/io_technologies/USB-Faq.html for the latest information about USB devices

Workaround: None.

Using FireWire–1394 Storage Devices Might Cause System Panic (6203680)

If you use FireWire-1394 mass storage devices with the removable media volume daemon (vold), the system might panic. Hard drives and CD or DVD drives are examples of such storage devices. The error message that might be displayed includes the entry “bad mutex.”

Workaround: Perform these steps before connecting FireWire–1394 mass storage devices to the system:

1. Become superuser.

2. Stop the Volume Management daemon to disable removable media management:

   # /etc/init.d/volmgt stop

For more information about the daemon, see the vold(1M) man page.

Pausing USB Audio Devices During Play or Record Operation Might Cause System Deadlock (6200924)

While a USB audio device is playing or recording, if you pause the device by using sdtaudiocontrol, for example, the driver might hang. You might need to reboot the system.

Workaround: Do not pause USB audio devices.

For appropriate information, see the following:

• http://www.sun.com/io for Solaris Ready products

• http://www.sun.com/bigadmin/hcl for additional compatible USB products

• http://www.sun.com/io_technologies/USB-Faq.html for the latest information about USB devices

Contention Exists Between Certain Devices That Share the Same Bus (6196994)

A bus contention occurs if Quad Fast-Ethernet (QFE) cards share the same bus with any of the following adapters:

• Sun GigaSwift adapter

• Sun Dual Gigabit Ethernet and Dual SCSI/P adapter

• Sun Quad Gigaswift Ethernet adapter

The infinite-burst parameter of the ce driver that is used by these adapters is enabled by default. Consequently, little or no bus time is available for the QFE ports that share the same bus.

Workaround: Do not place QFE cards on the same bus as the network adapters in the list.

Some Keyboard Keys Not Functioning With Num Lock Key On (6173972)

If the Num Lock key is turned on while you are running certain Java applications, other keys might cease to function. Some of the affected keys are the following:

• Back Space

• Delete

• Enter

• Tab

• Zero on the number keypad

Workaround: Turn off the Num Lock key.

SPARC: GigaSwift Fast and Gigabit Ethernet Devices With Revision IDs Lower Than 32 Might Cause System Panic (5090222)

A GigaSwift Fast or a Gigabit Ethernet card with a Revision ID (rev_id) that is lower than 32 might cause a system to panic. The panic is observed in the following systems that are running Solaris 10 OS:

• Sun Blade^TM 1500

• Sun Blade 2500

• Sun Fire V210

• Sun Fire V240

• Netra^TM 240

• Sun Fire V440

• Netra 440

The following error message is displayed:

panic: pcisch-1: Fatal PCI bus error(s)

Workaround: Follow these steps.

1. Determine the rev_id of the device.

   kstat ce:instance | grep rev

2. If the rev_id is lower than 32, replace the card with a later model that has a rev_id equal to or higher than 32.

The original card is still usable in x86 systems or in older SPARC based systems that are not included in the preceding list.

hat_getkpfnum() DDI Function Is Obsolete (5046984)

The hat_getkpfnum() DDI function is obsolete. Developers should update their device drivers to not use the hat_getkpfnum() DDI interface. If drivers are using hat_getkpfnum,() warnings similar to the following example are displayed:

WARNING: Module mydrv is using the obsolete hat_getkpfnum(9F)
interface in a way that will not be supported in
a future release of Solaris. Please contact the
vendor that supplied the module for assistance,
or consult the Writing Device Drivers guide,
available from http://www.sun.com for migration
advice.
---
Callstack of bad caller:
       hat_getkpfnum_badcall+93
       hat_getkpfnum+6e
       mydrv_setup_tx_ring+2d
       mydrv_do_attach+84
       mydrv_attach+242
       devi_attach+6f
       attach_node+62
       i_ndi_config_node+82
       i_ddi_attachchild+4a
       devi_attach_node+4b
       devi_attach_children+57
       config_immediate_children+6e
       devi_config_common+77
       mt_config_thread+8b

To determine if a driver is using hat_getkpfnum(), consult the driver source code, or examine the driver's symbols by using nm(). Using the driver mydrv as an example, type the following syntax:

% nm /usr/kernel/drv/mydrv | grep hat_getkpfnum

For guidance about migrating drivers away from hat_getkpfnum(), refer to Appendix B, Summary of Solaris DDI/DKI Services, in Writing Device Drivers.

Some Systems With USB 2.0 Hardware Might Hang or Panic (5030842)

Systems with certain USB 2.0 hardware might frequently hang or panic when running this Solaris release. These problems are associated with USB 2.0 devices that are not based on the NEC chip set. When these problems occur, the following error message about the Enhanced Host Controller Interface (EHCI) is displayed:

WARNING: /pci@0,0/pci8086,244e@1e/pci925,1234@2,2 (ehci1):
This controller is not supported.
Please refer to www.sun.com/io for Solaris Ready products
and to www.sun.com/bidadmin/hcl for additional compatible USB products

Workaround: Depending on your system's hardware configuration, choose one of the following options:

• Replace the USB 2.0 host controller hardware with hardware that is based on the NEC chip set. USB 2.0 hardware that is based on the NEC chip set is known to work well with the Solaris OS.

• On systems whose USB 2.0 host controller hardware is built into the motherboard and that have spare PCI slots, perform the following steps:

  1. Add a PCI-based USB 2.0 card that is based on the NEC chip.

  2. Become superuser.

  3. Disable USB 2.0 on the motherboard and enable USB 2.0 support only through the PCI card. Issue the following commands:

     # update_drv -d -i '"pciclass,0c0320"' usba10_ehci # update_drv -a -i '"pci1033,e0"' usba10_ehci # reboot

  4. For faster operation, connect your USB 2.0 devices to the card's ports instead of the original ports on the motherboard.

• Even if you cannot add new USB hardware to your system, you can still disable your system's EHCI by performing the following steps:

  1. Become superuser.

  2. Issue the following commands:

     # update_drv -d -i '"pciclass,0c0320"' usba10_ehci # reboot

USB 2.0 ports are operated by two companion hardware pieces:

• EHCI for the high-speed piece

• Either Open Host Controller Interface (OHCI) or Universal Host Controller Interface (UHCI) for the low-speed and full-speed piece

On x86 based systems, drivers for both OHCI and UHCI exist. On SPARC based systems, only OHCI USB 1.1 host controller hardware is supported. Therefore, only USB hardware with OHCI companion controllers continue to work on SPARC systems whose companion EHCI controller is disabled. Ports of the USB hardware remain operational even with EHCI disabled, provided that your system has the proper OHCI or UHCI drivers. USB 2.0 devices that are connected to these ports run only as fast as a USB 1.1 device.

To verify whether EHCI and OHCI host controllers exist on your SPARC based systems, type:

# prtconf -D

Check the output for EHCI entries next to one or more OHCI entries, similar to the following example:

pci, instance #0 (driver name: pci_pci)
usb, instance #0 (driver name: usba10_ohci)
usb, instance #1 (driver name: usba10_ohci)
usb, instance #0 (driver name: usba10_ehci)

x86: Using Two Adaptec SCSI Card 39320D Cards on a Sun Fire V65x Server Might Cause the System to Panic (5001908)

Using two Adaptec SCSI Card 39320D cards on a Sun Fire V65x server might cause that system to panic. The panic occurs during initial reboot after you have installed Solaris 10 software. The following error message is displayed:

Initializing system  Please wait... 
1 run-time error M6111: MATH
	- floating-point error: stack underflow

Workaround: Remove the second Adaptec card.

x86: Soft System-Shutdown is Not Supported in Solaris OS on x86 (4873161, 5043369)

The Solaris OS on x86 does not support a soft system-shutdown that is initiated by a command. A command to shut down simulates pressing the power button to turn the power off. On x86-based systems, issuing this command while the Solaris OS is running turns the power off immediately without properly shutting down the operating system. The improper shutdown process might corrupt the file system.

Workaround: Before powering off, shut down the operating system first. Perform the following steps:

1. Become superuser.

2. Use one of the available commands to shut down the Solaris OS properly, such as init, halt, or shutdown. For example:

   # shutdown

3. After the operating system shuts down completely, you can switch off the power by one of two ways:

   • If the system supports soft system-shutdown, issue the command to turn off the power.

   • If the system does not support soft system-shutdown, turn off the power manually by using the power switch.

For more information about the commands to shut down the operating system, see the man pages for the init(1M), halt(1M), and shutdown(1M) commands. For information about turning off your system's power, refer to the system's manuals.

Some DVD and CD-ROM Drives Fail to Boot Solaris (4397457)

The default timeout value for the SCSI portion of the SunSwift^TM PCI Ethernet/SCSI host adapter (X1032A) card does not meet the timeout requirements of Sun's SCSI DVD-ROM drive (X6168A). With marginal media, the DVD-ROM occasionally experiences timeout errors. The only exceptions are Sun Fire 6800, 4810, 4800, and 3800 systems. These systems overwrite the SCSI timeout value by means of OpenBoot PROM.

Workaround: For other platforms, use the on-board SCSI interfaces or DVD-ROM compatible SCSI adapters, such as the following examples:

• X1018A (SBus: F501-2739-xx)

• X6540A (PCI: F375-0005-xx)

iPlanet Directory Server 5.1 Issues

This section provides important information for users of iPlanet^TM Directory Server 5.1 who are upgrading to the new Solaris 10 release.

Installing Directory Server 5.1

Sun Java System Directory Server 5 2005Q1 replaces iPlanet Directory Server 5.1 that was integrated in the Solaris 9 Operating System. In Solaris 10 OS, this new Directory Server can be installed as part of the Sun Java Enterprise System.

For information about the Sun Java System Directory Server 5 2005Q1, refer to the documentation for the Sun Java System at http://docs.sun.com.

Solaris 10 OS continues to support Directory Server 5.1. You might need to install Directory Server 5.1 under the following circumstances:

• You need to recover Directory Server 5.1 data.

• You want to migrate your data to Directory Server 5 2005Q1.

In Solaris 10 release, you install the Directory Server 5.1 manually. Follow these steps:

1. Insert the Solaris 10 Software - 4 CD into your CD-ROM drive.

2. Become superuser.

3. In a terminal window, install the Directory Server.

   # cd /cdrom/cdrom0/Solaris_10/Product/ # pkgadd -d . IPLTnls IPLTnspr IPLTnss IPLTjss IPLTpldap \ IPLTdsr IPLTdsu IPLTadmin IPLTcons IPLTadcon IPLTdscon \ IPLTadman IPLTdsman

   To install Simplified Chinese localization packages, issue the following additional command:

   # pkgadd -d . IPLTcdsu IPLTcadmin IPLTccons IPLTcadcon \ IPLTcdscon IPLTcadman IPLTcdsman

   To install Japanese localization packages, issue the following additional command:

   # pkgadd -d . IPLTjdsu IPLTjadmin IPLTjcons IPLTjadcon \ IPLTjdscon IPLTjadman IPLTjdsman

4. After installation is complete, configure iPlanet Directory Server 5.1. Refer to Chapter 11, Sun ONE Directory Server Configuration, in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).

Migrating to the Sun Java System Directory Server 5 2005Q1

The database formats of the two Directory Server versions are incompatible. Thus, if you are a Directory Server 5.1 user, Sun recommends that you migrate your database to a database that is formatted for the Sun Java System Directory Server 5 2005Q1.

To perform a migration, both versions of the Directory Server must exist in the system that has been upgraded to the Solaris 10 OS. If you are a DS 5.1 user, but are using the compressed archive (.tar.gz) delivery format, you can skip immediately to the migration instructions in Step 2.

1. On a terminal window, check whether iPlanet Directory Server 5.1 packages are present in your system.

   $ pkginfo | grep IPLT

   If the following packages appear as output, then you can go to Step 2 to proceed with the migration. The output indicates that the iPlanet Directory Server 5.1 packages are in the system.

   system IPLTadcon Administration Server Console system IPLTadman Administration Server Documentation system IPLTadmin Administration Server system IPLTcons Console Client Base system IPLTdscon Directory Server Console system IPLTdsman Directory Server Documentation system IPLTdsr Directory Server (root) system IPLTdsu Directory Server (usr) system IPLTjss Network Security Services for Java system IPLTnls Nationalization Languages and Localization Support system IPLTnspr Portable Runtime Interface system IPLTnss Network Security Services system IPLTpldap PerLDAP $

   If the packages do not exist, then install the iPlanet Directory Server 5.1 packages first. Refer to the 4-step procedure in the preceding section Installing Directory Server 5.1. After installation is complete, go to Step 2 to proceed with the migration.

2. Migrate your iPlanet Directory Server 5.1 database to the current version. For instructions, refer to the documentation collection for the Sun Java System Directory Server at http://docs.sun.com/coll/DirectoryServer_05q1.

After migrating your data, make sure you continue to back up directory data in the same way as you backed up directory data before migration. Future disaster recovery might require the migrated database.

Issues While Running Debugger

The following issues involve the kernel debugger.

SPARC: Systems With Active Kernel Debugger Might Panic During Suspend/Resume Cycles (5062018)

After you execute several suspend/resume cycles on a system with an active kernel debugger (kmdb), the system might eventually panic. The panic occurs at the resume phase of the cycle. Typically, this problem occurs in systems that have undergone between 20 and 50 suspend/resume cycles. The system generates a panic message.

Workaround: Disable kmdb in all systems that are required to use the suspend and resume module (cpr).

System Might Loop When Master CPU Is Changed (4405263)

A system that is running the Solaris kernel debugger to debug a live system might loop with incomplete error messages. This loop occurs when the OpenBoot PROM's master CPU is changed. A system reset restores the system to operation. However, the traces of the original failure are lost. Consequently, you cannot perform a diagnosis of the fatal reset.

Workaround: When the system is at the PROM level, the OpenBoot's ok prompt is displayed. In a system with multiple CPUs, the ok prompt is preceded by a number that is enclosed in curly braces. This number indicates the active CPU in the system. To run your debug session while at the PROM level, use the following steps.

1. Raise pil to f by typing the following command:

   {0} ok h# 0f pil!

2. Use the switch-cpu command to selectively switch from the currently active CPU to different CPUs. For example, to switch from CPU #0 to CPU #1, type the following command:

   (0) ok 1 switch-cpu

   The ok prompt is now preceded by the number of the CPU to which you switched.

   {1} ok

3. Run your debugger.

4. At the end of your debugger session, issue a reset-all command to return the system to normal use.

Make sure that you upgrade the system to the latest version of the OpenBoot PROM.

Localization Issues

This section describes localization issues that apply to Solaris 10 OS.

Login Screen Marks UTF-8 Locales as Recommended

On the Language menu of the login screen, the UTF-8 locales are labeled as a recommended option. For example, for Japanese locales, the screen would appear as follows:

ja_JP.eucJP -------------- Japanese EUC
ja_JP.PCK  --------------- Japanese PCK
ja_JP.UTF-8 (Recommended) - Japanese UTF-8

Using UTF-8 locales is recommended to users of the Java Desktop System (JDS) because JDS uses UTF-8/Unicode as internal character encoding. This recommendation also applies to the announcement of future end-of-software support for non-UTF-8 locales. See Legacy or Traditional Non-UTF-8 Locales.

When migrating to UTF-8 locales, the files affect the method that you use to import or export data.

Microsoft Office Files

Microsoft Office files are encoded in Unicode. StarOffice applications can read and write the Unicode encoded files.

HTML Files

HTML files authored using HTML editors such as Mozilla Composer, or HTML files saved by a web browser, usually contain a charset encoding tag. After exporting or importing, you can browse such HTML files with the Mozilla Navigator web browser, or edit the files with Mozilla Composer, according to the encoding tag in the HTML file.

Fixing Broken HTML File

Some HTML files might be displayed in garbage characters. This problem is typically due to the following reasons:

• The charset encoding tag is incorrect.

• The charset encoding tag is missing.

To find the charset encoding tag in the HTML file, perform the following actions:

1. Open the file with Mozilla.

2. Press Ctrl-i, or click View to open the View menu.

3. Click Page Info.

The charset information is in the bottom of the General tab, for example:

Content-Type text/html; charset=us-ascii

If the string charset=us-ascii does not match the actual encoding of the file, the file might appear broken. To edit the encodings of the HTML file, perform the following actions:

1. Open the file with Mozilla Composer.

2. Open the File menu.

3. Select Save as Charset.

4. Choose the correct encoding. Mozilla Composer automatically converts the encoding and the charset tag as appropriate.

Emails Saved As Portable Format

Modern mails are tagged with the MIME charset tag. The Email and Calendar application accepts MIME charset tags. You do not need to perform any encoding conversion.

Plain Text Files

Plain text files do not have a charset tag. If the files are not in UTF-8 encoding, encoding conversion is needed. For example, to convert a plain text file encoded in Traditional Chinese big5 to UTF-8, execute the following command:

iconv -f big5 -t UTF-8 inputfilename



 > outputfilename

You can also use the File System Examiner for the encoding conversion.

You can use the Text Editor to read and write character encoding text automatically or by specifying an encoding explicitly when opening or saving a file.

To start Text Editor, click Launch, then choose Applications->Accessories->Text Editor.

File Names and Directory Names

If file names and directory names using multibyte characters are not in UTF-8 encoding, encoding conversion is needed. You can use File System Examiner to convert file and directory names and the contents of plain text files from legacy character encodings to UTF-8 encoding. Refer to the online Help for File System Examiner for more information.

To start File Systems Examiner, click Launch, then choose Applications->Utilities->File System Examiner.

When you access non-UTF-8 file or directory names on Microsoft Windows via SMB using File Manager, you can access the non-UTF-8 file or directory names without encoding conversion.

Launching Legacy Locale Applications

For applications that are not ready to migrate to Unicode UTF-8, you can create a launcher on a front panel to start the application in legacy locales. You can also launch the applications directly from the command line. Perform the following steps to create a launcher for an application.

1. Right-click on the panel where you want to place the launcher.

2. Choose Add to Panel->Launcher.

3. Use the following format to type the entry in the Command field in the Create Launcher dialog:

   env LANG=locale LC_ALL= locale application name

   For example, if you want to launch an application called motif-app from /usr/dt/bin in the Chinese Big5 locale, enter the following text in the Command field of the Create Launcher:

   env LANG=zh_TW.BIG5 LC_ALL=zh_TW.BIG5 /usr/dt/bin/motif-app

4. Click OK to create the launcher on the panel.

When you need to run CLI (command line interface) applications which are specific to a legacy locale, open a Terminal window in the legacy locale first and then run the CLI applications in the same Terminal window. To open a Terminal window in a legacy locale, enter the following command:

eng LANG=locale LC_ALL=locale GNOME-TERMINAL –disbable-factory.

Instead of opening a new Terminal window in a legacy locale, you can switch the locale setting from UTF-8 to a legacy locale in the current Terminal window by changing the encoding the Set Character Encoding menu in the Terminal window. Then you must also set the LANG and LANG environment variables to the current shell.

Hardware for Estonian Keyboard Type 6, French Canadian Keyboard Type 6, and Polish Programmers Keyboard Type 5 Not Available

Software support for three additional keyboard layouts has been added to the Solaris OS: Estonian keyboard Type 6, French Canadian keyboard Type 6, and Polish programmers keyboard Type 5.

This software gives users in Estonia, Canada, and Poland greater flexibility for keyboard input by modifying standard U.S. keyboard layouts to their own language needs.

Currently, no hardware is available for the three additional keyboard layout types.

Workaround: To take advantage of this new keyboard software, modify the /usr/openwin/share/etc/keytables/keytable.map file in one of the following ways:

• For the Estonian Type 6 keyboard, make the following changes:

  1. Change the US6.kt entry to Estonia6.kt in the /usr/openwin/share/etc/keytables/keytable.map file. The modified entry should read as follows:

     6 0 Estonia6.kt

  2. Add the following entries to the /usr/openwin/lib/locale/iso8859-15/Compose file:

     <scaron>	: "/xa8"	scaron
     <scaron>	: "/xa6"	scaron
     <scaron>	: "/270"	scaron
     <scaron>	: "/264"	scaron

  3. Reboot the system for the changes to take effect.

• For the French Canadian Type 6 keyboard, make the following changes:

  1. Change the US6.kt entry to Canada6.kt in the /usr/openwin/share/etc/keytables/keytable.map file. The modified entry should read as follows:

     6 0 Canada6.kt

  2. Reboot the system for the changes to take effect.

• If you are using the existing Polish Type 5 keyboard layout, make the following changes:

  1. Change the Poland5.kt entry to Poland5_pr.kt in the /usr/openwin/ share/etc/keytables/keytable.map file. The modified entry should read as follows:

     4 52 Poland5_pr.kt

     ---

     Note –

     If you are using a keyboard with dip-switches, make sure the switches are set to the correct binary value for the Polish keytable entry (binary 52) before rebooting the system.

     ---

  2. If you are using a standard U.S. Type 5 keyboard, change the US5.kt entry to Poland5_pr.kt in the /usr/openwin/share/etc/keytables/keytable.map file. The modified entry should read as follows:

     4 33 Poland5_pr.kt

  3. Reboot the system for the changes to take effect.

Cannot Print Documents in Portable Document Format (6239307, 6218079)

On all locales, the Document Viewer cannot print localized files that are in Portable Document Format (PDF).

Workaround: Choose one of the following workarounds:

• On SPARC based systems, use the Acrobat Reader to print localized PDF files.

• On x86 based systems, use StarOffice to create and then print PDF files.

x86: Login Process Might Hang in Certain Asian Non-UTF-8 Locales (6215527)

On some x86 based systems, if you log in to certain Asian non-UTF-8 locales, the login process might hang. The following are examples of the locales where the error is observed:

• zh_CN.EUC

• zh_TW.BIG5

• ko_KR.EUC

Workaround: At the login window's Language menu, choose UTF-8 locales.

localeadm -l Does Not List Installed Korean Locale Packages (6189823)

When re-creating the /usr/sadm/lib/localeadm/locales.list file, the localeadm -l command fails to include the Korean locales. Consequently, even though the Korean locales are installed in a system, the locales are not listed when you run localeadm -l. Furthermore, if you attempt to remove the Korean locales with localeadm -r ko after listing the installed locales, the following error message is displayed:

Region korean is not installed on this machine. Exiting.

Workaround: To update the /usr/sadm/lib/localeadm/locales.list file properly, run localeadm -a ko. You can then successfully remove the Korean locales with localeadm -r ko.

Alternatively, you can perform the following steps:

1. Become superuser.

2. Edit the /usr/sadm/lib/localeadm/locales.list file by adding the following entry:

   Korean (korean)

Special Keyboard Keys Do Not Work (5077631)

Special keys on the left of the keyboard do not work on European keyboard mappings. This problem affects all European locales.

Workaround: Use shortcut keys instead of the special keyboard keys. The following example lists shortcut keys and the corresponding functions:

• Ctrl-Z - Undo

• Ctrl-C - Copy

• Ctrl-V - Paste

• Alt-Tab allows you to switch between windows.

Modifier Keys Do Not Function Correctly (4996542)

On all locales, the Alt key and the Shift key might not function as modifier keys when you use the Internet/Intranet input method. For example, the Shift-arrow key combination might not allow you to select text. Instead, the combination might insert Latin characters.

Workaround: Use a different input method, for example, Default. To switch input methods, right-click on an object and select Input method.

Chinese and Korean Characters Are Printed In a Box (4977300)

The postscript printer does not bundle Chinese or Korean fonts. Consequently, in Chinese or Korean locales, if you attempt to print from the Mozilla browser, the characters are printed within a box. The Common UNIX Printer System (CUPS) needs to convert the Mozilla postscript fonts before a file can be printed.

Workaround: Perform the following steps.

1. Click Launch => Preferences => Printers.

2. Right-click the PostScript printer icon, then select Properties.

3. Click the Advanced tab.

4. Set the Ghostscript pre-filtering to Convert to PS level 1.

Sort Capability in the European UTF-8 Locales Does Not Function Correctly (4307314)

The sort capability in the European UTF-8 locales does not work properly.

Workaround: Before you attempt to sort in a FIGGS UTF-8 locale, set the LC_COLLATE variable to the ISO–1 equivalent.

# echo $LC_COLLATE
>  es_ES.UTF-8
# LC_COLLATE=es_ES.IS08859-1
# export LC_COLLATE

Then start sorting.

Networking Issues

The following networking bugs apply to the Solaris 10 release.

SPARC: RTM_IFINFO Message Has Different Sizes on 32-bit and 64-bit Compilations

Sixty-four-bit programs that create PF_ROUTE sockets and parse the contents of RTM_IFINFO messages in the if_msghdr_t structure might work incorrectly unless they are recompiled.

IP Forwarding Disabled by Default in Solaris 10 OS

In this Solaris release, IP forwarding is disabled by default. This setting applies to both IPv4 and IPv6 regardless of other system configurations. Systems with multiple IP interfaces that formerly forwarded IP packets by default no longer have this automatic feature. To enable IP forwarding in multihomed systems, administrators must manually perform additional configuration steps.

Workaround: The command routeadm enables IP forwarding. The configuration changes that are the result of routeadm usage persist across system reboots.

• To enable IPv4 forwarding, type routeadm -e ipv4-forwarding .

• To enable IPv6 forwarding, type routeadm -e ipv6-forwarding .

• To apply the enabled IP-forwarding configuration to the currently running system, type routeadm -u.

For more information about IP forwarding, see the routeadm(1M) man page.

Zone Not Booting When IP Address Belongs to a Failed IP Network Multipathing Group (6184000)

A zone can be configured so that the zone's IP address becomes part of an IP Network Multipathing (IPMP) group. The configuration process is documented in How to Extend IP Network Multipathing Functionality to Non-Global Zones in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

If all the network interfaces in the IPMP group fail, a zone does not boot if it has an IP address that is part of the IPMP group.

The following example illustrates the result if you attempt to boot the zone.

# zoneadm -z my-zone boot 
zoneadm: zone 'my-zone': bge0:1: 
could not set default interface for multicast: Invalid argument 
zoneadm: zone 'my-zone': call to zoneadmd failed

Workaround: Repair at least one network interface in the group.

ATM LANE Subnets for IPv4/IPv6 Might Not Complete Initialization (4625849)

During system boot, multiple instances might not connect to their LAN Emulation (LANE) instance if more than eight LANE instances are on a single adapter. This bug does not appear at multiuser level.

Workaround: To reinitialize your SunATM network, perform the following steps:

1. Verify the problem by issuing a lanestat -a command.

   Instances that are not connected have Virtual Circuit Identifier (VCI) values of 0 to the LAN Emulation Server (LES) and Broadcast and Unknown Address Server (BUS).

2. Stop and restart your SunATM network.

   # /etc/init.d/sunatm stop # /etc/init.d/sunatm start

3. Reset netmasks or any other network setup for the SunATM interfaces.

Configuring Multiple Tunnels Between Two IP Nodes With Filtering Enabled Might Result in Packet Loss (4152864)

If you configure multiple IP tunnels between two IP nodes, and enable ip_strict_dst_multihoming or other IP filters, packet loss might result.

Workaround: Choose one of the following:

• First, configure a single tunnel between the two IP nodes. Add addresses to the tunnel by using the ifconfig command with the addif option.

• Do not enable ip_strict_dst_multihoming on tunnels between two IP nodes.

Security Issues

The following security issues applies to the Solaris 10 release.

Nonpassword Logins Fail With pam_ldap Enabled

After the account management PAM module for LDAP (pam_ldap) is enabled, users must have passwords to log in to the system. Consequently, nonpassword-based logins fail, including those logins that use the following tools:

• Remote shell (rsh)

• Remote login (rlogin)

• Secure shell (ssh)

Workaround: None.

New Versions of encrypt() and decrypt() Are Not Backward Compatible

Output files that are generated by encrypt() are processed by the corresponding decrypt(). The current release uses a new version of encrypt() and decrypt(). These commands process files whose format differs from files that earlier versions generated and processed. Data that is encrypted by using the earlier encrypt() can no longer be recognized correctly by the new decrypt().

For more information, refer to the encrypt(1) and decrypt(1) man pages.

Workaround: To convert old encrypted data so that the data can be processed by the new encrypt() and decrypt() version, perform the following steps:

1. Decrypt the existing data by using the earlier version of decrypt().

2. Re-encrypt the same data by using the new encrypt().

Incorrect Parameters Might Cause Panic in Sun StorEdge T3 (4319812)

A Sun StorEdge^TM T3 system might panic if an application uses the HTTP interface to send tokens with out-of-range parameters.

Service Management Facility

This section describes issues that involve the Service Management Facility of Solaris 10 OS. For more information about this new feature in the Solaris OS, see Solaris Service Manager in Solaris 10 What’s New.

svccfg import Subcommand Does Not Refresh Dependent Services (6221374)

When the system first boots after a Solaris 10 OS installation, an error with dependent services might occur. The svccfg import subcommand might fail to activate dependent services that have been declared in a service's manifest file. Consequently, the dependent services might not start in order and generate error messages that refer to those services.

Workaround: Issue the command svcadm refresh for the dependent service. For example:

svcadm refresh dependent FMRI

Software developers can avoid this problem with the following workarounds:

• Declare dependent services at the instance level instead of the service level.

• For live installations, enable a package's postinstall script to run the svcadm refresh dependent FMRI command.

• For installations that use an alternate boot environment, append the svcadm refresh dependent FMRI command to the /var/svc/profile/upgrade file.

Print Services Have Offline Settings by Default (5100134)

When a host has no local printers configured, two print services, ipp-listener and rfc1179, are set to offline by default. These services are automatically moved to online after local printers are configured on the host. The default offline settings of these services do not indicate an error. Therefore, no user intervention is required.

Workaround: None.

keyserv Daemon Disables Some File System Services (5084183)

On systems that do not use Network Information Service (NIS) or NIS+ name service, the NFS and autofs services are disabled. The failure is due to these services' dependency on the keyserv daemon. The keyserv daemon relies on the RPC domain name, which is not set on systems that do not use NIS or NIS+. Consequently, the failure of the keyserv daemon causes the NFS and autofs services to become disabled.

Workaround: To enable the services, perform the following steps:

1. Become superuser.

2. Issue the following commands:

   # svcadm disable network/rpc/keyserv # svcadm disable -t network/nfs/client:default # svcadm enable network/nfs/client:default # svcadm disable -t network/nfs/server:default # svcadm enable network/nfs/server:default # svcadm disable -t network/rpc/gss:ticotsord # svcadm enable network/rpc/gss:ticotsord

Login Prompts Sometimes Appear Before File Systems Are Mounted (5082164)

During system startups, sometimes the login services such as console or ssh logins start before remote file systems and naming services become available. Consequently, the user name might not be recognized or the user's home directory might not be available.

Workaround: If the error occurs, wait for a few seconds and then log in again. Alternatively, log in from a local account to view the system state.

Smart Card

The following Smart Card bugs apply to Solaris 10 OS.

System Does Not Respond to Smart Card (4415094)

If ocfserv terminates and the display is locked, the system remains locked even when a smart card is inserted or removed.

Workaround: Perform the following steps to unlock your system:

1. Perform a remote login to the machine on which the ocfserv process was terminated.

2. Become superuser.

3. Kill the dtsession process by typing the following in a terminal window.

   # pkill dtsession

ocfserv restarts and smart card login and capability are restored.

Edit Config File Menu Item in Smartcards Management Console Does Not Work (4447632)

The Edit Config File menu item in the Smartcards Management Console does not edit smart card configuration files that are located in /etc/smartcard/opencard.properties . If the menu item is selected, a warning is displayed which indicates not to continue unless requested by technical support.

Workaround: Do not use the Edit Config File menu item in the Smartcards Management Console. For information on smart card configuration, see the Solaris Smartcard Administration Guide.

Solaris Commands and Standards

The following section describes behavior changes in certain commands and standards in Solaris 10 OS.

Bash 2.0.5b No Longer Sets Some Environment Variables

Solaris 10 OS includes Bash 2.0.5b. This shell no longer automatically exports the following variables to the environment:

• HOSTNAME

• HOSTTYPE

• MACHTYPE

• OSTYPE

This new behavior applies even if the shell assigns default values to these variables.

Workaround: Export these variables manually.

New ln Utility Requires -f Option

The behavior of /usr/bin/ln has changed to adhere to all of the standards from SVID3 through XCU6. If you use the ln command without the -f option to link to an existing target file, the link is not established. Instead, a diagnostic message is written to standard error, and the command proceeds to link any remaining source files. Finally, the ln command exits with an error value.

For example, if file b exists, the syntax ln a b generates the following message:

ln: b: File exists

This behavior change affects existing shell scripts or programs that include the ln command without the -f option. Scripts that used to work might now fail in Solaris 10 OS.

Workaround: Use the -f option with the ln command. If you have existing scripts that execute the link utility, make sure to modify these scripts to comply with the command's new behavior.

New tcsh Rejects setenv Variable Names That Use a Dash or an Equals Sign

In Solaris 10 OS, tcsh has been upgraded to version 6.12. This version no longer accepts environment variables whose names use a dash or an equals sign. Scripts that contain setenv lines and that work in earlier Solaris versions might generate errors in the current Solaris 10 release. The following error message is displayed:

setenv: Syntax error

For more information, refer to the tcsh man page for the Solaris 10 OS.

Workaround: Do not use the dash or equals sign in names for environment variables.

STDIO getc Family EOF Condition Behavior Change

Applications that were built in strict standard C conformance mode are affected by the behavior changes of certain library functions. An example is applications that were compiled by using the cc -Xc or c89 compilation mode. The behavior has changed for the following library functions:

• fgetc()

• fgets()

• fgetwc()

• fgetws()

• getc()

• getchar()

• gets()

• getwc()

• getwchar()

• getws()

A formal interpretation of the 1990 C Standard requires that after an end-of-file condition is set, no more data is returned from the file on subsequent input operations. The exception is if the file pointer is repositioned or the error and end-of-file flags are explicitly cleared by the application.

The behavior for all other compilation modes remains unchanged. Specifically, the interfaces can read additional newly written data from the stream after the end-of-file indicator has been set.

Workaround: Call fseek() or clearerr() on the stream to read additional data after the EOF condition has been reported on the stream.

Output Columns of the ps Command Have Been Widened

Due to larger UIDs, processor ids, and cumulative execution time, the columns of the ps command output have been widened. Customer scripts should not assume fixed output columns.

Workaround: Scripts should use the -o option of the ps command.

For more information, see the ps(1) man page.

Command ping -v Does Not Work on IPv6 Addresses (4984993)

The command ping -v fails when the command is applied to addresses that use Internet Protocol version 6 (IPv6). The following error message is displayed:

ping: setsockopt IPV6_RECVRTHDRDSTOPTS Invalid argument

Workaround: None. To obtain the same ICMP packet information that ping -v provides, use the snoop command.

Solaris Volume Manager

The following Solaris Volume Manager bugs apply to the Solaris 10 release.

Solaris Volume Manager metattach Command Might Fail

If you have a Solaris Volume Manager mirrored root (/) file system in which the file system does not start on cylinder 0, all submirrors you attach must also not start on cylinder 0.

If you attempt to attach a submirror starting on cylinder 0 to a mirror in which the original submirror does not start on cylinder 0, the following error message is displayed:

can't attach labeled submirror to an unlabeled mirror

Workaround: Choose one of the following workarounds:

• Ensure that both the root file system and the volume for the other submirror start on cylinder 0.

• Ensure that both the root file system and the volume for the other submirror do not start on cylinder 0.

By default, the JumpStart installation process starts swap at cylinder 0 and the root (/) file system somewhere else on the disk. Common system administration practice is to start slice 0 at cylinder 0. Mirroring a default JumpStart installation with root on slice 0, but not cylinder 0, to a typical secondary disk with slice 0 that starts at cylinder 0, can cause problems. This mirroring results in an error message when you attempt to attach the second submirror. For more information about the default behavior of Solaris installation programs, see the Solaris 10 Installation Guides.

Solaris Volume Manager metassist Command Fails in Non-English Locales (5067097)

In non-English locales, the Solaris Volume Manager metassist command might fail to create volumes. For example, if LANG is set to ja (Japanese), the following error message is displayed:

xmlEncodeEntitiesReentrant : input not UTF-8
Syntax of value for attribute read on mirror is not valid
Value "XXXXXX"(unknown word) for attribute read on mirror 
is not among the enumerated set
Syntax of value for attribute write on mirror is not valid
Value "XXXXXX"(Parallel in Japanse) for attribute write on mirror 
is not among the enumerated set
metassist: XXXXXX(invalid in Japanese) volume-config

Workaround: As superuser, set the LANG variable to LANG=C.

For the Bourne, Korn, and Bash shells, use the following command:

# LANG=C; export LANG

For the C shell, use the following command:

# setenv LANG C

Volume Creation Fails in Systems With Unformatted Disks (5064066)

Creating Solaris Volume Manager volume configurations with the metassist command might fail if an unformatted disk is in the system. The following error message is displayed:

metassist: failed to repartition disk

Workaround: Manually format any unformatted disks before you issue the metassist command.

Hot Spares Do Not Work Correctly When Solaris Volume Manager RAID-1 (Mirror) or RAID-5 Volumes Are Created in Disk Sets Built on Soft Partitions (4981358)

If you create a Solaris Volume Manager RAID-1 (mirror) or RAID-5 volume in a disk set that is built on top of a soft partition, hot spare devices do not work correctly.

Problems that you might encounter include, but are not limited to, the following:

• A hot spare device might not activate.

• A hot spare device status might change, indicating the device is broken.

• A hot spare device is used, but resynced from the wrong drive.

• A hot spare device in use encounters a failure, but the broken status is not reported.

  Workaround: Do not use this configuration to create a Solaris Volume Manager RAID-1 or RAID-5 volume in disk sets.

Solaris Volume Manager metadevadm Command Fails if Logical Device Name No Longer Exists (4645721)

You cannot replace a failed drive with a drive that has been configured with the Solaris Volume Manager software. The replacement drive must be new to Solaris Volume Manager software. If you physically move a disk from one slot to another slot on a Sun StorEdge A5x00, the metadevadm command fails. This failure occurs when the logical device name for the slice no longer exists. However, the device ID for the disk remains present in the metadevice replica. The following message is displayed:

Unnamed device detected. Please run 'devfsadm && metadevadm -r to resolve.

You can access the disk at the new location during this time. However, you might need to use the old logical device name to access the slice.

Workaround: Physically move the drive back to its original slot.

Solaris Volume Manager metarecover Command Fails to Update metadb Namespace (4645776)

If you remove and replace a physical disk from the system, and then use the metarecover -p -d command to write the appropriate soft partition specific information to the disk, an open failure results. The command does not update the metadevice database namespace to reflect the change in disk device identification. The condition causes an open failure for each such soft partition that is built on top of the disk. The following message is displayed:

Open Error

Workaround: Create a soft partition on the new disk instead of using the metarecover command to recover the soft partition.

If the soft partition is part of a mirror or RAID 5, use the metareplace command without the -e option to replace the old soft partition with the new soft partition.

# metareplace dx mirror or RAID 5 
old_soft_partition new_soft_partition

Sun Java Desktop System

This section describes issues that apply to the Sun Java Desktop System (Java DS) in the Solaris 10 OS.

Email and Calendar

Problems With Using Multiple Attachments (6260583)

If you drag and drop email messages to a new email message body, the content of the new email message is corrupted.

Workaround: To send multiple attachments, perform the following steps:

1. Select the messages you want to attach.

2. On the Menu bar, choose Action => Forward => Attached.

   Alternatively, you can press Ctrl-J to send the messages.

Problem With Changing Authentication Type (6246543)

After you change the authentication type for the incoming mail server, Email and Calendar might not work correctly.

Workaround: Restart Email and Calendar.

Problems When Saving Attachments With Localized Content (6204976)

The Evolution application, which includes Email and Calendar, cannot save attachments with localized content.

Workaround: None.

Incomplete List of Contacts in Contact Folder (5088514)

After you import an LDAP Data Interchange Format file containing several contacts, only some of the contacts are displayed in your contact folder. This is a display problem only. Email and Calendar has imported all the contacts.

Workaround: Restart Email and Calendar.

Login

Login Error Message

You might encounter the following error message when you log in to a Java Desktop System session:

Could not look up internet address for hostname.
This will prevent GNOME from operating correctly.
It may be possible to correct the problem by adding 
hostname to the file /etc/hosts

Workaround: Ensure that your hostname is set up correctly in the /etc/hosts file. Perform the following steps:

1. Set the hostname in the /etc/hosts file as follows:

   127.0.0.1 localhost loghost hostname localhost.localdomain

   hostname is the name of your system.

2. Ensure that your hostname is listed in the /etc/nodename file. This file must also contain the following line:

   127.0.0.1 localhost loghost hostname localhost.localdomain

3. Add the following entry to the /etc/inet/ipnodes file:

   127.0.0.1 hostname

$PATH issues (6247943)

When you log into Java Desktop System Release 3, your $PATH is set incorrectly to the following:

/usr/bin::/usr/dt/bin:/usr/openwin/bin:/bin:
/usr/ucb:/usr/openwin/bin:/usr/dt/bin

Workaround: Remove the following from your $PATH:

• /usr/openwin/bin:

• /bin:

• ::

The resulting path should be similar to the following example:

/usr/bin:/usr/dt/bin:/usr/ucb:/usr/openwin/bin:/usr/dt/bin

Remote Connection Problems (6203727)

If you use dtlogin remote connection, you cannot connect to the GNOME Display Manager from certain systems.

Workaround: When you are prompted to select the remote login, specify the IP address instead of the hostname.

Help System

Wrong Help Window Opened For Volume Control (6253210)

If you use the Yelp browser to open the online help for Volume Control, the help file for the Keyboard Accessibility panel application is opened instead.

Workaround: None.

Online Help Freezes (5090731)

If you open an application's online help and no help files exist for that application, an error dialog box is displayed. Unless you click OK, the online Help system freezes and you cannot open the online help of other applications that you start subsequently.

Workaround: You must click the OK button in the error dialog box.

Mozilla Browser

Cannot Print Certain Documents From the Mozilla Browser

You cannot print documents from the Mozilla browser if the documents contain Unicode characters that are not in the Basic Multilingual Plane (BMP).

Workaround: None.

Cannot Specify User Preferences for Roaming Access in Mozilla Browser (6200999)

In the Mozilla browser, you can specify that User Preferences should be transferred to and from the Roaming Access server. You specify your Roaming Access option by following these steps:

1. On the browser, click Edit and select Preferences.

2. Select Roaming User, then select Item Selection.

3. On the right panel, select User Preferences.

However, the selection of User Preferences does not take effect.

Workaround: None.

Keyboard Shortcuts Fail (6192644)

In the Mozilla browser, you enable caret browsing by pressing F7. When caret browsing is enabled, the keyboard shortcut Ctrl-Home brings you to the beginning of the web page that you are browsing. However, this keyboard shortcut does not work when you browse certain sites such as www.yahoo.com and www.mozilla.org.

Workaround: Disable caret browsing by pressing F7.

System-Level Issues

User Preferences Not Fully Compatible

User preferences in your home account for an earlier version of the GNOME Desktop might be partly incompatible with the version on the Java DS Release 3.

Workaround: Reset your preferences. Perform the following steps:

1. Log out of the Java Desktop System.

2. Click Session and choose Failsafe terminal.

3. Log in.

4. In the failsafe terminal window, enter the following commands:

   % gnome-cleanup exit

5. Log in again.

   Your GNOME preferences are now reset.

GNU Image Manipulation Program Missing From the Graphics Menu (6209566)

The GNU Image Manipulation Program (GIMP) is not available in the Graphics menu.

Workaround: Perform the following steps.

1. Open a terminal window.

2. Edit the /usr/share/applications/gimp-2.0.desktop file.

3. Change the Exec and TryExec lines to add the full path to the GIMP binary:

   TryExec=/usr/sfw/bin/gimp2.0 Exec=/usr/sfw/bin/gimp-remote-2.0 %u

Problems With Online Registration of StarOffice 7 Software (6208829)

You might be unable to complete the online registration of the StarOffice 7 software if the software cannot find Mozilla on the system. The software must be able to locate the Email and Calendar application to successfully send documents.

Workaround: Add /usr/sfw/bin to your PATH. Perform the following steps.

1. Open a terminal window.

2. Issue the following command:

   % export PATH=/usr/sfw/bin:$PATH

3. To start the StarOffice software, issue the following command:

   % soffice

4. Complete the StarOffice registration procedure.

Problems With Sound Recorder

The slide bar and the side counter do not work when the Sound Recorder is recording a new.wav file.

Workaround: None.

Volume Control Option Not Working

The option in the Volume Control panel application that enables you to start the Volume Control desktop applications does not work.

Workaround: None.

Problems When Using Keyboard Indicator (6245563)

Using the keyboard indicator might make the keyboard unusable when you switch between X servers.

Workaround: None. Do not use the Keyboard Indicator.

Certain View Options Might Cause File Manager to Fail (6233643)

The File Manager might fail if you use the following View options:

• View as Catalog

• View as Image Collection

Depending on the View options that you use, the following error messages might be displayed:

• The application nautilus has quit unexpectedly

• The Catalog view encountered an error while starting up

• The Image Collection view encountered an error while starting up

Workaround: None. Every time these problems occur, restart File Manager or click the Restart Application button on the crash dialog box.

Cannot Delete Files Outside of Home Directory (6203010, 5105006)

You can only delete files from your own home directory file system.

Workaround: To delete files outside your home directory file system, open a terminal window and use the command line.

Problems Creating Certain Types of Archives (5082008)

You cannot use Archive Manager to create the following types of archives:

• .arj

• .lha

• .bzip

• .lzop

• .zoo

Workaround: None.

Cannot Type Multibyte Characters in Text Editor 2.9.1 (4937266)

When you enable the Auto Indent function in the gedit text editor, you cannot type multibyte characters correctly.

Workaround: Disable the Auto Indent function. Perform the following steps in the text editor.

1. Choose Edit => Preferences.

2. In the Categories list, select Editor, then Auto Indent.

3. Deselect the Enable auto indentation option.

System Administration

This section describes system administration bugs in Solaris 10 OS.

Sun Patch Manager Tool 2.0 Not Compatible With Previous Versions

A system that runs the Sun Patch Manager Tool 2.0 can manage remote systems that run Patch Manager Tool, including Sun Patch Manager Tool 1.0.

However, a system with an earlier version of Patch Manager Tool cannot manage remote systems that run Patch Manager Tool 2.0. Earlier versions include the following:

• Sun Patch Manager Base Software 1.x

• Sun Patch Manager Tool 1.0

Common Information Model/Web Based Enterprise Management (CIM/WBEM) support for Patch Manager Tool does not exist in the Solaris 8 OS. Consequently, remote management with Patch Manager does not apply to Solaris 8 systems.

Sun Remote Services Net Connect Supported Only in the Global Zone

Sun Remote Services (SRS) Net Connect is supported only in the global zone. Error messages are displayed if you perform one of the following actions:

• You install SRS Net Connect in a local zone.

• SRS Net Connect is installed in the global zone at the time a local zone is created.

The error messages are as follows:

*** package SUNWcstu failed to install - 
interactive administration required:

Interactive request script supplied by package
pkgadd: ERROR: request script did not complete successfully

Installation of SUNWcstu was suspended (interaction required).
No changes were made to the system.  

*** package SUNWfrunc failed to install - 
interactive administration required:

Interactive request script supplied by package
pkgadd: ERROR: request script did not complete successfully

Installation of SUNWfrunc was suspended (interaction required).
No changes were made to the system.

Workaround: Ignore the error messages.

Error or Warning Messages Might Be Displayed While Installing Non-global Zones With the zoneadm Command

While installing a non-global zone by using the zoneadm command, error or warning messages might be displayed during package installation. The messages are similar to the following example:

Preparing to install zone zone1.
Creating list of files to copy from the global zone.
Copying 2348 files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize 790 packages on the zone.
Initialized 790 packages on zone.
Zone zone1 is initialized.

Installation of the following packages generated errors: 
SUNWjhrt SUNWmcc SUNWjhdev SUNWnsb SUNWmcon SUNWmpatchmgr

Installation of the following packages generated warnings: 
SUNWj3rt SUNWmc SUNWwbmc SUNWmga SUNWdclnt SUNWlvma SUNWlvmg 
SUNWrmui SUNWdoc SUNWpl5m SUNWpmgr

Problems about package installation are also recorded in /export/zone1/root/var/sadm/system/logs/install_log which contains a log of the zone installation.

Workaround: None.

The non-global zone can still be used even though these messages have been reported. Issues with package installation existed in earlier Solaris Express and Solaris 10 Beta releases. However, no notification about these problems was being generated. Beginning with this Solaris release, these errors are now properly reported and logged.

Solaris Product Registry Administration Utility Fails to Launch in a Zone (6220284)

If you attempt to launch the Solaris Product Registry administration utility in a zone, the attempt fails. During the zone installation, productregistry, the Solaris Product Registry database, is not duplicated in the zone. Consequently, the utility cannot run in a zone.

Workaround: As superuser, copy the productregistry database to the zone.

# cp /var/sadm/install/productregistry zone_path/var/sadm/install/

In the previous command, zone_path is the path to the root directory of the zone that you created.

patchadd Fails to Reapply Patches to Newly Installed Packages (6219176)

The patchadd command fails to reapply a patch under the following set of circumstances.

1. You patch a system that does not contain all the packages that are affected by the patch.

2. You later install the packages that were not installed when you applied the patch.

3. You reapply the patch to patch the newly installed packages.

The portion of the patch that applies to the package that you added later is not installed. A message that is similar to the following output is displayed.

patchadd ~tsk/patches/111111-01
Validating patches...

Loading patches installed on the system...

Done!

Loading patches requested to install.

Done!

The following requested patches are already installed on the system
Requested to install patch 111111-01 is already installed on the system.

No patches to check dependency. 

Workaround: Choose one of the following workarounds.

Workaround 1: If you have not created zones on your system, use the patchadd command with the -t option to patch the system.

# patchadd -t patch-ID

In the previous command, patch-ID is the ID of the patch you want to apply.

Workaround 2: If you have created zones on your system, follow these steps.

1. Back out the patch.

   # patchrm patch-ID

2. Install the additional packages that are not on the system but are affected by the patch.

   # pkgadd -d device pkgabbrev

   In the previous example, device specifies the absolute path to the package or packages you want to install. pkgabbrev specifies the abbreviated name of the package you want to install. You can specify multiple package names.

3. Reinstall the patch.

   # patchadd patch-ID

Non-Global Zones Created After Patching Global Zones Are Not Accessible by Remote Login Services (6216195)

If you create, and then patch, a global zone, remote login services are not enabled on any non-global zones you subsequently create. Examples of such remote services are rlogin and telnet. If you create a non-global zone after patching a global zone, you cannot log in remotely to the non-global zone. This issue affects systems that have been patched with patches that deliver or modify the SUNWcsr package.

Workaround: Choose one of the following workarounds.

Workaround 1: If you have not yet booted the non-global zone, follow these steps.

1. In the global zone, change to the /var/svc/profile directory in the non-global zone.

   global# cd zone_path/root/var/svc/profile

   In the previous example, zone_path is the path to the non-global zone. You can determine the path to the non-global zone by typing the following command in a global zone.

   global# zonecfg -z zonename info zonepath

2. Remove the inetd_services.xml profile.

   global# rm inetd_services.xml

3. Create a symbolic link for inetd_services.xml that points to the inetd_generic.xml profile.

   global# ln -s inetd_generic.xml inetd_services.xml

4. Boot the non-global zone.

   For more information about how to boot a zone, see System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

Workaround 2: If you have already booted the non-global zone, follow these steps.

1. Perform the steps that are listed in the previous workaround.

2. In the non-global zone, enable the services that are listed in the /var/svc/profile/inetd_services.xml profile.

   my-zone# svccfg apply /var/svc/profile/inetd_services.xml

3. Reboot the non-global zone.

   my-zone# reboot

Workaround 3: Before you create zones on the system, apply the appropriate patch for your platform.

• For SPARC based systems, apply patch ID 119015-01, or a later version.

• For x86 based systems, apply patch ID 119016-01, or a later version.

Cannot Delete Existing Diskless Clients From the System (6205746)

If you use the smdiskless command to delete a diskless client, the command fails. The diskless client is not removed from the system databases. The following error message is displayed:

Failing with error EXM_BMS.

Workaround: Unshare the /export partition before adding the client.

Net Connect 3.1.1 Installation Fails (6197548)

Installation of Net Connect 3.1.1 fails if you select the product at the beginning of a full Solaris 10 installation. This failure occurs when you are installing by using the Solaris 10 Operating System DVD. At the completion of the OS installation, the following error message is recorded in the Net Connect install log in /var/sadm/install/logs/:

Installation of SUNWSRSPX failed.
Error: pkgadd failed for SUNWsrspx 
Install complete. Package: SUNWsrspx

Workaround: After the OS installation is completed, follow these steps:

1. Insert the Solaris 10 Operating System DVD or the Solaris 10 Software - CD 4.

2. Change to the directory of the Net Connect product.

3. Run the Net Connect installer.

To download the latest version of the Sun Net Connect software and release notes, go to the Sun Net Connect portal at https://srsnetconnect.sun.com.

x86: Default C Library Might Cause Boot Failure When You Install Solaris Flash Archives (6192995)

A boot failure that involves the Solaris Flash archive might occur under the following circumstances:

• You create a Solaris Flash archive on a system that is using a libc C library with certain hardware-support capabilities.

• You install the archive on a clone system that has different hardware-support capabilities.

When you attempt to boot the clone system, the following error message is displayed:

WARNING: init exited with fatal signal 9; restarting.

Workaround: Follow these steps.

1. Before you create the archive, unmount the /lib/libc.so.1 library on the master system.

   # umount /lib/libc.so.1

   This command enables the master system to use the basic version of the libc C library.

2. Create the Solaris Flash archive on the master system.

   For more information about how to create Solaris Flash archives, see the Solaris 10 Installation Guide: Solaris Flash Archives (Creation and Installation).

3. Mount the /lib/libc.so.1 library on the master system.

   # mount -O -F lofs /lib/libc.so.1 /usr/lib/libc/libc_hwcap2.so.1

4. Install the Solaris Flash archive on the clone system.

   For more information about how to install Solaris Flash archives, see the Solaris 10 Installation Guide: Solaris Flash Archives (Creation and Installation).

SPARC: smosservice delete Command Does Not Successfully Remove All Directories (6192105)

If you use the smosservice delete command to remove a diskless client service, the command does not successfully remove all the service directories.

Workaround: Follow these steps.

1. Make sure that no clients exist that use the service.

   # unshare /export/exec/Solaris_10_sparc.all # rm -rf /export/exec/Solaris_10_sparc.all # rm -rf /export/exec/.copyofSolaris_10_sparc.all # rm -rf /export/.copyofSolaris_10 # rm -rf /export/Solaris_10 # rm -rf /export/share # rm -rf /export/root/templates/Solaris_10 # rm -rf /export/root/clone/Solaris_10 # rm -rf /tftpboot/inetboot.sun4u.Solaris_10

2. Remove the following entry from the /etc/bootparams file.

   fs1-24 boottype=:os

   ---

   Note –

   Remove this entry only if this file server does not provide functions or resources for any other services.

   ---

3. Remove the following entry from the /etc/dfs/dfstab file.

   share -F nfs -o ro /export/exec/Solaris_8_sparc.all/usr

4. Modify the /var/sadm/system/admin/services/Solaris_10 file.

   • If the file server is not Solaris_10, delete the file.

   • If the file server is Solaris_10, remove all entries after the first three lines. The deleted lines indicate the service USR_PATH and SPOOLED ROOT packages in /export/root/templates/Solaris_10 and the supported platforms.

patchadd Command Does Not Support Installing Patches From an NFS Server (6188748)

If you use the patchadd command to install patches across the NFS from another system, the command fails. The following example shows a patchadd operation that failed and the error message that is displayed:

Validating patches...

Loading patches installed on the system...
[...]
Loading patches requested to install.
[...]
Checking patches that you specified for installation.
[...]
Approved patches will be installed in this order:
[...]
Checking local zones...
[...]
Summary for zones:
[...]
Patches that passed the dependency check:
[...]

Patching global zone
Adding patches...

 Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

 Patch Patch_ID has been successfully installed.
See /var/sadm/patch/Patch_ID/log for details
 Patch packages installed:
   SUNWroute
[...]

Adding patches...
 The patch directory
 /dev/.SUNW_patches_0111105334-1230284-00004de14dcb29c7
 cannot be found on this system.  

[...]

Patchadd is terminating.

Workaround: Manually copy all of the patches to be installed from the NFS server to the local system first. Then use the patchadd command to install the patches from the directory on the local system where the patches were copied.

lucreate Command Does Not Create RAID-1 Volumes (5106987)

If you use the lucreate command to create RAID-1 volumes (mirrors) that do not have device entries in the /dev/md directory, the command fails. You cannot mirror file systems with the lucreate command unless you first create the mirrors with Solaris Volume Manager software.

Workaround: Create the mirrored file systems with Solaris Volume Manager software, then create the new boot environment with the lucreate command.

For more information about the lucreate command, see the lucreate(1M) or Solaris 10 Installation Guide: Solaris Live Upgrade and Upgrade Planning.

For more information about how to create mirrored file systems with Solaris Volume Manager software, see Solaris Volume Manager Administration Guide.

SPARC: Panics That Occur During Suspend and Resume Cycles Might Cause the System to Hang (5062026)

A system panic that occurs while you are performing a suspend-and-resume (cpr) cycle might cause the system to hang. More typically, this problem is observed in Sun Blade 2000 workstations that have the XVR-1000 graphics accelerator installed. Rarely, other SPARC based systems might similarly hang during a panic. When the panic occurs, the core dump is not saved, and no prompt appears on the console. The problem might be more prevalent if the kernel debugger (kadb) is active.

Workaround: To restore the system to a usable state, manually reboot the system.

SPARC: Stopping the System by Using Keyboard Sequences Might Cause a System Panic (5061679)

If you attempt to stop the system by pressing keyboard sequences such as Stop-A or L1-A, the system might panic. An error message similar to the following example is displayed:

panic[cpu2]/thread=2a100337d40: pcisch2 (pci@9,700000): 
consistent dma sync timeout

Workaround: Do not use keyboard sequences to force the system to enter OpenBoot PROM.

Using the ipfs Command With -W Option Fails (5040248)

The ipfs command saves and restores information about the state of the Network Address Translation (NAT) and packet-filtering state tables. This utility prevents network connections from being disrupted if the system reboots. If you issue the command with the -W option, ipfs fails to save the kernel state tables. The following error message is displayed:

state:SIOCSTGET: Bad address

Workaround: None.

Permissions for Mount Points Not Preserved in Created Boot Environment (4992478)

When you create a new boot environment by using lucreate, the permissions are not preserved for the file system mount points. Consequently, some user processes fail. If you create the new boot environment in a clustering environment, the cluster brings down the nodes, then boots from the CD-ROM to repair the permissions for the mount points.

Workaround: Follow these steps.

1. Create the new boot environment.

   # lucreate -n newbe -m /:c0t0d0s0:ufs -m /var:c1t0d0s0:ufs -m /usr:c2t0d0s0:ufs

   In the previous example, the lucreate command creates the newbe boot environment. This example defines the following file systems and mount points.

   • The root (/) file system is mounted on c0t0d0s0.

   • The var file system is mounted on c1t0d0s0.

   • The usr file system is mounted on c2t0d0s0.

2. Mount the root file system of the new boot environment.

   # mount /dev/dsk/c0t0d0s0 /mnt

3. For each mount point that is defined for the boot environment, change the permissions to 755.

   # chmod 755 /mnt/var # chmod 755 /mnt/usr

4. Unmount the root file system.

   # umount /dev/dsk/c0t0d0s0

kill -HUP Does Not Always Cause the Agent to Reread the snmpd.conf Configuration File (4988483)

After modifying the contents of snmpd.conf, you can issue the command kill -HUP snmp Process ID. This command stops the snmp process. The command then sends a signal to the System Management Agent's master agent (snmpd) to reread snmpd.conf and implement the modifications that you introduced. The command might not always cause the master agent to reread the configuration file. Consequently, using the command might not always activate modifications in the configuration file.

Instead of using kill -HUP, restart the System Management Agent after adding modifications to snmpd.conf. Perform the following steps:

1. Become superuser.

2. Type the following command:

   # /etc/init.d/init.sma restart

x86: Pressing the F4 Key During BIOS Bootup Fails to Boot the Service Partition (4782757, 5051157)

You are booting a Sun LX50 which has a Service partition and Solaris 10 OS on x86 is installed. Pressing the F4 function key to boot the Service partition, when given the option, causes the screen to go blank. The system then fails to boot the Service partition.

Workaround: Do not press the F4 key when the BIOS Bootup Screen is displayed. After a time-out period, the Current Disk Partition Information screen is displayed. Select the number in the Part# column that corresponds to type=DIAGNOSTIC. Press the Return key. The system boots the Service partition.

Solaris WBEM Services 2.5 Daemon Cannot Locate com.sun Application Programming Interface Providers (4619576)

The Solaris WBEM Services 2.5 daemon cannot locate providers that are written to the com.sun.wbem.provider interface or to the com.sun.wbem.provider20 interface. Even if you create a Solaris_ProviderPath instance for a provider that is written to these interfaces, the Solaris WBEM Services 2.5 daemon does not locate the provider.

Workaround: To enable the daemon to locate such a provider, stop and restart the Solaris WBEM Services 2.5 daemon.

# /etc/init.d/init.wbem stop

# /etc/init.d/init.wbem start

If you use the javax API to develop your provider, you do not need to stop and restart the Solaris WBEM Services 2.5 daemon. The Solaris WBEM Services 2.5 daemon dynamically recognizes javax providers.

Some com.sun Application Programming Interface Method Invocations Fail Under XML/HTTP Transport Protocol (4497393, 4497399, 4497406, 4497411)

If you choose to use the com.sun application programming interface rather than the javax application programming interface to develop your WBEM software, only Common Information Model (CIM) remote method invocation (RMI) is fully supported. Other protocols, such as XML/HTTP, are not guaranteed to work completely with the com.sun application programming interface.

The following table lists examples of invocations that execute successfully under RMI but fail under XML/HTTP:

Cannot Modify File-System Mount Properties With Solaris Management Console Mounts and Shares Tool (4466829)

The Solaris Management Console Mounts and Shares tool cannot modify mount options on system-critical file systems such as root (/), /usr, and /var.

Workaround: Choose one of the following workarounds:

• Use the remount option with the mount command.

  # mount -F file-system-type -o remount, additional-mount-options \ device-to-mount mount-point

  ---

  Note –

  Mount property modifications that are made by using the -remount option with the mount command are not persistent. In addition, all mount options that are not specified in the additional-mount-options portion of the previous command inherit the default values that are specified by the system. See the man page mount_ufs(1M) for more information.

  ---

• Edit the appropriate entry in the /etc/vfstab file to modify the file-system mount properties, then reboot the system.