Novell is now a part of Micro Focus

Recommended update for release-notes


(Last modified: 17AUG2005)

solutions Recommended update for release-notes SuSE Linux Maintenance Web (ae4451c5ff5007fc5609978de3c067a0)

Applies to

Package: release-notes
Product(s): SUSE CORE 9 for IBM POWER
Patch: patch-10428
Release: 20050817
Obsoletes: none


  • Add download locations to Emulex firmware section Two minor spelling fixes in vacation tool and PCI driver autoloading.
  • Update entry about required firmware level for Emulex adapters: LP10000, LP10000DC, LP10000ExDC 1.90a4 LP982, LP9802 1.81x1
  • Adding entry about changed partition types in YaST (#94918)
  • Adding entry about PCI driver autoloading via coldplug (#96878)
  • Update installation server howto for SP2. Use rescue file from SP instead of GA. (#95413 , #63327)
Complete new release notes:
SP2 Release Notes
A comprehensive list of what Service Pack 2 includes
(Features, driver updates)
can be found in the file Notes on the CD.
These release notes are structured as follows:
  • Issues applying for SP2 exclusively.
  • Original release notes as shipped with SLES9 GA.
    • General: Information that everybody should read.
    • Update: Explains changes that are not mentioned in the Admin Guide, Chapter 2.
    • Installation: Additional pertinent information for the installation.
    • Updates and Features: This sections contains a number of technical changes and enhancements for the experienced user.
    • Providing Feedback
If you intend to install the SLES9 GA release, skip the following section "SP2 Release Notes" and start reading below with the "GA Release Notes" section.
SP2 Release Notes
Installing with SP2
SP2 is just another install CD. It is important to ensure that you either boot of it directly or copy the file "driverupdate" to the installation server.
SPident Reports the Service Pack Level
SPident is a tool to identify the Service Pack level of the current installation.
SPident may report that the system has not reached the level of Service Pack 2. This happens, when so-called "optional" updates, which will not be automatically installed by YOU, are not manually selected during update. If you use or need any of these packages which have optional updates you should select these in order to reach SP2 level.
Included support for Oracle Cluster Filesystem 2 (ocfs2) for limited use
At the time of this release notes support is limited to the following conditions:
  • x86, AMD64 & Intel EM64T, IPF hardware platform (not: IBM POWER, IBM S/390 & zSeries)
  • valid support agreement with Novell and Oracle
  • use as a home for Oracle RAC (no general purpose use)
Support conditions may be extended over time. Please contact your Novell sales or support representative about the current status. Recognizing New Virtual DASD Devices (NWSSTG) from Linux Running in
On IBM POWER systems, new virtual DASD devices (NWSSTG) need user intervention to be recognized from Linux running in an LPAR. After creating and varying on a new NWSD and NWSSTG on the OS/400 side, the following command will make the device visible in Linux (this applies only to iSeries i5 Systems):
echo "scsi add-single-device x 0 y 0" > /proc/scsi/scsi
  • x = host device or adapter (the number from "scsi#" from the output of cat /proc/scsi/scsi)
  • 0 = bus
  • y = target (SCSI target ID)
  • 0 = lun
Boot Loader Installation to Emulex Attached Adapters
On IBM pSeries and IBM POWER i5/p5 systems, the bootloader installation to drives attached to Emulex adapters is now supported.
Boot Loader Installation to Qlogic FibreChannel Attached Adapters
On IBM JS20 blade systems, the bootloader installation to drives attached to Qlogic FibreChannel adapters is now supported.
YaST2 Expert Partitioner and Wrong /boot Proposal
On IBM POWER systems, the YaST2 expert partitioner suggests creating a partition for /boot. This partition is not needed on POWER systems and should not be created, because it may confuse the boot loader installation process and can result in an unbootable system.
Instead, a primary partition of type PReP boot (type 0x41) with no mount point and a recommended size of 16MB must be present. By default, YaST2 creates such a partition. The boot loader installation process (the lilo script for POWER architectures) takes care of reducing the size and changing the type of this partition to meet the boot loader requirements according to the type of POWER system on which the installation runs.
Booting from SLES9 Service Pack 2 CD 1 on IBM iSeries Systems
To boot from SLES9 Service Pack 2 CD 1 on IBM iSeries systems, set the "IPL stream file" parameter in the Network Server Description to
The SU90SP2.P01 part of the path is the disk label of CD 1.
On SLES9 SP2 non-existing SCSI devices may be reported for certain
With SCSI midlayer changes in SLES9 SP2, the interaction with certain SCSI drivers (such as the ibmvscsic driver) results in the reporting of LUN 0 for all possible SCSI targets. You will see this during boot time, or in /proc/scsi/sg/devices. This will have no adverse effects, however adding an extra storage controller may give you non-obvious results.
The lsvpd serviceability package also produces some messages, due to unexpected behaviour related to this issue. These messages do not indicate a problem.
On JS20 blades system, booting from the second port of the Qlogic JS20
Fibre Channel Expansion Card is not supported
Support for two port Qlogic JS20 Fibre Channel Expansion Card (Part Number 73P6112) only includes boot support to storage on the first port. If you try to install your boot loader to storage on the second port you will receive an error message like this at the end of the installation:
Error occurred while installing yaboot. running on chrp boot target is /dev/sda ERROR: returned error 1 while analyzing path /dev/sda1 ERROR: Internal problem: Could not determine open firmware path to '/dev/sda1'
To work around that problem please select a boot partition on another disk.
Systems with PERC3 or PERC4 RAID controllers
To update a GA version to SP2 you need to boot with the SP2 CD1. The 'Patch CD update' will not work on these systems.
An update from SP1 to SP2 can be made with any of the documented update methods.
Using SCSI or hotplug devices may lead to boot failure or mount
On reboot, SCSI or hotplug devices may be assigned to different device file names than before. If the root filesystem moved to a different device name, the kernel will not find it and fail booting.
For a root filesystem use mount by volume label, see below.
For all other filesystems configure mount by UUID using YaST2:
  • In YaST2 go to the Partitioner
  • For every SCSI device partition /dev/sd? with a mount point, go to Edit... -> Fstab Options and select Mount in /etc/fstab by UUID.
Using mount by volume label for root filesystem:
  • Assign a volume label to the root filesystem and activate mount by volume label Go to the YaST2 Partitioner. Select the root filesystem (Mount on /) and go to Edit, then Fstab Options. Check Mount in /etc/fstab by Volume label. Enter a label in the field Volume Label, e.g. rootvollabel. Be sure to use a volume label that is not used by any other volume in the system. Commit changes (press Ok, Ok, Next).
  • Set up the root= kernel parameter in the bootloader configuration Go to the YaST2 Boot Loader Setup. Press Edit Configuration Files. In the line that starts with append =, add root=LABEL=rootvollabel to the kernel command line. rootvollabel is the Label you assigned to the root filesystem above. Commit changes (press Ok, Finish).
Shared Update disks can't be mounted read only on multiple partitions
Shared virtual disks (NWSSTGS) between different secondary partitions are not supported on SuSE SLES9. Because of changes in the kernel infrastructure from 2.4 to 2.6, it is impossible for the viodasd driver to correctly test if the disk has already been mounted, a prerequisite for correct operation.
If you need a shared data area, you should investigate a network based solution such as NFS or Samba. You can run a solution like this across the virtual ethernet on your partitions.
Using the Rescue System on Systems with Many Devices
The rescue system contains device nodes for a limited number of devices. If your system has more devices, use the command
on the command line. This creates the missing device nodes in /dev for all devices that are listed in /sys.
Apache Modules util_ldap and mod_auth_ldap
The apache modules util_ldap and mod_auth_ldap have been updated from 2.0.49 to 2.0.52 level, because of the number of bugs fixed in these modules. They are still declared experimental by the authors. The update causes a minor binary incompatibility in the API exposed by the util_ldap module. Only third-party software built directly on top of util_ldap is affected by this incompatibility. There is *no* incompatible change in the functionality provided by the two modules or in their configuration.
GA Release Notes
These release notes cover the following areas:
  • General: Information that everybody should read.
  • Update: Explains changes that are not mentioned in the Admin Guide, chapter 2.
  • Installation: Additional pertinent information for the Installation.
  • Updates and Features: These sections contains a number of technical changes and enhancements for the experienced user.
  • Providing Feedback
Updated SLES 9 manuals and translations of YaST messages
You will find the SLES 9 manuals in pdf format on CD1 in the directory "docu". They contain a vast collection of valuable information. Please read them as they may answer many questions for you. Translations for YaST are also included. Feedback on documentation and translations should be mailed to
Polish language support
If Polish language support is needed, please make sure to install the packages kde3-i18n-pl and yast2-trans-pl. You have to select them manually from the selection list.
Removable Media / subfs
Removable media are now integrated via subfs. It is not necessary to mount the media manually. A cd /media/* triggers the automatic mounting. Note that media cannot be ejected while a program is accessing them.
Outdated boot loader message during CD install on POWER
When starting an install of SLES9 for POWER from CD, the user will be prompted with an outdated boot loader message saying: Welcome to SuSE Linux (SLES9 preview)!. This message can savely be ignored. It should read Welcome to SUSE Linux Enterprise Server 9 for POWER
Globus Toolkit 2.0
The Globus Toolkit 2.0 was part of SUSE Linux Enterprise Server 8. Because of major changes in the Globus TK API and of binaries we have decided to not include Globus Toolkit 2.x or 3.x into SUSE Linux Enterprise Server 9. Support for the Globus Toolkit is available through a consulting agreement. Please contact for available offerings.
The Common Internet File System (CIFS) which is shipped together with the Kernel is currently not supported. The current implementation is not stable enough to work in a production environment.
Network Device Setup
The network device setup has been changed. Previously the configuration of a non-existing interface triggered initialisation of the hardware. Now, new hardware is searched for and initialised first, which then triggers the setup of the new network interface.
Additionally new names are introduced for the configuration files. Since the name of a network interface is created dynamically and the usage of hotplug devices increases more and more, a name like ethX is not usable anymore for configuration purposes. Therefore we now use unique descriptions like the MAC-address or the PCI slot for naming of interface configurations.
Note: You can use interface names once they are present. ifup eth0 / ifdown eth0 still works.
The configuration for devices is found in /etc/sysconfig/hardware. The interfaces these devices provide is found as usual (only with different names) in /etc/sysconfig/network.
An extended README is available under /usr/share/doc/packages/sysconfig/README.
If the DHCP daemon is set to start at boot time and the system is updated from SLES8 to SLES9, this setting will be lost during the update process due to a packaging bug. To re-enable starting of the DHCP server at boot time, use the command chkconfig -a dhcpd or, alternatively, the YaST2 runlevel editor.
Sound configuration
After an update from an older distribution the sound cards will have to be reconfigured. This can be done using the sound module of YaST2. Invoke YaST as user root using the command yast2 sound.
Non UTF-8 filenames
Files on filesystems created by 9.0 and older distributions (when not set otherwise) use non-UTF-8 encoding. If these file names contain non ASCII characters, they will be garbled on SLES 9 and later versions. One fix is to use the convmv script which changes the encoding of the files to UTF-8.
XML Stylesheets and DTDs
The FHS now requires XML resources (DTDs, stylesheets, etc.) to be installed in /usr/share/xml. Therefore, some directories are no longer available in /usr/share/sgml. If you encounter problems, modify your scripts or makefiles or use the official catalogs (especially /etc/xml/catalog or /etc/sgml/catalog).
Codepage with mounting VFAT partitions
When mounting VFAT partitions the parameter formerly called code= must be changed to codepage=. If mounting a VFAT partition causes problems, check if the file /etc/fstab contains the old name for the parameter.
Apache 1.3 has been replaced by Apache 2
The apache web server (version 1.3) has been replaced by apache2 (version 2.0.49). A system update on a machine with a HTTP server installation will remove the apache package, install apache2 after which will need to adapt your setup manually, because there is no automated facility available.
Configuration files that were under /etc/httpd are now in /etc/apache2. Apache2 requires either package apache2-prefork (recommended for stability) or apache2-worker.
During update there may be some conflicts requiring manual attention
Known issues:
  • horde requires either apache2-mod_php4 or apache-mod_php4 In this case either deinstall horde (if you do not need it), or select the mod_php4 package belonging to the Apache version you want to use.
  • dprobes conflicts with oprofile (over libbfd) In this case please chose deinstallation of dprobes. dprobes is not provided with SLES 9.
Using SAMBA with LDAP
If you used Samba on SLES 8 with SAMBA_SAM set to "ldap" in /etc/sysconfig/samba you need to migrate your Samba LDAP configuration to the new Samba 3 LDAP schema as included in SLES 9.
Raw Devices
There have been significant changes in the implementation of raw devices. For more details, see /usr/share/doc/packages/util-linux/README.raw which is provided in the util-linux package.
Emulex Controller
Please use the following minimum firmware revisions on Emulex hardware.
LP10000, LP10000DC, LP10000ExDC 1.90a4 LP1050, LP1050DC, LP1050Ex 1.80a1 LP982, LP9802 1.81x1 LP9000, LP9002C, LP9002DC, LP9002L, LP9402DC 3.90a7 (3.92a2 for LP9002) LP8000, LP8000DC, LP850 3.90a7 (Dragonfly >= 2.00), 3.30a7 (Dragonfly < 2.00) LP952L 3.92a2 LP101 1.90a4 LP1005DC-CM2 1.90a5
To update the firmware of your Emulex hardware, install the Emulex Applications kit from here: And use either the lputil (text menu) or HBanywhere (gui) tools. You should also check the OEM page for information about your specific OEM adapter:
Installing with an FTP-Server
If you use an FTP-Server to provide the CDs for installation, there is a restriction for the path you specify during the installation. Currently, you may only specify relative paths. That means that every path specified starts at the login directory of the ftp server. There is no difference whether you use a personal or anonymous login.
Same CD requested twice
Depending on the selection you chose it is possible that some CDs have to be inserted twice during the installation process. This is a known issue, but due to dependencies it cannot always be avoided. A workaround is to install via network or harddisk instead of CDs.
Setting up an installation server for network installations
If you have a SLES9 already installed, use the YaST installation-server module to create a network install source. It can be found below Misc - Installation Server in the YaST main screen.
Note: the SLES9 GA version of the YaST installation-server module can not integrate SLES9 service pack iso images. This bug was fixed in SLES9 SP1. Either upgrade the server to SP1 or newer, or just update the yast2-instserver.rpm: rpm -Uvh /SP1-CD1/suse/noarch/yast2-instserver-2.9.22-0.2.noarch.rpm Restart YaST after the yast2-instserver package update.
Every new service pack CD provides an updated rescue system on CD1/boot/rescue. To use this new rescue system on a YaST generated installation source, remove the 'boot' symlink in the toplevel directory. rm boot mkdir boot cp SUSE-SLES-Version-9/CD1/boot/root ./boot/root cp SUSE-SLES-9-Service-Pack-Version-2/boot/rescue ./boot/rescue
To manually set up an installation Server for installations via NFS/FTP/HTTP the CDs have to be copied into a special directory structure.
Go to a directory of your choice and execute the following commands:
mkdir -p installroot/sles9/CD1
# now copy the contents of SLES CD1 into this directory
mkdir -p installroot/core9/CD1
# now copy the contents of SLES CD2 into this directory
mkdir -p installroot/core9/CD2
# now copy the contents of SLES CD3 into this directory
mkdir -p installroot/core9/CD3
# now copy the contents of SLES CD4 into this directory
mkdir -p installroot/core9/CD4
# now copy the contents of SLES CD5 into this directory
mkdir -p installroot/core9/CD5
# now copy the contents of SLES CD6 into this directory
mkdir -p installroot/sp2/CD1
# now copy the contents of SLES SP2 CD1 into this directory
mkdir -p installroot/sp2/CD2
# now copy the contents of SLES SP2 CD2 into this directory
mkdir -p installroot/sp2/CD3
# now copy the contents of SLES SP2 CD3 into this directory
cd installroot
mkdir boot
ln -s ../sles9/CD1/boot/root boot/root
ln -s ../sp2/CD1/boot/rescue boot/rescue
ln -s sp2/CD1/driverupdate driverupdate
ln -s sp2/CD1/linux linux
ln -s sles9/CD1/content content
ln -s sles9/CD1/control.xml control.xml
ln -s sles9/CD1/media.1 media.1
mkdir yast
echo "/sp2/CD1 /sp2/CD1" > yast/instorder
echo "/sles9/CD1 /sles9/CD1" >> yast/instorder
echo "/core9/CD1 /core9/CD1" >> yast/instorder
echo "/sp2/CD1 /sp2/CD1" > yast/order
echo "/sles9/CD1 /sles9/CD1" >> yast/order
echo "/core9/CD1 /core9/CD1" >> yast/order
If you are now asked for the installation directory just specify
If you want to set up an MS windows system as an install server go to the directory dosutils/install. There is a script install.bat that will create the structure and asks you for the CDs. There are also the files instorder and order that have to be copied to the directory \suseinstall\yast. Before you copy the order file please replace the Variables UserAccount, PASSword and IP-Number with the respective values of your MS windows machine. During the installation process you only need to specify the share suseinstall.
If you use a SAMBA-Server as installation server, simply use the commands mentioned above to create the appropriate structure. Use the instorder and order files from dosutils/install and replace the Variables UserAccount, PASSword and IP-Number with the respective values. The following shares need to be exported:
installroot (the directory installroot)
sles9-CD1 (the directory installroot/sles9/CD1)
core9-CD1 (the directory installroot/core9/CD1)
core9-CD2 (the directory installroot/core9/CD2)
core9-CD3 (the directory installroot/core9/CD3)
core9-CD4 (the directory installroot/core9/CD4)
core9-CD5 (the directory installroot/core9/CD5)
sp2-CD1 (the directory installroot/sp2/CD1)
sp2-CD2 (the directory installroot/sp2/CD2)
sp2-CD3 (the directory installroot/sp2/CD3)
Problems with "xhost +" to display remote X sessions on your local
This is only relevant if you control an installation over a network and want to display your remote X or YaST session on your local display. On some Linux/Unix-Systems it is no longer sufficient to enter the command "xhost +" to grant access to the local X-Server. For security reasons the X-Server no longer listens on port 6000. To verify whether the X-Server still listens on port 6000 enter the command:
netstat -an | grep 6000
If the line
tcp 0 0* LISTEN
does not show up, the server is not listening. In this case you can either enable port 6000 or use the command
ssh -X "Address of the system be installed"
which will always work.
Qlogic 2310 FC adapters
If there is more than one Qlogic FC Adapter installed and they are NOT used for multipathing, the parameter ql2xfailover=0 must be specified if the module qla2xxx is loaded. Otherwise the LUNS on the second adapter will not show up.
Adding storage drivers after initial installation needs manual
During installation, all block-device drivers for storage controllers are added to an "initial ramdisk". This ensures accessibility for attached storage at all times.
Adding such a controller (with attached storage) at a later point in time will initially work as expected (as a side-effect of the new hot/coldplug capabilities), but later (e.g. after creating a LV on those disks) it may not function.
To ensure system integrity at all times, we recommend to follow YaST2 standards and add the appropriate module to INITRD_MODULES in /etc/sysconfig/kernel, and then rerun /sbin/mkinitrd.
Multipathing with MD-Devices
To upgrade MD multipathing from SLES 8 to SLES 9 please start the system with the kernel parameter "barrier=off". YaST will then offer the MD device for update.
Multipathing with LVM1
During the update the multipathing volumes will only be recognised as standard LVM volumes.
It is then recommended to use EVMS. EVMS will recognise LVM1 multipathing.
Multipathing with LVM2
Please visit
for a describtion how to setup and use multipathing.
Power5 virtual ethernet devices (ibmveth) need manual configuration
If the Power5 virtual ethernet devices (ibmveth) are not used during installation, the driver needs to be configured with YaST2 in order to be available after reboot.
If you do not want to use YaST2 use:
modprobe ibmveth
for loading it once, or an alias entry
alias eth0 ibmveth
in /etc/modprobe.conf to make it available on reboot.
Power5 HVSI terminal connection needs manual configuration
If your console is a HVSI terminal, follow these steps to use it during and
after installation:
  • At the first yaboot prompt, enter "install console=hvsi0".
  • During installation, configure a network adapter. After installing, use SSH to log in as root and edit /etc/inittab, changing the line beginning with "hvsi0" to: hvs0:1235:respawn:/sbin/agetty -L 9600 hvsi0 vt102
Booting over the network on a pcnet32 card results in slow connection
When the system is booted over the network, the firmware does not use autonegotiation and sets the pcnet32 card to 10Mbps/half-duplex. In this case start autonegotiation with "ethtool -s ethX autoneg on".
Some disk drives need boot option to prevent hangs
Some hard drives do not support barrier mode correctly and cause the system to hang in some situations, for example during mounting and formatting. In these cases the system must be booted with the boot option "barrier=off".
Updates and Features
Updated core system with latest versions/features of all packages,
  • kernel 2.6.5 - SUSE Linux Kernel version
  • glibc 2.3.3 - main C library
  • GCC 3.3.3 - GNU compiler collection
  • XFree 4.3.99 - Xfree X11 graphical user interface
  • KDE 3.2.1 - K Desktop Environment
  • GNOME 2.4.2 - GNOME Desktop Environment
  • Samba 3.0.4 - file & print & more services
  • Apache 2.0.49 - apache webserver version 2.x
  • Bind 9.2.3 - domain name server
New and improved YAST (our install and administration tool)
  • new YaST license (GPL)
  • improved/new installation methods (NFS, HTTP, FTP, VNC, ssh, SLP)
  • many config modules have been added or improved: DNS - domain name server configuration front end DHCP - dynamic host configuration protocol front end NIS - network information service config front end LDAP - LDAP server configuration front end CA - certificate authority setup front end VPN - virtual private network setup front end Mail - mail server configuration front end TFTP - tiny ftp server configuration front end Install-server - configure SLES as an installation server YOU-server - provide updates to other SLES servers Boot-server - boot-and-deploy-other-systems setup CD creation - CD image creation support UML install - UserMode Linux installation front end
  • LDAP enablement (for users/groups + DHCP, DNS and Mail config)
  • Systems management enablement through CIM (providers + CIMOM)
Next generation 2.6.5 Linux kernel with many improvements over 2.4
  • performance
    • improved HT and NUMA support
    • better support of big SMP systems
    • fine granular locking which boosts parallel execution
    • many kernel tuning parameters (like I/O scheduler)
  • scalability
    • support more than 64 CPUs
    • support thousands of devices/disks (64bit major/minor)
    • new greatly improved block I/O layer
    • improved network stack with IPv6, IPSEC and Mobile IPv6
  • hotplug support (SCSI, USB, Firewire, PCI, CPU)
  • persistent device names, unified device handling through sysfs
  • new record breaking memory management (objrmap, anon VMA)
  • class based kernel resource management (CKRM)
  • ACPI improvements (xapic on big machines, suspend to disk/RAM)
  • RAS enhancements (netconsole, crash dump, dprobes, event log)
  • Infiniband support
umount.cifs permissions
By default umount.cifs isn't installed setuid root. If you would like to allow users a umount of CIFS filesystems please adjust the permissions by adding:
/sbin/umount.cifs root:root 4755
to /etc/permissions.local and run SuSEconfig afterwards.
Improved HA support
  • heartbeat, drbd and multipath working with 2.6 kernel
  • cluster volume manager (EVMS)
  • cluster IP alias
Full enablement and support of UTF-8
Ready for the Asian market including translations and commercial fonts
Inclusion of Red Carpet Enterprise daemon
SLES 9 includes the Red Carpet Daemon. To install the Red Carpet Daemon please execute the following command: /usr/sbin/inst-rcd.
New Type of Installation Source: SLP
New feature: linuxrc understands a new installation source, slp. If you select install=slp at the bootloader prompt, linuxrc will send a SLP (Service Location Protocol) request for service install.suse to the network and prompt you to select an entry from the list of returned URLs. See RFC 2608 and for more information on SLP.
OpenSSH Updated to Version 3.8p1
The gssapi support has been replaced with the gssapi-with-mic to fix possible MITM (man-in-the-middle attacks) attacks. These two versions are not compatible. This means that you cannot authenticate from older distributions by kerberos tickets because different methods for authentication are used.
libiodbc has been Dropped
People using FreeRADIUS now have to link against unixODBC as libiodbc has been dropped.
Change in Resolver Library
Incompatible change: the resolver library treats the .local top level domain as link-local domain and sends multicast DNS requests to the multicast address port 5353 instead of normal DNS requests. If you already use the .local domain in your nameserver configuration you will have to switch to another domain name. See for more information on multicast DNS.
Update of IBM Java SDK 1.4.2 for SLES9
Testing on SuSE SLES 9 has revealed new defects. To correct these defects an updated version of SDK 1.4.2 for this platform has been made available from the SuSE maintenance website.
In addition a kernel upgrade is recommended which is also available from the SuSE maintenance website.
Future Service Refresh releases of IBM Java SDK 1.4.2 will also be made available from the SuSE maintenance website as they become available.
Wireless LAN Cards
Some wireless LAN cards (PrismGT, Centrino, Atmel, ACX100) need firmware to operate. Due to licensing issues we can not ship these firmware binaries. Please read /usr/share/doc/packages/wireless-tools/README.firmware for information on how to obtain and install the firmware.
SSH and Terminal Applications
When using remote access (notably SSH, telnet and RSH) between SUSE LINUX 9.1 / SLES 9(in its default configuration with UTF-8 enabled) and older systems (9.0 and lower, where UTF-8 is not enabled by default or not supported), terminal applications might display garbled characters.
This is because OpenSSH does not forward locale settings so that system-defaults are used which might not match the remote terminal settings. This affects text mode YaST and applications run remotely as non-root user. The applications run as root are only affected when the users changes the default locales for root (only LC_CTYPE is set by default).
POSIX compliant, high performance threads support (NPTL)
SUSE LINUX 9.1 / SLES 9 features a new pthread implementation called NPTL, which is faster and better than the old implementation called linuxthreads.
If your program is incompatible with this new threading implementation, we also provide the old one. To switch to the old version, set the environment variable LD_ASSUME_KERNEL to 2.4.21 by using (e.g.) export LD_ASSUME_KERNEL=2.4.21 in bash.
Applications using ncurses
If problems occur with ncurses based applications running on the text console then simply issuing unicode_stop (reverting keyboard and console from unicode mode) should usually provide a fix.
SuSEplugger now supports drive notifications and therefore does not poll the devices. Drives that fail to support notification might not react. A workaround is to enable polling to get back the old behavior.
Printer Configuration
For information about the changes with printing see
modules.conf / modprobe.conf
Parameters for loadable modules have now to be placed in modprobe.conf.
Wrong system time after installation prevents YOU updates
After installation, if an installation failure of "suse-build-key" appears, the system time was set to year 1970 during the installation. Yast2 Online Update will not work in this situation.
To correct this, change the system time to the current date and year, e.g. using the Yast2 Time and Date settings module. Then reinstall the suse-build-key RPM.
After the first boot the installation may continue on a different
When the installation is started on a directly connected console and a serial console is attached to the system, the installation may continue on the serial console after the reboot into the installed system.
The installation on a graphical console may not start in graphical mode
Because of a problem with graphical consoles that use the frame buffer device on IBM pSeries, YaST2 does not start in graphical mode but falls back to ncurses mode.
Runtime Modules of IBM eServer iSeries Access for Linux
(c) Copyright IBM Corporation 2001-2003 All Rights Reserved
vacation tool
The current version of vacation is neither 32/64 bit nor endian-safe.
If you use this tool in mixed environments please run vacation on the mail delivering server, which is normally the NFS server, or retry with the added option -f to force the creation of ~/.vacation.db
YaST partitioner will fail to assign the correct partition type during
The yast2 partitioner can fail to assign the correct partition type when you
repartition. On a partition that was deleted and then recreated, if you change
the type on the partition YaST will assign the original partition type. This
may lead to a non-booting system if the partition is part of a software RAID or
For example, the default partition scheme sets sda1 to type PReP on ppc. If
delete and then recreate sda1 and then change the type to DOS, YaST will still
set it as PReP.
To change the partition type, boot into the rescue system. Run fdisk /dev/sda
(or whatever the disk device node is in your setup) and change the type using
the 't' command.
Autoloading of PCI drivers
Autoloading of PCI drivers is done via coldplug in SLES9. But not all drivers will be loaded automatically, because some hardware needs additional configuration options. A whitelist of known-to-be-good hardware exists in /etc/sysconfig/hotplug COLDPLUGING_PCI_CLASSES_WHITELIST. It lists the allowed PCI classes, per default network, storage and a few more. To add also serial PCI drivers (like the Jasmine serial adapter), add a '07' to the list of allowed classes. After this change, the jsm driver will be loaded automatically during boot. /sbin/lspci -n lists the available PCI adapters and their class number on your system.
Providing Feedback to our products
On the top level of the first CD you will find a very detailed ChangeLog. Please also read the READMEs on the CD.
In case of encountering a bug you may file a report via
Your SUSE LINUX Enterprise Team
Mon Aug 15 10:35:17 UTC 2005


Please install the updates provided at the location noted below.

Installation notes

This update is provided as an RPM package that can easily be installed onto a running system by using this command:
rpm -Fvh release-notes.rpm

links to download packages

Download Source Packages

Download the source code of the patches for maintained products.


The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.

Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

© Micro Focus