On 2006-03-29, Thoralf Will wrote:
> base: RedHat9
> kernel: 2.6.13 (i know that newer version are around, shouldn't be
> relevant here)

If you compiled the kernel, did you compile in IPTable support?
There is a little change in kernel 2.6.16. The options for IPtables
is no longer there! until you also choose the new Xtables entry
when configuring.

not 100% sure what you mean. of course i compiled iptables support into
the kernel. otherwise a modprobe would hardly work, wouldn't it?

the problem is rather why iptables isn't loading the (available and
working modules) on its own.

short amendment:
when compiling the parts in question (ip_tables, etc.) into the kernel
instead of using modules iptables works as well - as expected.

so it's really just a problem with loading the modules and so far i've
only noticed this problem with iptables, not with any other modules.

seems i was wrong. after testing around some more and also upgrading to
2.6.16.1 i noticed that no modules load automatically - even though
they work fine when getting loaded with modprobe or insmod.

root@rh9-work:~ > zcat /proc/config.gz |grep KMOD
CONFIG_KMOD=y
(so quite obviously the module auto loader is compiled into the kernel)

i'm really stuck here and would appreciate every idea that helps me to
solve that issue.

more information:

root@rh9-work:~ > mount -o loop halt -t tmpfs work/
mount: Could not find any loop device, and, according to
/proc/devices,
this kernel does not know about the loop device.
(If so, then recompile or `insmod loop.o'.)
root@rh9-work:~ > modprobe loop
root@rh9-work:~ > mount -o loop halt -t tmpfs work/
root@rh9-work:~ >

so seems the loop module works fine - but doesn't load on it's own
which i would expect when mounting a loop device.