hello,
I want to make a specific kernel for my P4 Hp DC7100 in order to achieve good boot times. I am trying around since few hours and could not find a howto.
Can somebody help and give to me an howto?

My latest status is:
- "sudo tar xf linux-3.0.3-patched.tar.xz" from my distro
- "mkdir /home/linux"
- "sudo ln -s /sdb1/files/linux-3.0.3/ /home/linux"
- "cd /home/linux"
- "sudo make localmodconfig"
error "make: *** No rule to make target ' localmodconfig' . Stop.").

Which OS you are using?

www.tinycorelinux.net
.. but no HowTo is there..

Actually for compiling you need a full compiling environment(headers etc), plus ncurses and perl.

Standard Linux kernel sources are available at:
http://www.kernel.org/pub/linux/kernel

The Tiny Core(TC) patches and other related files for the standard TC kernel are available at:
http://distro.ibiblio.org/tinycoreli...#/release/src/

The process to create a custom kernel could in short be described as:

1. Get the sources for the version of the standard Linux kernel that you are going to base your kernel on
2. Get the patches you intend to apply - both TC kernel patches and possibly others (in my case the RT-patches)
3. Unpack the linux sources and cd into the top level directory of the source package
4. Apply the patches using (in most cases) “patch -p1 < patchfile” for each patch file
5. Move the kernel config file from the standard TC kernel into the same directory and rename it to ”.config”
6. Do “make oldconfig” and answer all questions, in case you have no clue on the answer just provide the default ones (i.e. just hit Return)
7. Do “make menuconfig” and make any changes you need to the configuration
8. Do “make bzImage” to build the kernel itself
9. Do “make modules” to build the loadable modules
10. Do “make INSTALL_MOD_PATH=/path modules_install firmware_install” where /path is a path to a directory where you expect to find the modules.

At this point you will find the kernel file as “arch/x86/boot/bzImage” (relative to the directory from where you issues all the make commands). Further you will find all loadable modules and firmware files under ”/path/lib/modules/kernel_version” and ”/path/lib/firmware”

The bzImage file need to be moved to a location where your boot loader can access it and the boot loader needs also to be configured to boot using the new kernel.

1 members found this post helpful.

“make oldconfig” gives
"make: *** No rule to make target 'oldconfig' . Stop."
..

When it comes to the modules and firmware files, you basically have two options, either let them be part of your initrd (a file named “tinycore.gz” in TC) or let them be part of extension files (*.tcem). In most cases it is probably best to have some of them built into the initrd and some available as loadable extensions. If you are unsure, build all of your files into the initrd. This will give you a tinycore.gz which is significantly larger than the one provided by standard TC, but in most cases you could probably live with that until you have the time to sort out the details of what modules should be put where. When you build your initrd you need to place the modules found under ”/path/lib/modules” under “lib/modules” relative to the root of the initrd. Similarly the files under ”/path/lib/firmware” should be put under “lib/firmware” relative to the initrd root.

IMPORTANT: If you are using a custom kernel you should never use any *.tcem files from standard TC. You could probably load them and they will likely not produce any harm, but taking up memory space, but they will not provide the function you expected. As you can notice above the modules are placed under a directory that contains the current kernel version and the modprobe program will only load modules from the directory that matches the version of the current kernel.

1 members found this post helpful.

From which path you are executing make oldconfig command? In which directory you're when you're executing this command?

The standard TC initrd and the standard *.tcem packages are structured as follows to allow dynamic loading of module extensions:

1 members found this post helpful.

Try referring to Linux From Scratch for compiling help

Here is a site that I'm sure might help you with it:
http://www.linuxfromscratch.org/lfs/...08/kernel.html