Installation-Related Notes

Feature Updates

Driver Updates

Kernel-Related Updates

Other Updates

Technology Previews

Resolved Issues

Known Issues

If you are copying the contents of the Red Hat Enterprise Linux 5 CD-ROMs (in preparation for a network-based installation, for example) be sure to copy the CD-ROMs for the operating system only. Do not copy the Supplementary CD-ROM, or any of the layered product CD-ROMs, as this will overwrite files necessary for Anaconda's proper operation.

The contents of the Supplementary CD-ROM and other layered product CD-ROMs must be installed after Red Hat Enterprise Linux 5.1 has been installed.

When installing Red Hat Enterprise Linux 5.1 on a fully virtualized guest, do not use the kernel-xen kernel. Using this kernel on fully virtualized guests can cause your system to hang.

If you are using an Installation Number when installing Red Hat Enterprise Linux 5.1 on a fully virtualized guest, be sure to deselect the Virtualization package group during the installation. The Virtualization package group option installs the kernel-xen kernel.

Note that paravirtualized guests are not affected by this issue. Paravirtualized guests always use the kernel-xen kernel.

If you are using the Virtualized kernel when upgrading from Red Hat Enterprise Linux 5 to 5.1, you must reboot after completing the upgrade.

The hypervisors of Red Hat Enterprise Linux 5 and 5.1 are not ABI-compatible. If you do not reboot between upgrades, the upgraded Virtualization RPMs will not match the running kernel.

The CIFS client has been updated to version 1.48aRH. This is based upon the 1.48a release, with patches that apply the following changes:

Note that for users of the EMC Celerra product (NAS Code 5.5.26.x and below), the CIFS client hangs when accessing shares on EMC NAS. This issue is characterized by the following kernel messages:

kernel:  CIFS VFS: server not responding
kernel:  CIFS VFS: No response for cmd 162 mid 380
kernel:  CIFS VFS: RFC1001 size 135 bigger than SMB for Mid=384

After a CIFS mount, it becomes impossible to read/write any file on it and any application that attempts an I/O on the mountpoint will hang. To resolve this issue, upgrade to NAS Code 5.5.27.5 or later (use EMC Primus case number emc165978).

MODULE_FIRMWARE tags are now supported.

ICH9 controllers are now supported.

Greyhound processors are now supported in CPUID calls.

Oprofile now supports new Greyhound performance counter events.

Directed DIAG is now supported to improve z/VM utilization.

The Intel graphics chipset is now supported through the DRM kernel module. Further, the DRM API has been upgraded to version 1.3 to support direct rendering.

Updates to ACPI power management have improved S3 suspend-to-RAM and S4 hibernate.

gaim is now called pidgin.

Intel microcode updated to version 1.17. This adds support for new Intel processors.

Implicit active-active failover using dm-multipath on EMC Clariion storage is now supported.

The Chinese font Zysong is no longer installed as part of the fonts-chinese package. Zysong is now packaged separately as fonts-chinese-zysong. The fonts-chinese-zysong package is located in the Supplementary CD.

Note that the fonts-chinese-zysong package is needed to support the Chinese National Standard GB18030.

The Challenge Handshake Authentication Protocol (CHAP) username and password have a character limit of 256 each.

pump is deprecated in this update. As such, configuring your network interface through netconfig may result in broken ifcfg scripts.

To properly configure your network interface, use system-config-network instead. Installing the updated system-config-network package removes netconfig.

rpm --aid is no longer supported. It is recommended that you use yum when updating and installing packages.

A SATA bug that caused SATA-equipped systems to pause during the boot process and display an error before resuming is now fixed.

In multi-boot systems, parted now preserves the starting sector of the first primary partition where Windows Vista™ is installed. As such, when setting up a multi-boot system with both Red Hat Enterprise Linux 5.1 and Windows Vista™, the latter is no longer rendered unbootable.

rmmod xennet no longer causes domU to crash.

4-socket AMD Sun Blade X8400 Server Module systems that do not have memory configured in node 0 no longer panic during boot.

conga and luci can now be used to create and configure failover domains.

When installing the Cluster Storage group through yum, the transaction no longer fails.

During installation, incorrect SELinux contexts are no longer assigned to /var/log/faillog and /var/log/tallylog.

Installing Red Hat Enterprise Linux 5.1 using split installation media (for example, CD or NFSISO) no longer causes an error in the installation of amanda-server.

EDAC now reports the correct amount of memory on the latest k8 processors.

Logging in remotely to a Gnome desktop via gdm no longer causes the login screen to hang.

