Release Notes for SUSE Linux Enterprise Server 11

GCC 4.3.2

glibc 2.9

Linux kernel 2.6.27

perl 5.10

php 5.2.6

python 2.6.0

ruby 1.8.7

Apache 2.2.10 - Webserver

Bind 9.5.0P2 - The Bind Domain Name Server

Samba 3.2.5

GNOME 2.24

GNOME was updated to the latest version and uses PulseAudio for sound.

KDE 4.1

KDE was updated to the latest 4.1.3 version.

X.org 7.4

PAM configuration

The common PAM configuration files (/etc/pam.d/common-*) are now created and managed with pam-config.

Basic SELinux enablement

In addition to AppArmor, SELinux capabilities were added to SUSE Linux Enterprise Server. While it is not enabled by default, and not supported, this will allow customers to enable and run SELinux with SUSE Linux Enterprise Server if they want to do so.

What does SELinux basic enablement mean?

By enabling SELinux in our codebase, we add missing pieces of code that exist in the community already, and we allow those who wish to use SELinux to do so conveniently without having to replace a big portion of the distribution.

Enablement for TPM/Trusted Computing

SUSE Linux Enterprise Server 11 comes with support for Trusted Computing technology. To enable your system's TPM chip, make sure that the "security chip" option in your BIOS is selected. TPM support is entirely passive, meaning that measurements are being performed, but no action is taken based on any TPM-related activity. TPM chips manufactured by Infineon, NSC and Atmel are supported, in addition to the virtual TPM device for Xen.

IPv6 Improvements

SUSE Linux Enterprise Server can be installed in an IPv6 environment and run IPv6 applications. When installing via network, don't forget to boot with "ipv6=1" (accept v4 and v6) or "ipv6only=1" (only v6) on the kernel command line. Please see the Deployment Guide for additional details. See also "IPv6 Implementation and Compliance" below.

10G networking capabilities

OFED 1.4

traceroute 1.2

Support for traceroute over TCP

Open-FCoE

Open-FCoE is an implementation of the Fibre Channel over Ethernet working draft. Fibre Channel over Ethernet is the encapsulation of Fibre Channel frames in Ethernet packets. It allows users with a FCF (Fibre Channel over Ethernet Forwarder) to access their existing Fibre Channel storage using an Ethernet adapter. When leveraging DCB's PFC technology to provide a loss-less environment, Open-FCoE can run SAN and LAN traffic over the same link.

Data Center Bridging (DCB)

Data Center Bridging (DCB) is a collection of Ethernet enhancements designed to allow network traffic with differing requirements (e.g., highly reliable, no drops vs. best effort vs. low latency) to operate and co-exist on Ethernet. Current DCB features are:

Improved update stack

SUSE Linux Enterprise Server 11 comes with an improved update stack and a new command line tool - zypper - to manage the repositories and install/update packages.

Enhanced YaST partitioner

Extended built-in management infrastructure

CIM enablement with SFCB CIMOM.

Support for Web Services for Management (WS-Management)

The WS-Management protocol is supported via the openwsman project, providing client (package: openwsman-client) and server (package: openwsman-server) implementations. This allows for interoperable management with Windows winrm stack.

Kernel Resource Management

cgroups (Control groups, replaces and enhances CKRM from SUSE Linux Enterprise Server 9), with fine-grained control of CPU, Memory and Devices.

Added Novell developed, open source 'cpuset' command-line tool.

EVMS2 was replaced by LVM2

A public statement can be found at http://www.novell.com/linux/volumemanagement/strategy.html.

Default Filesystem

The default file system in new installations has been changed from ReiserFS to ext3. A public statement can be found at http://www.novell.com/linux/techspecs.html?tab=0 and in our FAQ at: http://www.novell.com/linux/filesystems/faq.html

UEFI enablement on AMD64/Intel64

SWAP over NFS

Hardware

z/VM

Storage

Network

Security

RAS

Web 2.0 Open Source Stack in SUSE Linux Enterprise Software Development Kit

Functionality implemented in SUSE Linux Enterprise Server 11 (and SUSE Linux Enterprise Server 10 Service Pack 2.)

L1: Installation and problem determination, which means technical support designed to provide compatibility information, installation configuration assistance, usage support, on-going maintenance and basic troubleshooting. Level 1 Support is not intended to correct product defect errors.

