Would you mind adding a few sentences about what NOEXTRAS=1, skipabi=yes and skipmodule=yes do?

Therefore:
1. You should not compile sources as root. If you prefer to build your sources in /usr/src, add your user to the src group, then unpack the sources tarball as your user, and use fakroot for all.. Then once you have the debs built in /usr/src, rename the source directory and then `sudo -i *.deb`, or just delete the source directory altogether, or better yet, build the sources in your home directory
2. If for some reason you did not do all in #1, and you ended up seeing ‘/lib/modules/2.6.xx-xx-xxxx/build’ symlinked to /usr/src/linux-2.6.xx, delete the symlink, and manually symlink it to your newly installed /usr/src/linux-headers-2.6.xx-xx-xxxxx. This way, when you reboot, and dkms kicks in to build and install your nvidia and ath5k and other dkms based modules, it will use the headers directory and not the “unclean” source directory
3. Make sure if you had had dkms build your nvidia or ath5k or other modules for that same custom kernel before, to “remove” them from the dkms build tree first, so they can be rebuilt upon reboot, rather than being installed from previously built sources that will most definitely have different modules versioning….

hope this helps u, or anyone else, give it’s been a while since you posted ur question and you probably figured it out by now

This article is one of my older posts, I revised an article on how to compile a kernel for Jaunty because the changes you are talking about, debian and debian.master are also made into the Jaunty 9.04 kernel.
This article explains how to go about with the changes.

Also, the naming convention of the config files changed.
For example, substitute:
debian/config/i386/config.core2
with:
debian.master/config/i386/config.flavour.core2

Finally, I realized that the two files, ‘control’ and ‘control.stub’, which I edited prior in the “debian.master” directory were somehow not used, and I got an error in the end saying something like linux-image-2.6.31-10blabla was not in control file…. I suspected my changes were reset, so I checked debian.master/control and debian.master/control.stub and my changes were still intact, but then I found clean (unedited) copies in the “debian” directory, dont ask… lol So, I just copied my edited “control” and “control.stub” files from “debian.master/” over to “debian/” and re-ran, and voila! I got me two debs

Thanks for this very useful howto… I was just so used to the “old-fashioned” debian way, and wanted to try the “ubuntu” way for conformance sake…

Cheers

Support for frame buffer devices FB->VESA VGA graphics support FB_VESA

Select all in the:

Console display driver support ->

selct all in the:

Bootup logo LOGO->

-in the GRUB, in the file menu.lst fix this row:

kernel /boot/vmlinuz-2.6.29.3 root=UUID=d5b52903-5…. video=vesafb vga=0×0323 ro quiet

-in the file /etc/modprobe.d/blacklist-framebuffer.conf, comment this row:

#blacklist vesafb

-in the file /etc/initramfs-tools/modules, add:

fbcon
vesafb

-in the end update initramfs this command:

update-initramfs -u

In all my UBUNTU not load boot logo!!!!!!!!

I need to modify the TCP protocol in the kernel (class project). I modified a few C (tcp_output.c) files in net/ipv4 and I compiled with no errors. I’m afraid the changes I made aren’t getting compiled for whatever reason.

I just tried entering “this should not work; ” in the C file, to check if any errors are generated during compile time, and it compiled fine. I think they aren’t being linked.

Sorry for such a basic question. How do I tell the compiler to include all files?

Thanks!