Im assuming that when you recompile a kernel all the modules for that kernel are put into /lib/modules/<kernel version> ?

All the NetFilter (iptables) stuff are modules (and other stuff too), but everytime i run my firewall script i get modprobe errors, even though i run the script as root? Ive also had problems with sound modules (emu10k1) being loaded as well. Its like all the modules i compiled with kernel just dont exist or something :S

Im using SuSE 8.1 and the commands I used to compile my kernel where:

make mrproper / clean <-- i tried both for fun
make xconfig
make dep
make modules
make modules_install
make bzImage
make install

Theres probably only a simple solution to all of this

Id appreciate any help, cheers

Which kernel is running when you reboot? 'uname -a' and if it doesn't say 2.4.20 then something's not right.

The stock kernel Makefile places the kernel in / and SuSE boots the kernel from /boot. For simplicity I just change the Makefile (uncomment the line '#export INSTALL_PATH=/boot')

The kernel that comes with SuSE 8.1 is 2.4.19-4GB, but when i compiled it i get a plain 2.4.19 with uname-a. The dir /lib/modules/2.4.19-4GB/ has lots of different modules in, so this is why im assuming that the standard stock kernel stores its modules in this directory. Its just that the directory /lib/modules/2.4.19 (which is where im assuming the modules for my kernel are stored) is pretty much empty compared to /lib/modules/2.4.19-4GB, coupled with the fact that im getting a couple of modprobe errors saying basically that it cant find certain modules. This is why im a little worried :S

Ooookay. My bad - I just assumed you got yerself one of them fancy new kernels.

You need to make sure you have selected the netfilter stuff in the networking options section in the xconfig. Actually you'll probably need to run through the entire dialog to make sure you're selecting all the fun things you need make linux go. Depending on your kernel you may need to select 'Prompt for development and/or incomplete code/drivers' from the Code maturity level options.

Ok, i think i may have made the mess up on this one

Ive just finished compiling my kernel, but this time in a slightly different order. This time i did:

make oldconfig <-- to reload my kernel configuration
make dep
make bzImage
make modules
make modules_install

and everything worked fine. My 2.4.19 directory is now populated with all the modules and stuff. This whole thing was probably an error on my behalf, but it all still seems a mystery. It'd be helpful (just for curiosity purposes) if anyone would be kind enough to shed some light on this ?

thanx