Kernel-lt for Enterprise Linux 5 and 6.

The kernel-lt packages are built from the sources available from The Linux Kernel Archives (external link), just like the kernel-ml packages. The difference is that kernel-lt is based on a "long term support" branch and kernel-ml is based on the "mainline stable" branch.

The kernel configuration is based upon the default RHEL configuration with added functionality enabled as appropriate. The packages are intentionally named kernel-lt so as not to conflict with the RHEL kernels and, as such, they may be installed and updated alongside the regular kernel.

To install kernel-lt you will need elrepo-release-5-3.el5.elrepo (or newer for EL5) or elrepo-release-6-4.el6.elrepo (or newer for EL6). Run:

yum --enablerepo=elrepo-kernel install kernel-lt

You can also Download manually from (external link) (EL5) or (external link) (EL6).
(Or from one of our mirror sites, if one is more conveniently located closer to you.)

There is no need to install the kernel-lt-firmware package. There are more firmware files contained within the distro package than in the kernel-lt-firmware package.

There is no need to install the kernel-lt-headers package. It is only necessary if you intend to rebuild glibc and, thus, the entire operating system. If there is a need to have the kernel headers installed, you should use the current distributed kernel-headers package as that is related to the current version of glibc.


These packages are provided 'As-Is' with no implied warranty or support. Using the kernel-lt may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-lt packages in regular service. These packages are not signed for SecureBoot.

If a bug is found when using these kernels, the end user is encouraged to report it upstream to the Linux Kernel Bug Tracker (external link) and, for our reference, to the ELRepo bug tracker. By taking such action, the reporter will be assisting the kernel developers, Red Hat and the Open Source Community as a whole.

Known Issues

With EL6 there are none currently known.

With EL5 there are a number, as shown below. If you have a solution or workaround for one of these issues, please let us know.

HAL does not provide battery information (affects eg. Gnome)

This is a regression in the Linux kernel (since 2.6.36) and is tracked in our bug-tracker at: (external link)

Hardware clock (/dev/rtc) not working

This is a regression in the Linux kernel and is tracked in our bug-tracker at: (external link)

Depending upon the hardware being used, the RTC may not be accessible. This can be checked by executing /sbin/hwclock --debug. If the hwclock binary reports that the RTC is not accessible by any means, the patch below fixes the problem after a reboot. A simple temporary work-around is to: ln -sf /dev/rtc0 /dev/rtc

Patch for /etc/rc.sysinit that fixes the known RTC issue
--- rc.sysinit.distro 2012-02-11 11:03:13.000000000 +0000
+++ rc.sysinit 2012-02-11 11:11:05.000000000 +0000
@@ -269,6 +269,19 @@ if [ "$PROMPT" != "no" ]; then

+### ELREPO: See if the RTC driver is built-in, otherwise load it
+if [ ! -f /proc/driver/rtc ]; then
+ action $"Loading rtc_cmos driver: " /sbin/modprobe rtc_cmos
+### ELREPO: Make the newer device nodes to accomodate hwclock
+RTC_MAJOR_NO=`/bin/awk '/rtc/ { print $1 }' /proc/devices`
+if [ -n "$RTC_MAJOR_NO" ]; then
+ action $"Creating /dev/rtc0: " /bin/mknod /dev/rtc0 c $RTC_MAJOR_NO 0
+ action $"Creating /dev/rtc: " /bin/ln -sf /dev/rtc0 /dev/rtc
+ [ -n "$SELINUX_STATE" ] && restorecon /dev/rtc0 /dev/rtc >/dev/null 2>&1
 # Set the system clock.
 update_boot_stage RCclock

mcelog reports incorrect record size

Only 64-bit systems are affected. The userland tool needs to be revised to distinguish between the mcelog record size of a distro kernel and a more modern kernel. As a work-around to avoid hourly e-mail messsages from the cron daemon, you can append 2>&1 to the last line of the /etc/cron.hourly/mcelog.cron file.

See also: RHbz #507026 mcelog: warning: record length longer than expected. (external link)

Missing dm-region-hash module

A warning message will be displayed on the system console at boot time about a missing dm-region-hash module.

One workaround to silence the message is to add the nodmraid kernel parameter as part of your kernel options in /etc/grub.conf. Another option is to remove the dmraid modules from the initrd if you do not use dmraid, however the mkinitrd options --without-dmraid and --omit-raid-modules do not work. You will have to comment out three findmodule lines in /sbin/mkinitrd that reference dm-mirror, dm-zero and dm-snapshot and then recreate your initrd. (Search for "132001" in the script)

See also: RHbz #132001 add dm-mirror and dm-snapshot if dm-mod is brought in (external link)

Some iptables modules fail causing iptables firewall to become effectively disabled.

Some iptables modules do not function correctly. This has a knock-on effect that iptables-restore fails to load any rules if any rule should fail, thus rendering the firewall effectively disabled. Please check your iptables rules carefully to ensure there are no errors and the rules are correctly loaded.

See Bug: (external link)

Page last modified on Thursday 20 of August, 2015 12:04:48 MDT