Solaris 10 10/09 Release Notes Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A.
Copyright 2009 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more U.S. patents or pending patent applications in the U.S. and in other countries. U.S. Government Rights – Commercial software.
Contents Preface ...................................................................................................................................................13 1 Installation Issues ................................................................................................................................17 General Information ........................................................................................................................... 17 BIOS and Firmware Upgrade ................
Contents x86: Serial Consoles of Some Sun Fire Systems Do Not Work (6208412) ............................. 32 Solaris Installation GUI Program Might Fail on Systems With Existing x86 fdisk Boot Partitions (6186606) .................................................................................................................... 32 Installation Bugs ..................................................................................................................................
Contents (6638175) ...................................................................................................................................... 47 Issues With DSR Upgrade With Zones (6616788) ................................................................... 47 Solaris Trusted Extensions Upgrade Issues (6616585) ............................................................ 47 System Cannot Communicate With ypbind After Upgrade (6488549) ...............................
Contents Access Problems Between Solaris NFSv4 Clients and NFSv4 Servers ................................... 63 Using mkfs Command to Create File System Might Fail on Very Large Disks (6352813) .. 63 System Crash Dump Fails on Devices Greater Than 1 TByte (6214480) .............................. 64 Hardware–Related Issues and Bugs .................................................................................................. 64 Reduced ixgbe Driver Performance in Solaris 10 10/09 (6885903) .............
Contents Wnn8 Japanese Input Method .................................................................................................... 79 Input Method Cannot Be Enabled With Primary Administrator Rights (6475081) ........... 79 New ChuYin Input Method Not Supported in Upgrade to IIIMF rev.12 (6492129) ........... 80 AltGr Does Not Work As Mode Switcher in Some Russian Locales (6487712) ................... 80 Arabic Text Not Appearing in ar Locales .........................................................
Contents Sun Java Desktop System .................................................................................................................... 94 Email and Calendar ..................................................................................................................... 94 Login Issues ................................................................................................................................... 95 Help System ..........................................................
Contents Known Software and Hardware Bugs ...................................................................................... 109 Dynamic Reconfiguration on Sun Fire Midrange Systems .......................................................... 110 Minimum System Controller Firmware ................................................................................. 110 Known DR Software Bugs .........................................................................................................
Contents CacheFS ....................................................................................................................................... 123 sdtudctool ................................................................................................................................. 124 SPARC: cg6 Driver for SBus Graphics Cards .......................................................................... 124 ctlmp and ctlconvert_txt ...............................................................
Contents Configuration Assistant's fp Plug-in Hardware Options ...................................................... 130 Device Allocation Interfaces For the Basic Security Module ................................................ 130 Obsolete Device Driver Interfaces ........................................................................................... 130 Device Management Entries in power.conf ..........................................................................
Contents Documents on the Software Supplement CD ................................................................................ 145 System Administration Guide: Basic Administration .................................................................. 145 Managing Diskless Clients (Tasks) .......................................................................................... 145 Solaris 10 Start Here and Solaris 10 Installation Guides ...............................................................
Preface This document describes the Solaris 10 10/09 operating system. For information about the Solaris 10 3/05, Solaris 10 3/05 HW1, Solaris 10 3/05 HW2, Solaris 10 1/06, Solaris 10 6/06, Solaris 10 11/06, Solaris 10 8/07, Solaris 10 5/08, Solaris 10 10/08, and Solaris 10 5/09 releases, see the “Solaris 10 5/09 Release Notes”, Sun part number 820–7273. The Solaris 10 10/09 Release Notes contain installation and runtime problem details.
Preface ■ Solaris 10 10/09 Installation Guide: Planning for Installation and Upgrade ■ Solaris 10 10/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning ■ Solaris 10 10/09 Installation Guide: Network-Based Installations ■ Solaris 10 10/09 Installation Guide: Custom JumpStart and Advanced Installations ■ Solaris 10 10/09 Patch List ■ Solaris 10 System Administrator Collection For information on current CERT advisories, see the official CERT web site at http://www.cert.org.
Preface Sun Welcomes Your Comments Sun is interested in improving its documentation and welcomes your comments and suggestions. To share your comments, go to http://docs.sun.com and click Feedback. Typographic Conventions The following table describes the typographic conventions that are used in this book. TABLE P–1 Typographic Conventions Typeface Meaning Example AaBbCc123 The names of commands, files, and directories, and onscreen computer output Edit your .login file.
Preface TABLE P–2 16 Shell Prompts (Continued) Shell Prompt Bourne shell and Korn shell $ Bourne shell and Korn shell for superuser # Solaris 10 10/09 Release Notes • October 2009
1 C H A P T E R 1 Installation Issues This chapter provides information and describes issues that relate to the installation of the Solaris 10 Operating System. Note – To see which bugs and issues are fixed and no longer apply to the Solaris 10 10/09 software, refer to Appendix A, “Table of Integrated Bug Fixes in the Solaris 10 Operating System.” General Information This section provides general information such as behavior changes in Solaris 10 OS.
General Information ■ ■ ■ 384 Mbytes of minimum memory 512 Mbytes is the recommended memory For ZFS root file systems: ■ ■ 786 Mbytes of minimum memory 1 Gbyte of memory is recommended for overall ZFS performance Changes in Upgrade Support for Solaris Releases Starting with the Solaris 10 8/07 release, for SPARC systems, you can upgrade the Solaris OS only from the following releases: ■ ■ ■ Solaris 8 OS Solaris 9 OS Solaris 10 OS For x86 systems, you can upgrade the Solaris OS only from the following
Before You Begin Before You Begin This section contains critical installation issues that you need to be aware of before installing or upgrading to Solaris 10 OS. These issues might have an impact that would prevent installation or upgrades from completing successfully. If bugs in this section apply to your system, you might need to perform the recommended workarounds before you install or upgrade.
Before You Begin ■ To upgrade your current Solaris 10 OS to the Solaris 10 10/09 release by using Solaris Live Upgrade, apply the following patches: ■ ■ For SPARC systems– 137321-01 or later For x86 systems– 137322-01 or later These patches provide the new p7zip functionality. Solaris Live Upgrade requires p7zip functionality in order to support upgrade to Solaris 10 10/09.
Before You Begin Upgrading a Solaris Trusted Extensions System That is Configured with Labeled Zones Solaris systems that are configured with Solaris Trusted Extensions use non-global zones. Upgrading these systems is the same as upgrading a Solaris system that uses zones, and has the same issues. ■ ZFS Zones– Solaris systems with ZFS zones cannot currently be upgraded. For Solaris Trusted Extensions systems with ZFS zones, the alternative is to recreate the zones.
Before You Begin 1. lumount the new boot environment: # lumount 2. Change to the /var/svc/profile directory of the boot environment: # cd /.alt./var/svc/profile 3. Link the name_service.xml link as appropriate. For example: # ln -fs ns_ldap.xml name_sevice.xml 4. luumount the boot environment: # luumount Note – If the system is booted without performing the steps mentioned above, you will need to manually start the appropriate name service-related SMF client services.
Before You Begin Additional Procedures Required When Installing GNOME Display Manager Patches for Solaris 10 10/09 Release The following patches are applied to resolve problems that were reported in CR 6277164 and CR 6214222: ■ ■ Patch ID 119366-05 for SPARC based systems Patch ID 119367-05 for x86 based systems The sections that follow provide further steps that you must perform to completely resolve the reported problems.
Before You Begin 3. From Lay Out File Systems, select Modify. The disk layout screen is displayed. 4. Type /var in the File System column for a specific slice, then click Apply. The installation program suggests a default size for the /var file system. 5. Edit the Size column entry for the /var file system to twice the disk space size. For example, if the installation program assigns 40 Mbytes of space, change the Size value to 80. 6. Complete the installation.
Before You Begin If you perform this upgrade, your HP system can no longer boot. Only a blank black screen with a flashing underscore cursor is displayed. Workaround: Do not upgrade HP Vectra XU Series systems with the latest BIOS Version GG.06.13 to the Solaris 10 release. This version no longer supports these systems. You can still boot your system by using the boot diskette or boot CD because the boot paths do not use the hard disk code.
Before You Begin Note – Upgrading firmware on both SPARC and x86 systems can lead to significant performance improvements. See the Firmware section on the BigAdmin Patching Hub at http://www.sun.com/bigadmin/patches/overview.jsp. See also, the FAQ at http://www.sun.com/bigadmin/patches/firmware/faq.jsp. Solaris Management Console 2.1 Software Is Not Compatible With Solaris Management Console 1.0, 1.0.1, or 1.0.2 Software Solaris Management Console 2.
Before You Begin Note – Do not remove any package that has “Solaris Management Console 2.1” in its description. For example, SUNWmc.2 might indicate Solaris Management Console 2.1 software. If the pkginfo output displays multiple versions of Solaris Management Console 1.0 packages, use the pkgrm command to remove both packages. Remove the original package. Then, remove the package that has been appended with a number. For example, if the SUNWmcman and SUNWmcman.
Before You Begin # # # # pkgrm pkgrm pkgrm pkgrm SUNWwbmc SUNWmc SUNWmcc SUNWmccom 2. Insert the Solaris 10 Software - 4 CD into your CD-ROM drive. Type the following in a terminal window: # # cd /cdrom/cdrom0/Solaris_10/Product # pkgadd -d . SUNWmccom SUNWmcc SUNWmc SUNWwbmc SUNWmcex SUNWmcdev \ SUNWmgapp SUNWmga SUNWdclnt SUNWlvmr SUNWlvma SUNWlvmg SUNWpmgr \ SUNWrmui All previous Solaris Management Console versions are removed. The Solaris Management Console 2.1 software is now functional.
Before You Begin 3. To select the disk whose fdisk partition you want to change, type the disk's number. 4. From the list of Format options, select fdisk. The disk's partition information and a list of fdisk options are displayed. 5. To change the disk's layout, choose one of the following: ■ ■ ■ To specify a different active partition, press 2. To add another disk partition, press 1. To delete an unused partition, press 3. 6. To save your changes and exit the fdisk menu, press 5. 7.
Before You Begin x86: Sun Java Workstations 2100Z Might Panic When Booting From Solaris 10 Operating System DVD (6214356) The DVD combo-drive firmware in a Sun Java Workstation 2100Z might cause a system panic. The panic occurs when you boot the workstation from the Solaris 10 Operating System DVD.
Before You Begin Note – The screen might display more than one attachment type for CD-ROM, for example, if your system has multiple optical drives. In such cases, you might need to open the system case to determine the DVD drive's point of attachment. Make sure that you select the correct attachment type that applies to the DVD drive. 3. After selecting the correct CD-ROM attachment type, press Enter. The next screen appears with Type:[Auto] automatically selected. 4.
Before You Begin x86: Serial Consoles of Some Sun Fire Systems Do Not Work (6208412) The serial console (ttya) on the following Sun Fire systems does not work by default: ■ ■ ■ ■ Sun Fire V20z Sun Fire V40z Sun Fire V60x Sun Fire V65x To use the serial console, you must manually configure the system's BIOS. Workaround: This workaround requires your system to have a Sun keyboard and a display monitor. Follow these steps: 1. 2. 3. 4. 5. Boot the machine.
Installation Bugs Workaround 2: If you use the Solaris installation GUI program, follow these steps. 1. Begin the installation. 2. At the prompt to select an installation type, select Custom Install. The custom installation panels prompt you for information about the locales, software, and disks that you want to install. 3. Answer the questions on the screens as appropriate for your system. 4. On the Fdisk Selection screen, check the disk that contains the x86boot partition. 5.
Installation Bugs The following error message is displayed: Can’t open boot_archive Fast Data Access MMU Miss %TL:1 %TT:68 %TPC:f0009ca4 %TnPC:f0009ca8 %TSTATE:8840001600 %PSTATE:16 ( IE:1 PRIV:1 PEF:1 ) DTLB-MATCH:ffffffffffffe ( VA:-2000 CTX:0 ) Workaround: Use Solaris Live Upgrade in place of DSR upgrade for change disk allocation.
Installation Bugs install_type upgrade root_device rootdisk.s0 backup_media local_filesystem /backup layout_constraint rootdisk.s0 changeable layout_constraint rootdisk.s7 available The DSR upgrade fails with the following error message: Auto-layout could not determine how to reallocate space on the file systems with the constraints you specified. Try other constraints Workaround: Label the rootdisk.s1 and rootdisk.s6 slices as “changeable”.
Installation Bugs Localized Installation Note Localized Solaris installer always runs in the EUC or ISO8859 locales. Thus, the install log is written in EUC or ISO8859 encoding. Workaround: While performing localized CLI (command line interface) install through a terminal, the locale on the terminal must be EUC or ISO8859 locale. SPARC: WAN Boot Installation Fails for Solaris 10 10/09 The installation fails, when installing WAN boot image from Solaris 10 10/09 release.
Installation Bugs # /boot/solaris/bin/root_archive unpackmedia remote_install_dir_path \ destination_dir remote_install_dir_path Specifies the path to the network installation image on the current Solaris release. destination_dir Specifies the path to the directory to contain the unpacked boot archive. 5. On the current Solaris release, patch the unpacked boot archive.
Installation Bugs bootadm: biodev command failed for disk: /dev/dsk/. bootadm: 1s_bootdisk(): cannot determine BIOS disk ID "hd?" for disk: /dev/dsk/ bootamd: get_grubroot(): cannot get (hd?, ?,?) for menu. menu not on bootdisk: /dev/rdsk/ Workaround: Choose one of the following workarounds: ■ Install a Solaris Flash archive from the Solaris 10 10/08 release or later.
Installation Bugs Workaround: Use shorter locale names such as th_TH, ko, ko.UTF-8, zh_TW, zh, zh.GBK, and zh.UTF-8, instead of longer locale names, PRODRM Has Problems Deleting prodreg Entry For Solaris Trusted Extensions (6616592) While upgrading Solaris Trusted Extensions from the Solaris 10 11/06 or Solaris 10 8/07 release to the Solaris 10 10/08, Solaris 10 5/09 release or the current Solaris 10 10/09 release, the prodreg entry for Solaris Trusted extensions is not removed.
Installation Bugs Sun Upgrade Detailed Patch Analysis Panel Not Scrollable (6597686) During a Solaris upgrade, if you select Detailed Analysis to see the patches that will be removed, the panel that displays the patches is not scrollable. The complete list of patches to be removed cannot be viewed. Workaround: Run the analyze_patches scripts manually: # cd /Solaris_10/Misc # .
Installation Bugs System panic: BAD TRAP: type=31 rp=2a101d31200 addr=8 mmu_fsr=0 occurred in module "pcie" due to a NULL pointer dereference Workaround: Before you install the Solaris 10 10/09 OS on a PCI Express (PCIe) based SPARC system, check if you have modified the driver.conf files as described below: 1. Change to the /kernel/drv directory. 2. Check if the parent attribute is set in the driver.conf file.
Installation Bugs x86: Install Hangs on Systems With 512 Mbyte of Memory (6423854) Installations can run out of memory and hang on 512-Mbyte systems under the following conditions: ■ ■ You install using a network installation image of the OS. The Solaris installation program is in a windowing environment: ■ The graphical user interface (GUI). ■ The -text option or “3. Solaris Interactive Text (Desktop session)” in the menu below.
Installation Bugs x86: Installation From CD Media Appears to Hang After Reboot Selection (6270371) A problem might occur when you are using the Solaris installation program and are using CD media. After the installation of the Solaris software from the Solaris 10 10/09 Software CD - 4, the following prompt is displayed: Press Reboot now to continue. If you press Reboot, the system might not respond. The installation is successful. However, the error prevents the installation program from exiting normally.
Upgrade Issues and Bugs 4. Stop the Java process. # pkill -9 java The system reboots without prompting for the CD media. x86: System Fails to Boot After Custom JumpStart Installation (6205478) If you use the Custom JumpStart installation method to install on an x86 based system, and explicitly configure slice 2 as the overlap slice in the profile, an error occurs. The system does not reboot successfully after the installation is completed.
Upgrade Issues and Bugs Audio Devices Unavailable After Upgrade on Solaris Trusted Extensions Systems (6866818) On systems configured for Solaris Trusted Extensions, audio devices are unavailable for allocation at user labels, after upgrading from the Solaris 10 5/08 or earlier releases to the Solaris 10 10/08 or later releases. This bug occurs because the /etc/logindevperm changes are lost during the upgrade. No error message is displayed. Workaround: After upgrading, manually merge the /etc/logindevperm.
Upgrade Issues and Bugs 4. Re-install the SUNWsmbar package: #pkgadd SUNWsmbar shutdown Command Might Cause the System to Hang After Upgrade (6751843) The shutdown command might cause the system to hang after it is upgraded to the Solaris 10 10/09 release. The hang occurs while the svc.startd daemon halts system services. The Sun Java Web Console debug log file at /var/log/webconsole/console/console_debug_log displays if the web console service is cycling, starting and stopping.
Upgrade Issues and Bugs SPARC: Upgrading with Solaris Live Upgrade From Solaris 8 and Solaris 9 Releases Fails (6638175) Upgrading to the Solaris 10 10/09 release using Solaris Live Upgrade, from the previous Solaris 8 and Solaris 9 releases fails. The install images compression file is now unzipped by using the 7za utility. The SUNWp7zip package is not included in the Solaris 8 and 9 releases. As a result, Solaris Live Upgrade fails.
Upgrade Issues and Bugs SUNWtgnome-l10n-ui-sv SUNWtgnome-l10n-ui-es SUNWtgnome-l10n-doc-ko SUNWtgnome-l10n-ui-ptBR SUNWtgnome-l10n-ui-ja SUNWtgnome-l10n-ui-zhTW SUNWtgnome-l10n-ui-zhCN SUNWtgnome-l10n-ui-fr SUNWtgnome-l10n-ui-de SUNWtgnome-l10n-ui-ru System Cannot Communicate With ypbind After Upgrade (6488549) This bug occurs during an upgrade from Solaris 10 Hardware 2 release to the current Solaris 10 10/09 release. In the Solaris 10 Hardware 2 release, the name_service.
Upgrade Issues and Bugs Note – The fix for CR 6411084, the SUNWcsr install or postinstall script, creates the correct link only if name_service.xml is not a link file. If name_service.xml is already a symbolic link file, as in the Solaris 10 Hardware 2 release, the fix for CR 6411084 will not work.
Upgrade Issues and Bugs # zlogin myzone svcs -x svc:/system/filesystem/local:default (local file system mounts) State: maintenance since Wed May 24 13:18:06 2006 Reason: Start method exited with $SMF_EXIT_ERR_FATAL. See: http://sun.com/msg/SMF-8000-KS See: /var/svc/log/system-filesystem-local:default.log Impact: 18 dependent services are not running. (Use -v for list.) Workaround: Reboot the non-global zone from the global zone.
Upgrade Issues and Bugs For example, if you run the following command, the progress bar should be displayed after you see the following output: Running installer on BE s10u1. However, the bar fails to appear. # luupgrade -i -n s10u1 -s /net/installsrv/export/s10u1 -O "-nodisplay -noconsole" Validating the contents of the media /net/installsvr/export/s10u1. The media is a standard Solaris media. The media contains a standard Solaris installer. The media contains Solaris 3 version 10. Mounting BE s10u1.
Upgrade Issues and Bugs uninstall_OpenGL_1_3.class uninstall_OpenGL_1_2_3.class uninstall_Netra_ct_Platform_1_0.class uninstall_Netra_t11xx_Alarms_2_0.class uninstall_Netscape_6_2_3.class uninstall_Netscape_6_2_1_Beta.class uninstall_PC_launcher_1_0_2.class uninstall_PC_launcher_1_0_1_PCfileviewer_1_0_1.class uninstall_RSC_2_2_2.class uninstall_RSC_2_2_1.class uninstall_RSC_2_2.class uninstall_ShowMeTV_1_3.class uninstall_Solaris_9_French_Localization.class uninstall_Solaris_9_German_Localization.
Additional Installation Issues uninstall_Web_Start_Wizards_SDK_3_0_1.class uninstall_Web_Start_Wizards_SDK.class uninstall_XML_Libraries_2_4_12.class Workaround: After you upgrade the system, manually remove the obsolete uninstallers in the /var/sadm/prod directory. Additional Installation Issues This section describes issues that are related to the installation of the Solaris OS.
Additional Installation Issues ■ ■ SUNWstaroffice-lang* where lang = es, fr, de, sv, or it SUNWstarsuite-lang* where lang = ja, ko, zh-CN, or zh-TW Additional Related Locales Might Be Installed When you select a locale for your installation, additional related locales might also be installed.
2 C H A P T E R 2 Solaris Runtime Issues This chapter describes runtime issues that are known to be problems. Note – To see which bugs and issues are fixed and no longer apply to the Solaris 10 10/09 software, refer to Appendix A, “Table of Integrated Bug Fixes in the Solaris 10 Operating System.” Common Desktop Environment The following bugs in Solaris 10 OS apply to the Common Desktop Environment (CDE).
File Systems 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.
File Systems zoneadm attach Fails and Mount Operation is Invalid for Branded Zones (6800618) Attach operation fails on branded zones, although it succeeds on native (Solaris 10) zones. The following error message is displayed: zone mount operation is invalid for branded zones. Cannot generate the information needed to attach this zone. Workaround: Use the attach -F command for non-native branded zones.
File Systems grub edit> kernel /platform/i86pc/multiboot kernel/unix Note – Changes made by editing the GRUB menu at boot time do not persist over system reboots. For more information, see “Modifying Boot Behavior on x86 Based Systems” in System Administration Guide: Basic Administration. zpool attach Command Does Not Copy bootblock Information (6668666) If you use the zpool attach command to add a disk to a ZFS root pool, the bootblock information is not copied to the newly added disk.
File Systems gda: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0 (Disk0): Error for command ’read sector’ Error Level: Informational gda: [ID 107833 kern.notice] Sense Key: aborted command gda: [ID 107833 kern.notice] Vendor ’Gen-ATA ’ error code: 0x3 scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0): timeout: abort request, target=0 lun=0 scsi: [ID 107833 kern.
File Systems 9. At the end of the installation, reboot the system. Repeat steps 1 through 7. 10. To make this change permanent so that the above steps do not need to be repeated for subsequent boots, do the following: Become the super user, when the system boot is completed. 11. Open the /etc/system file. 12. Add the following line: set use_mp = 0 ■ Workaround 5: Disable microcode update. Type the following command: # mv /platform/i86pc/ucode /platform/i86pc/ucode.
File Systems ■ ■ ■ ■ 6361650 6343113 6343039 6742203 fdisk -E Can Sweep Disk Used by ZFS Without Warning (6412771) If you use the fdisk -E command to modify a disk that is used by a ZFS storage pool, the pool becomes unusable and might cause an I/O failure or system panic. Workaround: Do not use the fdisk command to modify a disk that is used by a ZFS storage pool. If you need to access a disk that is used by a ZFS storage pool, use the format utility.
File Systems If you attempt to run the ZFS Administration application on a system without the embedded_su patch, you will only be able to browse your ZFS configuration. The following error message is displayed: /usr/lib/embedded_su: not found Workaround: Add the embedded_su patch (119574-02) to the system that runs a pre-Solaris 10 6/06 release.
File Systems ■ ■ 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.
Hardware–Related Issues and Bugs The following error message is displayed: With 15625 sectors per cylinder, minimum cylinders per group is 16. This requires the fragment size to be changed from 1024 to 4096. Please re-run mkfs with corrected parameters. Workaround: Use the newfs command instead. Or, assign a larger fragment size, such as 4096, when you use the mkfs command.
Hardware–Related Issues and Bugs 2. Reboot the system. ZFS root pool Requires Maintenance After Every Reboot (6856341) After reboot the ZFS root pool comes up in degraded mode. A mirrored root pool that might be impacted by this issue will contain disk devices that use different device drivers and the second driver isn't loaded during the boot process. A symptom of this issue is when the system is rebooted, the pool state is DEGRADED because both device drivers are not loaded at the same time.
Hardware–Related Issues and Bugs This bug affects Dell PowerEdge R610 and R710 servers. Workaround: Perform the following steps: 1. 2. 3. 4. 5. Use more than 1 Gbyte of RAM. Create a hostname.bnxX for each interface. Reboot your system. Download and install the latest BNX driver 4.6.2. Modify the bnx.conf file to use the default setting for tx_descriptor_count. x64: PCI Subsystem ID Changes in ConnectX Firmware 2.6.0 From Mellanox (6810093) Upgrading the ConnectX firmware to version 2.6.
Hardware–Related Issues and Bugs c. Search for lines that contain ibd and hermon, and delete those lines. d. Save the changes and close the file. 3. Remove the entries in the /dev directory: rm /dev/ibd?* 4. Reboot the system.
Hardware–Related Issues and Bugs ::bp pcie‘pcie_initchild :c pcie_aer_ce_mask/W 11C1 :d all :c When the system comes up append the following line to the /etc/system file to make the changes permanent: set pcie:pcie_aer_ce_mask=0x11C1 x86: i86_mwait Work Does Not Function as Designed (6736444) Systems with the Intel Xeon Processor MP 7400 series running the Solaris 10 10/09 OS might experience reduced performance and increased power consumption under light utilization.
Hardware–Related Issues and Bugs 4. Extract the cxflash utility from the .tar file: # tar -xvf ib_updates_3_s10u6.i386.tar usr/sbin/cxflash This will extract the relative path below your working directory: # ls -lR usr usr: total 2 drwxrwxrwx 2 staff staff 512 Mar 9 09:20 sbin usr/sbin: total 88 -rwxr-xr-x staff 44976 Jan 26 13:39 cxflash 1 staff 5. Copy the cxflash file to /usr/sbin. This utility can be used to flash firmware onto hermon and ConnectX HCAs.
Hardware–Related Issues and Bugs ncp-threads-per-core=6; USB Floppy Drive Fails to Mount (6650724) Floppy disks are not automatically mounted when inserted into USB floppy drives. No error message is displayed. The pcfs file system on the floppy disk is not accessible. Workaround: The file system on the floppy disk can be mounted manually by running the mount command.
Hardware–Related Issues and Bugs mpathadm Does Not Display Load-Balance Setting Specific to Device The mpathadm show logical-unit subcommand lists the load balancing global configuration value for the Current Load Balance property. However, entries in the csi_vhci.conf that change the load-balance type for a specific product are not reflected in the mpathadm output even when the setting is active.
Hardware–Related Issues and Bugs 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.
Hardware–Related Issues and Bugs 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.
Hardware–Related Issues and Bugs 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. 2. 3. 4. 5. Run kdmconfig. Select the Xsun server. Use the Change Keyboard option to change the keyboard type. Save the configuration. Run kdmconfig again to switch to the Xorg server.
Hardware–Related Issues and Bugs 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.
iPlanet Directory Server 5.1 Issues iPlanet Directory Server 5.1 Issues This section provides important information for users of iPlanetTM 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.
iPlanet Directory Server 5.1 Issues 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 Caution – The database formats of the two Directory Server versions are incompatible. Thus, if you are a Directory Server 5.
Localization Issues 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” on page 76. 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.
Localization Issues To switch the input language, you can also use Hotkey. To enable Hotkey, perform the following steps: ■ ■ ■ Go to Misc tab in the iiim-properties. Select the Enable Language/Script choice window using Hotkey option. Press Apply or Click the OK button. Note – When Attach to each application is selected, the language switcher list will not be displayed for GTK applications. You can switch input language by using Hotkey.
Localization Issues New ChuYin Input Method Not Supported in Upgrade to IIIMF rev.12 (6492129) When you upgrade the OS to the Solaris 10 6/06 or Solaris 10 11/06 release, the input method framework and individual input methods get upgraded from rev.10 to rev.12. However, ChuYin is not in the list of supported input methods. Also, you cannot use the function keys F2 and F3 to switch methods Workaround: Use PinYin to type traditional Chinese characters with Hanyu PinYin.
Localization Issues Several Arabic Fonts Do Not Work in GNOME (6384024) In GNOME when you select certain Arabic fonts, the characters do not display. This problem appears when you select fonts for applications, the desktop, or the window title using the GNOME font properties menu. The affected fonts include: ■ ■ ■ Akhbar MT (Regular, Bold) Shayyal MT (Regular, Bold) Naskh MT (Regular, Bold) No error message is displayed.
Localization Issues Migration Note to 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.
Localization Issues 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.
Localization Issues 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.
Networking Issues Malta UK Malta US Poland Brazil Portuguese Romania Serbia and Montenegro Slovakia Slovenia Workaround: Choose one of the following workarounds: ■ Workaround 1: To take advantage of this keyboard software, set up keyboard input using the kbd -s command line utility. For desktop sessions with the UTF-8 locale environment, use Input Method Preference Editor. If the required keyboard layout is not included in the kbd -s utility, use Workaround 2.
Networking Issues TCP Corruption Seen With Northstar Cards (6838180) The Intel 82571 chip DMAs might transfer incorrect data but a valid CRC on the network and stop responding. This lack of response results in the device hanging and getting reset. Workaround: Disable LSO by adding the following line in the e1000g.conf file: lso_enable=0,0,0,0,0,0,0,0; Ensure that '0's are in line with the e1000g interface numbers.
Networking Issues DR and showdevices Do Not Work After XSCF Reboot (6821108) After rebooting the XSCF service processor on OPL systems, IPsec communications are lost. The following error message is seen on XSCF service processor: XSCF> showdevices -d 0 Can’t get device information from DomainID 0. The following message is seen in the /var/adm/messages file on the domain: Apr 7 11:19:20 domain-0 sckmd: [ID 205163 daemon.
Networking Issues x86: bnx Driver Does Not Support Broadcom NetXtreme II 5709 Chipset (6637053) The Broadcom NetXtreme II 5709 (BCM5709) chipset is not supported in the Solaris 10 10/09 release. Workaround: Download the bnx driver from the http://www.broadcom.com/support/ ethernet_nic/downloaddrivers.php web site. Note – Existing chipsets might experience performance regression issues when the downloaded driver is installed.
Networking Issues System Domain of Interpretation Is Not Configurable (6314248) The system Domain of Interpretation (DOI) is not configurable. When the Solaris Management Console is used to create a new trusted network template, the Solaris Management Console sets the DOI to 0 and Solaris Trusted Extensions does not function correctly. Various error messages are displayed. Workaround: Set the DOI to 1 using the Solaris Management Console.
Security Issues # 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. Security Issues The following security issues applies to the Solaris 10 release.
Solaris Commands and Standards Workaround: Setting the environment variable to the following values causes alignment errors to be reported on stderr: ■ ■ THREAD_ERROR_DETECTION=1 THREAD_ERROR_DETECTION=2 Users should test their applications with the THREAD_ERROR_DETECTION environment variable set to one of these values and request corrections to noncompliant applications.
Solaris Commands and Standards Bash 3.00 No Longer Sets Some Environment Variables Solaris 10 OS includes Bash 3.00. This shell no longer automatically exports the following variables to the environment: ■ ■ ■ ■ ■ ■ ■ ■ HOME PATH SHELL TERM HOSTNAME HOSTTYPE MACHTYPE OSTYPE This new behavior applies even if the shell assigns default values to these variables. Workaround: Export these variables manually.
Solaris Commands and Standards 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.
Solaris Volume Manager Solaris Volume Manager The following Solaris Volume Manager bug applies 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.
Sun Java Desktop System 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. Login Issues This section describes login issues. 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.
Sun Java Desktop System 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. 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.
Sun Java Desktop System 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. Nautilus ACL MASK is Not in Sync With Group Permissions (6464485) The Group permissions in the Permissions tab should be the same as the Mask permissions in the Access Tab, but on some occasions they appear out of sync. Workaround: Click the Close button, and then click Reload.
Sun Java Desktop System x86: Cannot Configure Full-Screen Magnification on Systems With One Video Card If your Solaris 10 system has a single physical video card, you cannot configure the system for full-screen magnification. For such a configuration, you must use a separate configuration file in which you define settings for a dummy driver. First, make sure that the Xserver is not running. Then perform the following steps: 1. Log in to a command-line session.
Sun Java Desktop System Note – You might need to adjust the videoram value, depending on the screen width, height, and color depth of your particular graphics card. The value in Kbytes must be large enough for the intended screen. For example, you can compute the value by using the formula width * height * bpp/8. ■ Add a new screen section.
System Administration 13. Assign the following values for Magnifier preferences: ■ For Source: 0.1 ■ For Zoomer Placement: ■ ■ Left and Top: 0 Bottom and Right: maximum 14. Click Apply. Because of the overlaying full-screen magnification zoomer, the Gnopernicus windows become invisible. However, full-screen magnification is now available.
System Administration Workaround: Remove the following lines from the /var/sadm/smc/toolboxes/smc/smc.tbx file. file:/var/sadm/smc/toolboxes/tsol_files/tsol_files.tbx file:/var/sadm/smc/toolboxed/tsol_ldap/tsol_ldap.tbx x86: add_drv, update_drv, and rem_drv Commands Should Use Advisory Record Locking (6445040) The update_drv command does not remove the /tmp/AdDrEm.
System Administration Do Not Use patchadd -M to Install Patches on a System With Non-Global Zones On a system with non-global zones, it is recommended not to use the patchadd -M option. The current implementation of patchadd -M applies all the patches to the global zone first, and only then to the non-global zones.
System Administration # mount -F hsfs /dev/rdsk/c0t2d0s2 /mnt Cannot Log In to Solaris Management Console After Enabling Solaris Trusted Extensions (6639493) The SolarisTM Management Console hangs and does not allow root login to the Solaris Management Console after enabling Solaris Trusted Extensions. The following error message might be displayed the Solaris Management Console hangs: Configuring the Management Server... Workaround: Perform the following steps: 1.
System Administration The SATA mode setting in BIOS must not be changed after an initial Solaris installation. The SATA mode setting must also not be changed before or after a Solaris upgrade. If the SATA mode BIOS setting is modified after installing Solaris, the system will reset and fail to boot without indicating what led to the failure. Workaround: If boot failure is encountered as a result of changing the BIOS setting, revert back to the original setting in order to boot Solaris.
System Administration 2. Reboot your system. 3. Install the patch. 4. After you have completed the patch installation operation, restore or uncomment the same line from the /etc/system file. 5. Reboot the system to resume normal operations. No error message is displayed. Workaround: Sun recommends Solaris Live Upgrade to manage patching. Solaris Live Upgrade prevents the problems of patching a running system.
System Administration Note – The -R option works if the alternate boot environment has configured non-global zones, but no installed non-global zones. However, to avoid a potential problem, or if you are not sure whether there are any installed non-global zones used as the alternate root path, restrict the use of the -R option in all instances.
System Administration 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.
System Administration ■ 108 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.
3 C H A P T E R 3 System-Specific Issues This chapter describes issues specific to Sun midrange and high-end servers. Current Sun servers are part of the Sun Fire system family. Older servers are part of the Sun Enterprise system family. Note – The Sun Validation Test Suite release notes are now a separate document and can be found at http://sun.com.
Dynamic Reconfiguration on Sun Fire Midrange Systems GigaSwift Ethernet MMF Link Fails With CISCO 4003 Switch After DR Attach The link fails between a system with a Sun GigaSwift Ethernet MMF Option X1151A and certain CISCO switches. The failure occurs when you attempt to run a DR operation on such a system that is attached to one of the following switches: ■ CISCO WS-c4003 switch (f/w: WS-C4003 Software, Version NmpSW: 4.4(1)) ■ CISCO WS-c4003 switch (f/w: WS-C4003 Software, Version NmpSW: 7.
Dynamic Reconfiguration on Sun Fire Midrange Systems Note – To best utilize the latest firmware features and bug fixes, run the most recent SC firmware on your Sun Fire midrange system. For the latest patch information, see http://sunsolve.sun.com. TABLE 3–1 Minimum SC Firmware for Each Platform and Solaris Release Platform Solaris Release Minimum SC Firmware Sun Fire E6900/E4900 with UltraSPARC IV+ Solaris 10 3/05 HW1 (a limited release) or Solaris 10 1/06 5.19.
Sun Enterprise 10000 Release Notes # sh /etc/init.d/nfs.server start 6. Restart Boot Server services. # sh /etc/init.d/boot.
Sun Enterprise 10000 Release Notes ■ ■ ■ deleteboard showdevices rcfgadm You can run the cfgadm command on domains to obtain board status information. DR model 3.0 also interfaces with the Reconfiguration Coordination Manager (RCM) to coordinate the DR operations with other applications that are running on a domain. For details about DR model 3.0, refer to the Sun Enterprise 10000 Dynamic Reconfiguration User Guide.
Dynamic Reconfiguration on Sun Enterprise Midrange Systems OpenBoot PROM Variables Before you issue the boot net command from the OpenBoot PROM prompt (OK), verify that the local-mac-address? variable is set to false. This setting is the factory default setting. If the variable is set to true, you must ensure that this value is an appropriate local configuration. Caution – A local-mac-address? that is set to true might prevent the domain from successfully booting over the network.
Dynamic Reconfiguration on Sun Enterprise Midrange Systems The following I/O boards are not currently supported: ■ ■ ■ Type 2 (graphics) Type 3 (PCI) Type 5 (graphics and SOC+) Software Notes This section provides general software information about DR. Enabling Dynamic Reconfiguration To enable dynamic reconfiguration, you must set two variables in the /etc/system file. You must also set an additional variable to enable the removal of CPU/memory boards. Perform the following steps: 1.
Dynamic Reconfiguration on Sun Enterprise Midrange Systems cfgadm: Hardware specific failure: connect failed: board is disabled: must override with [-f][-o enable-at-boot] To override the disabled condition, two options are available: ■ Using the force flag (-f) # cfgadm -f -c connect sysctrl0:slot number ■ Using the enable option (-o enable-at-boot) # cfgadm -o enable-at-boot -c connect sysctrl0:slot number To remove all boards from the disabled board list, choose one of two options depending on the
Dynamic Reconfiguration on Sun Enterprise Midrange Systems Self-Test Failure During a Connect Sequence Remove the board from the system as soon as possible if the following error message is displayed during a DR connect sequence: cfgadm: Hardware specific failure: connect failed: firmware operation error The board has failed self-test, and removing the board avoids possible reconfiguration errors that can occur during the next reboot. The failed self-test status does not allow further operations.
4 C H A P T E R 4 End-of-Software Support Statements This chapter lists end-of-software support statements. Note – The Solaris 10 OS media kit contains not only the Solaris 10 OS software, but also developer tools for the Solaris OS and the Solaris Companion CD (useful and popular technologies offered as unsupported, value-add, free software). The information provided on http://www.sun.com/service/serviceplans/solaris/10/ lists the components of the Solaris 10 OS media kit.
Features That Might Be Removed in a Future Release fr_FR.UTF-8@euro it_IT.ISO8859-15@euro it_IT.UTF-8@euro nl_BE.ISO8859-15@euro nl_NL.ISO8859-15@euro pt_PT.ISO8859-15@euro Users should use the corresponding non-variant locales. StarOffice The StarOffice productivity suite might not be available in a future Solaris release. Users can purchase a copy of StarOffice from the Sun Store directly at http://globalspecials.sun.com or migrate to the OpenOffice.org productivity suite.
Features That Might Be Removed in a Future Release Xprt Server and Xprint Extension The Xprt server and Xprint extension to the X Window System might no longer be included in a future Solaris release. The libXp library will remain for binary compatibility. This enables existing users of this software to continue printing over the network to Xprt servers running on Solaris 10 and prior Solaris releases, or Xprint implementations on other platforms.
Features That Might Be Removed in a Future Release ■ ■ ■ ■ bsmconv(1M) bsmrecord(1M) bsmunconv(1M) audit_control(4) xorgcfg and xorgconfig Utilities The xorgcfg and xorgconfig utilities for generating xorg.conf files might no longer be available in a future Solaris release. The Xorg(1) server does not require an xorg.conf(4) file in many cases and will autoconfigure itself if the file is not present. Users should use one of the following alternative methods to generate an xorg.
Features That Might Be Removed in a Future Release Some audiorecord and audioplay Application Switches The -p and -b switches to both the audiorecord and audioplay applications, as well as the -m switch to audiorecord might be removed in a future Solaris release. If a filename is not specified on the command line and standard input and output is not a tty, both these applications will exit with an error.
Features That Might Be Removed in a Future Release sdtudctool sdtudctool might not be available in a future Solaris release. For more information, see User Defined Characters Migration Guide for the migration at http://developers.sun.com/ global/products_platforms/solaris/reference/techart/UDCGuide.
Features That Might Be Removed in a Future Release Features such as Display Postscript (DPS) and X Image Extension (XIE) that are available in Xsun but not in Xorg might no longer be included. Common Desktop Environment The Common Desktop Environment (CDE) might not be available in a future Solaris release. Users should migrate to the Java Desktop System. CDE Image Viewer CDE's Image Viewer sdtimage might not be available in a future Solaris release.
Features That Might Be Removed in a Future Release iButton Smartcard The Dallas Semiconductor iButton Java Card Smartcard and OpenCard Framework (OCF) terminal driver, as described in ocf_ibutton(7d) might not be supported in future Solaris releases. Users should migrate to other Smartcard devices that are supported by libpcsclite(3lib). Cyberflex Smartcard The Cyberflex Smartcard might not be supported by the pam_smartcard(5) and smartcard(1m) commands in future Solaris releases.
Features That Might Be Removed in a Future Release Transition From ipge to e1000g NIC Driver as the Default Ethernet Driver for Sun4V Systems The ipge driver and all its SUNWipge packages for Sun4V systems might not be available in a future release of Solaris. Starting with the Solaris 10 8/07 release, Ontario and other SPARC based platforms transition from ipge to e1000g drivers. The e1000g driver will be the default Ethernet driver for all Sun platforms that use Intel 1G chipsets.
Features That Might Be Removed in a Future Release SPARC: jfca Driver Support The JNI Fibre Channel Adapter (jfca) driver might not be available in a future Solaris release. For more information, see the jfca(7D) man page. zic -s Option Support The -s option in the zic command might not be available in a future Solaris release. For more information, see the zic(1M) man page.
Features That Might Be Removed in a Future Release SPARC: Certain Drivers Might Not be Supported in a Future Solaris Release The following drivers might not be supported in a future Solaris release: ■ SUNWrtvc: Device driver for the SunVideoTM real-time video capture and compression card ■ SUNWdial: Streams module for the Dials and Buttons devices ■ SUNWdialh: Header files for the Dials and Buttons devices Automated Security Enhancement Tool Support The checksum functionality provided by Automated Se
Features That Might Be Removed in a Future Release Audit Daemon Interfaces The following interfaces that are used by the Solaris audit daemon might not be supported in a future release: ■ ■ auditsvc(2) audit_data(4) Cfront Runtime Support Library The library libC.so.3 is the runtime support library for programs that are compiled by the Cfront C++ compiler C++ 3.0. Neither the compiler nor programs that are created by the compiler run on Solaris 10 OS.
Features That Might Be Removed in a Future Release Obsolete Interface Preferred Interface mmap devmap identify set to nulldev copyin ddi_copyin copyout ddi_copyout ddi_dma_addr_setup ddi_dma_addr_bind_handle ddi_dma_buf_setup(9F) ddi_dma_buf_bind_handle ddi_dma_curwin ddi_dma_getwin ddi_dma_free ddi_dma_free_handle ddi_dma_htoc ddi_dma_addr[buf]_bind-handle ddi_dma_movwin ddi_dma_getwin ddi_dma_nextseg ddi_dma_nextcookie ddi_dma_nextwin ddi_dma_nextcookie ddi_dma_segtocookie ddi_
Features That Might Be Removed in a Future Release Obsolete Interface Preferred Interface ddi_unmap_regs ddi_regs_map_free free_pktiopb scsi_free_consistent_buf get_pktiopb scsi_alloc_consistent_buf makecom_g0 scsi_setup_cdb makecom_g0_s scsi_setup_cdb makecom_g1 scsi_setup_cdb makecom_g5 scsi_setup_cdb scsi_dmafree scsi_destroy_pkt scsi_dmaget scsi_init_pkt scsi_pktalloc scsi_init_pkt scsi_pktfree scsi_destroy_pkt scsi_resalloc scsi_init_pkt scsi_resfree scsi_destroy_pkt scsi_s
Features That Might Be Removed in a Future Release Device Support and Driver Software The following table lists devices and driver software that might not be supported in a future release.
Features That Might Be Removed in a Future Release Korean CID Fonts Korean CID fonts will not be supported in a future release. You can use the Korean TrueType fonts that are included in the Solaris software as a replacement for Korean CID fonts. Legacy or Traditional Non-UTF-8 Locales Sun is adopting Unicode for character encoding. Therefore, except for zh_CN.GB18030 and C locales, non-UTF-8 locales might be removed as the Java Desktop System login locale in a future Solaris release.
Features That Might Be Removed in a Future Release New functions have been added to the library in Solaris 10 OS.
Features That Might Be Removed in a Future Release Network Information Service Plus (NIS+) Name Service Type NIS+ might not be supported in a future release. Tools to aid in the migration from NIS+ to LDAP are available in the Solaris 9 software. For more information, visit http://www.sun.com/directory/nisplus/transition.html. nstest Test Program The nstest is an interactive DNS test program to construct and send DNS queries. This program might no longer be supported in a future Solaris OS release.
Features That Might Be Removed in a Future Release Standalone Router Discovery The /usr/sbin/in.rdisc implementation of the IPv4 ICMP Router Discovery protocol might not be supported in a future release of the Solaris software. A near-equivalent version of this protocol, which is implemented as a component of /usr/sbin/in.routed, supports an enhanced administrative interface. The /usr/sbin/in.routed component supports the implementation of Routing Information Protocol (RIP) version 2. The /usr/sbin/in.
Features That Might Be Removed in a Future Release /usr/ccs/bin/nm $file | /bin/awk ’ /\|gld_register$/ { isgld=1; } END { if (isgld) print file, "uses GLD"; else print file, "does not use GLD"; }’ file=$file done For more information about generic LAN driver, see the gld(7D) man page as well as “Writing Device Drivers”.
Features That Might Be Removed in a Future Release x86: Xsun DDX Modules, Library, and Related Files Certain DDX modules for Xsun might be removed from a future Solaris release. These modules are used when you configure the Xsun X server on the kdmconfig screen, Video Device Selection, by selecting an entry that is not prefixed with “XF86.
5 C H A P T E R 5 Documentation Issues This chapter describes known issues that are related to documentation. System Administration Guide: IP Services The note on page 786 is incorrect and reads as follows: Note – The x86 architecture does not support IPQoS on VLANs. The correct note should read as follows: Note – Support for SPARC and x86 architecture, including IPQoS on VLANs. Some Translated Docs Are Not Updated The following translated docs have not been updated in the Solaris 10 10/09 release.
Some Translated Docs Are Not Updated Title of the doc Affected Languages Changes made in the English version Solaris Tunable Parameters Reference Manual Japanese Chapter 1 – Added tcp_local_dack_interval information Chapter 4 – Updated tcp_local_dack_interval information Appendix A – Added tcp_local_dack_interval information Appendix B – Added Solaris 10 information Solaris Security for Developers Guide 142 Japanese Solaris 10 10/09 Release Notes • October 2009 Updated Links Changed references to
Some Translated Docs Are Not Updated Title of the doc Affected Languages Changes made in the English version System Administration Guide: Devices and File Systems Japanese Chapter 3 – Updated removable media examples with Solaris 10 10/08 media names and structure Chapter 10 – Updated EFI label section to describe how to reapply a VTOC label when an EFI label is no longer needed Chapter 11 – Updated “Identifying Disks on a System” section to include steps for providing the disk marketing name on x86 s
Solaris 10 10/09 Patch List Title of the doc Affected Languages Changes made in the English version System Administration Guide: Solaris Printing Japanese Added missing examples Simplified Chinese Fixed typos and corrected any incorrect information Solaris 10 10/09 Patch List In the Solaris 10 10/09 release, the Solaris patch lists are not documented in the Solaris 10 10/09 Release Notes. The patch lists are documented in Solaris 10 10/09 Patch List.
Solaris 10 Start Here and Solaris 10 Installation Guides Application Server Documentation Refers to Derby Database Instead of Java DB Application Server documentation refers to the Java DB database as “Derby.” Replace all references to “Derby” with Java DB. The database is installed to /usr/appserver/javadb. Documents on the Software Supplement CD Beginning with Solaris 10 Operating System, the Supplement CD no longer exists.
Solaris 10 Start Here and Solaris 10 Installation Guides The following documents incorrectly state that Sun Java Enterprise System is installed by default during a Solaris 10 installation.
Solaris 10 Documentation and Man Pages Solaris 10 Documentation and Man Pages The company S2io has changed its name to Neterion. All references to S2io in the Solaris 10 documentation and man pages should read Neterion.
A A P P E N D I X A Table of Integrated Bug Fixes in the Solaris 10 Operating System The table in this appendix list bugs in these Release Notes that have been fixed in the Solaris 10 10/09 OS. Note – This table is only a partial list. Other fixed bugs in the operating system that were not previously documented in the Release Notes are excluded from this table. For a complete list, refer to the Solaris 10 Operating System Patch List.
