Scientific Linux Forum.org



  Reply to this topicStart new topicStart Poll

> Confused about kernels versions and updates, Kernel versions and upgrading
Powerslave
 Posted: Nov 15 2013, 04:04 PM
Quote Post


SLF Newbie


Group: Members
Posts: 13
Member No.: 2350
Joined: 12-March 13









Hi

I'm confused over releases versus kernel versions . . .

I'm running SL 6.4 - the "latest" release, correct?

My kernel (due to uname) reports as:

2.6.32-358.23.2.el6.x86_64

Now, I'm having problems building and compiling some codes and drivers. The developer explains that I'm using an old kernel.

So, how is that (given "latest" 6.4, and the fact that I did update the kernel via yum)?

Also, how can I update my kernel to (at least) 2.637 - as per developer's requirements?

Clearly, I'm completely lost and confused - and no doubt missing what many would call some "core" facts and knowledge.

I certainly need to get my head around this, and would very much appreciate your help.

Thank you . . . smile.gif
PM
^
toracat
 Posted: Nov 15 2013, 05:08 PM
Quote Post


SLF Geek
****

Group: Members
Posts: 303
Member No.: 11
Joined: 10-April 11









Scientific Linux is a rebuild of upstream product (RHEL). Being an enterprise linux distribution means stability. The kernel version may not be the latest. However security and bug fixes get backported constantly, so the version number itself does not mean much.

In your case, though, you may need to run a newer kernel to make use of the code. This is [relatively easily] achieved by using kernel-ml from ELRepo [1]. In SL, you can set up this repository by running:
CODE

yum install elrepo-release


[1] http://elrepo.org/tiki/kernel-ml

--------------------
ELRepo: repository specializing in hardware support for EL
PMUsers Website
^
Powerslave
 Posted: Nov 20 2013, 05:15 PM
Quote Post


SLF Newbie


Group: Members
Posts: 13
Member No.: 2350
Joined: 12-March 13









^^^ Thanks very much for the guidance and information smile.gif

I've taken a slightly different route to get to the "later" kernel from elrepo to that which you described.

Here's what I did (this is becuase I couldn't get the above solution to work, initially):

rpm --import http://elrepo.org/RPM-GPG-KEY-elrepo.org

rpm -Uvh http://elrepo.org/elrepo-release-6-5.el6.elrepo.noarch.rpm


yum --enablerepo=elrepo-kernel --skip-broken install kernel-lt kernel-lt-devel kernel-lt-headers

---
(output abbreviated, available if required . . . )

Installed:
kernel-lt.x86_64 0:3.10.19-1.el6.elrepo
kernel-lt-devel.x86_64 0:3.10.19-1.el6.elrepo

Skipped (dependency problems):
kernel-lt-headers.x86_64 0:3.10.19-1.el6.elrepo
---

As you can see, I have failed in my attempt to installed the new kernel header files.

I have been able to boot into the new kernel, but I am unable to build my application - and I suspect that it is because of the "missing" updated header files.

If you have any advice for taking forward the header file upgrade, then that would also be appreciated.

Thank you in advance smile.gif
PM
^
Powerslave
 Posted: Nov 20 2013, 05:17 PM
Quote Post


SLF Newbie


Group: Members
Posts: 13
Member No.: 2350
Joined: 12-March 13









Also, if I now try and deal with the headers in isolation . . .

yum --enablerepo=elrepo-kernel --skip-broken install kernel-lt-headers
Loaded plugins: refresh-packagekit, security
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package kernel-lt-headers.x86_64 0:3.10.19-1.el6.elrepo will be installed
--> Processing Conflict: kernel-lt-headers-3.10.19-1.el6.elrepo.x86_64 conflicts kernel-headers < 3.10.19-1.el6.elrepo

Packages skipped because of dependency problems:
kernel-lt-headers-3.10.19-1.el6.elrepo.x86_64 from elrepo-kernel


(Thank you!)
PM
^
burakkucat
 Posted: Nov 20 2013, 10:41 PM
Quote Post


SLF Administrator
****

Group: Admins
Posts: 207
Member No.: 14
Joined: 10-April 11









I would like to point you to the kernel-lt page. The two paragraphs immediately above the "Notes" heading read:

QUOTE

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.

(The same applies with the kernel-ml package set. As documented here.)

May I please see the output returned by --

rpm -qa kernel\* | sort

and, for good measure, the error message seen when you attempt to compile the application?

--------------------
user posted image 100% Linux and, previously, Unix. Co-founder of the ELRepo Project.
PMUsers Website
^
0 User(s) are reading this topic (0 Guests and 0 Anonymous Users)
0 Members:

Topic Options Reply to this topicStart new topicStart Poll