Executing commands before modules are loaded?

Question

Hi!
I'm searching for a way to execute some commands before the modules are loaded.
I have a Thinkpad 600E and I need to activate my soundcard via
# echo 'activate' > /sys/devices/pnp0/00:06/resources
# echo 'activate' > /sys/devices/pnp0/00:07/resources
as it won't get activated via BIOS.
This needs to be done before the modules get loaded, else the snd-cs4236 won't see the card.

Answer 1

This seems like a good idea. I posted the info for install below so you don't have to look it up:
install modulename command...
This is the most powerful primitive in modprobe.conf: it tells
modprobe to run your command instead of inserting the module in
the kernel as normal. The command can be any shell command:
this allows you to do any kind of complex processing you might
wish. For example, if the module "fred" worked better with the
module "barney" already installed (but it didn't depend on it,
so modprobe won't automatically load it), you could say "install
fred /sbin/modprobe barney; /sbin/modprobe --ignore-install
fred", which would do what you wanted. Note the --ignore-
install, which stops the second modprobe from re-running the
same install command. See also remove below.
You can also use install to make up modules which don't other-
wise exist. For example: "install probe-ethernet /sbin/modprobe
e100 || /sbin/modprobe eepro100", which will try first the e100
driver, then the eepro100 driver, when you do "modprobe probe-
ethernet".
If you use the string "$CMDLINE_OPTS" in the command, it will be
replaced by any options specified on the modprobe command line.
This can be useful because users expect "modprobe fred opt=1" to
pass the "opt=1" arg to the module, even if there's an install
command in the configuration file. So our above example becomes
"install fred /sbin/modprobe barney; /sbin/modprobe --ignore-
install fred $CMDLINE_OPTS"