Skip to contentSkip to conversation

kernel version problem after patching

DISCUSSION [email protected] 2 participants 2 messages Sep 18, 2014

lore
Share & tools
lore
#0 lore raw

There is a kernel version problem after patching the kernel. After installing the kernel and the kernel modules, without patching the kernel, then "uname" shows the right kernel version and in "/lib/modules/" there was the right directory created.

But after patching the kernel, installing it and the modules, then the kernelversion shown with "uname" and the modules directory in "/lib/modules/" is not correct anymore.

For example:
If i download the kernel 3.14.19, patch it, and install the kernel and the modules then "uname" shows kernel version 3.14.0 and the modules are installed in "/lib/modules/3.14.0/" instead of 3.14.19 which would be the correct version.

The same problem happens with other kernel versions too below 3.14.19 and also to kernel version 3.16.3 and versions below. But probably much more kernel versions are affected from this problem.

If someone has an older kernel installed correctly, 3.16 for example, and wants to install a patched second kernel, 3.16.3 for example, then the modules directory of the first one will be overwritten unwanted due to this version error because both kernels have the same modules directory "/lib/modules/3.16.0".

#1 lore raw
Quoted 19 lines · On Thursday 18 September 2014, [email protected] wrote:

There is a kernel version problem after patching the kernel. After installing the kernel and the kernel modules, without patching the kernel, then "uname" shows the right kernel version and in "/lib/modules/" there was the right directory created.

But after patching the kernel, installing it and the modules, then the kernelversion shown with "uname" and the modules directory in "/lib/modules/" is not correct anymore.

For example:
If i download the kernel 3.14.19, patch it, and install the kernel and the modules then "uname" shows kernel version 3.14.0 and the modules are installed in "/lib/modules/3.14.0/" instead of 3.14.19 which would be the correct version.

The same problem happens with other kernel versions too below 3.14.19 and also to kernel version 3.16.3 and versions below. But probably much more kernel versions are affected from this problem.

Quoted 5 lines

If someone has an older kernel installed correctly, 3.16 for example, and wants to install a patched second kernel, 3.16.3 for example, then the modules directory of the first one will be overwritten unwanted due to this version error because both kernels have the same modules directory "/lib/modules/3.16.0".

I got bit by that when I built the tarball of 3.1.6.0 the first time, it all went into 3.16. The .0 was missing in the tarballs Makefile. And, that is how it unpacked from the tarball too.

Cheers, Gene Heskett

Signature · 5 lines
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS