Social Sites
Syndication
Navigation
« Mmmm coffee | Main | Intricate complexities »
Saturday
Dec292007

Ubuntu kernel

 

So, I've had a couple issues here-and-there on my laptop with the released kernel for Ubuntu 7.10 (Gutsy Gibbon). These range from audio problems after suspend to WiFi card dropping out and causing the system to freeze. These problems are addressed by later kernels, which will not be available for another five months or so when Ubuntu 8.04 (Hardy Heron) is released. Naturally, I was caught between a rock and a hard spot. I could either hack away at the Ubuntu sources to get the newer drivers while maintaining the stability of the stock kernel, or I could go for broke and compile my own.

Me being who I am, I chose the latter. I downloaded a release candidate of the bleeding edge kernel sources, customized it a bit, tweaked the configuration how I like, and compiled everything up. Upon reboot I had a laptop that worked 100%, and did so quite consistently. But I scratched the initial itch- something I should have never done. Now, I find myself going far overboard.

I have found the Zen kernel, which has recently been compiled for Ubuntu. Compiling the kernel itself isn't too big a deal, but dealing with the patching and updating certainly can be. I've decided to re-compile the current Zen kernel to my liking, get my graphics drivers working properly, and see where I get. If I continue down this path, I should be back to my own custom kernel within a few days. But this time, I'll have a massive collection of patches to take with me.

This brings up an important point, though. If you compile your own kernel, do you take the opportunity to give up some debugging data to gain a bit of speed? If so, what is the trade-off and what kind of returns are you actually getting? If my WiFi card dies and I can't see why, but I can use kernel calls 2x as fast, then perhaps I accept the flaw. But, if I only gain 1-2% I may not like the trade. Also, keep in mind that most distributions turn ON debugging and tracing data so you can actively seek out bugs and flaws. This means you can actually submit meaningful data to the kernel developers, allowing them to fix problems other users may be stuck with. Naturally, with this comes international fame and recognition. Not really, but you never know.

So, the moral of this story is- Compiling your own kernel can be satisfying, frustrating, devastating, and minimally rewarding at the same time. There can be a lot of work for very little pay-off, but if you're that type of guy or gal, kernel work is for you! It would also be interesting to see the MOTU release a kernel like linux-image-unstable or something like that. Basically, a kernel package that is updated once a month or so, which would come with all of the other module and kernel packages recompiled as well. It would be a lot of work, but there are certainly enough dedicated gear-heads out there to move the project forward.

 

PrintView Printer Friendly Version

EmailEmail Article to Friend