If in the outside chance you feel you need to upgrade your kernel for any particular reason, this is how you do it THE EASY WAY. Note that this guide requires no compiling and works for Mint and Ubuntu only (it's probable that this works for other Ubuntu derivatives, but I haven't tested it and can therefore offer no opinion).

- 2 - In each of these directories you're going to see "BUILD.LOG", "CHANGES", three items that begin with "linux-headers", two that begin with "linux-image" and one that begins with "linux-source". The "BUILD.LOG", "CHANGES", and "linux-source" are completely unimportant right now. We're only worried about "linux-headers" and "linux-image".

- 3 - Download and then install the following IN THIS ORDER: first get the linux-headers file that ends with "all.deb". Second get the linux-headers file that ends with "i386.deb" or "amd64.deb" depending upon what architecture you need. Finally get the linux-image file that ends with "i386.deb" or "amd64.deb" again depending upon what architecture you need. Honestly it doesn't really matter what order you download them in, but you need to make absolutely sure that you install them in this order.

- 4 - Reboot your computer and you're done.

Disclaimer: I do this all the time and it's yet to not work for me. You do need to understand that there is an inherent risk associated with all low level system stuff like this. If it borks your system, I claim no responsibility.

Kendall wrote:Disclaimer: I do this all the time and it's yet to not work for me. You do need to understand that there is an inherent risk associated with all low level system stuff like this. If it borks your system, I claim no responsibility.

Could you post a how to "unupgrade" in the event the system doesn't respond, well, pleasantly, afterwards?

I, too, have used this procedure effectively in the past.

I like poetry, long walks on the beach and poking dead things with a stick.

Would also like to add that during the install of each of the .deb files, I like to click on the "triangle next to terminal" and watch the install happen and watch for any issues (especially true if you have proprietary drivers), this way you can make sure those drivers build properly against the kernel. If you see a failed proprietary driver build, "Don't boot into that kernel".

smsmith wrote:Could you post a how to "unupgrade" in the event the system doesn't respond, well, pleasantly, afterwards?

The simple solution is to simply not boot into that kernel, but I'll try and throw something together that adequately explains how to eliminate that particular kernel as an option.

MaddogF16 wrote:Would also like to add that during the install of each of the .deb files, I like to click on the "triangle next to terminal" and watch the install happen and watch for any issues (especially true if you have proprietary drivers), this way you can make sure those drivers build properly against the kernel. If you see a failed proprietary driver build, "Don't boot into that kernel".

I usually install via with "dpkg -l package-name.deb" so everything's right there in the first place, but if installing with gdebi, then this is very good information.

smsmith wrote:Could you post a how to "unupgrade" in the event the system doesn't respond, well, pleasantly, afterwards?

Kendall wrote:

smsmith wrote:Could you post a how to "unupgrade" in the event the system doesn't respond, well, pleasantly, afterwards?

The simple solution is to simply not boot into that kernel, but I'll try and throw something together that adequately explains how to eliminate that particular kernel as an option.

What is the problem here? It's very simple. When you install the new kernel, the old kernel is always there, its grub entry is also always there. The new kernel is just installed in addition, so if at reboot there is a problem, just reboot in the old kernel which works then open Synaptic (or if you prefer, you can use the command line) and remove the packages of the new kernel.

K.I.S.S. ===> "Keep It Simple, Stupid""Simplicity is the ultimate sophistication." (Leonardo da Vinci)"Everything should be made as simple as possible, but no simpler." (Albert Einstein)

smsmith wrote:Could you post a how to "unupgrade" in the event the system doesn't respond, well, pleasantly, afterwards?

Kendall wrote:

smsmith wrote:Could you post a how to "unupgrade" in the event the system doesn't respond, well, pleasantly, afterwards?

The simple solution is to simply not boot into that kernel, but I'll try and throw something together that adequately explains how to eliminate that particular kernel as an option.

What is the problem here?

No problem here. I just thought it'd be nice to have a back-out how to posted as well for those of us that stumble across this and decide, "Well, that sounds easy enough". And then, if mayhem ensues, presumably we've read the whole thing and would have a way to go backwards.

