1. Updates to Solaris 10 Release
x86: Support for Intel Integrated i810 and i815 Graphics Chipsets
Arabic Text Not Appearing in ar Locales
Compose Key Sequences Might Not Work When You Use X Keyboard Extension in Some Locales (6219932)
x86: kdmconfig Instructions to Configure Xorg X Server Are Incomplete (6205881)
x86: Program That Configures Keyboard, Display, and Mouse Not Working for X Server (6178669)
SPARC: Some UTF-8 Locales Are Unavailable in the Common Desktop Environment Login Service (5042573)
CDE Removable Media Auto Run Capability Removed (4634260)
Solaris PDASync Cannot Delete Last Entry From the Desktop (4260435)
SUNWsdocs Package Needed to Remove Other Documentation Packages
European Locale PDF Documents Available Only Through C Locale (4674475)
Upgrading From Some Solaris Express or Solaris 10 Releases Requires Remounting of File Systems
NFSv4 Access Control List Functions Might Work Incorrectly
Access Problems Between Solaris NFSv4 Clients and NFSv4 Servers
System Crash Dump Fails on Devices Greater Than 1 TByte (6214480)
Using smosservice Command to Add OS Services Results in Insufficient Disk Space Message (5073840)
Hardware-Related Issue and Bugs
SPARC: Sun Crypto Accelerator 4000 Board Versions 1.0 and 1.1 Not Supported in Solaris 10 OS
Certain USB 2.0 Controllers Are Disabled
Supported USB Devices and Corresponding Hub Configurations
x86: Limitations Exist With Certain Device Drivers in Solaris 10 OS
DVD-ROM/CD-ROM Drives on Headless Systems
x86: Manual Configuration Required to Specify Non-US English Keyboards
Using USB 2.0 Hubs With USB 1.x Devices Might Cause System Panic (6209619)
x86: EHCI Driver Unusable in Certain Motherboards (6204987)
Using FireWire-1394 Storage Devices Might Cause System Panic (6203680)
Pausing USB Audio Devices During Play or Record Operation Might Cause System Deadlock (6200924)
Contention Exists Between Certain Devices That Share the Same Bus (6196994)
Some Keyboard Keys Not Functioning With Num Lock Key On (6173972)
hat_getkpfnum() DDI Function Is Obsolete (5046984)
Some Systems With USB 2.0 Hardware Might Hang or Panic (5030842)
x86: Soft System-Shutdown is Not Supported in Solaris OS on x86 (4873161, 5043369)
iPlanet Directory Server 5.1 Issues
Installing Directory Server 5.1
Migrating to the Sun Java System Directory Server 5 2005Q1
SPARC: Systems With Active Kernel Debugger Might Panic During Suspend/Resume Cycles (5062018)
System Might Loop When Master CPU Is Changed (4405263)
Login Screen Marks UTF-8 Locales as Recommended
Emails Saved As Portable Format
File Names and Directory Names
Launching Legacy Locale Applications
Cannot Print Documents in Portable Document Format (6239307, 6218079)
x86: Login Process Might Hang in Certain Asian Non-UTF-8 Locales (6215527)
localeadm -l Does Not List Installed Korean Locale Packages (6189823)
Special Keyboard Keys Do Not Work (5077631)
Modifier Keys Do Not Function Correctly (4996542)
Chinese and Korean Characters Are Printed In a Box (4977300)
Sort Capability in the European UTF-8 Locales Does Not Function Correctly (4307314)
SPARC: RTM_IFINFO Message Has Different Sizes on 32-bit and 64-bit Compilations
IP Forwarding Disabled by Default in Solaris 10 OS
Zone Not Booting When IP Address Belongs to a Failed IP Network Multipathing Group (6184000)
ATM LANE Subnets for IPv4/IPv6 Might Not Complete Initialization (4625849)
Nonpassword Logins Fail With pam_ldap Enabled
New Versions of encrypt() and decrypt() Are Not Backward Compatible
Incorrect Parameters Might Cause Panic in Sun StorEdge T3 (4319812)
svccfg import Subcommand Does Not Refresh Dependent Services (6221374)
Print Services Have Offline Settings by Default (5100134)
keyserv Daemon Disables Some File System Services (5084183)
Login Prompts Sometimes Appear Before File Systems Are Mounted (5082164)
System Does Not Respond to Smart Card (4415094)
Edit Config File Menu Item in Smartcards Management Console Does Not Work (4447632)
Solaris Commands and Standards
Bash 2.0.5b No Longer Sets Some Environment Variables
New ln Utility Requires -f Option
New tcsh Rejects setenv Variable Names That Use a Dash or an Equals Sign
STDIO getc Family EOF Condition Behavior Change
Output Columns of the ps Command Have Been Widened
Command ping -v Does Not Work on IPv6 Addresses (4984993)
Solaris Volume Manager metattach Command Might Fail
Solaris Volume Manager metassist Command Fails in Non-English Locales (5067097)
Volume Creation Fails in Systems With Unformatted Disks (5064066)
Solaris Volume Manager metadevadm Command Fails if Logical Device Name No Longer Exists (4645721)
Solaris Volume Manager metarecover Command Fails to Update metadb Namespace (4645776)
Problems With Using Multiple Attachments (6260583)
Problem With Changing Authentication Type (6246543)
Problems When Saving Attachments With Localized Content (6204976)
Incomplete List of Contacts in Contact Folder (5088514)
Remote Connection Problems (6203727)
Wrong Help Window Opened For Volume Control (6253210)
Cannot Print Certain Documents From the Mozilla Browser
Cannot Specify User Preferences for Roaming Access in Mozilla Browser (6200999)
Keyboard Shortcuts Fail (6192644)
User Preferences Not Fully Compatible
GNU Image Manipulation Program Missing From the Graphics Menu (6209566)
Problems With Online Registration of StarOffice 7 Software (6208829)
Volume Control Option Not Working
Problems When Using Keyboard Indicator (6245563)
Certain View Options Might Cause File Manager to Fail (6233643)
Cannot Delete Files Outside of Home Directory (6203010, 5105006)
Problems Creating Certain Types of Archives (5082008)
Cannot Type Multibyte Characters in Text Editor 2.9.1 (4937266)
Sun Patch Manager Tool 2.0 Not Compatible With Previous Versions
Sun Remote Services Net Connect Supported Only in the Global Zone
Solaris Product Registry Administration Utility Fails to Launch in a Zone (6220284)
patchadd Fails to Reapply Patches to Newly Installed Packages (6219176)
Cannot Delete Existing Diskless Clients From the System (6205746)
Net Connect 3.1.1 Installation Fails (6197548)
x86: Default C Library Might Cause Boot Failure When You Install Solaris Flash Archives (6192995)
SPARC: smosservice delete Command Does Not Successfully Remove All Directories (6192105)
patchadd Command Does Not Support Installing Patches From an NFS Server (6188748)
lucreate Command Does Not Create RAID-1 Volumes (5106987)
SPARC: Panics That Occur During Suspend and Resume Cycles Might Cause the System to Hang (5062026)
SPARC: Stopping the System by Using Keyboard Sequences Might Cause a System Panic (5061679)
Using the ipfs Command With -W Option Fails (5040248)
Permissions for Mount Points Not Preserved in Created Boot Environment (4992478)
kill -HUP Does Not Always Cause the Agent to Reread the snmpd.conf Configuration File (4988483)
x86: Pressing the F4 Key During BIOS Bootup Fails to Boot the Service Partition (4782757, 5051157)
5. End-of-Software Support Statements
A. Table of Integrated Bugs in the Solaris 10 Operating System
The following hardware–related issue and bugs apply to the Solaris 10 release.
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.
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.
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.
Table 3-1 USB Devices and Configurations
|
The following list describes limitations with certain drivers and interfaces in this release of Solaris 10 for x86 platforms:
This functionality is turned off for all device types. In the DDI_SUSPEND code in your detach() function, you should return DDI_FAILURE.
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.
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.
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:
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.
Change the keyboard type to the type that corresponds to your system's keyboard.
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:
Run kdmconfig.
Use the Change Keyboard option to change the keyboard type.
Save the configuration.
If your system is running the default Xorg server, follow these steps:
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.
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.
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.
Note - 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
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.
Note - 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.
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:
Become superuser.
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.
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.
Note - 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
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.
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.
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 1500
Sun Blade 2500
Sun Fire V210
Sun Fire V240
Netra 240
Sun Fire V440
Netra 440
The following error message is displayed:
panic: pcisch-1: Fatal PCI bus error(s)
Workaround: Follow these steps.
Determine the rev_id of the device.
kstat ce:instance | grep rev
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.
Note - The original card is still usable in x86 systems or in older SPARC based systems that are not included in the preceding list.
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.
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:
Add a PCI-based USB 2.0 card that is based on the NEC chip.
Become superuser.
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
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:
Become superuser.
Issue the following commands:
# update_drv -d -i '"pciclass,0c0320"' usba10_ehci # reboot
Note - 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)
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.
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:
Become superuser.
Use one of the available commands to shut down the Solaris OS properly, such as init, halt, or shutdown. For example:
# shutdown
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.
The default timeout value for the SCSI portion of the SunSwift 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)