Joined: Nov. 2006
||Posted: Nov. 04 2006,18:01
It turns out the modules.conf file didn't need to be modified. After copying the new module to the relevent subdirectory in /lib/modules, and running depmod (which resulted in a dependancy error that I ignored), the module was loaded on every reboot thereafter. And I could see that modules.conf had not changed.
So it seems the process is to put the module somewhere in /lib/modules and run depmod, in case anyone else goes down this path.
I'm curious where the hook is, if it's not the modules.conf file that's telling the kernel to load my new module. I noticed that the boot process pauses for a minute on the line
"Running from HD, regenerating ld.so.cache and modules.dep..."
Is this where it determines which modules to load, and the order?