ISO images for SUSE LINUX Enterprise Server 9 Service Pack 2 for POWER
(Last modified: 08JUL2005)
solutions ISO images for SUSE LINUX Enterprise Server 9 Service Pack 2 for POWER SuSE Linux Maintenance Web (46a72fba9e55b150df2c21d6e902f583)
Product(s): SUSE CORE 9 for IBM POWER
Release Notes for SUSE LINUX Enterprise Server 9 Service Pack 2
1. Important general info
2.1 Installation / YaST2 2.2 Platforms / Hardware / Drivers 2.3 Standards 2.4 Availability 2.5 Serviceability 2.6 Scalability 2.7 Performance 2.8 Security 2.9 Applications and Tools 2.10 New packages introduced with SP2
3. Maintenance fixes
3.1 Bug fixes 3.2 Security fixes
4. Updating from SLES 9 GA or SP1 to SLES 9 SP2
4.1 Using the CD autorun mechanism 4.2 Calling YaST2 manually or remotely 4.3 Update selecting functional patches 4.4 Register the Service Pack as additional installation source 4.5 Update of individual packages 4.6 Multiple Kernels 4.7 Update everything using "System Update" 4.8 Update to SP2 using "Patch cd update"
5. Fresh installation using SP2
5.1 When is it needed? 5.2 Using the bootable SP CD 5.3 Setting up an installation server 5.3.1 Integrating the Service Pack into an installation server 5.4 Using special installation images
6. Known problems
7. More info and feedback
1. Important general info
These release notes are generic for all SLES 9 based products, so some parts may not apply to a particular architecture/product. In cases where this is not obvious the respective architectures are explicitly listed.
This SUSE Linux Enterprise Server Service Pack serves multiple purposes:
- Contains enhancements to the SLES 9 code base (see chapter 2).
- Contains all maintenance fixes (see chapter 3), which were released since GA of SLES 9.
- Provides an easy update (see chapter 4) of your system or individual packages to the latest Service Pack level. This is especially useful if you can not use online update mechanisms.
- Provides improvements for an easy fresh install (see chapter 5) using the latest kernel, drivers and updates to the installer.
- Include PTFs (special fixes for customers) which were folded back into the SLES 9 common code base making them maintained.
- Contains useful additional information and documentation (see chapter 7).
2.1 Installation / YaST2
- Added support in XFree86 and sax2 for Intel i915 GM and ATI server chip RN50
- Added detection support in hwinfo for new/updated hardware drivers (see 2.2)
- Added AutoYaST support for yast2-ca-management, enhanced support for yast2-bootloader
- Added support to force static IP address default via control file variable
- Added improvements to make yast2-network smarter in handling net devices
- Allow disable listening to IPP broadcasts in yast2-printer
- Added support in yast2-sound for Intel HDA chipsets
- Use resize2fs instead of parted for resizing ext2/3 filesystems
- Updated e2fsprogs to version 1.36 to allow creation of filesystems > 2 TB
- Updated reiserfs to version 3.6.19
- Several LVM and resize fixes in yast2-storage
- Several AutoYaST fixes and make module dependencies configurable in desktop files
- Updated YaST2 translations
- Fix V4 signature verification in RPM
- Fix mount by label and mount by uuid
- Allow root partition on LVM on RAID and update to version 188.8.131.52
- Added dialog to allow assigning PCI IDs to drivers This enables us to teach a driver about additional PCI IDs it is able to handle as well, because often an existing driver works well with new hardware released later but does not know it because the PCI IDs are unknown to the driver. This information will then be used during installation but also persist in the installed system.
- Added support in yast2-tune to select the detected PCI devices and get the IDs automatically.
- Fixed FTP installation source configuration in yast2-instserver.
- Improved PPC support in yast2-cd-creator, and also copy all available kernel images into the CD image now.
- In addition the following YaST modules have seen bugfixes:
yast2 yast2-backup yast2-bootloader yast2-ca-management yast2-cd-creator yast2-core yast2-dns-server yast2-http-server yast2-installation yast2-instserver yast2-ldap-client yast2-ldap-server yast2-mail-server yast2-ncurses yast2-network yast2-ntp-client yast2-packagemanager yast2-packager yast2-repair yast2-security yast2-sound yast2-users yast2-update
- Support many new hardware components via driver and PCI ID updates:
- updated tg3 to version 3.23
- updated bcm to version 8.1.11 to support Broadcom BCM5752
- updated e1000 to version 6.0.52
- updated e100 to version 3.4.7
- updated ixgb to version 1.0.95 to support 10 GB Ethernet
- updated ipr to version 184.108.40.206
- updated sk98lin to version 8.14
- updated qlogic qla2xxx to latest official version 8.00.02 plus several fixes
- updated qlogic qla4xxx to the latest official version 5.00.02
- updated cciss driver to version 2.6.6 and fixed wrong PCI ID
- Added 3w-9xxx driver for series 9000 SATA Raid cards
- Added PCI Express Card support to the pciehp driver
- added support Intel ICH7 chipset (PATA, SATA, I2C, PIRQ and AC97)
- added support Intel ICH4L chipset
- updated support for Intel i915 chipset (hwinfo, sax2, xf86)
- updated MPT fusion driver to version 3.02.18, adding an option to avoid automatic device deletion
- fixed aic7xxx driver probe info
- many improvements on SGI Altix hardware support, including improved error handling, VGA console support, improved support for IOC4
- chipset and RMP3 console port support for HP zx2 systems
- chipset recognition for HP sx2000 systems
- updated aic7xx to mainline kernel version 2.6.12-rc2
- updated aic79xx to mainline kernel version 2.6.12-rc2
- updated emulex-lpfc to version 220.127.116.11_p3
- updated ibmvscsi driver to level of 2.6.11 kernel.org
- updated ALSA sound system (kernel, lib, utils, ...) to 1.0.9rc2 to support latest sound chips and features
- added vt1211 support to i2c to handle sensors on VIA EPIA motherboards
- fixed keyboard to survive if any key (e.g. F2) is pressed early
- updated ndiswrapper to version 1.1 for latest wireless support
- updated wireless-tool to version 1.1.0 which adds support for ipw2100 and ipw2200
- Backported AMD dual core node detection support
- Added dual-core PowerNow! support for Opteron processors (single- and dual-core)
- Added multi-core/multi-thread identification for Montecito
- Support x86 cache identification through cpuid(4)
- Updated avm_fcdsl with new fixed drdsl version from AVM
- Updated tmscsim driver to 18.104.22.168
- Removed obsolete "cloned" (*-new) drivers from SP1 due to real driver
- 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, Itanium 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)
- Activate raw device for S/390
- Update hangcheck driver and enable it on all platforms
- Included support for Novell nss filesystem (km_nss)
- Various XFS (and DMAPI) and JFS fixes
- Assorted fixes for ext2, ext3, and Lustre
- Added autofs4 support with version 4.1.3 (kernel and userland)
You can enable autofs4 with the following steps:
- Deinstall autofs
- Install autofs4
- Uncomment following line in /etc/modprobe.conf:
alias autofs autofs4
- Remove loaded autofs module:
modprobe -r autofs
- Fixed an Oops in ACL code
- Updated CIFS to 1.33
- Updated libata to 2.6.11 level for various bugfixes and AHCI/SATA2 support Fixed error handling for ATAPI devices, plus various fixes on top of that
- Improved iSCSI and SAN/NAS support with patches from EMC, NetAPP and others
- Fix booting from iSCSI and allow static network interface config
- Backported several NFS and RPC bugfixes, stability and performance enhancements from upstream/mainline kernel and updated nfs-utils package
- NFS direct IO fixes
- Made NFSD DMAPI aware
- Fixed sunrpc xprt_bindresvport
- Enhanced /proc/mounts to include timeo and retrans
- Included several HP/Compaq devices in SCSI blacklist for correct handling
- Added various USB fixes
- Fixed mempool allocation deadlocks
- On x86-64, HPET timer is enabled as default, x86 requires the respective kernel parameter to be set ("hpet=enable")
- Fixed timers runing too fast on EM64T when HPET is not present
- Print only activated CPUs (s390 only)
- Integrated numerous other bugfixes from upstream/mainline kernel
- Updated microcode_ctl to version 1.11 and fix script activation on install. Adress problems on some hardware.
- Disabled MMConfig by default. Can be reenabled with pci=mmconf
- Disabled ASPM on all PCI Express cards
- Updated pciutils with more PCI IDs, to fix sysfs parsing and to support PCI-Express
- Added faster software suspend (swsuspend) The software suspend provided with SP1 worked, but we made a much faster implementation available with SP2.
- Updated CKRM
- Added I/O controller
- Enabled numtasks and cpu controllers
- Tweaked page coloring
- devs now creats all /dev/ttyS* device nodes.
- Fixed aio read-ahead performance regression
- Add some additional taints (on bad_page, mce, and forced rmmod)
- Favor SIGKILL to other signals
- Fix s2io link detection
- Several InfiniBand stack fixes
- Several SCSI layer fixes, and an update to handle broken SCSI 2 devices
- Updated syslinux to take bios memory size into account
- Updated linuxrc to use 0.0.0.0 as IP in bootp requests and handle '-' in module names correctly
- Allow skipping of IO-APIC ID check via kernel parameter
- Many further architecture- and platform- specific fixes
- Include AppArmor kernel support
- Add Xen patches to kernel-source We integrated Xen patches into the kernel-source package. This added an additional arch/xen subdir and does NOT have any influence on the regular SLES kernels and thus not invalidate any testing. IMPORTANT NOTE: XEN will not be supported with SP2 for production use, but we will make the needed Xen packages available as a "technology preview" on an FTP site, independently of SP2. This shall allow people to play with it and to get familiar with Xen. The exact location will be announced seperately.
- Make mmap POSIX conform
- Added convmv tool to convert encoding of files
- Updated libaio to version 0.3.102 and set soname back to libaio.so.1 to make it binary compatible with older versions.
- Added UTF8 compatibility to syslogd
- Added memory mirroring patches from Stratus
- Fixed several bugs in drbd
- Fixed several bugs in heartbeat (and build with OpenIPMI)
- Integrated multipath devices into hotplug and added fix for many devices
- Added support for multipathed devices in udev
- Added support for "multipath" option in initrd to support a delayed partition probing per host adapter needed in multipath setups
- Updated multipath-tools to 0.4.4 and added pp_alua path prio checker, fixed several bugs and enabled additional hardware
- Updated device-mapper to 1.01.01
- Backported device mapper snapshot fixes and multipath support from 2.6.11-rc3
- Included OCFS2 module from Oracle on i386, x86-64, and ia64
- Fixed several problems using EVMS, in particular related to multi-pathing and platform support
- Updated Linux kernel crash dump (lkcd) and lkcdutils
- Fix kdb interaction with lkcd dumps
- Reduce stack usage in lkcd
- Added support for polling I/O for diskdump on selected platforms
- Added support for more than 4GB for network dump
- Support dynamic bufsize
- Increase console loglevel before taking dumps
- Use fast gzip in lkcd dumps
- Added support for 'secure' mode of netdump
- Fix lcrash 'trace' failure with unwind
- Fix magic number handling
- Fix netdump-server looping
- Fix number of online CPUs (ia64 only)
- Fix 'whatis' command
- Enable poweroff on Altix
- Updated iprutils to version 22.214.171.124
- Updated net-snmp
- Better memory detection on non-i386 systems
- Enabled diskio subagent
- Dynamic CPU handling
- Updated sitar to version 0.9.3 and added enhancements for multi-pathing and ia64
- Updated strace to version 4.5.11
- Added POWER support to ltrace
- Improved SPident (for layered products, corner cases, output)
- Improved dual-core support for x86 and x86-64
- Enabled NUMA support on SLES9 for POWER
- Limit the number of concurrent hotplug processes
- Fixed shmget to not be limited to 2G
- Allowed shm to be executable
- Detect systems which always operate in physical APIC mode
- Significantly faster booting with thousands of disks attached
- Allow to optionally disable partition scan for devices
- Optionally disable blkid on boot by setting DISABLE_BLKID
- Made perfmon subsystem pluggable
- Added support for IA64 hardware performance counters via the perfmon interface
- Added cpu_relax to delay loop
- Increased MAX_IO_APICS
- Fixed performance problem with inode cache size
- Allow slab cache to be shrunk from userland
- Included all security fixes (see 3.1 below)
- NX support on x86: Unlike on x86_64, where NX has been shipping with SLES 9 GA, NX is not enabled by default on x86. Use the boot parameter "noexec=on" on the bigsmp kernel to enable this.
- Added protection against spoofed queue messages in iptables
- Backported SCTP iptable modules from 2.6.11
- SuSEfirewall2 no longer installs IPv6 rules if FW_IPv6=no
- Fixed aaa_base not to overwrite exported variables in bash and tcsh and use swapon -ae in boot.rootfsck
- Fixed input method "ami" to return correct feedback value
- Added bugfixes to apache
- fix start order for LUM (namcd)
- fix TLS upgrade patch: with SSLEngine set to Optional, an additional token in an Upgrade: header before "TLS/1.0" could result into an infinite loop
- mod_ssl: fix potential segfaults when performing SSL shutdown from a pool cleanup. Patch backported from 2.0.50.
- enable usage of sendfile on s390 31bit
- Fixed the tilde expansion bug in _cd_ and _exp_ complete shell function in the bash profile
- Fixed bastille on 64-bit architectures
- Fixed several bugs in binutils, glibc and GCC
- Fixed a security and one genuine bug for bzip2
- Updated clamav to version 0.86.1 which improves scanning capabilities and fixes several bugs
- Fixed cram-md5 auth problem in imap
- Added convmv tool which allows converting encodings of files
- Fixed cron wrt. jobs which are started too early
- Fixed several bugs in dhcp
- Fixed subfs compatibility in dosfstools
- Updated dvd+rw-tools and k3b to support DVD dual layer burning
- Fix efibootmgr parsing of bus info for network boot entry
- Fixed fetchmail to prevent lost mails with NULL envelope
- Updated GDB to version 6.3 plus additional bugfixes, require libunwind-devel and provide vDSO support on ia64.
- Updated ie32el to version 102.39.23 to fix problems under very heavy multithreading load and include an Errata fix
- Updated iprutils package to to version 2.0.15
- Updated kdebase3 to add mozilla plugin path in home directory to find manual installed plugins, fix support for Helix netscape plugins and fix file sharing visibility, as well as some other fixes
- Fixed kdelibs3 kimgio input validation errors
- Fixed input method "kinput2" to update its status description and properly handle spot location on Motif
- Updated kochi-substitute to address an incorrect glyph
- Updated libica
- Updated logrotate to chown and chmod files after rotate and compression
- Updated mkinitrd, adding DCSS support, fixing multipath support and mount by label/by uuid and not overwriting umount in the installed system
- Enhanced module-init-tools to support /lib/modules/$KERNELRELEASE/updates and handled quoted parameters
- Updated mozilla to version 1.7.8 to fix several bugs and security issues
- Added ncompress (old, traditional compress/uncompress utilities)
- Updated mysql to fix initializing database when mysql-Max is installed.
- Updated nagios-plugins to adjust check_swap to 2.6-based kernels
- Updated OpenLDAP to latest and compatible version 2.2.24 because of many bugfixes and stability enhancements
- Fixed OpenWBEM to create certificate on first startup instead of during the package postinstall, backport the explicit registration namespace feature.
- Fixed openslp to also listen on SLPv1 General Multicast address and to use poll instead of select, plus assorted fixes (including performance)
- Fixed OpenSSH keyboard/terminal problems and error output from PAM sessions
- Fixed several issues with the orarun package and added x84-64 support
- Fixed monitor mode in pdksh
- Updated permissions to include /opt/gnome/sbin/change-passwd
- Fixed several bugs in postfix
- Updated postgresql to version 7.4.7 to fix several bugs and security issues
- Updated procps to version 3.2.5 to fix many bugs
- Updated parted to version 1.6.21
- allow creation of partitions by exact sector number
- prevent shifted start sect when resizing with unknown fs
- improve proving for dvh/sgi disklabel and partitions
- Updated powersave for improved dual core support and work around machine-specific problems
- Added .netrc support to rexec
- Updated rpm to not catch ignored signals
- Fixed deadlock in rsh.
- Updated s390-tools to version 1.4.0, included lib-zfcp-hbaapi-1.2 (s390 only)
- Updated Samba to version 3.0.14
- more detailed info on changes/fixes comes with the samba-doc package in /usr/share/doc/packages/samba/WHATSNEW.txt
- Fixed some issues in sblim-cmpi-syslog
- Updated scim to version 1.0.3 to fix some serious bugs
- Updated src_vipa to version 2.0.3
- Updated star to support the "j" flag
- Lots of adjustments in sysconfig
- Updated syslogd with UTF8 compatibility
- Rolled back to wget version 1.9.1 although this means that wget is no longer capable of LFS (large file support) but there were simply too many problems with it
- Updated util-linux to make mount-guess-use-special honor the fake (-f) option and documented issues about NFS over UDP
- Fixed DNS resolving in webalizer
- Fixed xfsprogs to properly detect AG size
The following new packages have been introduced with Service Pack 2:
- autofs4 (network filesystem)
- certification-sles-ibm-eal4 (EAL4+ certification package)
- convmv (file conversion tool)
- ocfs2-tools (ocfs2 userland tools) on i386, x86-64, and ia64
- pam_mount (automatic mount of filesystems during login)
- sles-admin_ja (Japanese Manual)
- ncompress (old, traditional compress/uncompress utilities)
rpm -U <PACKAGE>
to install any of these packages.
3. Maintenance fixes
Service Pack 2 contains all the latest bugfixes for each package released via the maintenance Web since the GA version. See chapter 4.3 how to install these and chapter 7 where to find detailed documentation for each patch.
3.2 Security fixes
Service Pack 2 contains all the latest security fixes for each package released via the maintenance Web since the GA version. See chapter 4.3 how to install these and chapter 7 where to find detailed documentation for each patch.
4. Updating from SLES 9 GA or SP1 to SLES 9 SP2
Important Note: After completion of any form of update, look at the contents of the file /var/adm/rpmconfigcheck. This file contains a list of configuration files that could not be updated automatically. Usually this means the installed version was modified. These files must be checked and the configurations adjusted manually.
4.1 Using the CD autorun mechanism
The most convenient way to update your system to SP2 is to use the CD autorun feature. Log into KDE and insert SLES 9 SP2 CD1. After some seconds a window will pop up, ask you for the root password (in case you are logged in as a regular user) and offer you to install the patches from this CD. You can either install all recommended updates (this is the default) or select individual updates you are interested in. Basically you will find yourself in the update method described in 4.3, so continue to read there for more details. Don't forget to reboot at the end.
4.2 Calling YaST2 manually or remotely
The autorun of chapter 4.1 might not be an option if you have to update machines remotely or even without a CD-ROM drive. In this case you have to call YaST manually as the superuser root with the command "yast2". Then call the respective YaST module as mentioned in any chapter below. So a YaST2 reference like "Software -> Patch CD Update" means that you shall select "Software" on the left side and then the "Patch CD Update" icon on the right side.
In case you want to use YaST remotely you can login via ssh with
ssh -X root@<YOUR_MACHINE>
and then call "yast2". See also chapter 7 for references to our manuals and documentation, including sophisticated other methods to call and use yast, like via VNC or a serial line.
4.3 Update selecting functional patches
The maintenance updates to SLES 9 are grouped into logical functional units, called "patches", which are (or will be) available via the maintenance Web, but also available on this Service Pack. This method is much more convenient and less error-prone than updating packages individually and also supports special hooks for PRE and POST scripts of a complete patch. This method can be used calling YaST -> Software -> Patch CD Update. Even though it was designed for CDs initially, it can also be used via many other sources like NFS or a local directory.
There are 4 classes of patches. First there are patches to YaST itself. These are always selected and must be installed first. Second there are security patches, which should always be installed. Third there are recommended patches, which usually should be installed. Check the indications and contraindications for these. Last there are optional patches which are only needed in very special cases.
You can view details on a patch by clicking the button 'Description'. If additional information or warnings are available for any packages selected for installation, YaST2 will show those in popup message windows during the installation process. Please do not ignore these messages, as they contain important information for your system.
Usually the right patches for your system are automatically selected, so in most cases you can just accept the defaults.
In case your were told by one of the popup screens that a reboot is necessary then reboot now.
4.4 Register the Service Pack as additional installation source
In order for the YaST package manager to know about the updated packages residing on the Service Pack CD you have to register this CD as an additional installation source.
You can do this by YaST -> Software -> Change Source of Installation and then "Add" and "CD" and then use the "Up" button to move SP2 to the top (highest priority). This will make sure that if a newer version of a package is found on the Service Pack CD then this version will be used.
4.5 Update of individual packages
You first have to register SP2 as an additional install source (see 4.4). Then you can use the "Install and Remove Software" module of YaST to update, install or remove individual packages.
4.6 Multiple Kernels
It is possible to install multiple kernels side by side. This feature is meant to allow administrators to upgrade from one kernel to another by installing the new kernel, verifying that the new kernel works as expected, then uninstalling the old kernel. While YaST does not yet support this feature, kernels can easily be installed and uninstalled from the shell using rpm -i <package>.rpm. For information about managing packages from the command line, refer to the Administration Guide.
The default boot loader menus contain one kernel entry. Before installing multiple kernels, it is useful to add an entry for the extra kernels, so that they can easily be selected. The kernel that was active before installing a new kernel can be accessed as vmlinuz.previous and initrd.previous. By creating a boot loader entry similar to the default entry and having this entry refer to vmlinuz.previous and initrd.previous instead of vmlinuz and initrd, the previously active kernel can be accessed.
4.7 Update everything using "System Update"
You first have to register SP2 as an additional install source (see 4.4). Then you can update all packages with the "System Update" module of YaST.
4.8 Update to SP2 using "Patch CD Update"
When updating to SP2 by means of a "Patch CD Update" and a network installation source, it is necessary to copy all SP2 CDs into one directory and then use this directory as that source.
5. Fresh installation using SP2
In case you are doing a fresh install, you can benefit from SP2 as well. Architecture-specific information can be found at
Enhancements in the installer are listed in chapter 2.1 and additional platform/hardware support and driver updates in chapter 2.2.
5.1 When is it needed?
If you have already successfully installed SLES 9 GA or SP1 there is of course no need to do a fresh install. Just use any of the update mechanisms described in chapter 4 to get your system to SP2 level.
In cases though where the SLES 9 GA or SP1 version did not work for you, either because of missing hardware support or bugs in the installer you should try a fresh install with SP2 using any of the methods listed below.
5.2 Using the bootable SP CD
Insert the bootable Service Pack CD1 in your drive and boot your machine. The kernel will be loaded and the following dialog will appear:
"Make sure that CD number 1 is in your drive."
At this point insert the first product (!) CD, in our case CD1 of the SLES 9 GA ISO set. Hit "Ok" and the regular installation (with the new kernel, drivers and the new YaST) will run. Continue as usual with the installation.
The benefit of this method is that you will directly install the newest version of every package in this mode, so no need to call any of the update methods listed above afterwards.
If you have to install many machines we recommend to boot of the SP2 CD1 but use a network install server. Chapter 5.3 explains how to set up an installation server.
5.3 Setting up an installation server
Here is a step-by-step guide to set up a SLES 9 install server. As example we are setting up an NFS install server, but the other methods like HTTP or FTP install server are very similar.
- Call YaST -> Misc -> Installation Server
- Select "Configure as NFS Source" and as Directory whatever you like, in our example we use "/install"
- Hit then "Next" button
- Leave the defaults for "Host Wild Card" and "Options"
- Hit then "Next" button
- With this an NFS Server serving "/install" will be set up automatically
- The "Source Configuration" dialog will show up
- In the "Sources to Configure" subwindow hit the "Configure" button
- As "Source Name" enter what you like to name this install source. In our example we name it "sles9". This will create a subdirectory "sles9" under /install
- Enable the checkbox "Announce as Installation Service with SLP" This will make this server broadcast himself as an installation server and any SUSE product will automatically find it in SLP install mode.
- If you have CDs of SLES 9 and SP2 then skip the next step
- In case you have ISO images instead of CDs then enable this checkbox and browse via "Select Directory" to the directory that contains all ISO images of all CDs.
- Hit "Next" button
- You will now be prompted to insert "CD1"
- Insert "SLES 9 CD1" (which is the main product CD) and hit the "Continue" button. Now the data from CD1 will be copied to the local directory, in this example under /install/sles9
- Proceed the same way when prompted for CD2 ... CD6
- Press the "Finish" button
- Now your installation server for SLES is ready.
- The directory structure will look like this
/install/sles9/ SUSE-CORE-Version-9/ CD1/ CD2/ CD3/ CD4/ CD5/ SUSE-SLES-Version-9/ CD1/ boot -> SUSE-SLES-Version-9/CD1/boot content -> SUSE-SLES-Version-9/CD1/content control.xml -> SUSE-SLES-Version-9/CD1/control.xml media.1 -> SUSE-SLES-Version-9/CD1/media.1 yast/ instorder orderYou may have noticed that the 6 CDs actually are 1 SLES CD, which is really defining the product settings, and 5 so-called CORE CDs, which contain the common code base for SUSE business products (the common code base avoids that ISVs or IHVs have to do multiple certifications).
- Now you can easily install another machine via the network
using the install server
- Boot the machine you want to install from SLES 9 CD1
- On the initial dialog scroll one line down and chose "Installation"
- In the "Boot Options" field enter "install=slp" (or change this with "F3" if this is available on your platform)
- The machine will boot and then show you a selection of install options it has found via SLP
to force the installation to use a certain install server.
The YaST2 install server module needs some bugfixes to be able to read and integrate Service Pack CDs. Thus please make sure you have at least version 2.9.20-0.2 of yast2-instserver installed (you will find such a newer package on the Service Pack CD itself).
Then to the following steps:
- Call YaST -> Misc -> Installation Server -> Change -> Edit
- Enable the checkbox "Prompt for additional CDs (Service Packs, Additional Package CDs, etc.)"
- Hit "Next" button
- It will say that contents already exists in this directory
- Hit "Ok" button
- It will prompt for CD1
- Now insert the "Service Pack CD1" and hit "Continue"
- The contents of Service Pack CD1 will be copied to the local disk
- Proceed the same way when prompted for CD2
In case you can not boot from CD you will find corresponding floppy images for boot and modules floppies under /boot on CD1.
6. Known problems
- SGI Altix and Silicon Graphics Prism systems (ia64) SGI recommends PROM 4.30 or subsequent versions for all SGI Altix and Silicon Graphics Prism systems running SLES9 SP2. The updated PROM contains key bug fixes, along with support for new kernel features, such as memory error recovery. The latest PROM firmware can be obtained from SGI Supportfolio(TM): http://support.sgi.com Caveat: PROM 4.30 and subsequent versions are not compatible with SLES9 SP1 or earlier kernels. If you want to switch between SLES9 SP1 and SLES9 SP2 kernels, DO NOT upgrade the PROM on your system.
- For S/390 and zSeries For Installation more than 256 MB is needed.
- For x86_64 For update to SP2 more than 256 MB are needed.
- For Intel x86 and x86-64 CPUs Prior to SP2, the microcode update init script was disabled by default; normally the script should be enabled to allow for fixes to be applied to the microcode of Intel x86 and x86-64 CPUs. The default has been changed in SP2, so the microcode updating will be enabled on new installations. However, on old installations where SP2 is apllied as an update, the script will not be enabled if it was disabled before. We recommend to enable it by issuing the command "insserv microcode" on the command line of a root shell or by enabling it in the YaST runlevel editor.
- For IBM LS20 If only one CPU is populated with DIMMs, you may experience an early crash of the system. We recommend populating both CPUs with RAM. Alternatively you can turn NUMA off by specifying 'numa=off' on the kernel commandline to work around this problem.
- Using SCSI or hotplug devices may lead to boot failure or mount problems
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.
- 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).
These release notes are still a mixture of "what is new" and "hints on installation and update". The "what is new" part will stay in the "Notes" file, but the hints on installation and update will end up in the toplevel README on CD1 and this README will be translated into the supported SLES 9 languages.
- Detection of systems which always operate in physical APIC mode doesn't work yet
Please also read the READMEs on the CDs.
You will find high-level information on all patches contained in this Service Pack under the directory docu. Just point your browser to
You can of course always get the very detailed changelog information about a particular package from the RPMs themselves by doing
rpm --changelog -qp <FILENAME>.rpm
where <FILENAME>.rpm is the name of the rpm.
The file "ChangeLog" in the toplevel of CD1 contains a chronological log of all the changes that were made for these updated packages.
You will also find a lot more useful information in the directory "docu" of CD1 of the original SLES 9 GA (!) CDs. This includes PDF versions of the SLES 9 installation and administration manuals, which explain many other sophisticated methods to install and use SLES 9, for example using AutoYaST or VNC.
http://portal.suse.com/sdb/en/2005/04/sles_multipathing.html describes how to setup and use multipathing.
Please visit http://www.novell.com/linux/ for the latest Linux product news from SUSE/Novell.
The MD5 sums for the ISO images are:
SLES-9-SP-2-ppc-GM-CD1.iso 6a0e7e1a1b8f34a2031dd471e3f5d209 SLES-9-SP-2-ppc-GM-CD2.iso 618d2bac3af08643ae0c7e6e78d72851 SLES-9-SP-2-ppc-GM-CD3.iso 9e969fa5195b948a5afe3ab37a1a8e86
The images can be written to a blank CD-R. To do that on a Linux system, we recommend to use the program cdrecord. A sample command line to cdrecord looks like this:
cdrecord dev=0,4,0 -v -eject -speed=8 SLES-9-SP-2-ppc-GM-CD1.iso
Please adjust the values for dev and speed according to your system.
Note: We are not going to send out an individual 'Maintenance Support Information' mail for every single patch to reduce the mail load. You could also update to SLES9 SP2 using YOU.
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.