My kernel compile guide for Slackware 11

ericfx · 03-19-2007, 05:18 PM

I wrote a how-to on how to compile the 2.6.18 kernel that is on the Slackware FTP.

It might be helpful too you, check it out.

http://www.h0nke.com/help-kernslack11.php

Nem · 03-19-2007, 10:25 PM

Hey thx!
I found it useful because I never
built my own kernel and when I will
want to, this will be a good guide!

rkrishna · 03-20-2007, 12:02 AM

Quote:

make -j3 bzImage

i think u dont need the two "make -j3 .." lines
make modules_install will do all the job.

what i usually do is untar the kernel to my home, so that i have full control, will use xconfig or gconfig, from my xwindow, too coool

cowyn · 03-20-2007, 04:33 AM

not bad.
just said as rkrishna:
sudo make -j4
sudo make modules_install
and then cp ... to ...
that's it.to compile kernel 2.6 is diff from 2.4.

rkrishna · 03-20-2007, 08:46 AM

PART FROM MY PAGE it is in a pretty bad condition now

Code:

$ make menuconfig 
$ make 
# cp System.map /boot/System.map-2.6.x.x ; ln -sf /boot/System.map-2.6.x.x /boot/System.map
# make modules_install
# cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.x.x
#lilo ------ edit lilo before this
#reboot ------to test the new kernel

pdw_hu · 03-20-2007, 11:34 AM

Imo a bit simpler method is to just use 'make install' and don't waste time on copying files. This will copy the old vmlinuz to vmlinuz.old. And this way you don't even need to edit lilo.conf.

ericfx · 03-22-2007, 05:06 PM

My current web host sucks, so if my site is down, you can view the how-to on Open Addict:

http://www.openaddict.com/how_to_com...ware_11_0.html

markomarko · 03-23-2007, 09:46 AM

i have slack 10.2. with 2.4.31 kernel, if i compile and install latest kernel, does that means that i will have to reinstall some programs that i compiled and installed with ./configure;make;make install?

and, this is maybe offtopic, but i want to know what are pros and cons when we are talking about replacing kernel?

thanx!

titopoquito · 03-23-2007, 10:39 AM

Most programs should still work, only some that for example build a kernel module (like fuse to get ntfs-3g driver working, proprietary video drivers or vmware) would require to build them again.

About pros and cons: You would have to read the kernel changelog or some reviews to see if you need it. If your system is like you like it and works without problems, IMHO you should not switch. Of couse if you intend to learn something just do it

Drone4four · 03-24-2007, 11:53 AM

Thanks h0nke for this extremely useful guide.

cyb0rg777 · 04-01-2007, 01:34 PM

I've been having trouble with the configuration.
If I copy my configuration from /boot to the /usr/scr/linux-<>/.config,
and then do a make,
it should produce exactly the same kernel,
right?

What if I upgrade my kernel and want the same config as the old kernel?

props666999 · 04-01-2007, 02:18 PM

Hi

When you compile your kernel you copy from /usr/src/linux to /boot
the following files
1)bzImage
2)System.map
3).config

the .config file contains all the choices that you have made during the make menuconfig time ( or xconfig etc)

what i usually do is to keep a copy of .config on my usb stick and whenever i want to compile my kernel after a fresh Slackware install,

to use the exact stored .config

hope i was helpful

props

bioe007 · 04-01-2007, 09:47 PM

Quote:

Originally Posted by pdw_hu

Imo a bit simpler method is to just use 'make install' and don't waste time on copying files. This will copy the old vmlinuz to vmlinuz.old. And this way you don't even need to edit lilo.conf.

but this could screw you if you do something dumb and evoke kernel panic...

not that i've ever done that myself

its nice to have my old images around in case I 'over-optimize' my current kernel.

especially when still learning its good to keep some old ones in lilo.conf