Compiling A Custom Linux Kernel

<div align="center">Hardware Cheat Sheet</div>

Use the following cheat sheet to write down your system's hardware. Examples have been provided in italics. RAM type and speed, hard drive make and models, or any type of cooling and lighting systems are not necessary for compiling your own kernel.

CPU:
<blockquote>Make, Number of Cores:
Make, Number of Cores: AMD Athlon64 3200+, 1 core</blockquote>

Hard Drive Controllers:
<blockquote>Type, Make, and Chipset:
Type, Make, and Chipset:
Type, Make, and Chipset:
Type, Make, and Chipset: Serial ATA, Via, 8239 Chipset
Type, Make, and Chipset: Parallel ATA, Via, VT82C586A Chipset</blockquote>

Video Card:
<blockquote>Make, Model, Chipset:
Make, Model, Chipset:
Make, Model, Chipset: ASUS, V9750TD, nVidia 5700 Chipset</blockquote>

Sound Card:
<blockquote>Make, Chipset:
Make, Chipset:
Make, Chipset: Creative Labs, ES1371 chipset</blockquote>

Network Card:
<blockquote>Type, Make, Chipset:
Type, Make, Chipset:
Type, Make, Chipset: Wireless, D-Link DWL-G520, Atheros AR5212 a/b/g Chipset
Type, Make, Chipset: Ethernet, Onboard NIC, Marvell Yukon Gigabit 10/100/1000 chipset</blockquote>

Other Devices:
This includes USB/Firewire, TV input cards, HAM radios, or anything else not covered above.

<blockquote>Type, Make, Chipset:
Type, Make, Chipset:
Type, Make, Chipset:
Type, Make, Chipset: Onboard Firewire, IEEE 1394 Firewire Controller, VIA-based
Type, Make, Chipset: TV recorder card, Hauppage!, BT878 chipset</blockquote>

Thank you Andrew Many of us will come to look at your guide -- repeatedly.

thanks a lot!!

Excellent info, the one thing I would add though, is that it may be better to use rpm -ivh to install the kernel; this will keep it from overwriting the existing kernel, and leave a fallback in case something goes wrong with the new kernel.

Also, another thing that is often useful is the option in the make configure screen for "Local version - append to kernel release" (under General Options), this is great if you want to try different versions of the same kernel. I always add "-elsewhere", which gives me a kernel version of 2.6.24.3-elsewhere, for instance. When I've experimented in the past, I've created "-elsewhere-ck", or "-elsewhere-rt", etc. for experimenting with different configurations, and I can pick my poison from the grub bootscreen. The option you add here will differentiate the kernel packages from other compilations of the same kernel. Using a local release option will also keep your kernel from conflicting with any possible openSUSE generated kernels of the same version.

Hope I'm not complicating things too much, just my 2c...

Cheers,
KV

Excellent info, the one thing I would add though, is that it may be better to use rpm -ivh to install the kernel; this will keep it from overwriting the existing kernel, and leave a fallback in case something goes wrong with the new kernel.[/b]

It won't overwrite the openSUSE kernel; that's called "kernel-default" or "kernel-smp". Changed anyway, though, since I suppose people wouldn't want to overwrite their previous custom kernels.

Also, another thing that is often useful is the option in the make configure screen for "Local version - append to kernel release" (under General Options), this is great if you want to try different versions of the same kernel. I always add "-elsewhere", which gives me a kernel version of 2.6.24.3-elsewhere, for instance. When I've experimented in the past, I've created "-elsewhere-ck", or "-elsewhere-rt", etc. for experimenting with different configurations, and I can pick my poison from the grub bootscreen. The option you add here will differentiate the kernel packages from other compilations of the same kernel. Using a local release option will also keep your kernel from conflicting with any possible openSUSE generated kernels of the same version.[/b]

Thanks, I'll add that when I have time.

It won't overwrite the openSUSE kernel; that's called "kernel-default" or "kernel-smp". Changed anyway, though, since I suppose people wouldn't want to overwrite their previous custom kernels.
[/b]

True, but if you're copying an existing config from -default etc., it will append itself. Likely not a big issue, particularly since this is about upgrading to latest mainline, but I've sadly burned myself this way in various manners I'm too embarrassed to mention because of this, so I always feel obliged to mention it, if only to make myself feel better about the sins of my past, or my own stupidity. They're often one and the same...

Cheers,
KV

hello...

i want to know what is this...

ksym(default_wake_function) = ffd5a395 is needed by kernel-2.6.24.4smp-1.i386

when i run/install the newly created rpm, i get this error... there are lots of errors and the only difference is wrote it in italics.

what is ksym? is it a variable?

thanx...

if you want the whole error just pm or email me at xeroblast1981@gmail.com

STEP 23. Reboot your system. When you are given the choice of operating systems to boot, you should see your new kernel listed next to the stock kernel.

STEP 24. Select and boot from your new kernel.
[/b]

I quite sure that I've done everything right, like explained in the steps above. However, I don't when and how to choose to boot into my new kernel. Any help would be much appreciated.

Thanks

I quite sure that I've done everything right, like explained in the steps above. However, I don't when and how to choose to boot into my new kernel. Any help would be much appreciated.

Thanks
[/b]

if you all the steps you should have added it to the menu.lst so when your grub menu comes up it should be there

if you all the steps you should have added it to the menu.lst so when your grub menu comes up it should be there
[/b]

Hi Havoc, thanks for your reply.

I've been googling for this a bit yesterday night and found that my new kernel should be added to /boot/grub/menu.lst like you say. However I don't find a /boot/grub directory and thus no menu.lst file either. Is it possible that I don't have grub installed? I've only one OS installed (OpenSuse 10.3) so I guess there was no need for it until now.

I did however found a way to boot into the new kernel by adding it to OpenSuse's Boot Loader. I need a vmlinuz file for that, that I found in /boot and an initrd file. I presume the one I made in step 22, but I don't kow where it is located. Can anyone help me with that please?

Kind regards