According to this message, I understand, that I haven't install the kernel, so I have downloaded and uncompressed the mhvtl-2013-10-20.tgz file but with no success
1. tar xvzf mhvtl-2013-10-20
3. cd kernel
4. # make
make -C /lib/modules/2.6.39-400.211.3.el5uek/build SUBDIRS=/tmp/mhvtl-1.4/kernel modules
make: *** /lib/modules/2.6.39-400.211.3.el5uek/build: No such file or directory. Stop.
make: *** [default] Error 2
does someone have a tip to help me with this issue?
Actually i meant if you have upgraded your kernel then reboot :-)
Ok here is what i meant, on my m/c
# uname -r
The above is my kernel version
ls -l /lib/modules/`uname -r` | grep build
lrwxrwxrwx. 1 root root 51 Oct 14 13:03 build -> ../../../usr/src/kernels/2.6.32-358.18.1.el6.x86_64
lrwxrwxrwx. 1 root root 5 Oct 14 13:03 source -> build
Basically build directory required is a symbolic link to /usr/src/kernels/.6.32-358.18.1.el6.x86_64
Now lets see who provides usr/src/kernels/.6.32-358.18.1.el6.x86_64
#rpm -qf /usr/src/kernels/2.6.32-358.18.1.el6.x86_64
Lets see who creates the symbolic link
#rpm -qf /lib/modules/`uname -r`/build
So you see when the kernel rpm installs the modules under /lib/modules/ it creates a symbolic link to the build directory. However the symbolic link is invalid until the kernel devel package is installed, Cases where the kernel and the kernel-devel packages are present but you still have an invalid symbolic link is when you upgraded the kernel, but didn't upgrade the kernel devel package etc.
ls -l /lib/modules/`uname -r`/ on your m/c should give more information on your problem
First of all Tons of thanks for you explanation.
Second: you are right. The problem was that kernel-devel was not installed. You gave me the clue when I found that there were a symbolic link to a non existing folder.
Finally: Thank you for make me understand all the process.