L2: Reproduction of problem isolation, which means technical support designed to duplicate customer problems, isolate problem area and potential issues, and provide resolution for problems not resolved by Level 1 Support.

L3: Code debugging and problem resolution, which means technical support designed to resolve complex problems by engaging engineering in patch provision, and resolution of product defects which have been identified by Level 2 Support.

Technology Previews and SELinux Basic Enablement

Sounds, Graphics, Fonts and Artwork

Packages, which require an additional customer contract

Packages on the Software Development Kit (SDK)

BEA Java (Itanium only)

MySQL Database

PostGreSQL Database

WebSphere CE Application Server

Hot-Add of Memory

Hot-Add-memory is currently only supported on the following hardware:

If your specific machine is not listed, please call Novell support to confirm whether or not your machine has been successfully tested. Also, please regulary check our maintenance update information, which will explicitly mention the general availability of this feature.

Restriction on using IBM eHCA InfiniBand adapters in conjunction with Hot-Add of Memory on IBM System p:

The current eHCA Device Driver will prevent dynamic memory operations on a partition as long as the driver is loaded. If the driver is unloaded prior to the operation and then loaded again afterwards, adapter initialization may fail. A Partition Shutdown / Activate sequence on the HMC may be needed to recover from this situation.

Internet Storage Naming Service (iSNS)

The Internet Storage Naming Service (iSNS) package is by design suitable for secure internal networks only. Novell will continue to work with the community on improving security on this.

Linux Filesystem Capabilities

Our kernel is compiled with support for Linux Filesystem Capabilities. This is disabled per default and can be enabled by adding file_caps=1 as kernel boot option.

eCryptfs Filesystem

The eCryptfs kernel modules and the ecryptfs-utils package shipped with SUSE Linux Enterprise Server 11 are a preview of a stacked cryptographic filesystem for Linux.

Ext4 Filesystem

The Ext4 kernel modules and userland tools shipped with SUSE Linux Enterprise Server 11 are a preview of a new filesystem for Linux.

PerfMon2

The PerfMon2 kernel modules and userland tools shipped with SUSE Linux Enterprise Server 11 are a preview of a performance monitoring tool for Linux. It will be replaced with a successor if accepted and integrated into the official Kernel.

KVM

SUSE Linux Enterprise Server 11 contains KVM as an additional virtualization solution. It is not supported by Novell, but an area of interest for future development and deliveries.

puppet

The puppet tools shipped with SUSE Linux Enterprise Server 11 are a Technology Preview.

biosdevname

biosdevname in its simplest form takes a kernel name as an argument, and returns the BIOS-given name it "should" be. This is necessary on systems where the BIOS name for a given device (e.g., the label on the chassis is "Gb1") doesn't map directly and obviously to the kernel name (e.g., eth0).

Read-Only Root Filesystem

It is possible to run SUSE Linux Enterprise Server 11 on a read-only root filesystem. Due to the large number of possible configurations, this is currently not a supported scenario.

The /tmp and /var/tmp directories need to be on a separate partition and cannot be mounted read-only.

After the installation has finished and all services are configured, login as root and do the following modifications:

Modify /etc/fstab and add "ro" to the mount options of the root filesystem entry.

   rm /etc/mtab
   ln -s /proc/mounts /etc/mtab
   mkdir /var/lib/hwclock
   mv /etc/adjtime /var/lib/hwclock
   ln -s /var/lib/hwclock/adjtime /etc/adjtime
   # the following two steps are only necessary if you use dhcp:
   mv /etc/resolv.conf /var/lib/misc/
   ln -s /var/lib/misc/resolv.conf /etc/resolv.conf
   # Now mount root filesystem read-only and reboot
   mount -o remount,ro /
   reboot
   

Modified operation against Novell Customer Center

Effective on 2009-01-13, provisional registrations will be disabled in the Novell Customer Center. Registering an instance of SUSE Linux Enterprise Server or Open Enterprise Server (OES) products now requires a valid, entitled activation code. Evaluation codes for reviews or proofs of concept can be obtained from the product pages and from the download pages on novell.com. If a device is registered without a code at setup time, a provisional code is assigned by Novell Customer Center (NCC) to the device, and an entry for it is made in your NCC list of devices. No update repositories are assigned to the device at this time. Once you are ready to assign a code to the device, starting the YaST Novell Customer Center registration module and putting in the appropriate code (replacing the un-entitled provisional code that NCC generated) will fully entitle the device and activate the appropriate update repositories.

Operation against Subscription management Tool

Operation under the Subscription Management Tool (SMT) package and registration proxy is not affected. Registration against SMT will assign codes automatically from your default pool in NCC until all entitlements have been assigned. Registering additional devices once the pool is depleted will result in the new device being assigned a provisional code (with local access to updates), and the SMT server will provide appropriate notification to the administrator that these new devices need to be entitled.

Minimal Pattern

The minimal pattern provided in YaST's Software Selection Dialog targets experienced customers and should be used as a base for your own specific software selections.

Please do not expect that an unchanged / not-extended minimal pattern provides a useful basis for your business needs.

This pattern does not include any dump- or logging-tools. To fully support your configuration, Novell Technical Services (NTS) will request the installation of all the tools which are needed for further analysis, in case of a support request.

SPident

SPident is a tool to identify the Service Pack level of the current installation. This tool is not delivered with SUSE Linux Enterprise Server 11 GA, but is replaced by the new SAM tool (package "suse-sam").

Linux Completely Fair Scheduler affects Java performance

Problem (Abstract)

Java applications that use synchronization extensively might perform poorly on Linux systems that include the Completely Fair Scheduler. If you encounter this problem, there are two possible workarounds.

Symptom

You may observe extremely high CPU usage by your Java application, and very slow progress through synchronized blocks. The application may appear to hang due to the slow progress.

Cause

The Completely Fair Scheduler (CFS) is a scheduler that was adopted into the mainline Linux kernel as of release 2.6.23. The CFS algorithm is different from previous Linux releases. It might change the performance properties of some applications. In particular, CFS implements sched_yield() differently, making it more likely that a thread that yields will be given CPU time regardless. More information on CFS can be found here: "Multiprocessing with the Completely Fair Scheduler", http://www.ibm.com/developerworks/linux/library/l-cfs/?ca=dgrlnxw06CFC4Linux

The new behavior of sched_yield() might adversely affect the performance of synchronization in the IBM JVM.

Environment

This problem may affect IBM JDK 5.0 and 6.0 (all versions) running on Linux kernels that include the Completely Fair Scheduler, including Linux kernel 2.6.27 in SUSE Linux Enterprise Server 11.

Resolving the problem

If you observe poor performance of your Java application, there are two possible workarounds:

You should not use these workarounds unless you are experiencing poor performance.

Tuning performance of simple database engines

Simple database engines like Berkeley DB use memory mappings (mmap(2)) to manipulate database files. When the mapped memory is modified, those changes need to be written back to disk. In SUSE Linux Enterprise 11, the kernel includes modified mapped memory in its calculations for deciding when to start background writeback, and when to throttle processes which modify additional memory. (In previous versions, mapped dirty pages were not accounted for, and the amount of modified memory could exceed the overall limit defined.) This can lead to a decrease in performance; the fix is to increase the overall limit.

The maximum amount of dirty memory is 40% in SUSE Linux Enterprise 11 by default. This value is chosen for average workloads, so that enough memory remains available for other uses. The following settings may be relevant when tuning for database workloads:

These limits can be observed or modified with the sysctl utility (see sysctl(1), sysctl.conf(5)).

Memory controller (cgroup) is disabled by default

Memory cgroup is runtime-disabled by default in SUSE Linux Enterprise Server 11 due to speed regressions introduced by this facility. Please pass "cgroup_enable=memory" to the kernel commandline to have this enabled.

Multipathing - SCSI Hardware Handler

Some storage devices, e.g. IBM DS4K, require special handling for path failover and failback. In SUSE Linux Enterprise Server 10 SP2, this was handled at the dm layer as hardware handler.

One drawback of this implementation was that the underlying SCSI layer didn't know about the existence of the Hardware Handler. Hence, during device probing, SCSI would send I/O on the passive path, which would fail after a timeout and also print extraneous error messages in the console.

In SUSE Linux Enterprise Server 11, this problem is resolved by moving the hardware handler to the SCSI layer, hence the term SCSI Hardware Handler. These handlers are modules created under the SCSI directory in the Linux Kernel.

In SUSE Linux Enterprise Server 11, there are four SCSI Hardware Handlers: scsi_dh_alua, scsi_dh_rdac, scsi_dh_hp_sw, scsi_dh_emc.

