You are not logged in.
Pages: 1
I don't get my own compiled vanilla kernels to work really good.
They seems to lag sometimes, like multi-threading is not working properly.
So I wonder if someone could make a wiki page, as a part 2 of the already existing one.
What to enable in menuconfig and so forth.
I've read something about ck-kernels but I don't have a clue how to enable it.
arch + gentoo + initng + python = enlisy
Offline
+1...I have dabbled around with the Con Kolivas patch and building a custom kernel but the array of options can be confusing. I would like to know what the some of the default options are in the Arch kernel and why they where added.
Here's a link to Kolivas's patch site for further reference. http://members.optusnet.com.au/ckolivas/kernel Also I think another developer has included the ck patchset in their patches...Is it in Andrew's mm patchset?
Offline
i am having good luck with 2.6.9-rc2-nitro1 for the desktop. It's based on the ck patchset, but includes some other patches and fixes. I wasn't able to get 2.6.9-rc2-ck8 running on my box, but nitro1 worked like a charm. If interested, here's the PKGBUILD:
http://bbs.archlinux.org/viewtopic.php?t=7003
by the way, the standard nvidia arch package works with this kernel.
Offline
AFAIK, ck (or the 'derived' cko, nitro) are the best suited for desktop usage, with the appropriate parameters. CK homepage describes pretty well what each patch does. I find that really interesting (& important).
The cko and the nitro patches mostly add patches that introduce features (or update the already existing ones).
:: / my web presence
Offline
These articles may help with standard settings
http://www.micromart.co.uk/content/feat … e=&ID=1906
I would say that rcX kernels are to be avoided waaaay unstable ...
nitroX well nitro1 is fine as has been said, nitro2 onwards nothing but pain..
ck patches build ok...nothing to radical...
Mr Green ArchBang Developer...
Offline
thanks for the info guys,
I will look into this further and try it when 2.6.9 is released,
arch + gentoo + initng + python = enlisy
Offline
You can take the .config from the /usr/src/linux... directory and use that as your starting point when compiling your own, that way you get the arch basic config and you can add/remove from there, rather than trying to get to the arch settings from default.
Offline
Pages: 1