Building a kernel from source.
hi all, is alienBoB's howto
http://alien.slackbook.org/dokuwiki/...kernelbuilding work for a 3.* kernel? |
Yes. But if you are building a x86_64 kernel, you won't have to enable 64GB of ram. That kernel will already see all your ram. Good luck! Building a kernel is a great exercise.
|
Thanks mlangdn, I only have 32 bit systems.
|
Works. Actually, I am running kernel 3.4.11 on Slackware64 current. I just picked up config file from testing/, two options changed(processor family & Preemptible kernel) and followed Alien's instructions.
|
I've been using the smp kernel when using 13.37, should I be using the generic config for single core?
|
No, unless you have a very old CPU. If you hit "F2" at time of choosing the installation kernel this will be reminded to you:
Quote:
But maybe your question was more "should I choose a generic kernel, versus a huge one". If that is the case, and whatever you CPU be, though not mandatory switch to generic is generally recommended as in some cases having conflicting drivers buit-in *could* cause problems. |
Quote:
|
It seems I've quoted /isolinux/f2.txt included in Slackware 13.37 instead of Slackware current. Oh, well...
|
|
Then you can safely use the smp kernel. As side note, the output of "uname -p" would have been sufficient.
|
Has anyone tried starting with a config from http://kernel-seeds.org/? I was going to try this at some point to get the latest kernel running, our of curiousity not necessity, but haven't had the time yet.
|
Quote:
I just had a look there and would advise anybody wanting to tweak their kernel's configuration or install a newer kernel not included in Slackware to use one of the config files shipped with Slackware (either in /boot or in /testing) as a basis, copy it at the root of your (possibly new) kernel source tree then run "make oldconfig" followed by "make xconfig" instead. As for taking in account your hardware configuration e.g. running "lspci -k" or "cat /proc/cpuinfo", of course you can do that yourself. Use the search feature (Ctrl+F) of "make xconfig" to help you finding you way in the kernel tree and don't forget to edit the LOCALVERSION string to avoid overwriting the stock kernel and modules. |
Ok, i'm using this new kernel. I want to create a kernel package, so when I reinstall I don't have to keep building the kernel. Would the script on a previous post on LinuxQuestions work?
http://www.linuxquestions.org/questi...ackage-369142/ Maybe modifying it to add my .config file for building. |
I would suggest you use the SlackBuilds provided in /source/k instead. You will have to replace the source tarball and its signature file, the config file and either edit the VERSION variable in the relevant SlackBuilds or execute them like this : "VERSION=<your kernel version> /path/to/the/SlackBuild"
|
Thanks Didier Spaier, i'll give that ago. :)
|
All times are GMT -5. The time now is 03:34 AM. |