Newbie Guide To Compiling A Kernel!
first and foremost, THIS may pertain to you so read that first and then you can proceed ;)
and here is a similiar site www.kernel.org **"Go get the kernel source"** cd /usr/src **"Change Directory To /usr/src"** ls -alc **"check for symlink (ex. /usr/src/linux->/usr/src/linux-2.4.18)"** **"also note since its being ask recently, that if there is no symlink"** **"then move on to the untarring of the kernel"** file linux **"double check with this command (output ex.) linux: symbolic link to linux-2.4.18-14"** rm linux **"remove symlink"** tar -zxvf linux-x.x.x.tar.gz **"unpack the tarball (new kernel)"** ln -s /usr/src/linux-x.x.x /usr/src/linux **"make a new link to the new kernel"** cd linux **"type this to change to the directory"** ---------------------------- Now Comes The Fun Part~! ---------------------------- make mrproper **"this removes the current .config and other files"** cp /usr/src/linux-2.4.x/.config /usr/src/linux ***this is if you want to use your old config*** <-->Your Choice<--> make config **"basic config from terminal"** make menuconfig **"for ncurses GUI in the terminal"** make xconfig **"for X-based GUI with modular explanations"** (QT Based) make gconfig **"same as above, but for 2.6.x kernel only"** (GTK Based, and might be still buggy) /********** Note: Don't forget to add module support and kernel support for future hardware. Do not compile your harddrive and filesystem type as a module. The configure program enables you to specify an enormous number of features. It is advisable to skim through all the sections to get a feel for the different things you can do. Most options are about specifying whether you want a feature[*] compiled into the kernel image, [M] compiled as a module, or [ ] not compiled at all. You can also turn off module support altogether from Loadable module support -->. The kernel configuration is one LINUX program that offers lots of help--select < Help > on any feature. The raw help file is /usr/src/linux/Documentation/Configure.help can be also worth reading. When your done the config click exit and save current configuration. Your file is now known as .config . **********/ SKIP THE FOLLOWING IF DOING A 2.6.x KERNEL make dep **"ensures dependancies such as include files are in place"** (vi, pico, emacs) Makefile **"Want A Unique Kernel Name? Edit /usr/src/linux/Makefile and change EXTRAVERSION" make clean **"to clean your sources for they compile correctly"** START HERE IF COMPILING A 2.6.x KERNEL make bzImage **"to make the kernel image (compile and creates compressed image of kernel)"** make modules **"compile your selected modules"** make modules_install **"to install newly compile modules (installs to /lib/modules/linux.x.x.x)"** -------------------------------------------- Now Its Time To Install Your New Kernel~! -------------------------------------------- Remove the following links: rm -rf /boot/System.map rm -rf /boot/vmlinuz Then copy the newly created kernel and system.map to /boot cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-x.x.x cp /usr/src/linux/System.map /boot/System.map-x.x.x Make the new links: ln -s /boot/vmlinuz-x.x.x /boot/vmlinuz ln -s /boot/System.map-x.x.x /boot/System.map <-> NOTE: <-> Before doing the next step, read this [1] and this [2] about the initrd.img and see if you even need to do this step ... there is alot of posts about this step, so i am adding this section ... <-> END NOTE <-> Next remove existing initrd.img file: rm -rf /boot/initrd.x.x.x.img ..And create the new one: /sbin/mkinitrd /boot/initrd-x.x.x.img x.x.x (Note: ) The last set of x.x.x is the eqivalent to your new kernel version and it looks to /lib/modules for that version. -------------------------------------------------------------------- Use The Steps That Pertain To You If You Use Grub Then Edit grub.conf If You Use Lilo Then Edit lilo.conf -------------------------------------------------------------------- remember to leave the entry to your old kernel image just in case, so modify what is in the config originally to point to the old image and make a new entry for you new image you just made .... -------------------------------------------------------------------- <-> And Finally Edit Your /etc/grub.conf file <-> <-> Note some distros now use menu.lst, so if you can't find grub or lilo, then you know what to look for <-> title New Kernel :D kernel /vmlinuz-x.x.x ro root=LABEL=/ initrd /initrd-x.x.x.img (Note: ) look at the previous parameters in the grub.conf file and note what "root=" and use what is existing. Exit and Save grub.conf type "/sbin/grub-install" AND REBOOT!!! <-> And Finally Edit Your /etc/lilo.conf file <-> image = /boot/vmlinuz-x.x.x label = New Kernel :D root = /dev/hdx read-only (Note: ) look at the previous parameters in the lilo.conf file and note what "root =" and use what is existing. Exit and Save lilo.conf type "/sbin/lilo" AND REBOOT!!! /******EDIT******* as requested there was wanting the instructions on how to apply patches to your kernel. ****END EDIT*****/ read this or look below .. This step comes after untaring your kernel source. When you download the patch place it in the folder that you untarred you new kernel. Then type: patch -E -p1 < sound_patch Purely an example and you would type whatever the file name is in replace of sound_patch. As of having alternative boot options, well this is no problem.. The stuff above that i tell you to add to your lilo or grub file above could just append the file, and just add ".old" to the title of your oringinal kernel name for you will know the difference. and whether its grub or lilo add "read-only", to the end of the oringinal entries in the lilo.conf, or grub.conf file. |
so why did i do this?
well i figured i would write a completely new guide with detailed explanations on whats going on, and these steps can address a larger crowd then most guides do, with how they are set up.. so if anyone notices anything wrong or feels there is something i missed, then i'll be glady to add to it or fix it... |
Thanks a lot, that's very helpful -- when I'm a grown up ;) Linux person I will try that ...
I think most people are a little nervous, when you ask them to delete their kernel. Or at least I would be. Why not create the new kernel as an alternative (and show the changes in the symlinks, GRUB / LILO), so one has (two or more) different boot options. Oh, yes, what about handling patches? <- more work for you :D |
thank very much ,Drozz~!
I compiled the new kernel ,but there is some puzzle. I compiled the APM in the kernel ,but why i still cant shut the the computer with poweroff ?(it cant shut down with power) if I want to put my modem modules in the kernel ,what should i do? help me please~thanx |
as of the APM laxi i am not too sure about that, hopefully someone can help you with that, i can't see why its not working if you compiled it into the kernel, unless you compiled it as a module and the module is not loaded...so i guess maybe you could try modprobe apm, and then try shutting down to see if that was the case.
and the modem, maybe this applies to the patch section i described above. |
Hey laxi, are you sure your laptop isn't using ACPI instead of APM? A lot of laptops are using ACPI these days..
|
also another alternative thats there if you want to use it is something like this :
cp -R /boot /boot2 mv /usr/src/linux/System.map /boot2 mv /usr/src/linux/arch/i386/boot/bzImage /boot2/vmlinuz mv /usr/src/linux/vmlinux /boot2 before you do any of the steps mentioned above. thats a very brief and quick explanation and i may have missed something but i am sure you'll get the idea if you want to setup your old kernel like so...also making changes to your .conf files of course, etc,etc.... |
What's the use of System.map and initrd-x.x.x.img? My system is working fine without them?
Thanks |
Quote:
Quote:
|
Quote:
PS. there's a file called module-info, what's it? how can I generate it when compiling a new kernel? I'm using Red Hat 9. Thanks |
well i am not quite sure how your system is set up and why it does / doesn't work how it does...what distro are you using, i only wrote this article to be used on alot of distros not all distros....
as of the module-info file it is a link to module-info-{kernel-version} Contains information about all available modules (at least those included in the default kernel config.) might be used by kudzu to determine default parameters for modules when it creates entries in /etc/modules.conf (guessing here) thats all i can gather, maybe someone else has some better answers for you specific question. |
thank you Drozz,i use the old kernel ,and when i modprobe apm
the power can shut down with the command poweroff,but i use the kernel compiled by myself (i add the apm into kernel,when i compiled it),it cant shutdown ,just display Power Down in the end. is there something else i should do when i use the new kernel? thanks everbody~ |
thanks Pcghost,but my computer is not a laptop.the ACPI is a power manage module,all right?can it use in my computer ?
|
did you compile it as a module ? if so is it being started, if not, did you try modprobe apm with the new kernel? you may have meant to answer these things, but i don't seem to see the answers to these questions in what you just said.
|
Why recreate the wheel
|
All times are GMT -5. The time now is 01:39 AM. |