SUSE® Linux* Enterprise Desktop 10 SP1 Release Notes

May 11, 2007

2.5 Other
4.2 Xgl

1.0 Installation

1.1 Upgrading to SP1

Using “System-Update” from the running system is not supported.

If you do update, you might get an error message that the timezone RPM could not be updated: You can click Ignore and disregard this message.

If you boot your system using the SP1 media, then start a fresh install or an upgrade, you can take advantage of new architecture-optimized packages. If you upgrade a running system, not all optimized packages are used.

1.2 Online Update From Behind a Mandatory Proxy Server

If you cannot access https://update.novell.com directly but via a mandatory proxy server, proceed as explained in the Technical Information Document (TID) at http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=3377050&sliceId=SAL_Public.

1.3 Migrating to SP1 with Kernel Module Packages/Add-On Products Installed

The SUSE Linux Enterprise 10 products offer various migration paths for updating the system to Service Pack 1. This item is important if you plan to migrate a system that has an Add-on product or Kernel Module Packages installed (for example, third party drivers from ATI or nVidia).

Updating the system via PatchCD is only possible if no further installation source (such as the SDK) was previously registered. If you depend on this update path, the workaround is to provide the PatchCD via FTP/NFS/HTTP as the installation source.

For more information, see Migration_to_SP1_with_Add-on_and_kmps.

2.0 Platforms, Hardware, and Driver Enhancements

The following new hardware components are now supported via driver and PCI ID updates:

2.1 Network Drivers

  • Updated Broadcom tg3 driver to version 3.69c, with additional support for BCM5754, BCM5755, BCM5715S, BCM5722, BCM5787M, BCM5906M chipsets.

  • Updated Broadcom bnx2 driver to version 1.5.1c, with additional support for BCM5709, BCM5708S chipsets, and fixed IP renewal defect.

  • Added QLogic qla3xxx driver version 2.02.00-k36.

  • Updated Intel e1000 driver to version 7.3.15-NAPI with additional support for ICH8 chipsets.

  • Added NetXEN netxen driver version 2.20.

  • Updated Marvell sky2 driver to version 1.10, fixed interrupt storm handling, and improved hibernation/resume.

  • Updated Intel ipw3945 driver to version 1.1.0 and split from wlan-kmp package provided by ipw3945.

2.2 Storage Drivers

  • Updated Adaptec aic94xx driver to version 1.0.2, and added wide port off expander support.

  • Updated Adaptec aic79xx to support 29320ALP HBA.

  • Updated Emulex lpfc driver to version 8.1.10.2, with advanced sysfs integration and improved management interfaces

  • Updated LSI mptsas driver to version 3.04.02-suse with additional support for LSI1078, SAS6i chipsets.

  • Updated LSI megaraid_sas driver to version 3.05 with additional support for LSI1078, LSI1068 chipsets.

  • Updated LSI megaraid_mbox driver to version 2.20.4.9.

  • Updated LSI megaraid_mm driver to version 2.20.2.7.

  • Updated QLogic qla2xxx driver to version 8.01.07-k3, with additional support for ISP54XX chipset and QLE220, QLE2432 HBAs, and preserved the dump_poll() callback.

  • Updated QLogic qla4xxx driver to version 5.01.00-d1 with additional support for QLA4010, QLA4022 HBAs.

  • Updated HP cciss driver to version 3.6.14.

2.3 Audio Support

  • Additional support for Realtek ALC861 chipset.

2.4 Graphics Support

  • Additional support the Intel 965 and VIA CLE266 chipsets.

2.5 Other

  • Added SATA AHCI link power management.

  • Added support for C2 and C3 states on x86-64 mobility platforms.

  • Added memory support up to 1024GB on x86-64 platforms.

  • Improved memory hot add support.

  • Added ACPI 3.0 System Locality Information Table (SLIT) support.

3.0 ThinkFinger Driver