These modules need to be included in the initrd image so that SCSI knows about the special handling during probe time itself.

This can be done by following these steps:

Multipathing: failed paths do not return after a path failure

To work in a fully certified environment with all storage backend systems and fully supported by Novell and your storage vendor, please make sure that you have installed at least multipath-tools-0.4.8-40.2 or a later version. Appropriate packages are available as a maintenance update for SUSE Linux Enterprise 11.

Local Mounts of iSCSI Shares

An iSCSI shared device should never be mounted directly on the local machine. In an OCFS2 environment, doing so causes all hardware to hard hang.

Installation on systems with many LUNs (storage)

While the number of LUNs for a running system is virtually unlimited, we suggest not having more than 64 LUNs online while installing the system, to reduce the time to initialize and scan the devices and thus reduce the time to install the system in general.

Reiserfs and HP Storage (on Itanium only)

HP and Novell are currently evaluating a report that Reiserfs filesystems show unexpected behaviour under heavy load.

Other filesystems (xfs and ext3) are not affected by those findings, and we encourage you to use one of those two according to your needs and preference.

This is addressed with high priority. We will issue a maintenance update via http://support.novell.com/ once this has been resolved.

Supported Hardware / Systems

All POWER3, POWER4, PPC970 and RS64–based models that were supported by SUSE Linux Enterprise Server 9 are no longer supported.

Loading the installation kernel via network on POWER

With SUSE Linux Enterprise Server 11 the bootfile DVD1/suseboot/inst64 can not be booted directly via network anymore, because its size is larger than 12MB. To load the installation kernel via network, copy the files yaboot.ibm, yaboot.cnf and inst64 from the DVD1/suseboot directory to the TFTP server. Rename the yaboot.cnf file to yaboot.conf. yaboot can also load config files for specific ethernet MAC addresses. Use a name like yaboot.conf-01-23-45-ab-cd-ef match a MAC address. An example yaboot.conf for TFTP booting looks like this:

  default=sles11
  timeout=100
  image[64-bit]=inst64
    label=sles11
    append="quiet install=nfs://hostname/exported/sles11dir"
   

Please note that this will not work on POWER4 systems. Their firmware can only load files up to 12MB via TFTP.

Huge Page Memory support on POWER

Huge Page Memory (16GB pages, enabled via HMC) is supported by the Linux Kernel, but special kernel parameters must be used to enable this support. Boot with the parameters "hugepagesz=16G hugepages=N" in order to use the 16GB huge pages, where N is the number of 16GB pages assigned to the partition via the HMC. The number of 16GB huge pages available can not be changed once the partition is booted. Also, there are some restrictions if huge pages are assigned to a partition in combination with eHEA / eHCA adapters:

IBM eHEA Ethernet Adapter:

The eHEA module will fail to initialize any eHEA ports if huge pages are assigned to the partition and Huge Page kernel parameters are missing. Thus, no huge pages should be assigned to the partition during a network installation. To support huge pages after installation, the huge page kernel parameters need to be added to the boot loader configuration before huge pages are assigned to the partition.

IBM eHCA InfiniBand Adapter:

The current eHCA device driver is not compatible with huge pages. If huge pages are assigned to a partition, the device driver will fail to initialize any eHCA adapters assigned to the partition.

Installation on POWER onto IBM vscsi target

The installation on a vscsi client will fail with old versions of the AIX VIO server. Please upgrade the AIX VIO server to version 1.5.2.1-FP-11.1 or later.

IBM Linux VSCSI server support in SUSE Linux Enterprise Server 11

At this point, there is no support for the VSCSI server functionality in SUSE Linux Enterprise Server 11. Customers who serve disks or partitions from Linux should not upgrade. Please continue to use the ibmvscsis driver in either SUSE Linux Enterprise Server 9 or 10.

Virtual Fibre Channel devices

When using IBM Power Virtual Fibre Channel devices utilizing N-Port ID Virtualization, the Virtual I/O Server may need to be updated in order to function correctly. Linux requires VIOS 2.1, Fixpack 20.1, and the LinuxNPIV I-Fix in order for this feature to function properly. These updates can be downloaded from the following URL: http://www14.software.ibm.com/webapp/set2/sas/f/vios/home.html

Virtual Tape Devices

When using a virtual tape served by an AIX VIO server and running

