Ubuntu – How to install an older 2.6.37 Kernel Version

11.10kernel

I have a Sony VAIO P netbook and for several issues (graphics driver, audio driver and power management), I want to install an older version of the Linux kernel on Ubuntu 11.10 (actually its Xubuntu) that seems to be much more suitable.

So I searched for Ubuntu kernels and found this link which includes all versions of the Linux kernel distributed by Ubuntu. I am looking for a version before 2.6.38 (to escape the known power management issue) and of course solve my many driver problems!

I guess my best bet is 2.6.37 but there are several 2.6.37.x-x kernels! Can someone point me to the right choice?
In each folder (for example: this one) there are several DEB packages. Which packages should I install? (Note: I have a 32-bit system)
What is the installation process? sudo dpkg -i *.deb ? Is this fine or additional steps are required?

Thanks.

Best Answer

first the warning

Changing the kernel is not to be taken lightly - you can leave yourself with serious graphics issues and other issues - and even non booting scenarios.

It is wise to disk-image with a good imaging tool such as Clonezilla BEFORE you start.

mainline kernels vs ubuntu stock kernels

The mainline kernels are built using an older toolchain than stock ubuntu kernels. Its perhaps better to consider downloading ubuntu kernels from specific Ubuntu versions

For example - 2.6.38 for Natty, 2.6.35 for Maverick and 2.6.32 for Lucid.

However, you could look forward to v3.2 that is going to be used in Precise - some have reported good power-management issues with this kernel as well as the latest drivers.

There is a similar question here that will give you some further information: How to downgrade the Kernel on 11.10

Assuming your main issue is power-management, then before you consider changing your kernel - consider installing Jupiter - this is an excellent power-management tool.

installing from the mainline

If you must download from the mainline then the full instructions are on the community wiki. In summary 32bit or 64bit deb packages for headers & generic image together with a common "all" deb package.

All .deb packages can be installed with the same syntax:

sudo dpkg -i [package_name].deb

If you want to use 2.6.37 - then just use the latest 2.6.37.x version. Note - none of these kernels will be receiving security updates - you will need to patch these yourself.

If you are using proprietary drivers (e.g. nvidia or fglrx) then you will need to reinstall those drivers. It may be wise to rename your /etc/X11/xorg.conf file first before booting.

Related Solutions

Ubuntu – Default kernel is missing from grub 1 menu

According to your menu.lst, Ubuntu 11.04, kernel 2.6.38-11-generic is the first and default option. Normally if you installed originally a release of Ubuntu prior to 9.10, it used grub legacy, and the upgrade process will leave that in place. I also notice that your menu.lst has an option to chain load grub2, so it looks like you somehow got both grub legacy and grub2 installed, which is not allowed. Did you manually install grub-legacy with a livecd?

At this point I would suggest trying to purge all traces of grub legacy and reinstall grub2:

sudo rm -fr /boot/grub
sudo apt-get install --reinstall grub-pc
sudo update-grub

During the reinstall step, you should be presented with a menu with a blue background asking you to check off which drives grub should be installed to. Make sure your boot drive is selected. If you don't get that screen, then you can force it by running sudo dpkg-reconfigure grub-pc.

Ubuntu – A realistic date for the kernel power regressions fixes

There is no actual date or any realistic release. Not even in the staging area for the 3.2 version of the Kernel. you can only wait until the diverse groups that are working on this start showing some progress (if any) on this problem which is one of 3 huge ones I see:

Faster Power Consumption
Multiple Problems Related to Intel's New Architecture (Sandy & Ivy Bridges)
Increased Temperature

There are other but this 3 are the ones that affect more users.

I know it has been a long time since this problems appeared (Since the 2.6.38. 2.6.37 was fine), not only for battery drain and temperature but Sandy & Ivy also. The only thing is to wait and know that, since this is an open sourced work, there are thousands of eyeballs looking at the code and trying to help in any way they can to solve the problem.

For what I have read in several places, trying to solve one problem creates others for other users and this is something most developers do not want. They want to solve the actual problem without creating new ones and since Linus Torvald is VERY EXPLICIT in this particular way of working, any added merges to the kernel that fix one of this, or any other for that matter BUT create other problems will not be added to the master kernel. I find this to be a better way of working towards a regression free kernel than as it did not too long ago were an added patch created more problems than it solved.

I will not say that at the end of the 3.2 version or in the 3.3 version, 3.4,...4.0 version this problem will be solved but our only thing right now is to wait or be part of the developers of the kernel and work on that problem.

There are many studies at phoronix about this issue (and other specific stuff like Intel) like:

So to answer your questions that is in all of us the short answer is: There is no sure date to when this problem will be fixed but it WILL be fixed.

UPDATE

As mentioned by our very own famous user29347 (who we will now call the mistery man) there are 2 Phoronix links that show progress in regards to the Power regressions and other related news but one in particular where is mentioned that there was a Pull a couple of days ago that finally solved this problem in the 3.3 Kernel. This link is: http://www.phoronix.com/scan.php?page=news_item&px=MTA0MTM

So the 3 points mentioned above about power consumption, multiple architecture problems for ivy and sandy bridges, video problems and temperature problems will be solved in the 3.2 and 3.3 kernel versions. Most probably any left over misc bug will be addressed in the 3.4 kernel and finally finish anything left over.