ThinkFinger is a driver for the UPEK/SGS Thomson Microelectronics fingerprint reader included with some IBM/Lenovo ThinkPads. This technology lets you swipe your finger on the fingerprint reader instead of typing a password to log into your system or to su to root.

Use the tf-tool utility to acquire and verify fingerprints. Run the following command as root:

tf-tool --add-user <login>

to acquire the fingerprint for the user specified in <login>. You will be prompted to swipe your finger. You need three successful swipes to get a fingerprint, which is then stored in /etc/pam_thinkfinger/<login>.bir.

You must also run the command with root as the <login> user:

tf-tool --add-user root

4.0 Known Issues

4.1 ZMD-based Software Management Tools

The ZMD-based software management tools (rug, zen-installer, and zen-updater) show packages from deleted service.

4.2 Xgl

Here are the basic steps to get XGL running if you have supported ATI or NVIDIA* graphics hardware:

NVIDIA

  1. Make sure that the gcc and kernel-source packages are installed.

  2. Go to http://www.nvidia.com/object/unix.html and get the appropriate driver for your hardware. This will be a .run file.

  3. In a terminal as root, issue the init 3 command to switch to runlevel 3.

  4. Use chmod to make the .run file from step 2 executable.

  5. Run the utility ( .run) file, answering yes to all the questions

  6. After the install has completed, we recommend rebooting the system, although running init 5 might be sufficient on most hardware.

  7. Log back in to the desktop. You should now be able to enable 3D Desktop Effects (Xgl) like normal.

ATI

  1. Make sure that the gcc and kernel-source packages are installed.

  2. Go to http://ati.amd.com/support/driver.html and get the appropriate driver for your hardware. This will be a .run file.

    (The ati-driver-installer-8.34.8-x86.x86_64.run driver was posted on 21 February 2007.)

  3. Generate a distribution specific driver package.

    1. Run the installer using the console as root:

      sh ati-driver-installer-8.34.8-x86.x86_64.run --listpkg

      This lists the distributions you can use to build a driver.

    2. Run the following command adding your distribution at the end:

      For example: sh ati*.run --buildpkg SuSE/SLED10-IA32

      The ATI Driver Installer makes a driver package for your system, located in /usr/src/packages/RPMS/i386 or /usr/src/packages/RPMS/x86_64.

  4. Install the driver package.

    1. If you are in runlevel 5, go to runlevel 3 by typing the following command as root:

      init 3

    2. Log in and go to the directory containing the drivers packages you just made.

      For example: cd /usr/src/packages/RPMS/i386

    3. Install the driver packages:

      rpm -Uvh fgl*.rpm

      Make sure you install the following packages:

      x11-video-fglrxG01

      ati-fglrxG01-kmp-<kernel-flavor>

      <kernel-flavor> depends on your installed kernel. Use uname -r to check for the installed default/smp/bigsmp kernel.

    4. After the install is finished, launch the aticonfig utility.

      ldconfig aticonfig --initial --input=/etc/X11/xorg.conf

  5. Configure the newly installed ATI driver by running the following command:

    sax2 -r -m 0=fglrx

    This forces sax2 to use the fglrx driver. Set up your resolution, save, and exit

  6. After the install has completed, we recommend rebooting the system, although running init 5 might be sufficient on some hardware.

  7. Log back in to the desktop. You should now be able to enable 3D Desktop Effects (XGL) like normal

4.3 ATI fglrx Driver

The proprietary ATI fglrx driver does not work with the RC1 kernel.

If you want to use the ati-fglrx driver, workaround kernel packages are provided on the public beta site. This is the same kernel included in RC1 with one less patch that causes this regression in the ATI driver. We are currently working with ATI to get this driver fixed so that is will work with our kernel version going forward.

4.4 Enabling Xgl When Using Proprietary Graphics Drivers

If you enable Xgl when using proprietary graphics drivers, the ability to suspend to ram and to suspend to disk are disabled by default (because they might fail and cause data loss). You can activate these functions manually by editing the /etc/powersave/sleep file.

To activate suspend to ram, set the following value to No:

DISABLE_USER_SUSPEND2RAM=”no”

To suspend to disk, set the following value to No:

DISABLE_USER_SUSPEND2DISK=”no”

Before you do any production work, we recommend testing the suspend and resume functions after you change these values to make sure they are working properly.

4.5 ATI and NVIDIA Drivers Not Supported with Xen

The ATI and NVIDIA proprietary graphics drivers are not supported with Xen.

4.6 Installing with XEN

When installing with XEN on a new install, make sure you select the SUSE Linux Enterprise Desktop 10 option at the GRUB screen during first boot rather than SUSE Linux Enterprise Desktop 10 (Xen). It will default to the latter option, which means you will finish the install in text mode.

XEN Paravirtualized VM cannot be installed from CD.

If you select the XEN pattern during your initial install, the virt-manager package is not installed. You must install this package after the SLED 10 SP1 installation is finished.

4.7 Booting SLED 10 SP1 in VMWare

After installing SLED 10 SP1 in a VMWare virtual machine instance, SLED might not be able to mount the partitions of the virtual disk when booting. If this happens, change the mount by setting from by device id to by device name during the installation.

In the Installations Settings screen, click the Partitioning link.

In the Suggested Partitioning screen, select the Base Partition Setup on this Proposal option. If you want to change the partitioning scheme, select either the Create Custom Partition Setup or Create LVM Based Proposal option. Then click Next.

In the Expert Partitioner screen, perform the following steps for all partitions listed that you want to mount (including swap) or for each new partition you created.

  1. Highlight the partition and click Edit.

  2. In the Edit Partition... dialog box, click Fstab Options.

  3. In the Fstab options dialog box, select the Device name option under Mount in /etc/fstab by, then click OK.

  4. Click OK in the Edit Partition... dialog box.

NOTE:The base hard drives that also appear in the list in the Expert Partitioner screen (usually as /dev/sda or /dev/sdb) do not need editing. The partitions will end in a number (for example, /dev/sda1 or /dev/sdb2).

4.8 OpenOffice.org

OpenOffice.org Writer crashes when recording a simple macro.

4.9 Evolution

Evolution crashes when sending a meeting to a GroupWise user.

4.10 Joining a Local Active Directory Domain During Installation

If you want to join a “.local” Active Directory domain during the SLED 10 SP1 installation, disable the mdns handling by adding mdns off to the /etc/host.conf file.

5.0 More Information and Feedback

Please read the READMEs on the CDs.

You can get detailed changelog information about a particular package from the RPMs themselves by using the following command:

rpm --changelog -qp <FILENAME>.rpm

where <FILENAME>.rpm is the name of the rpm.

The ChangeLog file at the toplevel of CD1 contains a chronological log of all the changes that were made for these updated packages.

Please visit http://www.novell.com/linux/ for the latest Linux product news from SUSE®/Novell®.

6.0 Documentation

For SUSE Linux Enterprise Desktop 10 SP1 documentation, see http://www.novell.com/documentation/sled10.

In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (®, ™, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.

7.0 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to www.novell.com/info/exports/ for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2007 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, 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 of the U.S. patents listed at http://www.novell.com/company/legal/patents/ and one or more additional patents or pending patent applications in the U.S. and in other countries.

For Novell trademarks, see the Novell Trademark ad Service Mark list. All third-party trademarks are the property of their respective owners.

This Novell product includes materials licensed to Novell under the GNU General Public License (GPL). The GPL requires that Novell make available certain source code that corresponds to those GPL-licensed materials. The source code is available for download at http://www.novell.com/linux/source. Also, for up to three years from Novell's distribution of the Novell product, upon request Novell will mail a copy of the source code. Requests should be sent by e-mail to sle_source_request@novell.com or as otherwise instructed at http://www.novell.com/linux/source. Novell may charge a fee to recover its reasonable costs of distribution.