mt -f <Virtual Tape Device> setblk <Size>

the command will fail. To use the tape device again, VIOS has to be rebooted or the tape has to be reloaded.

Please check for updates on the IBM Virtual I/O Server support page for fixes to this problem.

ITrace

Using the ITrace instrumentation library, libperfutil, to start and stop tracing on your application may result in a system hang. A workaround for this problem is to insert a call to ITraceDisable() prior to calling ITrace_off() in your instrumented application.

Chelsio cxgb3 iSCSI offload engine

The Chelsio hardware supports ~16K packet size (the exact value depends on the system configuration). It is recommended that you set the parameter MaxRecvDataSegmentLength in /etc/iscsid.conf to 8192.

For the cxgb3i driver to work properly, this parameter needs to be set to 8192.

In order to use the cxgb3i offload engine, the cxgb3i module needs to be loaded manually after open-scsi has been started.

For additional information, please refer to /usr/src/linux/Documentation/scsi/cxgb3i.txt in the kernel source tree.

Known TFTP issues with yaboot

When attempting to netboot yaboot users may see the following error message: "Can't claim memory for TFTP download (01800000 @ 01800000-04200000)" and the netboot will stop and immediately display the yaboot "boot:" prompt. Use the following steps to work around the problem.

IBM System z Architecture Level Set (ALS) preparation

To exploit new IBM System z architecture capabilities during lifecycle of SUSE Linux Enterprise Server 11 support for machines of type z900, z990, z800, z890 is deprecated this release. Novell plans to introduce an ALS earliest with SUSE Linux Enterprise Server 11 Service Pack 1 (SP1), latest with SP2. After ALS SUSE Linux Enterprise Server 11 only executes on z9 or newer processors.

With SUSE Linux Enterprise Server 11 GA only machines of type z9 or newer are supported.

When developing software, we recommend to switch gcc to z9/z10 optimization:

The minimum required machine loader level for IPL of SUSE Linux Enterprise Server 11 from a SCSI disk is v1.4 which is included in the follow MCLs:

For older levels of the machine loader, the ramdisk load address of the installed SUSE Linux Enterprise Server 11 system needs to be manually changed from 0x2000000 to 0x1000000. To do this, open the /etc/zipl.conf file and change lines containing ramdisk = <initrd filename>,0x2000000 into ramdisk = <initrd filename>,0x1000000and run the zipl command afterwards. Note that this workaround may not work on systems with large amount of memory.

For LUN Scanning to work properly, the minimum Storage firmware level should be:

Large Page support in IBM System z

Possibility for processes to allocate process memory in chunks of 1 MByte instead of 4 KByte. This works through the hugetlbfs.

Installation onto an unformatted ECKD DASD (System z)

An unformatted DASD has to be formatted before its first usage. The procedure is as follows:

For more information please consult the SUSE Linux Enterprise Server Deployment Guide.

Autoyast installation on System z.

When installation via autoyast is done, an error message may pop up after the hardware detection, saying: "No hard disks were found for the installation." This is because the disk configuration will happen after automatic hardware detection. Just click "OK" or let the message timeout. The installation will continue as expected.

IBM zfcp and multipathing / MPIO

The IBM zfcp SCSI driver is currently not taking full advantage of the new multipath/failover functionality in the SCSI midlayer in SUSE Linux Enterprise Server 11.

Packages containing this improved functionality will be provided via maintenance updates. Customers will be informed via the usual communication paths.

OSA Layer2 Installation on LPAR: MAC address mandatory

When installing with a OSA network device in Layer 2 mode in LPAR, it is mandatory to enter a unique MAC address in the format 01:23:45:67:89:AB when asked for. Leaving this field blank doesn't work in LPAR.

Collaborative memory management Stage II (CMM2) currently not available

IBM and Novell are working to integrate this technology into the Linux Kernel and move it to a supported solution in SUSE Linux Enterprise Server as soon as available upstream.

Issue with SLES 11 and NSS under z/VM

Starting SLES 11 under z/VM with NSS sometimes makes guest to logoff by itself.

Solution: IBM addresses this issue with APAR VM64578.

All modules of a self-recompiled kernel are by default marked as unsupported.

Kernel Modules supported by Novell partners and delivered using Novell's Partner Linux Driver process are marked "external".

