Comment 14 for bug 576602

To rectify, don't forget to put a space before *and* after the keyword 'pre:'

You can test the workaround in this way (adapt with your modules names):

Checks that the modules are loaded:

root@ubuntu ~ # lsmod | grep '^it87\|^k10temp\|^fam15h_power' | cut -f1 -d' '
fam15h_power
k10temp
it87

Removes all modules:

root@ubuntu ~ # modprobe -r it87 k10temp fam15h_power

Checks that all modules are unloaded:

root@ubuntu ~ # lsmod | grep '^it87\|^k10temp\|^fam15h_power' | cut -f1 -d' '
[nothing]

Load the module to be loaded first:

root@ubuntu ~ # modprobe it87

Checks that it is alone:

root@ubuntu ~ # lsmod | grep '^it87\|^k10temp\|^fam15h_power' | cut -f1 -d' '
it87

Remove this module:

root@ubuntu ~ # modprobe -r it87

Checks that all modules are unloaded:

root@ubuntu ~ # lsmod | grep '^it87\|^k10temp\|^fam15h_power' | cut -f1 -d' '
[nothing]

Load the module to be loaded last:

root@ubuntu ~ # modprobe fam15h_power

Checks that all the other modules are loaded:

root@ubuntu ~ # lsmod | grep '^it87\|^k10temp\|^fam15h_power' | cut -f1 -d' '
fam15h_power
k10temp
it87

You can adapt this workaround to your computer, this is better than "blacklisting a module to load it succesfully", otherwise in a few years when you read your code you do not understand what it will mean. :)