Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My kernel is 3.2.27 and /lib/modules/ contains 3.2.27 + folder. But when I am using

/# uname -r

It's showing a strange output. My problem is that for modprobe depends on uname when I put

/# modprobe somemodule
modprobe: chdir(3.1.9+): No such file or directory 

It finding the modules in a wrong path. I have cross compiled the kernel with gcc version 4.5.2. Can anyone tell me why this strange problem happens?

Thank you

share|improve this question
uname uses the uname() system call, so fetch this info directly from the running kernel. Alternatively, cat /proc/version, which should yield the same info. – BatchyX Jan 1 '13 at 10:43
cat /proc/version also showing 3.1.9+ – Shantanu Banerjee Jan 1 '13 at 14:18
I have cross compiled the kernel with gcc version 4.5.2 – Shantanu Banerjee Jan 1 '13 at 14:31
Then somewhere within your compilation you are setting the kernel version to 3.1.9+ – fpmurphy1 Jan 1 '13 at 15:44
You're clearly running kernel 3.1.9. Are you sure you booted the kernel you intended? – Gilles Jan 1 '13 at 15:54

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.