Tinkster, I'll try this! Thanks!
What I am confused of is:
I'm generating modprobe.conf file for new kernel and mod-init-tools.
Maybe there is some way to do the same with old modules.devfs ?
Also I am confused with the question: when new modprobe.conf file is being loaded, why old modules.conf is empty and am I really need old modules.conf file, if new modprobe.conf already exists?
The same goes to modules.devfs...