A bug in autofs that prevented multi-mounts from working properly is now fixed.

Running tvtime and xawtv with the bttv kernel module no longer causes the system to freeze.

Several patches to utrace apply the following fixes:

A RealTime Clock (RTC) bug that prevented alarms and periodic RTC interrupts from working properly is now fixed.

The first time the Release Notes button is clicked in Anaconda, a delay occurs while the window renders the Release Notes. During this delay, a seemingly empty list appears in the window. The rendering normally completes quickly, so most users may not notice this.

This delay is mostly due to the fact that the package installation phase is the most CPU-intensive phase of installation.

Some machines that use NVIDIA graphics cards may display corrupted graphics or fonts when using the graphical installer or during a graphical login. To work around this, switch to a virtual console and back to the original X host.

Host bus adapters that use the MegaRAID driver must be set to operate in "Mass Storage" emulation mode, not in "I2O" emulation mode. To do this, perform the following steps:

If the adapter is incorrectly set to "I2O" emulation, the system will attempt to load the i2o driver. This will fail, and prevent the proper driver from being loaded.

Previous Red Hat Enterprise Linux releases generally do not attempt to load the I2O driver before the MegaRAID driver. Regardless of this, the hardware should always be set to "Mass Storage" emulation mode when used with Linux.

Laptops equipped with the Cisco Aironet MPI-350 wireless may hang trying to get a DHCP address during any network-based installation using the wired ethernet port.

To work around this, use local media for your installation. Alternatively, you can disable the wireless card in the laptop BIOS prior to installation (you can re-enable the wireless card after completing the installation).

Currently, system-config-kickstart does not support package selection and deselection. When using system-config-kickstart, the Package Selection option indicates that it is disabled. This is because system-config-kickstart uses yum to gather group information, but is unable to configure yum to connect to Red Hat Network.

At present, you need to update package sections in your kickstart files manually. When using system-config-kickstart to open a kickstart file, it will preserve all package information in it and write it back out when you save.

Boot-time logging to /var/log/boot.log is not available in this update of Red Hat Enterprise Linux 5. An equivalent functionality will be added in a future update.

When upgrading from Red Hat Enterprise Linux 4 to Red Hat Enterprise Linux 5, the Deployment Guide is not automatically installed. You need to use pirut to manually install it after completing the upgrade.

The system may not successfully reboot into a kexec/kdump kernel if X is running and using a driver other than vesa. This problem only exists with ATI Rage XL graphics chipsets.

If X is running on a system equipped with ATI Rage XL, ensure that it is using the vesa driver in order to successfully reboot into a kexec/kdump kernel.

Installing the Virtualization feature may cause a time went backwards warning on HP systems with model numbers xw9300 and xw9400.

To work around this issue for xw9400 machines, configure the BIOS settings to enable the HPET timer. Note that this option is not available on xw9300 machines.

This will be resolved in an upcoming BIOS update by HP.

When using Red Hat Enterprise Linux 5 on a machine with an nVidia CK804 chipset installed, the following kernel messages may appear:

kernel: assign_interrupt_mode Found MSI capability
kernel: pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS

These messages indicate that certain PCI-E ports are not requesting IRQs. Further, these messages do not, in any way, affect the operation of the machine.

Removable storage devices (such as CDs and DVDs) do not automatically mount when you are logged in as root. As such, you will need to manually mount the device through the graphical file manager.

Alternatively, you can run the following command to mount a device to /media:

mount /dev/<device name> /media

The Calgary IOMMU chip is not supported by default in this update. To enable support for this chip, use the kernel command line option iommu=calgary.

The IBM System z does not provide a traditional Unix-style physical console. As such, Red Hat Enterprise Linux 5 for the IBM System z does not support the firstboot functionality during initial program load.

To properly initialize setup for Red Hat Enterprise Linux 5 on the IBM System z, run the following commands after installation:

When upgrading from Red Hat Enterprise Linux 5 to Red Hat Enterprise Linux 5.1 via Red Hat Network, yum may not prompt you to import the redhat-beta key. As such, it is advised that you import the redhat-beta key manually prior to upgrading. To do this, run the following command:

rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-beta

When a LUN is deleted on a configured filer, the change is not reflected on the host. In such cases, lvm commands will hang indefinitely when dm-multipath is used, as the LUN has now become stale.

To work around this, delete all device and mpath link entries in /etc/lvm/.cache specific to the stale LUN.

To find out what these entries are, run the following command:

ls -l /dev/mpath | grep <stale LUN>

