Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 11.1 Release Notes Oracle Solaris 11.1 Information Library |
Issues When Installing Oracle Solaris 11.1
AI Services Created From Oracle Solaris 11 Images Install Oracle Solaris 11.1 (7144329)
SPARC: FMD Errors During Installation of Oracle Solaris on a T-Series Server (16081077)
Automated Installer Configuration Profiles Are Openly Accessible From the Web Server (7097115)
Automated Installer Fails to Match Target Disks When Using Dual-Path Boot Disk (7079889)
Multiple AI Service Name Conflicts on AI Servers (7042544)
Text Installer Displays in English When Another Language Is Chosen (7095437)
sysconfig and Text Installer Applications Terminate Unexpectedly From Timezone Screens (7026383)
Installation Fails If Non-ASCII Characters Are Specified in the Real Name Field (7108040)
Network-Based Automated Installer Fails on x2100 Platform With nge Drivers (6999502)
x86: 64-bit: DVD Installation Might Fail on Oracle's Sun Fire x4170m3 and x4270m3 Servers (7185764)
A. Previously Documented Bugs That Are Fixed in the Oracle Solaris 11.1 Release
This section describes hardware-related issues in Oracle Solaris 11.1.
A few Dell desktop models, for example, the Precision T1600 and Optiplex 790 models, hard-hang at boot time when booted in the Unified Extensible Firmware Interface (UEFI) mode. This problem is a known Dell firmware issue.
Workaround: To complete the installation, boot the system by specifying the -B uefirt_disable=1 boot attribute.
To specify this attribute for a one-time boot, edit the GRUB menu at boot time.
To make the change permanent, use the bootadm command with the change-entry subcommand.
# bootadm change-entry -i entry-number kargs='-B uefirt_disable=1'
After installation, you must run the bootadm change-entry command again on the boot environment that the installer created.
Caution - Make sure to run the bootadm change-entry command before creating any new boot environments to ensure that all new boot environments inherit the same kernel argument strings. Otherwise, you will need to manually change every boot entry that you create. For more information about using the bootadm command to make changes to a particular boot entry, see How to Set Attributes for a Specified Boot Entry in the GRUB Menu in Booting and Shutting Down Oracle Solaris 11.1 Systems. |
Note - These workarounds disable UEFI runtime services, meaning that Oracle Solaris cannot set the system's default boot device. As a result, you might have to manually set the system's default boot device after installation. You can do so by using the system's firmware setup utility, for example, the UEFI Boot Manager.