modules dont load at boot time
 

I have tried to configure my system (rc.sysinit, halt) for 2.6.0 kernel as it was shown on:

http://thomer.com/linux/migrate-to-2.6.html

But was unsuccessfully...
Now i got problem loading modules. I have saved rc.sysinit and halt before modifing them and restored them after reconfiguring didn't work. But now i get at boot up:

Flushing all current rules and user defined chains:iptables v1.2.7a: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
[FAILED]
Clearing all current rules and user defined chains:iptables v1.2.7a: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
[FAILED]
Applying iptables firewall rules: iptables-restore v1.2.7a: iptables-restore: unable to initializetable 'filter'

Try `iptables-restore -h' or 'iptables-restore --help' for more information.
[FAILED]

Tried to install iptables-1.2.9rc1... didn't work either..
The problem to first two faliurs is that moduls are not loaded correctly.
But i don't know who to make them load during boot.

Also my ppp moduls won't load (at boot up), and to be able to dial-up or use iptables filter i need to load modules by hand...

Tried to reconfigure /etc/modules.conf, didn't work.
When i try /sbin/modprobe -c this si what i get:

path[kernel]=/lib/modules/kernel

But i think it should be /lib/modules/2.4.23/kernel... like i said tried it but it had no effect...
Thou when i try to load them by had it works so this isn't either... hm..

I remember changing in rc.sysinit mousdev to usbmouse and now at boot there is:

modprobe: modprobe usbmouse the modules can not be found (or something like that)

also i modified fstab and re-modified it but mount is still searching for /sys mount point?
And it is not listed in fstab.

Please help.
I have leaved the same post on newbies but nobody answered and this is urgent (for me) so i am posting it again here. (sorry)

The first step listed in your url reference is to mkdir /sys. Is this a script entry in initrd, or is it a pivit point that you need also in your root directory?

Here is part of a message I found doing a google/linux search: initrc /sys

> There is a chicken and egg problem with initrd on 2.6. When
> root=/dev/xxx is passed to kernel, kernel will call try_name, which
> uses /sys/block/drive/dev, to find out the device number for ROOT_DEV.
> The problem is /sys/block/drive may not exist if the driver is loaded
> by /linuxrc in initrd. As the result, /linuxrc can't use
> /proc/sys/kernel/real-root-dev to determine the root device number.

Other messages from redhat users mentioned path differences which needed changes in rc.sysinit. Maybe you need to make links linking old locations to new locations for different modules.

Also, did you do a mkinitrd? This is needed to produce a new initrd file from your module changes and rc.sysinit edits. (or is the command mk_initrd in redhat?)

You may want to copy your initrd file( i.e. to /tmp), unbzip it and mount the file as a loopback device. Then check the modules present, and their locations, and read through the startup script in initrd.

I hope this gives you ideas. I'm not a linux guru, and you know more about Redhat then I do.