If the "supported" flag is not set, loading a module will taint the kernel. Kernels which are tainted are not supported. To avoid this, not supported Kernel modules are included in an extra RPM (kernel-<flavor>-extra) and will not be loaded by default ("flavor"=default|smp|xen|...). In addition, those unsupported modules are not available in the installer, and the package kernel-$flavor-extra is not on the SUSE Linux Enterprise Server media.

Kernel Modules not provided under a license compatible to the License of the Linux Kernel will also taint the Kernel; see /usr/src/linux/Documentation/sysctl/kernel.txt and cf. the state of "/proc/sys/kernel/tainted".

Linux Kernel

The value of /proc/sys/kernel/unsupported defaults to 2 on SUSE Linux Enterprise Server 11 ("do not warn in syslog when loading unsupported modules"). This is the default used in the installer as well as in the installed system. See /usr/src/linux/Documentation/sysctl/kernel.txt for more information.

modprobe

The "modprobe" utility for checking module dependencies and loading modules appropriately checks for the value of the "supported" flag. If the value is "yes" or "external" the module will be loaded, otherwise it will not. See below, for information on how to override this.

Note: Novell does not generally support removing of storage modules via modprobe -r.

You can override the default by changing the variable allow_unsupported_modules in /etc/modprobe.d/unsupported-modules and set the value to "1".

If you only want to try loading a module once, the --allow-unsupported-modules command-line switch can be used with modprobe. (see: man modprobe).

During installation, unsupported modules may be added through driver update disks, and they will be loaded.

To enforce loading of unsupported modules during boot and afterwards, please use the kernel command line option oem-modules.

While installing and initializing the module-init-tools package, the kernel flag "TAINT_NO_SUPPORT" ("/proc/sys/kernel/tainted") will be evaluated. If the kernel is already tainted, allow_unsupported_modules will be enabled. This will prevent unsupported modules from failing in the system being installed. (If no unsupported modules are present during installation and the other special kernel command line option is not used, the default will still be to disallow unsupported modules.)

If you install unsupported modules after the initial installation and want to enable those modules to be loaded during system boot, please don't forget to run depmod and mkinitrd.

Section 3: RFC 4862 - IPv6 Stateless Address Autoconfiguration

Some tests fail because of the default DAD handling in Linux; disabling the complete interface is possible, but not the default behavior (because security-wise, this might open a DoS attack vector, a malicious node on a network could shutdown the complete segment) this is still conforming to RFC 4862: the shutdown of the interface is a "should", not a mandatory ("must") rule.

The Linux kernel allows you to change the default behavior with a sysctl parameter. To do this on SUSE Linux Enterprise Server 11, you need to make the following changes in configuration:

Section 4: RFC 1981 - Path MTU Discovery for IPv6

On these two tests ping6 needs to be told to allow defragmentation of multicast packets. Newer ping6 versions have this disabled by default. Use: ping6 -M want <other parameters>. see man ping6 for more information

Enable IPv6 in Yast for SCTP support

SCTP is dependent on IPv6, so in order to successfully insert the SCTP module, IPv6 must be enabled in YaST. This allows for the IPv6 module to be automatically inserted when `modprobe sctp` is called.

Changes to network setup

The script modify_resolvconf is removed in favor of a more versatile script called netconfig. This new script handles specific network settings from multiple sources more flexibly and transparently. Please review the documentation and man-page of netconfig for more details.

Locale Settings in ~/.i18n

If you are not satisfied with locale system defaults, change the settings in ~/.i18n. Entries in ~/.i18n override system defaults from /etc/sysconfig/language. Use the same variable names but without the RC_ namespace prefixes; for example, use LANG instead of RC_LANG. For more information about locales in general, see "Language and Country-Specific Settings" in the Reference Manual.

Configuration of kdump

The kernel is crashing or otherwise misbehaving and a kernel core dump needs to be captured for analysis.

Please use YaST (System->Kernel Kdump) to configure your environment.

JPackage Standard for Java Packages

Java packages are changed to follow the JPackage Standard (http://www.jpackage.org/). Please read the documentation in /usr/share/doc/packages/jpackage-utils/ for more information.

Pulseaudio

For better sound functionality on SUSE Linux Enterprise systems we strongly recommend that pulseaudio 0.9.14 or higher is installed. This version is available via maintenance channels for SUSE Linux Enterprise systems registered with Novell.