For example, if <stale LUN> is 3600d0230003414f30000203a7bc41a00, the following results may appear:

lrwxrwxrwx 1 root root 7 Aug  2 10:33 /3600d0230003414f30000203a7bc41a00 -> ../dm-4
lrwxrwxrwx 1 root root 7 Aug  2 10:33 /3600d0230003414f30000203a7bc41a00p1 -> ../dm-5

This means that 3600d0230003414f30000203a7bc41a00 is mapped to two mpath links: dm-4 and dm-5.

As such, the following lines should be deleted from /etc/lvm/.cache:

/dev/dm-4 
/dev/dm-5 
/dev/mapper/3600d0230003414f30000203a7bc41a00
/dev/mapper/3600d0230003414f30000203a7bc41a00p1
/dev/mpath/3600d0230003414f30000203a7bc41a00
/dev/mpath/3600d0230003414f30000203a7bc41a00p1

When attempting to create a fully virtualized Windows™ guest from a CD or DVD, the second stage of the guest install might not continue upon reboot.

To work around this, edit /etc/xen/<name of guest machine> by properly appending an entry for the CD / DVD device.

If an installation to a simple file is used as a virtual device, the disk line of /etc/xen/<name of guest machine> will read like the following:

disk = [ 'file:/PATH-OF-SIMPLE-FILE,hda,w']

A DVD-ROM device located on the host as /dev/dvd can be made available to stage 2 of the installation as hdc by appending an entry like 'phy:/dev/dvd,hdc:cdrom,r'. As such, the disk line should now read as follows:

disk = [ 'file:/opt/win2003-sp1-20061107,hda,w', 'phy:/dev/dvd,hdc:cdrom,r']

The precise device path to use may vary depending on your hardware.

If the sctp module is not added to the kernel, running netstat with the -A inet or -A inet6 option abnormally terminates with the following message:

netstat: no support for `AF INET (sctp)' on this system.	

To avoid this, install the sctp kernel module.

Installing Red Hat Enterprise Linux 3.9 on a fully virtualized guest may be extremely slow. In addition, booting up the guest after installation may result in hda: lost interrupt errors.

To avoid this bootup error, configure the guest to use the SMP kernel.

Current kernels do not assert Data Terminal Ready (DTR) signals before printing to serial ports during boot time. DTR assertion is required by some devices; as a result, kernel boot messages are not printed to serial consoles on such devices.

Upgrading a host (dom0) system to Red Hat Enterprise Linux 5.1 may render existing Red Hat Enterprise Linux 4.5 SMP paravirtualized guests unbootable. This is more likely to occur when the host system has more than 4GB of RAM.

To work around this, boot each Red Hat Enterprise Linux 4.5 guest in single CPU mode and upgrade its kernel to the latest version (for Red Hat Enterprise Linux 4.5.z).

The AMD 8132 and HP BroadCom HT100 used on some platforms (such as the HP dc7700) do not support MMCONFIG cycles. If your system uses either chipset, your PCI configuration should use the legacy PortIO CF8/CFC mechanism. To configure this, boot the system with the kernel parameter -pci nommconfig during installation and add pci=nommconf to GRUB after rebooting.

Further, the AMD 8132 chipset does not support Message Signaled Interrupts (MSI). If your system uses this chipset, you should also disable MSI. To do this, use the kernel parameter -pci nomsi during installation and add pci=nomsi to GRUB after rebooting.

However, if your specific platform is already blacklisted by the kernel, your system does not require the aforementioned pci kernel parameters. The following HP platforms are already blacklisted by the kernel:

The Virtual Machine Manager (virt-manager) included in this release does not allow users to specify additional boot arguments to the paravirtualized guest installer. This is true even when such arguments are required to install certain types of paravirtualized guests on specific types of hardware.

This issue will be addressed in a future release of virt-manager. To specify arbitrary kernel arguments in installing paravirtualized guests from the command line, use virt-install.

With the default dm-multipath configuration, Netapp devices may take several minutes to complete failback after a previously failed path is restored. To resolve this problem, add the following Netapp device configuration to the devices section of the multipath.conf file:

devices {
        device {
                vendor                  "NETAPP"
                product                 "LUN"
                getuid_callout          "/sbin/scsi_id -g -u -s /block/%n"
                prio_callout            "/sbin/mpath_prio_netapp /dev/%n"
                features                "1 queue_if_no_path"
                hardware_handler        "0"
                path_grouping_policy    group_by_prio
                failback                immediate
                rr_weight               uniform
                rr_min_io               128
                path_checker            directio
        }