uname -a gives wrong info
 

Have just upgraded my kernel to 2.6.10 and my box fired up faultelssly first time, but, as a check, I issued the command uname -a, and it tells me that I am still using 2.6.7. Now as I have physically moved my 2.6.7 kernel from where it normally resides, I can´t quite figure out why this is. I use grub as a bootloader, so no answers please telling me to re-run lilo.
So where does uname get it´s info from? is it from withing the kernel itself, or from within the /etc/motd file (which would explain it.

TIA

Update Lilo....LOL j/k man

Yeah I think uname gets it's info from motd

Made me laugh anyway. As it happens, I have edited the motd, but still get 2.6.7 from uname
Anything more

It's a shot in the dark but go back to the kernel source tree and take a peek at the Makefile, it shows the version numbers in there, see if there set to 2.6.10.. lol that would be funny if they were not.

Question, in your /lib directory is there a 2.6.7 folder under modules? it could just be looking to see if that folder exists and if it does that's probly what it reports.

Other then that, I am stumped, sorry guy :(

If uname says 2.6.7, then you're running 2.6.7. Also check `uname -v` to see the compile time for the kernel you're running. I believe uname gets the kernel information from the kernel.

I do not use grub, but don't you have to update it somehow when you upgrade the kernel just like you do with lilo? Have you done that? Did you copy the new kernel to /boot? I know, it's the stupid things, but they're easy to forget.

Anyone using grub want to fill us in on how to update it to use the new kernel.

Not necessarily.

http://www.linuxquestions.org/questi...ighlight=uname

I don't see anything in that thread about uname being based on the motd file, just about the motd file being wrong in some cases. It appears that uname returns the correct kernel version number (i.e. the one you're running).

Back to my theory that the thread starter is not actually running 2.6.10.

I am having the same problem. Just that, I am running 2.6.10 but uname is telling me I am running 2.6.9.

Will dig up a few files to check.

EDIT:
Sorry, false alarm. my /usr/src/linux is actually linked to 2.6.9 instead of 2.6.10. So, I got 2.6.9 running. :)

OK,
Beats self around head with large wooden club.

It turns out that during my compilation etc, during the cp bzImage stage that I copied my existing image, not my new one.

Have since corrected this, re-installed the Nvidia drivers, and hey presto, back to working again with the new Kernel.

Thanks to all for the suggestions though, pointed me in the right direction.