|
|
Release Notes for the OpenSolaris 2008.05 ReleaseFor additional information on the following issues, look up the bug number in Bugzilla. Languages
Translation for this page
This page lists the following Release Notes for the OpenSolaris 2008.05 Release : Important Package Update Instructions for All Users. 6696145 - Install Causes Panics on Intel 965 With GM965 Chipset. 64 - Installer, but not Desktop, Allows Empty Passwords. 1045 - beadm create Fails When Run as User. 1109 - Locale Information Inaccurate in Installer Summary Panel. 1156 - Booting a BE That Was Left Mounted Before the Reboot Fails. 1333 - Creating BE and Renaming BE Fails to Handle Subordinate Legacy-Mounted Datasets. 1334 - Compiz Hangs System that Uses Intel Graphics Card i915 or i965GM. 1559 - GRUB Entry for Windows Incorrect From USB Stick Install. 1565 - Nautilus Process Hangs After Gnome Login. 1771 - Install will fail if rpool ZFS pool already exists. 1685 - Renaming a Busy Boot Environment can Fail. 6676221 - setxkbmap Can't Locate Rules file for Xorg. 6687328 - vim Command Cannot Display Multibyte Characters. 6690194 - fdisk(1M) Doesn't Clear VTOC When Partition Starts After, or Exceeds, 4 Gbytes. 6690824 - fdisk(1M) Corrupts Solaris VTOC, if Linux Swap Primary Partition is Defined. 6694783 - Input Method Duplicate Causes IDE Crash. 2900 - Firefox dumps core in NV95. Important Package Update Instructions for All UsersA number of issues in the Image Packaging System (IPS) have been identified and resolved since the initial release of OpenSolaris 2008.05. As a result, the following steps should be performed immediately following an OpenSolaris installation and boot in order to ensure correct operation of the software packaging system. 1. Once the system has booted following an installation, the user should login to the system and bring up a terminal window by performing a right-click on the desktop and selecting "Open Terminal". For users who have a single-button pointing device, the menu in question can be raised by holding the "Control" key down while clicking on the desktop. 2. In the terminal window, the following sequence of commands should be performed:
$ pfexec pkg refresh
$ pfexec pkg install SUNWipkg@0.5.11-0.86
$ pfexec pkg install entire@0.5.11-0.86
$ pfexec pkg install SUNWipkg-gui
After these steps have been performed, packaging operations using the pkg(1) command can be performed. For more information on this command and the IPS technology, refer to the pkg(1) and pkg(5) manual pages and Getting Started With the Image Packaging System. If you have already installed packages from the repository without upgrading the IPS software, it is possible that your software installation may contain packages that are incompatible with one another. In some cases, the system may not boot completely or will boot with errors. If you would like to restore your system software, see Restoring Your System Software to the Initial Installation for more information. Development builds of OpenSolaris are also available for use by using the pkg image-update command. For critical information on this feature, see Updating Your System to OpenSolaris Development Builds. # 6696145 Install Causes Panics on Intel 965 With GM965 ChipsetDescriptionInstalling the OpenSolaris release on certain laptops that are equipped with the Mobile Intel GM965 Express chipset (Intel GMA X3100 Graphics) is known to cause panics. This issue has been reproduced on the following models that are equipped with the GM965 chipset.
How can I tell if my laptop is running the GM965 chipset?You can use the Device Driver Utility on the LiveCD. Or, open a terminal window and run the following command: pfexec /usr/X11/bin/scanpci This command identifies which Graphics Controller you have on your laptop. WorkaroundUse the VESA driver to install the OpenSolaris 2008.05 release onto your system. Use the following procedure for the vesa driver:
# 64 Installer, but not Desktop, Allows Empty PasswordsDescriptionIf, during installation, no root password is entered and no user account is created, you will not be able to log in to the installed system. WorkaroundSelect one of the following workarounds:
# 1045 beadm create Fails When Run as UserDescriptionWhen using the beadm command, as a non-root user, to create a new BE, the command fails with the following traceback: user@opensolaris:~$ beadm create newBE
Traceback (most recent call last):
File "/usr/sbin/beadm", line 1296, in ?
ret = main()
File "/usr/sbin/beadm", line 557, in main
return(parseCLI(sys.argv[1:]))
File "/usr/sbin/beadm", line 532, in parseCLI
rc = create(optsArgs)
File "/usr/sbin/beadm", line 146, in create
if initBELog("create", be) != 0:
File "/usr/sbin/beadm", line 1244, in initBELog
os.makedirs(os.path.dirname(be.log), 0644)
File "/usr/lib/python2.4/os.py", line 156, in makedirs
makedirs(head, mode)
File "/usr/lib/python2.4/os.py", line 159, in makedirs
mkdir(name, mode)
OSError: [Errno 13] Permission denied: '/var/log/beadm'
WorkaroundBecome root or assume root privileges before using the beadm command to create a new boot environment. # 1109 Locale Information Inaccurate in Installer Summary PanelDescriptionThe final Summary panel in the installer displays inaccurate language support information. The installer summary panel states that only the following language support will be installed: Locale
The correct information is that the OpenSolaris installer installs all language support that is included in the Live CD. # 1156 Booting a BE That Was Left Mounted Before the Reboot FailsDescriptionIf a boot environment (BE) is mounted by using the beadm mount command, and the system is rebooted before that BE gets unmounted, selecting that BE from the GRUB menu causes a boot failure. In the particular case where a BE has been activated by using the beadm activate command, this BE is the default selection in the GRUB menu. Therefore, leaving this BE mounted before a reboot causes a boot failure. A typical boot failure message is: Use is subject to license terms.
Hostname: opensolaris
Apr 28 16:05:08 svc.startd[7]: svc:/system/sysevent:default: Method
"/lib/svc/method/svc-syseventd start" failed with exit status 95.
Apr 28 16:05:08 svc.startd[7]: system/sysevent:default failed fatally:
transition to maintenance (see 'svcs -xv' for details)
'/usr/sbin/pmconfig: cannot open/create "/etc/.cpr_config", Bad file number
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Root password for system maintenance (control-d to bypass):
WorkaroundReboot the system and select the previously active boot environment. When the system comes up, reset the mount point of the activated boot environment by running the following command as root. # beadm unmount boot_environment Then reboot your system. # 1333 Creating BE and Renaming BE Fails to Handle Subordinate Legacy-Mounted DatasetsDescriptionWhen a boot environment (BE) has a legacy mount point for one of its subordinate datasets, creating a new BE based on this BE by using the beadm create command fails. Also, renaming a BE that has a legacy mount point for one of its subordinate datasets fails to update the /etc/vfstab properly. WorkaroundUse one of the following workarounds:
# 1334 Compiz Hangs System that Uses Intel Graphics Card i915 or i965GMDescriptionEnabling Compiz on a machine that has an Intel graphic card i915 or i965GM will probably hang the system due to driver issues. How can I tell if my laptop is running the GM965 chipset? Use the Device Driver Utility on the LiveCD. Or, open a terminal window and run the following command: pfexec /usr/X11/bin/scanpci This command identifies which Graphics Controller you have on your laptop. WorkaroundDo not enable the visual effects in the GNOME appearance preference dialog. # 1472 Creating a new BE From a Mounted BE Results in Incorrect Mount Points for Subordinate DatasetsDescriptionWhen you create a new boot environment (BE) from an BE that is currently mounted, some of the subordinate datasets of the new BE have incorrect mount points. WorkaroundUse the zfs list command to look at the mount points for the datasets of the new BE. For example: # zfs list -r rpool/ROOT/be2
NAME USED AVAIL REFER MOUNTPOINT
rpool/ROOT/be2 73.5K 31.0G 2.23G legacy
rpool/ROOT/be2/opt 0 31.0G 3.60M /mnt/optUse the zfs set command to reset the subordinate file system at the correct mount point. # zfs set mountpoint=/opt rpool/ROOT/be2/opt # 1559 GRUB Entry for Windows Incorrect From USB Stick InstallDescriptionWhen the OpenSolaris 2008.95 release is installed from a USB stick, the GRUB entry for Windows does not reference the correct disk device. WorkaroundEdit the /rpool/boot/grub/menu.lst file. Modify the rootnoverify entry in that file. Typically a USB installed system will have the following entry: rootnoverify (hd1,0) This entry should be changed to the following: rootnoverify (hd0,0) #---------- ADDED BY BOOTADM - DO NOT EDIT ---------- title Windows rootnoverify (hd0,0) chainloader +1 #------------------- END BOOTADM -------------------- If a diagnostic partition exists, a similar change is required. # 1565 Nautilus Process Hangs After Gnome LoginDescriptionWhen you log in to the Gnome desktop, Nautilus might hang. In this case, the desktop background is a solid, blue-gray color and right-clicking on the background does not open a menu. The nautilus-debug-log.txt is added in your home directory. If Nautilus hangs, it can consume 50% of the CPU time. WorkaroundManually kill the broken Nautilus process as follows:
# 1771 Install will fail if rpool ZFS pool already existsDescriptionIf a ZFS pool that is named “rpool” is present on the system , the installer fails when the Install button is clicked on the installation summary screen. A failure screen is displayed immediately. The last message in the installation log is: Root pool rpool exists, we can't proceed with the installation. A root pool that is named “rpool” might be present on the system under any of the following conditions:
You can use the zpool list rpool command to confirm existence of a ZFS pool that is named “rpool.” WorkaroundSelect one of the following workarounds:
# 1685 Renaming a Busy Boot Environment can FailDescriptionRenaming a boot environment (BE) might fail if the BE has a dependent clone that is currently mounted or otherwise busy. A typical example of this situation is when the live BE has been successfully upgraded. If you then try to rename the auto-generated and upgraded BE, the renaming fails. The renaming fails because the upgraded BE has been activated and the live BE is now its clone. WorkaroundUse the following procedure:
For example, if the live boot environment name is “opensolaris”, and the auto-generated BE name of the upgraded boot environment is “opensolaris-1,” use the following commands: # beadm activate opensolaris # beadm rename opensolaris-1 new_name # beadm activate new_name # 6676221 setxkbmap Can't Locate Rules file for XorgDescriptionBy default, setxkbmap has not defined the correct path to the rules file for Xorg, /usr/X11/lib/X11/xkb/rules/xorg. When you try to set a Keyboard Layout by using setxkbmap, the following error message appears: /bash-3.2$ /usr/X11/bin/setxkbmap br Couldn't find rules file (xorg) WorkaroundTo correctly set the path to the rules file, type: -bash-3.2$ setxkbmap -rules /usr/X11/lib/X11/xkb/rules/xorg/ Once this path is set, the system remembers the path until you restart your Xserver. # 6687328 vim Command Cannot Display Multibyte CharactersDescriptionThe vim command can not display multibyte characters. This bug affects other commands which symbolically link to /usr/bin/vim such as vi, view, and ex commands. WorkaroundAdd the $HOME/.vimrc file that contains the following line: set encoding=utf-8 Or, use the /usr/has/bin/vi command instead. # 6690194 fdisk(1M) Doesn't Clear VTOC When Partition Starts After, or Exceeds, 4 GbytesDescriptionThe symptom of this bug in OpenSolaris 2008.05 is that the installation will fail immediately after starting, and one of the last messages in the installation log will be "No space left on device: '/a/./.livecd'". When a new Solaris2 partition is created, or an existing Solaris2 partition is resized or moved, the following problems can occur, if the Solaris2 partition starts after, or exceeds, 4 Gbytes. The fdisk(1M) command clears the primary VTOC, as well as clearing the backup VTOCs. So, the default VTOC is chosen by the kernel. The appropriate operations which handle clearing the VTOC, lseek(2) and write(2), are 32-bit limited. This situation causes the following issues.
WorkaroundA Solaris2 partition must always fit into first 4 Gbytes, otherwise data corruption might occur. # 6690824 fdisk(1M) Corrupts Solaris VTOC, if Linux Swap Primary Partition is DefinedDescriptionThe symptom of this bug in OpenSolaris 2008.05 is that the installation will succeed, but the system will fail to boot with a "Bad PBR sig" or just a "grub>" prompt. If you install on a Solaris2 partition which precedes a Linux swap partition, the following problem occurs. After the installation, while marking the Solaris2 partition as active, the fdisk(1M) utility corrupts Solaris2 VTOC, thus making the installed Solaris partition unusable. WorkaroundUse one of the following workarounds.
# 6694783 Input Method Duplicate Causes IDE CrashDescriptionOn rare occasions, when you log in to the desktop, you may encounter the following issue. The Input Method(IM) status icon is displayed at the bottom of main window. When you open a new child window, such as when you select File->Open, a new IM status icon displays in the main window. When you close this child window, the new IM status icon remains. If you click on an IM status icon at this point, IDE crashes. Workaround
# 2900 Firefox crashes on NV 95DescriptionFirefox dumps core in NV build 95 due to Flash Player bug. Flash plugin v9.0 r124 has a bug that causes Firefox to crash. This issue has been fixed in the flash plugin v 9.0 r125. Note - This affects only users of Flash Player v9.0 r124 and below. Workaround
|