Ok, I JUST installed Slackware 9.1. I am trying to install Kernel 2.6.0-test11. This is the first thing I tried after getting Slackware installed. Here's the exact procedure I followed.

1. Extracted the source to /usr/src
2. Ran make xconfig, configured all needed components (and probably extras)
3. Ran make bzImage
4. Copied bzImage to /boot and configured lilo.config
5. Ran lilo
6. Ran make modules
7. Ran make modules_install

Upon reboot, it begins to load fine, but gives me tons of messages such as "Cannot find module agppart" .

When I login and type startx (using KDE) I get a screen and X cursor, but it doesn't load. When I hit CTRL+ALT+Backspace to kill X Server, there's a ton of errors.

What do I need to do?? I have YET to get ANY version of a kernel compiled properly... and its getting really frustrating.. I've followed at least 30 sets of instructions...

try compiling with just menuconfig outside of X

u probably need to reinstall ur AGP drivers too, for the new kernel... Im a newbie too, and I've compiled and run atkeast 4 new kernels, but none of them had ALL the features that i needed! So, wait for more responses... but, I think its just a matter of reinstalling the AGP dirvers... BTW, did u get ALSA working with the new kernel??? Thats the one that has PAINED me in all my kernel compilations!!! If u did, please lemme know...

Well there's LOTS of stuff wrong, so much that pretty much nothing works... and I was told that installing a new kernel is easiest with Slackware.. however I am finding NOTHING easy with it or anything else...

That doesn't look any different than other 25 sets of directions I've followed... Also, make dep doesn't apply to 2.6.0 I thought?

So confusing!!

These are the steps I follow when compiling a kernel on Slack 9.1.
Edit lilo.conf before you begin so that if you make a mistake you can boot your old kernel(don't run /sbin/lilo yet, make modules install will do that for you)
(After unpacking the new kernel in /usr/src)
1. rm /usr/src/linux
2. ln -s /usr/src/linux-2.6.0-test11 /usr/src/linux
3. cd /usr/src/linux
4. make mrproper(not really neccessary with new kernel source)
5. make config/xconfig/menuconfig(whatever you prefer)
6. configure the kernel how you like it(trial and error)
7. make clean(make dep no longer needed with 2.6.0)
8. make bzImage
9. make modules
10. mv /vmlinuz /vmlinuz.old
11 cat arch/i386/boot/bzImage > /vmlinuz
12. mv /boot/System.map /boot/System.map.old
13. cp System.map /boot/System.map
14. make modules install

What is that System.map about?

I've never done that and never had problems with (better without ) it before.

First of all, you're using the 2.6.x series... basically these are still beta builds, and if you're new at kernel compilation and troubleshooting, and not interested in filing bug reports, try to stay away from it unless you're really adventurous and willing to spend hours upon hours just troubleshooting and not actually using your computer productively.

Well, before I look like a meanie who's trying to put you down... what you need is module-init-tools. Don't ask me how to use it though, I only used it once and it was quite long ago.

Another easier way out is to compile everything into your kernel and avoid modules altogether.

P/S: This experience is what kept me on the 2.4.x builds from then on. Sure the 2.6.x series is fast... but at the expense of a near-crippled system? Nahhh... not worth it for me

Click here for the answer

Try this.

When you run "make config," the configuration file that you modify is called .config and it's in the root of the kernel source directory. For example, if your kernel source tree is at /usr/src/linux then its configuration file is /usr/src/linux/.config

Slackware comes with many pre-built kernels along with configuration files for them. For example, if you look in the kernels/bare.i directory on the Slackware archives, you will find a file called "config".

If one of the Slackware kernels work, then try copying its configuration file over to /usr/src/linux-2.60test11/.config and then doing "make oldconfig." That way, you'll begin with a configuration that you know will work (or at least boot), and then you can make your modifications from there.

I hope this helps.

hey, u cant use the old config files with the 2.6 series... Apparently it was Linux Torvalds himself who recommended against mixing the 2.4 and 2.6 config files...