Kernel version after upgrade?

[ElEdwards]

I did a clean Mint v6 installation about a week ago (finally getting rid of XP..... YAY!) and everything is going perfectly!

However, I just realized that during one of the updates, a new kernel was downloaded but it isn't in use. In /boot, I can see both 2.6.27-7 and 2.6.27-9.

My Grub menu only has an entry for 2.6.27-7. Is there a reason why the menu wasn't updated to include 2.6.27-9?
....and would it hurt anything to manually add it?

Thanks!
El

[Husse]

Is there a reason why the menu wasn't updated to include 2.6.27-9?

The new kernel may simply not have been installed correctly
When a new kernel is installed you should always get a new option in grub
To copy the present line in menu.lst and change -7 to -9 is perfectly OK
Of course you need the other lines surrounding it too

[ElEdwards]

OK,I made those changes and so far, so good.

Any idea why the changes didn't happen automagically?

El

[Husse]

What is the difference one can expect using the two different kernels?

Mostly nothing
It's some new hardware added or ... or...
In the Mint Newsletter there's a link to news about the kernel and you can find out exactly what it is
The 2.6.28 has major improvements, but that will have to wait until Gloria (Mint 7)

[ElEdwards]

Husse,

FYI, I just updated to 2.6.27-11....and had to manually change the Grub menu again.

Any idea my Grub menu doesn't update automatically with the update?

Thanks!

El

[exploder]

I think it is because of the version of grub we are using.

[mcurran]

Since my OEM manufacturer (ASUS) sucks the big one, and refuses to correct our BIOS issues, I still need to recompile the kernel with every Mint release/update in order to get my system to use more than 2GB of DRAM AND VRAM. This time around, I downloaded the latest linux-image and linux-headers for kernel 2.6.27-11-generic. Everything went well and patched successfully; however, for some reason, Felicia x64 wants to build the updated deb packages as 2.6.27-12* versions. This would be fine; however there are currently no header packages available for the 2.6.27-12-generic kernel yet, and therefore the created package will not install, and the whole process is broken without the headers. Does anyone know how I can prevent Felicia from creating newer packages from the sources and image I provided (2.6.27-11-generic). Please let me know. Here is the command I'm currently using to build my deb packages after I patch the kernel.

sudo CONCURRENCY_LEVEL=2 fakeroot debian/rules flavours=generic

[Husse]

@ mcurran
Sounds strange - but there must be a reason for it
Anything stating -12 somewhere?
Something that adds 1 to -11?
Ever had the problem before?