Awesome guide, exactly what I've been looking for, a good kernel-source compile guide for slackware.

Also, you may want to include to take out a lot of stuff from the config that just bloats the kernel, and you don't even need it.

Such as, ISA, Firewire, etc, being a former gentoo user, who compiled a fresh kernel, had it very bare, but still worked, I'd say you can safely remove close to 75% of stuff in pat's kernel.

Also, you may want to make things built in to the kernel, <NOT alsa or any sound though>, I made my network card built in, and basically everything else, and now it all autoconfigures and autoloads, without rc-update or whatever you have to do to autoload modules.

Your guide saved me hours of fumbling. Thank you, thank you, thank you kind soul for taking the time to write this out. It is very much appreciated.

I have a suggestion. Perhaps it is best to copy the config file from the kernel source directory instead of move it. Some programs (the ndiswrapper, I found out the hard way) rely on seeing your kernel config (named .config) in your kernel source directory. ndiswrapper could not compile until I made a copy of it from my /boot and named it .config. I ask you at least at a note about this to help people who aren't knowlegable enough to figure this out.

Thank you again.

absolutely right. and in fact, i have already corrected it, however i have no access to modify this guide.

moved_please ignore

Hi,

Great guide! I successfully compiled a custom 2.6.10 kernel with it.

The only problem I encountered was the following:

/usr/src/linux# mv .config /boot/config-2.6.10

When I tried to install the Nvidia driver later on, I found that the installer needs the .config file in /usr/src/linux. If it's not there the installer exits, saying the module could not be build.

Just wanted to note that the LinuxAnswer has been updated to the latest revision at the request of acidjuice. Thanks acidjuice.

--jeremy

as per similar post here below, you should CP and not MV this file. please refer to the original article which is now fully updated.

thank you

Forgive me for ressurrecting such an old thread... I tried compiling 2.6.14 on Slack 10.2 using your guide but I have a problem getting network connectivity-- I can ssh into the default 2.4.x kernel, but the 2.6.14 kernel won't go out to the DHCP server for an inet address. I do not understand what I could possibly be doing wrong.

I was compiled and installed Linux-2.6.15.6 kernel step by step using your article titled: Compiling kernel 2.6.10 on a Slackware 10.1. But after rebooting an error occur:

Cannot open root device "815" or unknown block (8,21)
Kernel panic – not syncing:
VFS: Unable to mount root fs on unknown block (8, 21)

LILO start loading kernel and last steps of loading process are:

SCSI device sda: 253952 512 byte hdwr sectors (130 mb)
Sda assuming drive cache: write throw
Sda: sda1
0:0:0:0: attached SCSI removable disk sda
0:0:0:0: attached SCSI generic sg0 type 0
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
Using IPI Shortcut mode
Cannot open root device "815" or unknown block (8, 21)
Kernel panic – not syncing:
VFS: Unable to mount root fs on unknown block (8, 21)

I have compiled all file systems directly into core. I’m using ReiserFS on my disks. As I have SATA disks, I have chosen all necessary options while configuring kernel:

Device drivers->SCSI device support
'SCSI disk' and 'SCSI generic' selected <*>
Under SCSI Low Level Drivers I have selected necessary drivers not loaded in modules. All other steps I have done as written in your article.

What could be wrong?

Have u selected ext2 fs support to be built in your kernel,not as modules.?

Yes I have selected ext2 support to be built in my kernel... All in all I have solved my problem. The problem was that SATA driver’s conflict cause kernel panic. When I disabled all SATA drivers in other sections, except SCSI section, problem was solved.

Hi,

i try use your howto to step-by-step upgrade from 2.4.30 (default Slackware 10.2) to kernel 2.6.14.

but, when i try run
it return a error:
and /etc/modprobe.conf has been generated, but modprobe can`t load modules... for example command modprobe ah4 returns error:
and in dmesg is:
i don`t know where problem is... i try upgrade to last module-init-tools from slackware packages (module-init-tools-3.2.2-i486-2.tgz)
and also i check if i compile "loadable modules support" to my new kernel, and it is there:
part of .config (module):
pls can u help me resolve my problem? thank u a lot!