Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am trying to debug the pci mapping code that the kernel executes on boot, as I have a card that does not get mapped properly. To do this I am adding debug messages to the relevant bits of code, so I can see what's going on.
Then I build the kernel using the "debian way":
make-kpkg --initrd --append-to-version=-pci kernel_image kernel_headers
dpkg -i kernel-headers-220.127.116.11-ubuntu1-pci_10.00.Custom_i386.deb
dpkg -i kernel-image-18.104.22.168-ubuntu1-pci_10.00.Custom_i386.deb
which works fine. But the compile takes about an hour, and I boot the new kernel once, read the debug messages, add a few more messages and compile again.
As I'm only making small changes each time, and not changing the configuration, is it possible to only rebuild the parts I have changed?
By not doing the
Then you have to use the same revision I suppose.
And probably before installing the new package, it is best to remove the old one. Removing the one you are running one works, ignore the warnings.
Fortunatly it has always worked like this!
It should, its the purpose of make. (On my system, it works)
Did you modify code or changed some #include (which could require a make dep)?
Did you touch any makefile.am or makefile?
Yes you can use make but you should have the same result, make-kpkg calls make. And then with make only, you won't have a package, but it doesn't matter; a kernel package is a list of files in /boot, the tree /lib/modules/2.xxxx so you can easily remove these files manually.
Here's something to try, I'm not promising it will work, though. Make your change, and recompile without the clean. Then, copy the changed module (xxx.ko) over top of the one in the /lib/modules/(version)/kernel/(whatever) directory. Then reboot. If things come down around your head, you should be able to just reboot from a previous kernel and fix it before proceeding.