How To Compile the new 2.6.16 kernel from kernel.org

[ajarmoniuk]

I think there is a problem with GCC 4.1 in Ubuntu Edgy. Try installing the gcc-4.0 package and then use this version to compile the kernel.

Works for me.

[Orbitr8]

Just now compiled 2.6.18.2 using gcc 4.12 + by following the instructions on page one of this thread, reinstalled the nvidia drivers, and everything works just swell on my conroe.

Actually, the first time I tried, I fluffed up something along the way, so I tried again, disabled a ton of modules and it booted fine, so I did it over with even more disabled options and drivers, etc.

My first compile.

They take 15 minutes each, and the resulting .deb file comes out to 12.3 megs.
Being a linux noob and all, how does the time and size stack up to 'normal' compilations, if there is such a thing.

Seems like it took longer to go through the modules than it did for anything else.

Compiz works fine, although I'm using a VIA board, so I can't get true NVAgp, but games play great. I get almost 200 fps in UT2004 with a 6800 XT.

happy here ~ long live the Penguin

btw. The Ubuntu experience has been awesome. The amount of information available for Ubuntu is amazing, and growing all the time.

[goldenatom]

Would this be pretty much the same for the 2.6.19 kernel?

[Orbitr8]

Just now compiled 2.6.19, with basically the same step-by-step instructions from page 1 of this thread, reinstalled my nVidia video drivers, and it's up and running so far, including Beryl.

Had to reselect sound manager in a couple of programs.

If I weren't such a noob in Linux, I might be able to give some further insight to changes in gconf, but I basically went through each option and most options were already selected from the previous kernel upgrade (2.6.18.2).

I did have some issues trying to get a command line after the expected X failure , and so recompiled again, double checking all steps. It worked the second time. (or was it the third ?)

Breaks VMWare at this point, so if you're reliant on VMWare... don't do this thing yet.

~kc

[thathatman]

I compiled the 2.6.19 kernel on dapper with no problems.
In order to get fglrx support working, I had to do several things:
Change the make script to executable as described in the ati fglrx wiki.
Change every reference to config.h to autoconf.h in /usr/src/modules/fglrx/*
Move the fglrx.ko file to the right place. For some reason it installed in

/lib/modules/misc

when it should have installed to:

/lib/modules/2.6.19/misc

After that, I did a modprobe fglrx, restarted X, and i was back in business.
Let me know if anyone has any similar questions.

[happy-and-lost]

I tried compiling the 2.6.19 kernel on Edgy, but it stops dead at boot. Just sits there. Nothing. So now I'm left with 600mb of files created during the compilation in /usr/src/linux What can I do with them?

[twinszg]

Thanks m8,it works for me. Great tutorial

[muxecoid]

Compiled and installed successfully. :b:

[michie86]

hello.. i was wondering.. are the steps you stated are the way to "upgrade" my kernel from 2.6.15 to a 2.6.16? Coz i'm currently having problems with detecting my modem for dialup connection and somebody told me that the solution is either upgrading to ubuntu 6.10 or compiling my own 2.6.16 kernel. Is this it? I decided that maybe i'll just compile since i do not have a 6.10 cd installer. Am i on the right track? And also, the "sudo apt get build....." in the first step, that requires internet connection? Am i right? If so, how can i download the necessary files manually? since my i can't fix my dialup connection as of now. Thanks.

[ryan76]

I tried this HowTo to get DRI working and it still isn't.

make sure fglrx is in the Driver section.

What does this mean?