But, a hypothetical for you. Suppose I decide to boot up my computer and then go get some coffee, forgetting that the kernel update I did broke something major. Grub has an auto timeout to boot whichever kernel is FIRST in the list. As I am away getting my coffee, I boot into the broken kernel. Now I need to reboot.

And since I was the one asking, here's how I backed out one of the kernels I tried in the hopes it fixed something else irritating me, only to find out that my sound no longer worked...

1. Open up KPackageKit or whatever it is you use to manage packages.2. Searched for linux-headers.3. Selected for removal the linux-headers version that matched the not-so-nice kernel. Hit apply.4. Repeat steps 2 and 3 using linux-image.5. Close KPackageKit.

On reboot, the offending kernel was no longer listed in Grub.

I like poetry, long walks on the beach and poking dead things with a stick.

Kendall wrote:If in the outside chance you feel you need to upgrade your kernel for any particular reason, this is how you do it THE EASY WAY. Note that this guide requires no compiling and works for Mint and Ubuntu only (it's probable that this works for other Ubuntu derivatives, but I haven't tested it and can therefore offer no opinion).

- 2 - In each of these directories you're going to see "BUILD.LOG", "CHANGES", three items that begin with "linux-headers", two that begin with "linux-image" and one that begins with "linux-source". The "BUILD.LOG", "CHANGES", and "linux-source" are completely unimportant right now. We're only worried about "linux-headers" and "linux-image".

- 3 - Download and then install the following IN THIS ORDER: first get the linux-headers file that ends with "all.deb". Second get the linux-headers file that ends with "i386.deb" or "amd64.deb" depending upon what architecture you need. Finally get the linux-image file that ends with "i386.deb" or "amd64.deb" again depending upon what architecture you need. Honestly it doesn't really matter what order you download them in, but you need to make absolutely sure that you install them in this order.

- 4 - Reboot your computer and you're done.

Disclaimer: I do this all the time and it's yet to not work for me. You do need to understand that there is an inherent risk associated with all low level system stuff like this. If it borks your system, I claim no responsibility.

Hi there, I just wondered (as a newbie) if there was something wrong with using Update Manager in Mint 8 as I did, it took care of everything perfectly, installed the new Kernel 2.6.31-20 and all and any dependant files, without a single error or bleep. I then rebooted using the new Kernel, tested everything I could think of, did this a few times just to be sure then used Ubuntu Tweak to delete the old Kernel and clean out the app caches.

I am glad to say that everything on my system is working perfectly, no errors whatsoever. Apart from the rebooting to test everything all that was needed were 2 clicks of a mouse for this surely this is by far the easiest way or am I missing something here???

Note: if you are using the restricted drivers you may get an error (if using the command line: it will identify the driver and fail). If you just double click the .deb files you may miss this and when you reboot you get a message that Ubuntu will / can launch in low graphics mode, or you can reconfigure etc. So I suggest that you remove the restricted driver before you start the how-to, which btw is very good.I was using the nvidia 185.nn.nn driver on my laptop

If anyone else with an Intel wireless 6200 WLAN is having trouble in Mint 8 (e.g. Dell Studio 1558 users), following the above kernel upgrade method seems to have worked for me. I chose the 2.6.32.9 kernel at http://kernel.ubuntu.com/~kernel-ppa/ma ... v2.6.32.9/ and it connected to my wifi immediately after rebooting.

Well guys, the problems with upgrade the kernels are... sad for Ubuntu. I have done many kernels updates in other distros (e.g. Frugalware, Debian Testing, CentOS, Fedora, Parsix...) over the years with absolutely no problems. Never. And with different computers with different hardware. Ok I don't use wireless etc but still. Maybe I'm a lucky man?

K.I.S.S. ===> "Keep It Simple, Stupid""Simplicity is the ultimate sophistication." (Leonardo da Vinci)"Everything should be made as simple as possible, but no simpler." (Albert Einstein)

Great stuff man! Following the steps was a bit hard but I managed to push through. I could use this for as long as Unix is alive! Great work on the tutorial man. I guess you know how much help you have shared! God Bless!