2.6.11.11 is out. Works fine so far after migrating from the 2.6.11.10 .config (which was copied from 2.6.11.6 to 2.6.11.7 all the way to .11) file.

After I ran a apt-get dist-upgrade I get the following error message when I try to do a make menuconfig
in the linux kernel source directory:

Error message:
HOSTCC scripts/basic/fixdep
In file included from /usr/include/bits/posix1_lim.h:130,
from /usr/include/limits.h:144,
from /usr/lib/gcc-lib/i486-linux/3.3.6/include/limits.h:122,
from /usr/lib/gcc-lib/i486-linux/3.3.6/include/syslimits.h:7,
from /usr/lib/gcc-lib/i486-linux/3.3.6/include/limits.h:11,
from scripts/basic/fixdep.c:113:
/usr/include/bits/local_lim.h:36:26: linux/limits.h: No such file or directory
In file included from /usr/include/sys/socket.h:35,
from /usr/include/netinet/in.h:24,
from /usr/include/arpa/inet.h:23,
from scripts/basic/fixdep.c:115:
/usr/include/bits/socket.h:305:24: asm/socket.h: No such file or directory
scripts/basic/fixdep.c: In function `use_config':
scripts/basic/fixdep.c:201: error: `PATH_MAX' undeclared (first use in this function)
scripts/basic/fixdep.c:201: error: (Each undeclared identifier is reported only once
scripts/basic/fixdep.c:201: error: for each function it appears in.)
scripts/basic/fixdep.c:201: warning: unused variable `s'
scripts/basic/fixdep.c: In function `parse_dep_file':
scripts/basic/fixdep.c:297: error: `PATH_MAX' undeclared (first use in this function)
scripts/basic/fixdep.c:297: warning: unused variable `s'
make[1]: *** [scripts/basic/fixdep] Error 1
make: *** [scripts_basic] Error 2

i was using the defaul kernel with slackware 10.1(kernel 2.4.29)... I try compile 2.6.10 and 2.6.12..but i couldn't... when i rebooted my computer (after compiling both kernels)I got a black screen... thats it.... what am i doing wrong???

any help will be apreciated...

If your boot partition is on Reiserfs you either need to compile reiserfs support into the kernel or use an 'initial RAM disk (initrd). If I remember correctly there are instructions on howto upgrade from 2.4 to 2.6 kernel included on the install disc.

for some reason when lilo is run after compiling the 2.6.12.2 kernel, I am getting the error: "Fatal: vmlinuz too large" I'm have no idea as to why this is occuring, as I am using the same procedure and configuration as I always do. Any help would be appreciated.

Menestrel, are u in the right forum?
Isn't apt-get a Debian distribution utility?
Why are u using it for Slackware...?

So, I've successfully recompiled my kernel for the first time suing this guide- thanks!. However, I'm getting the 'unable to load nvidia.ko' error while trying to install NVIDIA drivers- which I have been told is fixed by deselecting the nvidiafb driver. My question is this: I want to tweak my 2.6.12 kernel again, but I want my present backup kernel 2.4.29 to remain the backup- since my recompile might not work. So how do I make sure that this 2.4 kernel is the backup after I recompile again rather than the first attempt at 2.6 becoming the new backup?
In my boot folder I have the vmlinuz and vmlinuz.old- can i simply rename the vmlinuz.old to vmlinuz and repeat the steps I took the first time?
Thanks for any help.

It seemed to make sense- so I answered my own question and it worked.

mv System.old System.map
mv vmlinuz.old vmlinuz
cd /usr/src/linux
make menuconfig
etc

just had to keep up with which is which in lilo

I've installed Slack 10.1 on another machine, so I can experiment with compiling a kernel. Where do I start? Do I just get the kernel source from kernel.org and follow the guide here? I've never done this before, so am a bit unsure.

Thanks.

Yes. It's really not as daunting as it seems at first- I just recompiled successfully for the first time- after a few days of messing around with it to get the kernel just the way I want it. This is also the best guide I've seen- I follow it to the mark. If you make sure to edit lilo correctly and follow this guide you will be given two options at boot- you're newly compiled kernel and the original kernel installed with slackware 10.1. This way if you did mess things up you can always go back.
I would suggest using the make menuconfig command- I personally found this easiest- though you may think different. This particular kernel editor will load the kernel that slackware built for you- which is already working- and you can just tweak it from there. This way you have a jumping-off point. The help sections for each option in the kernel are very helpful and usually have a good recommendation for whether or not you need that item, in case you have no idea what it is for.

Just prepare to spend a bit of time looking around the first few times as reading every options help section takes a while, but is worth the effort getting it right so your recompile works. If you know alot about your hardware you will move along alot faster.

Good luck!

Thanks for the reply. Another quick question: when you edit lilo.conf to add the info to boot the old kernel as well, with the line

image = /boot/vmlinuz.old,

I assume I need to rename the actual vmlinuz to vmlinuz.old?

actually no- it will be done automatically if you follow the rest of this guide. after you've edited your kernel and you run

make
su -c "make modules_install"
make install

the present vmlinux and System.map will be renamed for you as backup links

Ok, thanks again. I'll have a go . Edit: I have more questions:

1. I do still need to run /sbin/lilo after editing lilo.conf, right?
2. This bit:

From /usr/src

rm -f linux
ln -s linux-2.6.0 linux
cd /linux

make mrproper

Then copy your existing .config to your new kernel source tree...

cp /usr/src/linux-2.4.?/.config /usr/src/linux

I downloaded and extracted to /home/nick/linux-2.6.12.4. Is that ok? I assume I don't need to do the rm -f, ln -s and cd /linux commands? Can I just do make mrproper and cp /usr/src/linux-2.4.29/.config /home/nick/linux-2.6.12.4?

I should also have asked, is this guide ok for 2.6.12.4, as well as 2.6.0?

Thanks again.

1. Even that is done automatically with the make commands

2. As far as I know you can do it in /home, but I'm a noob so not completely sure. And it worked for me with kernel 2.6.12

Sorry, had to edit my post because there was more stuff to ask! Heh, that's good to know about LILO, thanks for that .